On Fri, 14 Nov 2014, Shawn Highfield wrote to mark lewis:   
      
    SH>   Got it. ;)  Once I got rid of the OS/2 based mailer and just had   
    SH> Ezycom answer the "phone" the comport was able to share.  So   
    SH> working fine now.  Just thought I'd let you know.   
      
   ahhh! perhaps you need to use the '-' in your comport definition line in   
   config.sys?   
      
      
   DEVICE=X:\SIO160D\SIO.SYS (COM1,3F8,4,-) (COM2:115200,2F8,3,-) (   
   OM3,INTERNET:3E8,NONE:4,-) (COM4,INTERNET:2E8,NONE:3,-) (COM5,IN   
   ERNET:1F8,NONE:3,-) (COM6,INTERNET:1E8,NONE:3,-) (COM7,INTERNET:4F8,NONE:3,-)   
   (COM8,INTERNET:4E8,NONE:3,-)   
      
      
   or perhaps it is setting SIO_Share_Access_With_OS/2 but then, reading this,   
   i'm not sure...   
      
      
     "SIO_Share_Access_With_OS/2"  This DOS setting defaults to ON and   
     it applies to all communications ports used by the DOS session.   
     When ON, SIO will allow an OS/2 session to access a   
     communications port which the DOS session first opened (and has   
     not closed).  If set to OFF, then the DOS session will have   
     exclusive use of the communications port(s) that it uses.   
      
     This setting does not apply to a second DOS session attempting to   
     access a communications port,  two different DOS sessions are   
     never allowed to access the same port at the same time.   
     Additionally, this setting has no affect upon the access to a   
     communications port which is first opened by an OS/2 session.   
      
      
   the last part of the last paragraph seems to say that you are correct about   
   the os/2 mailer being in the way... i use both FD/2 and FD but have never done   
   the os/2 door thing as noted previously...   
      
   interesting find... you've written it down for when you need it in another 20   
   years, right? ;)   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)