The comspec is required in order to redirect the output of the command to the log files. Did you try that? did anything show up in the log files that might lend additional clues? If you're redirecting to log files, you won't see any output on the screen. Also, since this is a login process, I'd try Shell instead of Run, so it's synchronous. I've not used Run in the login script for anything that takes more than a second or two to execute, so I'm not sure of any consequence on the children when the parent process exits. I assume your executable taks a bit of time to run.
Another diagnostic step - Create a batch file in the same folder. The batch file should just write the time to a log file (time /t > .\startlog.txt). Execute the batch file just before you execute your installer. That will validate that the drive is mapped and you can execute objects on that share.
If you're mapping a drive to the executable location, why are you using UNC syntax to specify the command path? If you
net use x: \\server\share
your command line should be something like
x:\ezaudit\exstart.exe
Hmm... "ezstart"??? 
Don't seem to be this time! 
Last thing - please try my example exactly as shown. Only modify paths to suit your environment. If it fails, post the logs that it generates.
Glenn
Edited by Glenn Barnas (2008-07-11 07:51 PM)
_________________________
Actually I
am a Rocket Scientist!
