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 reliability.
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 other computer and "push" the reset button for the computer
that is locked up.
I have seen a product called the PC weasel that can do this same thing, and
let you access the bios if you want to as well, but is was $300-400 IIRC.
My solution is cheep, you can find single 8255 boards for under $50, and the
software is free for linux/windows/dos. This it is probably not elegant
enough for some people, though.
--
Bryan Fields, KB9MCI
____________________
The chief cause of problems is solutions.
-- Eric Sevareid
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
