🚀 go-pugleaf

I'm sure this isn't a windows problem, but I suspect someone from this
group is more likely to have run across (and resolved, I hope) this.

I'm attempting to run both WNQVTNET and NBP over a 3-COM 3C503 card
simultaneously.  I have WNQVTNET v1.5, LANMAN v1.1, w/3COM E-LINK II
v1.1, 3COM NEMM v1.1.  My problem is that the last set of TSR's loaded
kill/interfere with the earlier loaded TSR's.  That is, if I load the
Clarkson 3C503 driver first, then fire up the 3COM stuff, the 3COM
stuff works but WNQVTNET can't talk to 3C503 via PKTINT.   If I reverse
the order of loading, I can do FTP and terminal sessions, but none of
my NBP-mounted drives are available.

The 3COM card shared memory jumper is set at c8000.  (had to be
set at one of the four settings per the Clarkson instructions.)

I suspect a conflict somewhere, but which one?  The IOAddress looks
like a likely candidate, but what other values are legitimate?

PROTOCOL.INI entry:
; 3Com 3C503
[ETHERLINKII]
  DRIVERNAME = ELNKII$
  Interrupt = 5
  IOAddress = 0x300
  xmitbufs = 2
  DMAChannel = 1

Clarkson PD startup:
3c503 0x7e 5 0x300 1

qvt_tcp.rc entry:
packet_vector=7e

Other possibly pertinent info: COMPAQ 386/20e, 4MB RAM, 40 MB HD.
I am able to load the v1.2 TCPIP/FTP package from 3COM and use it
concurrently with NBP.  It just ends up leaving me with ~325K real.
The Clarkson drivers leave me with ~480K (both figures include
NBP and friends already loaded, along with a few other items).

Has anybody worked this out already?

-- 
name & address   (this account) -> dwn@swbatl.sbc.com
David Neill       office -> 405-291-1990 -> ..texbell!oktext!mktco
Mgr - Mktg.(SWBTCo) home -> 405-843-4464 -> ..texbell!oktext!frodo!david