-=> /* Quoting Clay Tannacore to Lawrence Mintz */ <=-
 CT> @PID: FDAPX/w+ 1.12a BJ00002
 LM> * In a message originally to Lawrence R. Mintz, David Bowerman said:
 >> Neither of the two machines I updated using the Wizard had the comm port
 >> locked.  A common point?
 
 LM> I suspect that locking the comm port while running the Wizard has the 
same
 LM> affect as running the SDL for the Courier does when its comm port is
 LM> locked. For others who don't know, the SDL for Couriers will not find a
 LM> Courier to update if the comm port is locked while the SDL is running.
 CT> In that case, there is a Gremlin in my machine that must sneaked into
 CT> the CPU just before I run an SDL and unlock the port.  Because I've
 CT> applied the last four SDL's the X2 upgrade and the V.90 upgrade
 CT> without removing the lock status of the port.  
Since it appears that you're running Windows, how are you
locking the port?  If you're using a FOSSIL in the EXE mode
in your program batch file the port is only locked during
the execution of the program.  Maybe your port was not
locked when you actually ran the Wizard?
-Frank
(fsexton@ibm.net - http://www.concentric.net/~fsexton)
--- Blue Wave/OS2 v2.30
---------------