🚀 go-pugleaf

Scenario: I am modifying a communications program that uses COM1 only
for serial communications. I have added push/pop capability to this
program, to allow a user to use go out over COM2 for a brief period,
then return to a database search on COM1. The program that is used to
go out over COM2 is, incidentally, Crosstalk.

Problem: When returning to the session on COM1, the first response to
any command is garbage. One has to drop DTR and logon anew, precisely
what the user wants to avoid. Now, after the user "exits" from DOS back
to my program, I make sure that I reset INT 0Ch to point back to my
interrupt routine, and I re-enable IRQ4 on the 8259. I assume COM1 is
configured as I set it, since the Crosstalk session is configured to
go out over COM2. So what could be wrong? If anyone has any
suggestions, especially about how to proceed about this in a
well-behaved way, I'd sure appreciate them.

Note: If I push out of my program and do some editing, then exit back
to the session, the session is still there. The garbage occurs only if
another communications program has been run.

-- 
Charles Blair   			    ..!ihnp4!gargoyle!sphinx!cjdb
The University of Chicago		    lib.cb%chip@UChicago.Bitnet