🚀 go-pugleaf

In article <92230.152601U55870@uicvm.uic.edu> you write:
:   I am writing a bbs program that will run under ms-dos and will require a
: special term program.  To do this properly, it would seem easiest to hook
: up two machines through the srial prot, and develop the bbs program on one,
: the the term on the other.  However, I do not have two machines at my disposal,
: so I have a problem.  I would like to use os2( I'm using it now anyways ) and
: run the term program in one window, and the bbs program in another.  I can
: develop the software this way, and worry about adding the serial/phone routines
: when the bbs software is completely written/debugged.  Does anyone know of a
: practical way to communicate between DOS windows in os2?  I need to send
: information bolth ways, obviously, just like a bbs and term.  Thank you
: for any help.
: 
: 
: dave

I take it you do not want to emulate the actual serial comms - just any byte
stream will do.

Well with named pipes, a Dos program can communicate with an OS/2
program. With this as a basis, you can have DOS to DOS comms. Here's 
how it works ...

-	run the OS/2 program. It sets up 2 pairs (4) of named pipes.
	call them "\pipe\termread", "\pipe\termwrite", "\pipe\bbsread"
	and "\pipe\bbswrite". I'll refer to them by the short form
	names termread,termwrite,bbsread,bbswrite.

- 	The OS/2 program is the server for this. It reads from termread
	in order to write to bbswrite and reads from bbsread to write to
	termwrite.

-	The DOS term program reads from termwrite and writes to
	termread. The DOS bbs program reads from bbswrite and writes
	to bbsread.

That's all. DOS programs can open and use pipes using normal file system
IO calls. Your main problem is writing the probably short OS/2 program
to do this.

How's that?

hope it helps

jin meng