Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!brutus.cs.uiuc.edu!wuarchive!texbell!texsun!newstop!sun!amdcad!pepsi!phil
From: phil@pepsi.amd.com (Phil Ngai)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Fun with 386SX BUGS
Message-ID: <29194@amdcad.AMD.COM>
Date: 16 Feb 90 03:15:30 GMT
References: <995@fiver.UUCP>
Sender: news@amdcad.AMD.COM
Reply-To: phil@pepsi.AMD.COM (Phil Ngai)
Organization: Advanced Micro Devices, Inc. Sunnyvale CA
Lines: 17

In article <995@fiver.UUCP> palowoda@fiver.UUCP (Bob Palowoda) writes:
| When starting up MS windows "win386" program the init sequence crashes.
|When it does crash you can see some ascii text on the screen along with
|binary trash that says "Microsoft EMSXXX.0 " and then it drops to dos.

Funny, I just saw an ad bragging about how compatible their
(not dataexpert) 386 was and how good it ran win386. I dismissed
it as baloney. Perhaps there really is something to it.

Do you have any of your 2 meg as EMS? You shouldn't, I think.

Did you know that MS uses Win286 on 386^Max? I wonder why.


--
Phil Ngai, phil@amd.com		{uunet,decwrl,ucbvax}!amdcad!phil
When guns are outlawed, only governments will have guns.