GU>     The other possibility could be my IO card.  It is a DTC 2278 VL-bus
GU>EIDE/IO card.  I know that DOS/Win. required special drivers for 32 bit
GU>file and disk access.  Perhaps OS/2 requires special drivers to properly
GU>access the ports.  Then again, I may be overanalyzing this since the
GU>OS/2 TCP/IP stack and Procomm Plus for Windoze both access my external
GU>modem without a hitch and my serial mouse works fine.
I missed the original post, but let me theorize for a second, is your
mouse by chance on a COM port that is 2 away from the one that you are
trying to use Laplink on?  ie, Mouse on COM1, Laplink on Com3?  Mouse on
Com2, Laplink on Com4?  The problem in that case is that you are trying
to use two ports with the same IRQ value.  That is, Com1 and Com3 share
IRQ 4, Com2 and Com4 share IRQ 3.  You can only use one port that
shares an IRQ at a time under OS/2 and you have to TELL OS/2 that you
want it to share IRQ's for those ports. If this is the problem, then you
have to reconfigure your IO card to use a different IRQ, and tell OS/2
about it in your CONFIG.SYS file on the DEVICE=D:\OS2\BOOT\COM.SYS
(1,3f8,4) (3,3e8,4) line.  Mine tells both COM1 and COM3 to use IRQ4.
If you don't do this, OS/2 will tell Laplink that the port you are
trying to connect to doesn't exist.
You might also want to check that the COM_DIRECT settings are enabled in
the settings for the DOS session you are using.
Rob.
I used Laplink Parallel yesterday, and I have used laplink serial a
number of times here on Com1.  (My mouse is on Com2, Modem on Com3).
___
 X SLMR 2.1a X WinError020: Error recording error codes. Errors lost.
--- Maximus/2 3.01
---------------