Hello,
> "RAL" == Robert A LaRock writes:
>>> TightVNC 1.2.3 has been finally released.
RAL> I have been testing TightVNC and, with one exception, it seems
RAL> good to me.
RAL> I am fond of the Win2VNC program by Fredrik Hubinette. If I use
RAL> TightVNC, closing the Win2VNC program cras
Constantin
>> TightVNC 1.2.3 has been finally released.
I have been testing TightVNC and, with one exception, it seems good to me.
I am fond of the Win2VNC program by Fredrik Hubinette. If I use TightVNC,
closing the Win2VNC program crashes the TightVNC server. This happens if I
right click
Agree!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 26, 2002 8:32 AM
To: [EMAIL PROTECTED]
Subject: Re: TightVNC 1.2.3 released
The problem is the admins want to see what has hung, and because of this
they are switching to PC Anywhere which
mann
cc:
Sent by:Subject: Re: TightVNC 1
According to Constantin Kaplinsky:
> Hello,
>
> TightVNC 1.2.3 has been finally released.
[snip]
vncsnapshot (http://vncsnapshot.sourceforge.net) is based on TightVNC.
I used TightVNC 1.2.2 as the base. However, after inspecting the new version
(1.2.3) I have found that the portions of TightVNC
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, 2002-03-26 08:03
Subject: fyi 8255 PPI card [was Re: TightVNC 1.2.3 released]
> If you feel cheated that you end up with 16 leds hidden away inside each
PC where the sun doesn't shi
ailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 26, 2002 2:04 PM
> To: [EMAIL PROTECTED]
> Subject: fyi 8255 PPI card [was Re: TightVNC 1.2.3 released]
>
>
> On 25/03/2002 20:18:50 Bryan Fields wrote:
> >
> > The way I fixed this, is to put a 8255 Peripheral
> co
On 25/03/2002 20:18:50 Bryan Fields wrote:
>
> The way I fixed this, is to put a 8255 Peripheral controller card in both
> computers, and wire one logic from each card to the other computers reset
> line. Then you can ssh/vnc into one and reboot it proper. If it hangs, then
> connect to the othe
although he does not document it, there are a
couple of codes you can issue as arguments to rundll32 setupapi which might
be usable to do a direct command-line forced reboot.
- Original Message -
From: "Mike Miller" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Mon
PROTECTED]>
Sent: Monday, 2002-03-25 15:18
Subject: Re: TightVNC 1.2.3 released
> On Monday 25 March 2002 13:48, you wrote:
>
> > TightVNC is similar to VNC in this aspect. If somebody knows how to
> > solve the problem the most correct way, please let me know, I'll try
>
There was a good thread on this subject ("shutdown gotcha with Win32
host") about 3 weeks ago. Andrew van der Stock had a good description
of what the problem is and some suggestions for how it might be fixed.
Jake Hoover found this handy workaround:
http://www.winguides.com/registry/display.
On Monday 25 March 2002 13:48, you wrote:
> TightVNC is similar to VNC in this aspect. If somebody knows how to
> solve the problem the most correct way, please let me know, I'll try
> to fix that, if that would not take too much time.
This solution requites 2 computers for the utmost reliabilit
[EMAIL PROTECTED]Subject: Re: TightVNC 1.2.3
released
Hello Tony,
> "tc" == tony caduto <[EMAIL PROTECTED]> writes:
tc> Does tight VNC shut down before everything else like standard VNC?
tc> For those of you who don't know when you reboot a server with vnc,
tc> the vnc service is the first to die, and if something else hangs ,
tc> you will nev
On Mon, 25 Mar 2002 [EMAIL PROTECTED] wrote:
> Does tight VNC shut down before everything else like standard VNC? For
> those of you who don't know when you reboot a server with vnc, the vnc
> service is the first to die, and if something else hangs , you will
> never know it.
>
> This is ok if t
Does tight VNC shut down before everything else like standard VNC?
For those of you who don't know when you reboot a server with vnc, the vnc
service is the first to die, and if something else hangs , you will never
know it.
This is ok if the server is down the hall, but when it is across town or
> "DW" == Dave Warren <[EMAIL PROTECTED]> writes:
>> TightVNC 1.2.3 has been finally released.
DW> I have a number of computers running regulat WinVNC. Can I simply
DW> stop the VNC service, kill winvnc.exe vncviewer.exe, drop in the
DW> new EXE and DLLs (Into the existing \Program Files\ORL
Constantin Kaplinsky wrote:
> TightVNC 1.2.3 has been finally released.
I have a number of computers running regulat WinVNC. Can I simply stop
the VNC service, kill winvnc.exe vncviewer.exe, drop in the new EXE and
DLLs (Into the existing \Program Files\ORL\VNC directory) and restart
the serv
Hello,
TightVNC 1.2.3 has been finally released. I'm sorry for the delay, but
it allowed me to fix more problems, including that zlib "double-free"
issue.
New version is available from the usual place:
http://www.tightvnc.com/download.html
Here is a brief list of changes over 1.2.2:
- Uni
19 matches
Mail list logo
