Xref: utzoo comp.os.msdos.programmer:5999 comp.os.msdos.apps:2370
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!caen!spool.mu.edu!snorkelwacker.mit.edu!linus!linus!mwunix.mitre.org!jcmorris
From: jcmorris@mwunix.mitre.org (Joe Morris)
Newsgroups: comp.os.msdos.programmer,comp.os.msdos.apps
Subject: Re: HIMEM.SYS problem on 486 machine.
Message-ID: <jcmorris.678059933@mwunix.mitre.org>
Date: 27 Jun 91 21:58:53 GMT
Article-I.D.: mwunix.jcmorris.678059933
References: <1991Jun27.202435.16001@magnus.acs.ohio-state.edu>
Sender: news@linus.mitre.org (News Service)
Distribution: usa
Organization: The MITRE Corporation, Bedford MA
Lines: 26
Nntp-Posting-Host: mwunix.mitre.org

slahiri@magnus.acs.ohio-state.edu (Santanu Lahiri) writes:

>Hi Folks,

>Next, heady with the success of an easy (well, relatively) installation,
>I offered to help a friend install his 5.0 on his 486 machine.  This monster
>sported a 220M drive, and 8M memory, so I figured "No Problem."

>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

What type of system is this '486 with the problems?  Some configurations
can't be reliably detected by HIMEM's code and you have to tell it which
platform it's running on.

Section 2.15 of README.TXT describes this procedure.

You may have a machine which isn't listed there but still requires some TLC.
Try calling Microsoft; they may know a special switch required by your system.
(Or if you post it to the net maybe someone else will know the magic 
incantation.)

Joe