Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ncar!csn!boulder!daemon
From: pjones@cisco.com (Patrick Jones)
Newsgroups: comp.dcom.sys.cisco
Subject: Ultimate weird Novell IPX bug and cisco routers: save your sanity!
Message-ID: <33436@boulder.Colorado.EDU>
Date: 19 Mar 91 18:08:14 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 21

I ran into a similar, but not debugged to your level, problem
with XMSnet3(4) at another customer site.  Things looked fine
with bridges and Novell routers but not our gear.  As it
turned out, XMS requires some extended memory mangaement tools
for it to work, as, the way I understand it, XMS is extended
memory but not a manger of memory.

In this situation, the customer was using QEMM versions A and B
(sorry - no numbers).  Version A, the earlier version, worked
just fine.  B, however, which is the latest, had a bug where it
was trashing packets.  This was difficult to trace as well as it
looked like a cisco - XMS interoperability problem.  Then, when a
user finally said, "Oh, but I am running version B of QEMM", 
further tests were made and the bug found.  The customer contacted
QEMM.  I do not know the outcome of that conversation.  Hope it
helps.

regards

patrick
cisco Customer Engineering