Kathy,
If I may make a suggestion...
Write small scriptlets and test them in isolation before including them in the main script. That cuts down on the calls that puts everyone in fire-fighting mode and frustrates the users. You can test them first without logging out/in by just dragging and dropping them onto KIX32.
Then what you do is to have a JoeBlow account that is set to use a different logon script (say, test.kix) called from another bat file (say, logon2.bat). You take the scriptlet and test it with the JoeBlow account during logon on a variety of OSes. Once you've work out the proof of concept, you take the production script, include your new code, save it as test.kix, and test it up the ying-yang. After the problems are worked out you put it in production.
[ 20. October 2002, 00:02: Message edited by: LLigetfa ]
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
