home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!usenet.ins.cwru.edu!cleveland.Freenet.Edu!al919
- From: al919@cleveland.Freenet.Edu (Bruce Halco)
- Newsgroups: comp.os.os2.misc
- Subject: Make COM3 talk to COM4
- Date: 4 Jan 1993 03:07:15 GMT
- Organization: Case Western Reserve University, Cleveland, Ohio (USA)
- Lines: 26
- Message-ID: <1i89l3INNte@usenet.INS.CWRU.Edu>
- NNTP-Posting-Host: slc10.ins.cwru.edu
-
-
- Some DOS software I'm writing involves async communications, and
- I figured using OS/2 to serve as 2 DOS machines would be more
- convenient than hooking up two physical computers. So I
- installed a 2-port serial card as COM3 and COM4 and looped the
- connectors back on the card. I modified CONFIG.SYS to correspond
- with the serial ports thusly:
-
- DEVICE=C:\OS2\COM.SYS (3,3E8,5) (4,2E8,9)
-
- But I _CAN NOT_ get reliable communications between the ports.
- What really drives me nuts is that I don't even get REPEATABLE
- results. One time I'll need COM_DIRECT_ACCESS on, the next day
- it needs to be off. COM_SELECT is restricted to the individual
- ports. IDLE_SENSITIVITY is set to 100 (disabled). I know the
- physical connection is OK because I can send individual bytes
- with DEBUG. Even when it _almost_ working, one port will send
- for a while, than pause until I hit a key in that session. Other
- times it sends nothing, or even refuses to start the session with
- an error about another session having access to that port (even
- if nothing else but the WPS is running). I've about run out of
- DOS session settings to modify, and I think I'm completely on the
- wrong track by now. What have I overlooked? BTW, the system is
- a 486/33, 16M RAM, SP installed over the GA release.
-
- Any and all suggestions will be welcomed.
-