3.3.3r2 for Wintel problems

[Roby Van Hoye]

Hi there,

Hmm, I'm rather disturbed about the idea these "pseudo services" are run
only AFTER somebody logs in. (they are /vital/ to me). As I was getting
nervous about the idea v3.3.3r2 might have this 'undocumented feature' in
it I started experimenting and here is my version of the story (running on
a portable, W95B). 

1) I've got the distributed.net client running from the mentionned registry
key and the program is definitely run during startup, wether someone logs
in or not. (I've got the logs to prove it :)

2) I've got WinVNC v3.3.3r2 running from the registry key and as an
experiment I tried to ping & VNC the machine as this guy had done too.

* ping requests time out for a while... (boot sequence)
* 3 seconds after the networkcard (PCMCIA) is initialized ('Tuudee') the
pings start returning
* some time later the computer shows a login screen and harddisk activity
indicates "something is going on"
* when I VNC the machine from a remote client the program lets me log in
and "remotes" the portable's screen.

I can now use the client computer to log in to windows and start using the
portable. Sigh.

Conclusion, it is not VNC that is causing this behavior : I guess there is
something really weird about ngkuisp "at" interpath.com's machine... but what ?

You are absolutely sure the key is located in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices ? 
(if it is in '\Run' or 'RunOnce' the program indeed will only be run AFTER
somebody logs in...)

Cu
Roby

At 19:46 16/02/00 +0000, James [Wez] Weatherall wrote:
>On Wed, 16 Feb 2000 ngkuisp "at" interpath.com wrote:
>
>> No... I can ping the machine both by IP and by hostname before the first 
>> signon attempt.
>> Actually... using ping -t I can watch the machine go down and pings start 
>> failing, then as the machine comes back up, it starts pinging again while 
>> the Windows 95 banner is still on the screen shortly before the GUI pops 
>> up.

>I'm afraid I'm stumped, then.  Win9x is supposed to run the RunServices
>stuff before a user logs in.  I'm not aware of any setting that would
>change that behaviour, but clearly something is.
>The machine doesn't display any WinVNC-related dialogs when it starts up,
>does it?
>
>Cheers,
>
>James "Wez" Weatherall
>--
>Laboratory for Communications Engineering, Cambridge - Tel : 766513
>AT&T Labs Cambridge, UK                              - Tel : 343000
>
>
>---------------------------------------------------------------------
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to majordomo "at" uk.research.att.com
>See also: http://www.uk.research.att.com/vnc/intouch.html
>---------------------------------------------------------------------
>
>
Cu
Roby.


---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------