Right.  What's happening is that the hooks are continuing to post messages
to WinVNC, even though it's temporarily gone away to send an update - it
can't handle the incoming messages while it's transmitting the update.  The
fix is to separate the update thread from the hook handling thread but
that's non-trivial.  I'll have a look at it, though.

Cheers,

James "Wez" Weatherall
--
          "The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK                              - Tel : 343000

----- Original Message -----
From: "Michael Milette" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 18, 2001 4:25 PM
Subject: Re: A Simple Problem? (with a simple solution?)


> Sorry about that. I was afraid it might look that way.
>
> Anyway, the resources are being eaten up while the initial screen is
> loading. It is not an instantaneous thing. The longer it takes to get that
> initial screen, the lower the resources go until, well, there are no more
> to be had.
>
> What I was trying to say was that the problem doesn't begin until after
you
> enter your password (there is no drain happening while you are being
> prompted for a password).
>
>                          Michael Milette
>
> At 12:29 PM 2001-04-18 +0100, you wrote:
> > > 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.
> >
> > > >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 second paragraph suggests the server crashes the instant the password
> >has been entered, while the first paragraph indicates there should be a
> >delay while the server eats resources trying to transmit the data.
> >
> >These two symptoms sounds different to me.  Can you clarify whether this
is
> >the case?
> >
> >Cheers,
> >
> >J.N.Weatherall
> >---------------------------------------------------------------------
> >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
> >---------------------------------------------------------------------
> ---------------------------------------------------------------------
> 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
> ---------------------------------------------------------------------
---------------------------------------------------------------------
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
---------------------------------------------------------------------

Reply via email to