You would think - eh?
The environment I inherited recently had 130+ bat files, 130+ kix files (calling additional VBS scripts) and somewhere around 40 VBS scripts. Even worse, some kix scripts called 3 separate VBS scripts, which each mapped one drive. All of this to support the login process! One of the most bizzare things I've seen in the technology world.
Can anyone guess how many .KIx and .VBS scripts are present today? 
As for your issue, a sleep called from your VBS would work, but not from within Kix (the window would open/shut, then kix would wait). Richard had the best idea for troubleshooting - don't run the .VBS script from kix (even temporarily). Alter a copy of your login scrip to run SHELL '%COMSPEC%' - kix will pop open a command prompt and wait for YOU to close it.
Modify your account to run the modified login script, then log in. Run the VBS script manually when the command window opens - check the results, and type EXIT - the kix script will continue. This way, you can closely control the actual process of the login script, during login time.
Glenn
_________________________
Actually I
am a Rocket Scientist!
