Michael,
It worked. I set the colors to 256 on the host and no more crashes.
1. The issue appears to be a function of color depth on the Win98 machine.
If I lower the color depth to 256 (from 16 bit), it works fine and does not
crash. Resource drain is minimal (from 62/62/79 to 59/59/76). However, if I
set the color depth to 16 bit, then it crashes at ANY resolution on the
host. "Crash" means I get a Doc Watson error noting a conflict with
dibeng.dll. The good doctor intercepts the message and stops the thread, but
doesn't take the system down completely.
2. Setting the remote option to request only 8-bit color does not solve the
problem. BTW, I'm using an AGP Intel 740 card on the host.
3. I'll be surprised if it is a function of connection speed. I'm testing
this over my 100Tx LAN, and it's crashing. My guess is that the memory
conflict is occuring completely within the Win 98 (or ME) host.
4. I'm a veteran of pcAnywhere and use it a lot. I was looking for a cheaper
and thinner solution to manage a lot of hosts in a LAN, but it looks like
Symantec does a better job with Win9x color management. If I have to modify
the host colors, or risk the host crashing when a remote logs on, VNC's
probably not an option.
Thanks for the help,
Ovid Bailey
BTW, I copied the developers on this too.
>Date: Wed, 18 Apr 2001 03:15:05 -0400
>From: Michael Milette <[EMAIL PROTECTED]>
>Subject: Re: A Simple Problem? (with a simple solution?)
>
>To see exactly why your system is crashing, run the Windows Resource Meter
>on your task bar. You will notice that after you enter your password (as
>the initial screen is loading up), your system resources will drop like a
>rock. If you manage to finish downloading the initial screen before you run
>out of resources, most of your resources will come right back. However if
>the initial screen doesn't finish coming up before you run out of
>resources, the system will crash.
>
>I have found it to be more of a problem over slow connections (like modem)
>however it can be a problem even on a high speed LAN if the machine you are
>trying to take over doesn't respond immediately (for example if the hard
>drive has to spin up).
>
>This isn't a problem when doing the same thing on Windows NT or Windows
>2000 since you don't have the same 128k limit on resources. I have
>mentioned this issue on the list several times in the past but nothing has
>been done about it in any release over the last couple of years.
>
>What can you do about it? Reduce the number of colours and the resolution
>of your hosts screen. It won't make the problem go away, but it will give
>you a better chance of getting that initial screen before the system
>crashes. Alternatively you could simply use one of the commercial programs
>out there like PCAnywhere or Microsoft NetMeeting. I haven't tried a recent
>version of Laplink but the one I have tried, which is a couple of years
>old, had the same problem as VNC over slow connections with Win9x.
>
> Michael Milette
>
>At 10:05 PM 2001-04-17 +0000, you wrote:
> >There is a message from p.vinten on April 6 (with no reply yet) with the
> >identical symptom with version 3.3.3.R9. I am having the same problem,
>and
> >details of the crash show the same dll culprit as Mr.
>Vinten...dibeng.dll.
> >
> >On that box, I am running Windows 98 SE with two network cards. One is
> >using DHCP (to my DSL modem) and the other uses a 192.168.100.xxx
>address.
> >Using that computer as a remote, it works great going to my Windows 2000
> >laptop. But when using it as a host, as soon as the password is entered
>by
> >the remote, the Win 98 system crashes.
> >
> >The same software version works fine as a host on my Windows 2000 system
> >(single NIC), but not on the Win98SE box.
> >
> >Any ideas?
> >
> >Thanks
> >>
> >>Date: Mon, 16 Apr 2001 01:35:25 -0400
> >>From: "Mikhil Bopaiah" <[EMAIL PROTECTED]>
> >>Subject: A Simple Problem? (with a simple solution?)
> >>
> >>Hey, I've searched all the faq's and documentation but I can't figure
> >>this one out: I'm trying to run VNC (3.3.3r9) on my old compaq at home
> >>(W95). I installed WinVNC with the default settings and no problems.
> >>Running WinVNC in App mode works fine. When I try to access the server
> >>from a web browser (http://my.ip.address:5800) I get the prompt for the
> >>password, but as soon as I enter it my server machine displays the
> >>message "An error has occured on your computer..." and the server shuts
> >>off WinVNC. I tried accessing from the vncviewer but the same thing
> >>happens (as soon as I enter the password in the viewer, the server
> >>disconnects and displays error message "An error has occurred on your
> >>computer..."). The strange thing is that when I do this, the wallpaper
>on
> >>my server desktop is removed. I tried removing the wallpaper, and
> >>changed the resolutions and color settings so that they matched on my
> >>server and client machine. I also tried accessing from different
> >>computers and the same thing happens (it's obviously a problem with my
> >>server machine). If you have any suggestions I'd be much obliged.
>I've
> >>been tinkering with this for a while and it's driving me crazy...
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
---------------------------------------------------------------------
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
---------------------------------------------------------------------
