aking shortcuts
for specific machines.
-Original Message-
From: Andre Tertling [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 20, 2001 4:00 AM
To: [EMAIL PROTECTED]
Subject: Re: TightVNC vs regular VNC
I'd like to have "RAW" encoding set as default as I am using VNC
(TightVN
Glenn Mabbutt wrote:
[how to pick raw encoding as default]
> don't know about a reg key, but a work-around would be to connect once to
> the server using whatever encoding and other settings you want, click on the
> "vnc" system menu icon in the top left corner of the viewer, select "Save
> Conne
ually launch vncviewer using the
command prompt via "vncviewer -config somefile.vnc"
Glenn
-Original Message-
From: Andre Tertling [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 20, 2001 4:00 AM
To: [EMAIL PROTECTED]
Subject: Re: TightVNC vs regular VNC
"Todd A. Jacobs"
"Todd A. Jacobs" wrote:
> Of course, if you have a Fast Ethernet connection or similar, you're much
> better off running raw encoding. YMMV.
I'd like to have "RAW" encoding set as default as I am using VNC
(TightVNC in particular as I wanted to test modem performance) on my
fast ethernet lan mos
On Fri, 3 Aug 2001, Edric wrote:
> On a 10base-T network, I noticed that if I use the "tight" encoding,
> the screen display is slower than if I just use "hextile". I'm
> assuming this is because it takes more time for the Unix box to
> compress the data
I suppose it depends on what you're send
> On 8 Aug 2001, at 6:00, vnc-list-digest wrote:
>
> > I eventually used:
> > Password = REG_BINARY 0x8 0xDDCCBBAA 0xHHGGFFEE
> > and that worked.
>
> > Is there an easier version that I am missing here??
>
> The easiest way to find your password settings, is to set the
> password under WinVNC (
On 8 Aug 2001, at 6:00, vnc-list-digest wrote:
> I eventually used:
> Password = REG_BINARY 0x8 0xDDCCBBAA 0xHHGGFFEE
> and that worked.
> Is there an easier version that I am missing here??
The easiest way to find your password settings, is to set the
password under WinVNC (winvnc -default
> On NT, if you can ping the remote PC and have adminstrator
> access to it, then you can use my fastpush script to upgrade
> them. It's only a batch file, so it would be easy to alter it to push
> TightVNC instead of one of the Tridia flavours I've got.
Nice script! All our machines are NT or 2
Speaking of upgrading, I have been trying to compile tightvnc without much success.
Is there anyone who has sucessfully compiled it on the solaris platform? I am using
Solaris 7. If anyone can sent me the compiled files, I would be very grateful. Thanks.
PS : Any version of solaris is worth a
Hi all
> My biggest problem is that the machine that it'd be most useful on is one
> that we've shipped off to a site 1200 miles away, and something tells me
> that I can't upgrade to a newer VNC while operating the machine via VNC. ;)
I find NT easier to upgrade than 9x, mainly due to NT's
can use Windows Explorer to copy from one directory (e.g. on
your machine) to another (i.e., the server's share/directory).
Bob Germain
-Original Message-
From: BugTraq Recipient [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 3:13 PM
To: [EMAIL PROTECTED]
Subject: Re: Tig
> 1. Run Server Manager and stop the VNC service on the remote machine.
> 2. Map a drive to the location where the VNC programs are installed on the
> remote machine.
> 3. Copy the the TightVNC files over the original VNC files on the remote
> machine.
> 4. Re-start the VNC service (using Server M
service (using Server Manager).
You should now be able to connect using VNC!
Let me know if I'm missing something...
Bob Germain
-Original Message-
From: Yan Seiner [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 10:57 AM
To: [EMAIL PROTECTED]
Subject: Re: TightVNC vs regula
>If you're running WinNT... hmm... aren't there ways to start/stop services
>from the command-line? (i can't think of them right now) In such a case,
>you could remotely text-edit a batch file to:
At the machine itself use the NET STOP and NET START commands... like...
NET STOP winvnc
do stuff
>>>that we've shipped off to a site 1200 miles away, and something tells me
>>>that I can't upgrade to a newer VNC while operating the machine via VNC. ;)
>>>-Original Message-
>>>From: Edric Bulalacao [mailto:[EMAIL PROTECTED]]
>>>Sent: M
To: [EMAIL PROTECTED]
Subject: Re: TightVNC vs regular VNC
This is a problem for me, too. A number of our machines I control through
VNC (Linux, Solaris, Win*). For Windows, I still have some running ORL VNC
3.3.3r9, some running TightVNC release and some TightVNC Preview. I would
like to
>
>Ryan
>- Original Message -
>From: "David Brodbeck" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, August 06, 2001 10:36 AM
>Subject: RE: TightVNC vs regular VNC
>
>
> > My biggest problem is that the machine that
IL PROTECTED]]
>>Sent: Monday, August 06, 2001 10:14 AM
>>To: [EMAIL PROTECTED]
>>Subject: RE: TightVNC vs regular VNC
>>
>>My findings were based on the latest preview source code of Tight
>>VNC...downloaded from www.tightvnc.com. Indeed, if bandwidth is your main
rst place.
11) edit email to simply read "call me when you get this"
12) send email, go out for beer
Brian Rea
PhysioMetrics
Mount Laurel, NJ
USA
- Original Message -
From: Yan Seiner <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 06, 2001 10:56 A
Actually I've done that a few times. All that's needed is a way
to run the TightVNC program after a delay period. Start the
timer, then close VNC. As long as nothing goes wrong the new
server comes up. Having someone at the other end who's capable of
running VNC is a nice safety blanket :)
Chris
David Brodbeck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 06, 2001 10:36 AM
Subject: RE: TightVNC vs regular VNC
> My biggest problem is that the machine that it'd be most useful on is one
> that we've shipped off to a site 1200 miles away,
Hmm, that shouldn't be much of a problem. Just create a script that
replaces the files in question during boot time. Windows supplies all
needed mechanisms off-the-shelf, just read the docs, *nix shouldn't be a
problem anyway.
David Brodbeck wrote:
>
> My biggest problem is that the machine that
newer VNC while operating the machine via VNC. ;)
>
> -Original Message-
> From: Edric Bulalacao [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 06, 2001 10:14 AM
> To: [EMAIL PROTECTED]
> Subject: RE: TightVNC vs regular VNC
>
>
> My findings were based on th
EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 10:14 AM
To: [EMAIL PROTECTED]
Subject: RE: TightVNC vs regular VNC
My findings were based on the latest preview source code of Tight
VNC...downloaded from www.tightvnc.com. Indeed, if bandwidth is your main
concern, then go with Tight VNC and play
My findings were based on the latest preview source code of Tight
VNC...downloaded from www.tightvnc.com. Indeed, if bandwidth is your main
concern, then go with Tight VNC and play around with the Custom and JPEG
compression levels and the mouse cursor thingie. But in addition, you'll
need to co
25 matches
Mail list logo
