Xref: utzoo comp.os.msdos.programmer:6000 comp.os.msdos.apps:2371
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!sdd.hp.com!think.com!yale.edu!cmcl2!panix!schuster
From: schuster@panix.uucp (Michael Schuster)
Newsgroups: comp.os.msdos.programmer,comp.os.msdos.apps
Subject: Re: HIMEM.SYS problem on 486 machine.
Message-ID: <1991Jun28.010441.25454@panix.uucp>
Date: 28 Jun 91 01:04:41 GMT
References: <1991Jun27.202435.16001@magnus.acs.ohio-state.edu>
Distribution: usa
Organization: PANIX - Public Access Unix Systems of NY
Lines: 22

In article <1991Jun27.202435.16001@magnus.acs.ohio-state.edu> slahiri@magnus.acs.ohio-state.edu (Santanu Lahiri) writes:
>
>Wrong.  The Setup Program ran without a hitch.  However, on rebooting,
>the first message I get is
>
>       HIMEM.SYS Extended Memory Manager  (or some signature)
>       Cannot control A20 address line, aborting
>

HIMEM.SYS has got to be the most finicky device driver I've ever seen.
It uses a different strategy to control the A20 line on many different
types of machines, and "guesses" incorrectly on a lot of clones.
How QEMM386 and 386^MAX do it so transparently is beyond me.
Try playing with the /MACHINE:n (n ranges from 1-17 or so) command
line switch (it's documented in the README file) until you find
the right one.


-- 
                Mike Schuster                      |   -CIS: 70346,1745
-NY Public Access UNIX:  schuster@panix.com        |   -MCI Mail, GENIE:
-The Portal (R) System:  schuster@cup.portal.com   |           MSCHUSTER