🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.os2.misc
Article #14768

Re: Make COM3 talk to COM4

#14768
From: Gregory Youngblood
Date: Mon, 04 Jan 1993 04:55
48 lines
2678 bytes
al919@cleveland.Freenet.Edu (Bruce Halco) writes:

> 
> 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.

I'm not sure, but I'm doing the same thing.  I haven't been able to get it 
going myself.  Frist suggestion.  Use external cables, don't try to jumper
the two on the card itself.  Second suggestion.  Get a NULL Modem cable,
or get a cable and null modem adapter.

The trick is to:
     2    to     3
     3    to     2
     7    to     7
     5,20 to    8  ?  I think
There are several needed to be complete.  Dont have that information off the
top of my head.. sorry.

Greg

.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.
.   TCS Consulting Services   P.O. Box 600008   St. Paul, MN  55106-0008    .
.   ..!srcsip!tcscs!zeta                 ..!src.honeywell.com!tcscs!zeta    .
.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.
Technical Details
Message-ID: <ee4TwB2w165w@tcscs.UUCP>
Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!uwm.edu!src.honeywell.com!tcscs!zeta
References: <1i89l3INNte@usenet.INS.CWRU.Edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!uwm.edu!src.honeywell.com!tcscs!zeta
From: tcscs!zeta@src.honeywell.com (Gregory Youngblood)
Newsgroups: comp.os.os2.misc
Subject: Re: Make COM3 talk to COM4
Message-ID: <ee4TwB2w165w@tcscs.UUCP>
Date: Sun, 03 Jan 93 22:55:01 CST
References: <1i89l3INNte@usenet.INS.CWRU.Edu>
Reply-To: zeta%tcscs@src.honeywell.com
Organization: TCS Consulting Services
Lines: 48