Date: Mon, 26 Apr 93 18:14:55 EDT
From: peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Cc: jrd AT cc DOT usu DOT edu
Subject: go32, ms-kermit and ethernet card

A while back, I complained that running any go32 program left my system in
a state where ms-kermit could not make a connection through my ethernet
card.  But, ncsa programs could use the ethernet card until I ran kermit,
after which, they would also fail.  An almost identical machine in the next
office does not have this problem.

Recently, I noticed that starting Windows 3.0 would unsnag the ethernet card.
But, starting Windows takes about the same amount of time as rebooting, so
I'd like to figure out how Windows does its magic.  Any suggestions?

A few things which don't help:
   mark / go32 / release
   mark / packetdriver / go32 / release / reload packetdriver
   sending a non-specific EOI to interrupt controller
   vanilla configuration (no QEMM)