> >Also, I have tried the Java viewer (most people here use the Java viewer
> >actually). It dithers down to 8-bit automatically so you can usually
work a
> >bit longer, but it will eventually lock up and BSOD like the standalone
> >viewer. Yesterday I BSOD'd about 4 times in a row because of this one
> >computer I just needed to do a LITTLE work on. I ended up walking to
> >another computer which had NT4, transferring the call, and finishing it
> >there :)
>
> Same symptoms with the Java viewer. That pretty much eliminates VNC as
> the cause of the problem - see if the NIC helps.
>
> VNC couldn't have been the cause of the problem in the first place - if
the
> OS is crashing then it's definitely an OS problem!
>
> Cheers,
>
> James "Wez" Weatherall
Well, we know it's an OS issue :) It's always an OS issue with Windows.
Swapping the NIC's worked just fine, thanks for the idea. I never thought
of that.
Using an Intel NIC now and haven't bluescreened once. Might want to put
that in the FAQ cause I know there's a few people other than me at other
companies who have experienced the "faulty NIC driver" problem .. might just
want to explain that it's not VNC's fault, it just exploits the shoddy code
in the network card drivers.
Thanks again!
Chad Pommiss <[EMAIL PROTECTED]>
LAN Administrator - Sears Home Improvement Products
(407) 767-0990 x107 | Fax (407) 551-3169 | (800) 222-5030
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
