There're a couple of good suggestions so far. But start /b should not be one. That's equivalent to appending & to a command on UNIX/Linux, not nohup, which ignores SIGHUP signal. Windows doesn't have the signal concept. The Windows equivalent of nohup is running a command even after the user logs off. An "overkill" solution is to create a service to run your command. An easier way is to schedule a task. But if you have psexec.exe (from sysinternals.com), you can run the command as the pseudo user system, which obviously never logs off: psexec -s -d yourcommand. The -d switch is like start /b or & on UNIX. Yong Huang -- //www.freelists.org/webpage/oracle-l