>>P.P.S. I've also found VNCThing has an anoying bug with dragging.
>
> Yep, this is on my bug list to look at for the next release.
Oh, good! I'm glad it's not just me...
>>when viewing an Xvnc server, though - seems to be OK for another Mac.
Do you find this too, Dair (/anyone)?
Any idea why
> For example, if the Windows Key could be mapped to the Command Key
> on a Mac
As far as I'm aware, that should happen for ChromiVNC Server.
I have to admit that I've never tried this (since I don't go near any form
of Windows OS as a general rule), but provided that the viewer
> I just got MacVPC (AT&T distro, are there others?)
Yes - check out ChromiVNC for a server and VNCThing for a client.
Also, you may find my vncPatches68k could be worth a try with the
ChromiVNC Server (even if you are using a PowerPC Mac).
ChromiVNC Server: http://www.chromatix.uklinux.net/v
> This is a generic...
> .
> .
> .
> ...This is all I wanted to say.
Ummm...
Try it out...?
(You'll be amazed how many of your questions will be answered
within 30 seconds)
Bye!
Adrian
-
To unsubscribe, send a message with th
> As I held down the button, the cursor started shaking back and forth
That's the Time Manager task in my patches which is used to overcome the
Drag Manager problem. -It only kicks in if it detects that the standard
patches are not being called (i.e. in that 'sticky' situation where a
drag is not
>I installed VNCThing and tried it. Same problem.
Yes, VNCThing does not have such an extensive ability to map keypresses
as the original AT&T version. 'twould be nice...
>For example, if I'm in the Finder and issue Command-N (new folder),
>VNCThing's New Session window pops u
oops...
sorry - just noticed the e-mail I was replying to was not sent to the
list (I'm at home typing into a terminal and didn't think to look at
the original address before typing in the list address... Doh!)
Adrian
-
To
> Adrian should rename his patch from vncPatches68k to vncPatchesNo68k.
???
> I find that it works on newer Macs, NOT on 68K Macs.
??? again!!
It *was* designed for 68k Macs - that was its original purpose (and it
still works fine on them, though I would not recommend trying to use
VNC server
> which window manager are you using?
I don't think it is associated with the window manager.
If I kill the window manager (or 'workspace manager' as they call
it on these alpha boxes - it's dtsession running dtwm) it still does
it after the obligatory 15 minutes.
> I don't have that probl
>> ...the 'gray' background with the big X
>
> The grey pattern and the large X is the X server
No - I'm talking about the *screensaver* (at least, I presume that's what
it is) - Check out the -s and -p options for Xvnc...
The 'big X' I refer to is not the 'default X server cursor' that you get
I was just reminded today of something I've been struggling with regarding
Xvnc - that is the screensaver pattern (the 'gray' background with the big X).
Is there a way to stop this coming up?
There is a '-s' option listed for Xvnc, but it did not seem to make any difference
at all to the time b
> Considering we are using UDP,
???
That's news to me...
At the very least I know the Mac version uses TCP.
Don't see how others could be different... anyone else know different?
=
Adrian Umpleby [EMAIL PROTECTED] http://w
> is a discussion of wether or not an openssh (or ssh) solution can be used
> cross-platform.
SSH is available on Windows and Mac.
When I was trying out the Mac clients I tunnelled VNC through SSH without
any problems (apart from speed - my Duo is very old).
I have not tried contacting a Mac VNC
Hi (again...)
Looking back through my code, it looks like the annoying mouse tracking
bug was also in the vncPatches68k release for ChromiVNC Server alpha 4.
I'm somewhat surpised nobody has mentioned it, since it is *really*
annoying!!
Does that mean there isn't anyone currently using vncPatc
> Just to let users know that there is a rather annoying bug in
> vncPatches68k for alpha 5.
New versions of vncPatches68k have now been posted.
http://wrench.et.ic.ac.uk/adrian/software/vnc/
I recommend anyone who has downloaded vncPatches68k-a5, or
vncPatches68ka5-nostagger, or vncPatches68k
Just to let users know that there is a rather annoying bug in
vncPatches68k for alpha 5.
Because of some 'temporary code' that got left in, there is a
problem with mouse tracking - this appears to only affect fast
computers (G3/G4), and possibly only on a fast connection too.
Since I've only had
> Can someone explain to me what TridiaVNC is?
www.tridiavnc.com might have something to say about that...
Here's a snippet of blurb from their web site:
TridiaVNC takes the risk out of deploying VNC by
providing the key elements missing from any
other VNC distribution. It is enhan
> You create a "HTML" folder anywhere on the computer
Well, mine's called "TridiaVNC Server HTTP Folder", but there you go...
> I haven't looked at the AT&T HTML files...
Here's the index.vnc file - the comment explains all:
$USER's $DESKTOP desktop ($DISPLAY)
Does that help...?
> Jonathan
Sorry for butting in...
> can you include in your instructions... how one can activate the HTTP
> java stuff with your server?
... but I thought I'd let you know that it seems to work fine for me
just using the files from the Xvnc distribution, with a couple of minor
modif
>> there are now installation instructions
>
> Nice instructions Jon, but perhaps you could put some screen shots in
> to help the wieners.
I'm not clear on what screenshots could be added to the installation
instructions - all you have to do, once downloaded (and unstuffed - but
even that is
>>I suspect these features need a lot more tuning based on processor type
>>(How's your 5300 Jonathan...?)
>
> In my "internal" version (due to become alpha 6 after some time), I have
> introduced another feature which should reduce the "blocking" behaviour.
> ...
Sounds good.
> This makes the Q
Ok, folks...
The recent release of ChromiVNC Server alpha 5 (hot on the heels of alpha 4)
has seen a few changes in the way that the server deals with screen updates.
These latest offerings of vncPatches68k take these changes into account, and
will hopefully provide a better 'feel' to using the
>> does it cause some kind of odd timing problems if both the patches
>> and the server try to do this, or is it not noticeable?
>
> It's not *too* noticeable, at least on my Quadra
But it *is* noticeable, then?
In what way? (i.e. what are the differences in _feel_ between the
buffered and non-b
> Fixes authentication bugs as noted by Adrian Umpleby,
You'll be really pleased to hear that it's not convenient for me to
download and scrutinise your code until after the bank holiday.
You can have a bit of a breather for a few days... ;-)
But that does prompt the question of whether vncPat
> Probably a damn silly question,
Don't worry - this is the place for silly questions ;-)
> why can't the server block mouse or keyboard commands from the viewer?
> The control for this is on the viewer side.
> Is there any way (on a MAC) to block viewer desktop control...
I'm not 100% sure I
>> So I've managed to hack together a VNC server for OS X
>> ...(It's a native server--it reflects the OS X Aqua desktop over VNC.)
> Very, very cool...
Wow!
I didn't expect the 'Aqua screen' to be VNCed so soon...
By "native server--it reflects the OS X Aqua desktop" do you mean you
see the sa
Dear all (...at least, those of you with Macs and ChromiVNC Server)
The recent release of ChromiVNC Server v3.4 alpha 4 has brought about
the need for some minor changes to vncPatches68k.
vncPatches68k for alpha 4 is now available:
http://wrench.et.ic.ac.uk/adrian/software/vnc/
Once downloade
I think I see the bug with the view-only password...
First, this is done for the main password (if it exists):
// key is simply password padded with nulls
for (i = 0; i < 127 && i < strlen(password); i++) {
key[i] = password[i];
}
And then the key is used to encrypt
> You might want to try regenerating your Preferences from scratch
No, didn't help. -But I have been doing some more playing around and
I found that it only works if there are at least as many letters in
the view-only password as in the main password.
Try having a single letter for your view-onl
> If the main password is blank, access is only granted using the View-
> -only password, with View-only priveleges.
This is the only one that works for me...
The rest of your description is as I expected (and understood from the
readme file).
Having looked at the code, I can't see any reas
Hey Jonathan! You've been busy while I've been on my hols...!
OK, just to let people using the Chromi server know that I'll post
an updated vncPatches68k for alpha 4 a.s.a.p.
My initial testing with the vncPatches68k for alpha 3 suggests that
it is compatible with alpha 4, although the server gi
> Is this some type of security feature
Yes.
> xhost +
This is, as mentioned a nice easy way of allowing anyone to open anything on
the display.
I suggest you only do this if it is a fairly brief time that you will spend
as another user - so do the xhost + just before you su, then do xhost -
> The remote computer is running the Server, of the ChromiVNC variety.
> They are using the vncPatches that came with ChromiVNC.
Good - as it should be...
But still worth checking for any other 'rogue' vncPatches hanging
around the System Folder and/or Control Panels folder, or an accidentally
r
> Should I be using ChromiVNC's vncPatches
Yes - the one that you downloaded with ChromiVNC.
> ...with the Viewer
It comes with the server - the viewer is only a simple application that accepts
and displays framebuffer sent from the server.
The vncPatches are needed to 'capture' screen updates
> when I click in the menu bar of the remote Mac I don't see the menu bar drop
Sounds like you have not installed the vncPatches that comes with ChromiVNC.
This should go in your Extensions folder, and then restart.
It's also a good idea to make sure that you have not accidentally (somehow)
got
> if we had SSH on all needed platforms (maybe Macintosh is problem)
SSH2 is available for Mac. (and I think there is some SSH capability
bundled with OS X.)
I've tunnelled VNC through SSH quite successfully on my Macs (although
rather slow - the main Macs I use are quite old) with the Macs as
c
> ...a weird issue with MacVNC 3.3 Beta and/or 3.4 Alpha 3...
When you say MacVNC 3.3 Beta I assume you are talking about the AT&T
VNC server for Mac?
And 3.4 Alpha 3 is ChromiVNC Server (aka TridiaVNC Server)?
> this causes a hard lockup of the machine under either vers
>> Can we stop this somehow, please?
>
> The signature needs to stay
Sorry - I wasn't meaning to imply removal of the signature altogether.
> people need to take a bit more care to trim quoted messages
Agreed!
However, in the face of user-peculiarities I was just wondering if there
might be a
Can we stop this somehow, please?
I'm getting fed up of having to scroll back up my terminal to read a
couple of lines of text... (yes, I know I'm so old fashioned reading
my e-mail on a command line-based terminal)
>>> -
>>> To
> there were only 61 messages in the my VNC group.
The times they are a-changin'...
The VNC newsgroup idea is now 'out of the bottle' - and I don't see it
now having 'the cork put back in'. I suspect that a newsgroup will be
used by a majority of VNC users (and I shamelessly include myself).
Ho
> If everyone can receive email and not everyone has access to
> newsgroups then how would it be available to a wider audience?
EMAIL_LIST + NEWSGROUP > EMAIL_LIST
assuming NEWSGROUP > 0 (and I'd like to see you argue it's -ve)
I would hope to see 'mirroring' (i.e. anything posted to list
>>>(Just out of interest, has anyone on this list any experience of using
>>>a Windows VNC server on a 386? How bad is it?)
>>
>>I wouldn't imagine many people have tried running windows '95 on a 386,
>>alone VNC!
Good point!
Oh! Why not! Let's just go for it...!
Just before I go to bed tonight, I'm 'formally' anouncing the 68k patches
built specially for the latest alpha 3 Tridia/ChromiVNC server for Mac.
Notice the totally redesigned new website (which has been sitting there
since Wednesday while I tried to think u
I should have added one more point to the 'bad news' section (though it's
hardly surprising)...
4) Running the alpha 3 server on a 68k Mac (duo 230, 33MHz 68030 CPU) is
still very painful indeed! And that's when using only raw encoding -
switching on CoRRE/RRE increases the pain by a factor
>>2) Double-clicking in the Finder is improved somewhat, but still
>> quite unreliable
>
> I'll try fiddling with some code, and see if I can get it to give some
> extra time back to the system in between mouse button transitions,
> which should help if the Finder really is doing it's own double
>>>1) I found the same instability that I had on the duo
>>
>>Will test specifically for that...
>
>OK, been playing around on both the 8100 and the 5300 for a while,
>especially with the Server application in front. No crashes.
Hmmm.. I've had it (with exactly the same symptoms each
> has anyone been able to duplicate the reported instability
I don't think I reported it to the list.
But as it happens I have just completed some more testing on machines
other than my (somewhat anomalous) duo 2300.
First the bad news:
1) I found the same instability that I had on the duo
i
Hi Jonathan,
Your webpage links are invalid.
For the sake of others on the list, here are direct links:
http://www.chromatix.uklinux.net/vnc/bin/chromivncserver.340a3.sit.bin
http://www.chromatix.uklinux.net/vnc/bin/chromivncserver.340a3.sit.hqx
for the binaries (MacBinary and BinHex respecti
> create different lists concerning differents aspects of VNC.
Yes, I've been aware recently that there is a lot of 'discussion' going
through the list which might be better off split into different 'segments'
somehow.
One first p
> There is a proper fix in my internal version of the VNC Server,
> I might yet be able to make a new release before Xmas!
OK, fine - there's little point me working on this next crazy fix
then (pity, cos I'm sure I've got it this time - patching the
CursorDevice Manager so that if it is called f
> it don't work any differently on my G3 beige 266 running 8.5.1
rrrgghh!
'scuse me while I just go throw myself off a tall building.
splat!
OK, feel better now...
So, is there anyone out there that can explain why my Duo 2300 and my
PB 1400 just don't have this problem? Is it OS 8.1
Hi all,
Those of you that have been following the minor saga that is vncPatches68k
will be aware that there remains an outstanding issue concerning double-
clicks of Finder icons.
I believe that the latest version (vncPatches68k-tick) will finally sort
out this issue. Those of you that use v
Hi all!
I've updated vncPatches68k (yet again) to include a patch which forces
mouse events to be separated by at least 5 ticks.
This should help to alleviate the Finder double-click problem (well, it
does on my Duo anyway...)
It also has the keymap support that was in the previous version (w
I said:
> If you are using a keyboard without a command key (apple/cloverleaf
> thingy) then the following key combinations should be used for mouse
> click/drag modifiers:
Of course, even if you are using a keyboard with this key (i.e. you are
viewing a Mac from a Mac), then it will still most l
> Why not make the Windows key (it's on most PC keyboards) correspond to
> Command?
Basically, because I'm currently nowhere near a Windows machine to find
out what key mapping it sends when this key is down...
But, yes - it will probably happen, once I get the chance!
Adrian
--
I have added the aforementioned Time Manager task hack that will
attempt to 'nudge' away the 'sticky situations'.
I have also added something else that I think some of you will
probably be very pleased about - namely, mouse modifier keys...
Since this was accidentally switched off by the alpha-
I asked:
>>>Can anyone out there (Tim, Mike, Jonathan?) verify they still have a
>>>drag problem, in the case I outlined above?
Tim said:
>>yep, if i drag a finder icon up into the menubar area, it "halts" on the
>>remote viewer, but a nudge with the local mouse clears things up.
Jonathan resp
> Tim Senecal at [EMAIL PROTECTED] wrote:
>
>> downloaded, installed, and I have found no problem with it, drags of
>> finder icons drag the icon, and relatively quick on the updates too.
>
>Mike Babulic also concurred:
>
>> Yep, it fixes the drag problem & seems a bit faster.
>
>And then I threw
I said:
> Actually, I would very much like to hear from people using the Tridia
> VNC Server (both PPC and 68k), to find out if the drag phenomenon is
> widespread.
Mike Babulic answered:
> I have the drag problem too.
Glad to see it is a 'normal' problem (if you see what I mean...)
What machi
> a way to have the viewer only update the cursor and not the
> whole viewer page?
The VNC server should only send regions of the screen that have
been updated (i.e. only the blinking cursor).
It might help if you let us know on which platform the server
is running, and which VNC version?
> th
> Biege G3 266...
> vncpatches68k
>
> moving an icon in the finder from a vnc viewer causes the machine to lock
> up no mouse or keyboard on local machine.
It locks it completely - you have to restart?
> swapping the vncpatches68k for the tridiavnc patches...
> nudging the local console mouse "u
I said:
>> it's related to the drag manager on newer OSes
>> (I've had no trouble with 8.1, only >=8.5)
>
Mike Babulic responded:
> Problem solved. I had neglected to remove the VNC control panel when
> I removed 3.3.2b2 (aka Beta 3.0.1)
OK, fine - I'm good at finding the mos
62 matches
Mail list logo
