Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!indetech!fiver!palowoda
From: palowoda@fiver.UUCP (Bob Palowoda)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Fun with 386SX BUGS
Message-ID: <998@fiver.UUCP>
Date: 17 Feb 90 08:38:41 GMT
References: <29194@amdcad.AMD.COM>
Organization: Fiver Communications  Fremont, Ca
Lines: 29

From article <29194@amdcad.AMD.COM>, by phil@pepsi.amd.com (Phil Ngai):
> 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.
  
   Remember this is a 386SX. I have ran win386 on a real 386 machine 
(Everex Step) and it works fine. The speed was disappointing but
it ran and didn't crash. Reminds me of the old Osborne machine and
bankswitching memory. What a nightmare. 
  
> Do you have any of your 2 meg as EMS? You shouldn't, I think.

   No, it's configured as extended. I tried it both ways. Another strange
thing that bothers me is if you turn the bit to enable 'external ems control'
the system hangs on a cold boot.  But I don't use this anyway.
 
 ---Bob

 
-- 
Bob Palowoda  pacbell!indetech!palowoda    *Home of Fiver BBS*  login: bbs
Home {sun|daisy}!ys2!fiver!palowoda         (415)-623-8809 1200/2400
Work {sun|pyramid|decwrl}!megatest!palowoda (415)-623-8806 2400/9600/19200 TB
Voice: (415)-623-7495                        Public access UNIX XBBS