Peter Knapper wrote in a message to Roy J. Tellason:

 PK> Hi Roy,

 PK> Sleep2 is a program that waits for x seconds and then exits, in 
 PK> this case x = 60 seconds. 

 RJT> Isn't there a command that's already likely to be on my system 
 RJT> that will do this?  Something in REXX, maybe?

 PK> Yes, you can write the function in REXX using SysSleep(x) if 
 PK> you wish, however at this point I wish to keep REXX out of the 
 PK> script.

Maybe I was mistaken,  but I thought that there was some system command that
did this.  Oh well.



 PK> Well it wont exit the loop until it DOES find ALL the files... 
 PK> The NET USE will display an error message within a few seconds 
 PK> if it can't find the resource so all the mappings are attempted 
 PK> again, but other than the error message there is no other 
 PK> adverse affect.

 RJT> I may end up using a separate process,  though,  to run in the 
 RJT> background and see if the w95 box has been turned on and
 RJT> then to establish that connection,  if so,  rather than hanging 
 RJT> up startup.cmd with continuing attempts to access a machine 
 RJT> that may not be turned on.

 PK> My STARTUP.CMD does not "hang-up", it actually performs various 
 PK> startup functions including STARTing STARTUP2.CMD, which starts 
 PK> up the Requestor, logs in a default user, maps the drives, 
 PK> removes old FLAG files, then EXITS the STARTed session, so it 
 PK> runs as a seperate process and ends itself.

Oh,  okay...

This approach makes sense to me.

 PK> It does not hold up anything other than the functions it 
 PK> controls... You can set the wait period to be anything you like 
 PK> if you want. In this case the CLIENT machine is MUCH faster at 
 PK> starting up, so I frequently have it waiting about 4-5 mins 
 PK> before the drives map ok. The only time the script failed me is 
 PK> when the Server machine failed to restart after a power fail 
 PK> that required manual intervention.

 PK> Another warning, if an OS/2 machine has TCP/IP AND NETBIOS 
 PK> configured, then checking for network connectivity using TCP/IP 
 PK> (EG PING) is going to work LONG before PEER Services (and 
 PK> subsequently the NET USE command) is up and running.

Yeah,  that's another aspect of this stuff that is somewhat puzzling to me,
why it takes so long for that to come up.  I see "The requester service is
starting........" (or something close to that) and it sits there,  on the
screen.  Any idea how I'd make that one come up minimized?

---