Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!stat!kerce From: kerce@nu.cs.fsu.edu (Kingsley F. Kerce) Newsgroups: comp.windows.ms Subject: HIMEM.SYS woes Message-ID: Date: 5 Jul 90 23:21:26 GMT Sender: news@stat.fsu.edu Distribution: comp.windows.ms Organization: Florida State University Computer Science Lines: 23 After finishing the MS Windows 3.0 installation, I anxiously rebooted but found that the HIMEM.SYS device doesn't like my extended memory. I would greatly appreciate any suggestions. Specifically, HIMEM is the first line of CONFIG.SYS and it complains something about A20 hardware. Following that, drivers and other software that require expanded memory complain about memory not being there. Starting Windows results in the machine doing a cold boot i.e. the power on tests (POSTs) commence. Hardware: Gateway 2000 386/20 ordered around March 1989 Motherboard is 386 Gene II by Hawk Computers 4 MB memory is located on a 8 MB 32 bit daughterboard The memory has worked great with Quarterdeck's QEMM-386 for 10 or so months. (I'd rather not wait for the newest Windows-compatible QEMM.) Has anyone experienced this behavior? Thanks in advance, -- Kingsley Kerce USnail: Dept. of Computer Sci. (or Dept. of Psych.) Email: kerce@nu.cs.fsu.edu Florida State University Work Phone: (904) 644-5436 Tallahassee, FL 32306