Quote:

I never had a problem with Win9x logins, of course each script is fairly unique.

When KiXtart exits it should release memory and clean up automatically, with the exception of COM automation objects which may hang around - you should explicitly clear/close these if you have any.

My guess is that it is a timing issue, and your extra code to clear down the variables is delaying the script long enough so that the problem does not appear.

I've seen similar problems with scripts that run asynchronously, or mess about with the Z: drive mapping.


I run all logon scripts synchronously, so the redirection of shell folders (my docs, favorites, etc) is in effect before the profile is loaded. I have a safety check that the Z: drive cannot be mapped, so that's not it as well..

I do run some WMI code (WMIQuery UDF) though, does WMI get info trough COM scripting (or am I way off :P ) perhaps? And do you mean I need to empty all vars used in the WMIQuery function or how can I nicely close up COM scripting?
_________________________
Ruud is my hero