Rick Collins wrote in a message to Tom Rutherford:
TR> Why in the Sam Hill do people lock the port with SIO, anyway?  Isn't the
TR> comm. software supposed to handle whether or not the port is locked?  In
TR> my situation, I use Qmodem 4.6 Test Drive for DOS, in a DOS session
TR> under Warp 3.0, and Qmodem locks the port.  So, I just let SIO float.  I
TR> don't recall programs like WiveWire or Zap-O-Com *not* locking the port,
TR> but maybe they don't...?
 RC> It's really poor terminology.  The port is going to stay at
 RC> whatever speed you set it to - there's no command to "lock" it.  In
 RC> reality, you're telling the comm software not to change the port
 RC> speed.
Using SIO.SYS and VSIO.SYS under OS/2, the ports can be truly "locked" at a 
specific speed, where no comm program (OS/2 or DOS) is able to change the 
speed.
                                   - Bob
Internet  : bob@juge.com
Telnet, Vmodem, WWW or FTP to juge.com
--- timEd/2 1.10+
---------------