JB> I've asked this before and never got an answer so I thought I'd give it 
 JB> one more try.  I've got a couple of programs in my startup folder which 
 JB> I want to start after the workstation or server have started.  However, 
 JB> I've got a couple of these tasks which require a service to be running 
 JB> first.  In one case the service, which one of these tasks depends upon, 
 JB> takes a while to start, due to the nature of the service.  The question 
 JB> is whether I can delay tasks in the startup folders by says 60 secods or 
 JB> can I have the tasks startup in a particular sequence in the startup 
 JB> folder ?
I had this problem also. NT comes with a cute little utility called wait. I 
used wait in a startup.cmd file that I ran from the starup folder. It was 
something like:
SUBST H: C:\
SUBST I: D:\
WAIT 120
WINGATE
NET USE LPT2: \\COWBOYC\LASER4
etc.
Would wait 120 seconds and then start wingate and any other network dependent 
commands. 
I quit doing it using wait when I found I could start all my apps as a 
service using srvany and instsrv. Apps started as a service with instsrv, 
like wingate, don't start until after the workstation and server services 
have started. You might try starting them as a service and see what shakes 
out jeff. For the stuff I was doing, I found starting them as a service 
cleaner.
--- Maximus/NT 3.01b1
---------------