On 30 Mar 98  11:31:01, Lawrence Mintz said this to David Bowerman
about "OS/2 Update Wizard Word A":
 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
 LM> same affect as running the SDL for the Courier does when its comm port
 LM> is locked. For others who don't know, the SDL for Couriers will not
 LM> find a Courier to update if the comm port is locked while the SDL is
 LM> running.
 LM> Larry
Why in the Sam Hill do people lock the port with SIO, anyway?  Isn't the
comm. software supposed to handle whether or not the port is locked?  In
my situation, I use Qmodem 4.6 Test Drive for DOS, in a DOS session
under Warp 3.0, and Qmodem locks the port.  So, I just let SIO float.  I
don't recall programs like WiveWire or Zap-O-Com *not* locking the port,
but maybe they don't...?
      -=> Tom Rutherford -- Team OS/2 <=-
... Barnum of Borg - "There's one assimilated every minute."
--- Blue Wave/OS2 v2.30
---------------