Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!microsoft!t-tomdi
From: t-tomdi@microsoft.UUCP (Thomas DIMITRI)
Newsgroups: comp.os.os2.misc
Subject: Re: Trap 000D on booting OS/2 on 80486 clone please help !!
Message-ID: <56215@microsoft.UUCP>
Date: 31 Jul 90 23:37:14 GMT
References: <6652.26b2c01b@vax1.tcd.ie>
Reply-To: t-tomdi@microsoft.UUCP (Thomas DIMITRI)
Organization: Microsoft Corp., Redmond WA
Lines: 17

In article <6652.26b2c01b@vax1.tcd.ie> doherty@vax1.tcd.ie writes:
>I am installing 3-com 3+open on a no-name clone 80486-24,VGA,colour,8MB,
>,300mb disk (set up as multiple 32mb drives),mouse and 3C503 card.
>The set up involves installing a server adapted version of OS/2 supplied by
>3Com as the first step. This seems to work OK and it tells me to reboot the
>system to bring it up under OS/2 prior to installing 3+Open.

Chances are the problem is with the OS/2 Device Driver 3COM supplied to their
etherlink II card.  To wait for I/O programs typically attempt to flush the
pre-fetch queue by a jmp $+2 (jump to the next line).  The 486 is too smart.
If the jump is within the pre-fetch queue it will not flush the queue and thus
a jmp $+2 is much like a NOP.  The new 3COM Etherlink II device driver for
OS/2 does not have this problem.  Perhaps 3COM will send you an OS/2 device
driver update.  The new device driver is included in LanMan 2.0

Hope that helps!
P.S.  I'm just an intern.