Date: 26 Apr 1993 17:40:43 -0600 (MDT)
From: Joe Doupnik <JRD AT CC DOT USU DOT EDU>
Subject: Re: go32, ms-kermit and ethernet card
To: peprbv AT cfa0 DOT harvard DOT edu
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu

Bob,
	Just to clarify things in my mind about your GO32 + Kermit problem.
I presume you are running Kermit over a Packet Driver, Int = ??, and maybe
NCSA Telnet directly to the Ethernet board rather than to a Packet Driver.
The board is ??, and you have taken steps to protect its shared memory
segment from intrusion both at DOS and Windows levels, not to mention keeping
the IRQ away from serial port values.
	Does the same thing happen if you run say Kermit over ODI rather than
a Packet Driver. I'm looking for conflicts in the Int 60h..7fh region with
GO32 (whatever that is, some protected mode DOS extender I presume).
	One does not want to treat comms drivers like ordinary TSRs so Mark
and Release are inappropriate to Packet Drivers and such, as you discovered.
	If GO32 is a DOS extender then I would expect some machine personality
issues to arise from the way a particular board gets into and out of protected
mode, as well as the usual bus timing aspects of all this. Notice how Windows
has the A20 Gate timing funtion to cope with different machines.
	If you ran both NCSA Telnet and Kermit over the same Packet Driver
then there are still systems problems to consider, such as MSK grabs very
few interrupts but NCSA Telnet grabs more. In particular MSK does not play
with the keyboard interrupt material, and we know the keyboard controller
chip may be used to handle protected mode on some machines.
	Clarity disappears about this point. Further insight would be welcomed.
	Joe D.