Xref: utzoo comp.sys.ibm.pc:45178 comp.windows.ms:1619
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!ames!pacbell!indetech!fiver!palowoda
From: palowoda@fiver.UUCP (Bob Palowoda)
Newsgroups: comp.sys.ibm.pc,comp.windows.ms
Subject: 386SX and 386 Windows bug cont
Message-ID: <1006@fiver.UUCP>
Date: 25 Feb 90 07:42:22 GMT
Reply-To: palowoda@fiver.UUCP (Bob Palowoda)
Organization: Fiver Communications, Fremont, Ca
Lines: 30



  About a week ago I posted a message about running 386 version of 
windows on a DataExpert 386SX machine. It appears to be a combination
of hardware and firmware that cause the problem.
 
  C&T Chipset
  Adaptec RLL controller Model 2370T
  AMI Bios 

 I use the onboard controller adpatec bios to format the drive. Also useing
AMI's bios I set the drive type to 47 user defined. Now what appearently
happens is when I try to initialize 'win386' it takes the memory mapped
in by the Bios (somewhere around the controller bios) and gives it over
to windows 386 as Extended memory to convert over to EMS memory. It's 
either that or the AMI Bios is relocateing the Adaptec controller bios.
This is my best guess. I have had previous experience with AMI's bios
incorrectly handleing disk drive controllers.  Other than changeing my
Bios over to Phenoix, or takeing the dealers suggestion like don't use
that disk controller. I there a way to get Windows 386 not to map 
certain regions of memory? Also I would like to hear from anyone else
who has run into this problem and has any workarounds or fixes.

---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