• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 670
  • Last Modified:

Win 98 installation problem .Error : Unable to control A20 line ??

Hi

I had my pc running Windows NT 4.0. I had the pc formatted as I wanted to install Windows 98 and therefore the PC had to be formatted in FAT thus overwriting the NTFS format. Though the formatting did take place smoothly, Windows 98 managed to run the setup program almost 80 % installing all the necessary files and also showed the startup screen at first attempt, however it gave an error saying

"ERROR: Unable to control A20 line ! XMS Driver not installed.... and furthur Himem,sys is missing.Windows has stopped."

Though himem.sys is in place, I feel the problem is somewhere else. I formatted the 8 GB hard disk twice to confirm but .. still the same problem.

Please help... this matter is urgent

Regards,
KC



0
explorer007
Asked:
explorer007
1 Solution
 
mklpCommented:
explorer007,
     Whose BIOS is it? Can you describe exactly the procedure used to format it and which version of fdisk and format were used?
mklp
0
 
jjeff1Commented:
I have seen this problem once before, but I cannot recall the exact problem.

Some older BIOSes have an option to control the A20 line. Try changing that setting to see if it will help.

Also, do you simply have a corrupt copy of himem.sys?

Jeff
0
 
tonnybrandtCommented:
I have seen this problem on older compaq computers. Usually the errors disappeared when we switched the computer off and let it sit there for a while. I did try to mingle with the control A20 line in the compaq bios, but was not successfull.
Did some research at the time and the Himem.sys error is directly linked to the A20 error. Solve the A20 error and you automatically solves the Himem.sys error.
Some more exact information and maybe the answer here:
http://support.microsoft.com/support/kb/articles/q73/7/13.asp
Good luck
0
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 
hkmdjCommented:
From Microsoft Knowledge Base -

There are two workarounds for this problem:
 
 - Add the "/M:x" switch to the HIMEM.SYS line in the CONFIG.SYS file, where x is number from the valid range of 1-14 and 16, shut down and then restart your computer. For example:
 
DEVICE=C:\DOS\HIMEM.SYS /M:1
 
NOTE: In Windows 95/98, The Himem.sys file is located in the Windows folder,
not the DOS folder.
 
 NOTE: An incorrect handler may lock or hang the system at boot up. You should
have an MS-DOS version 5.0 bootable floppy disk available to boot from before you experiment with different machine switches.
 
 - Upgrade your machine's BIOS or contact your machine vendor for assistance in modifying your CMOS settings. You may need to disable a FastGate (or similar) option.
 
   For more information, query on the following words in the Microsoft Knowledge Base:
   FAST GATE A20
 
MORE INFORMATION
================
 
The A20 line is the start of the first 64K of extended memory, known as the high memory area (HMA). The HIMEM.SYS device driver must control the A20 line to provide management of extended memory. The error message is reported by
HIMEM.SYS if it incorrectly identifies the extended memory handling mechanism of the computer or if the handling method of the machine's BIOS is unknown.
 
For more information concerning HIMEM.SYS, please refer to the Microsoft MS-DOS version 5.0 "User's Guide and Reference" and to the README.TXT file.
 
If you are using MS-DOS 6.x, type "help himem.sys" at the MS-DOS command prompt,
and then press ENTER.
Norton Utilities or Norton AntiVirus Installed
----------------------------------------------
 
This behavior may also occur if you have Norton Utilities or Norton AntiVirus installed. For additional information, please see the following Symantec Web site:
 
   http://service1.symantec.com/SUPPORT/nav.nsf/335b6917c8364f40852565d3005cec4e/fb02cc471900e83a852566c200721864?OpenDocument
 
The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Microsoft in no way guarantees the accuracy of this third-party contact information.
 
The third-party products discussed here are manufactured by vendors independent
of Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.


-----------

I hope this helps!

David Johnson
http://davidj.org/
0
 
tonnybrandtCommented:
hkmdi:
You can't post other experts comments as your answer. Look at the comment right above your answer. It points to the same file that you have posted.
Kindly withdraw your answer.
Tonny
0
 
hkmdjCommented:
My apologies.
0
 
SysExpertCommented:
Unless this computer is really old, you may have a hardware problem or RAM problem. In anycase please provide details on the hardware you are using. Computer type, motherboard, BIOS, Hard drive, and VGA card.
In any case I would make sure you have the newest BIOS installed.
Also clean the CD-ROM drive. Maybe a corrupted himem,sys is being transferred due to a bad CD-ROM.
Have you tried copying the win98 dir to the hard disk and then installing ?
I hope this helps.
0
 
bkostermCommented:
What does FDISK tell you?  Sounds like there might be remnants of the NTFS affecting the install.
You did not mention whether you used FDISK first before the format.  So my advice would be to start over and FDISK first.
0
 
tonnybrandtCommented:
explorer007:
I refer to my previous comment.
I submit this as an answer, because you have not respondet in 15 days.
You should reject this answer, if you didn't use my comment to solve your problem.

Tonny
0
 
tonnybrandtCommented:
explorer007:
                    I refer to my previous comment.
                    I submit this as an answer, because you have not respondet in 15 days.
                    You should reject this answer, if you didn't use my comment to solve your problem.

                    Tonny
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now