Jonathan de Boyne Pollard wrote to Thomas W. Mueller on 03-03-1998
JP>  JdB>> (2)        Start the requester when you boot.  Do this by creating 
a
JP>  JdB>> shadow of the "Start File and Print Client" object in your Startup
JP>  JdB>> folder.
JP> 
JP>  TWM> The problem with that is, that it takes ages to start. Since Warp 4
JP>  TWM> takes a lot of time to boot anyway, it is possible to just start 
he
JP>  TWM> requester from the config.sys: run=c:\ibmlan\netprog\net.exe start
JP>  TWM> req
In fact, there are several APARs addressing race conditions which will
lock the machine due to sequenceing problems during initialization of
the requester and TCP/IP code.  At last check, they have gone to a
semaphore file in a effort to syncronize the contending sessions, so
the timing and sequence are improtant.
 
JP> I wouldn't recommend using RUN= in CONFIG.SYS for this purpose. 
JP> There are  session management issues that affect processes started 
JP> from CONFIG.SYS.  If you want to start the Requester  earlier than
JP> the processing of the desktop Startup folder,  then I'd suggest
JP> using \STARTUP.CMD .
JP> 
JP> ( Which is, in fact, where earlier versions of IBM LAN 
JP> Requester used to install themselves. )
JP> 
JP>  > JdeBP <
Will Honea 
--- Maximus/2 2.02
---------------