Himem.sys

[Tech2D2]

Hi All

Here is my Question:

When I start my computer it is telling me that the HIMEM.SYS is missing or corrupt- it advises to select the command prompt only and run scanreg - when i type that at the command prompt it says bad command or file name

Can I do a SYS C: from the A: Prompt using a 98 Boot disk and solve my problem or do i have to reinstall w98

Thanks in advance for yor assistance

[deseqer]

sounds like a bad memory module. try replace the memory and see if that error dispear.

[deseqer]

http://www.goldmemory.cz/

This is a good utily to kept on hand.

[NooNoo]

Sys C: will make the drive bootable again, but will not put back himem.sys.

Try changing directory to c:\windows\command then type scanreg /restore

[Penman]

I know I'm stating the obvious but have you tried a manual copy of the file from a Windows 98 boot disk to your c:\windows directory and overwriting any himem.sys that's already there?

[Garak]

try this, i had a simular problem about a year back

here (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296636)

also, after i fixed that problem i got another error heres the fix for that too incase you get that.


here (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q73713)

[edball]

If it was a problem with your system files, you would never get to that message. It may be a path problem or a problem with the himem.sys file itself. I don't think it is anything scanreg will help because it would load himem.sys before the registry. You might try scandisk c: , you will have to change into the directory scandisk is in or it won't find it.

[King Grover]

I agree with the above.


It is most likely related to a path problem with himem.sys in the path missing or something along those lines.

I have, in the past, simply copied the himem.sys file from one working PC to another and had no problems.

Maybe look in your sysedit and see if there's anything that looks messed up. But be careful in there. things can get ugly fast

g'luck

[Orangeman]

If the above solutions don't work try putting a semi-colon in the beginning of the line in MSCONFIG that includes your Himem.sys. Doing this 'troubleshoots' it and sometimes corrects the problem.

Good Luck,
Orangeman

[silencio]

Look in your config.sys file for the reference to himem.sys. Place a copy of himem.sys from from your exact version of windows in the directory it mentions. If it doesn't mention a directory drop it in the root c:\

Orangeman, isn't it the msdos.sys file that contains a copy of himem.sys?

Concerning scanreg, open your autoexec.bat file and look for a path statement. Make sure the path statement includes the directories c:\windows and c:\windows\system ..if memory serves me correctly c:\windows\command is also handy to have in your path.

[Orangeman]

'Orangeman, isn't it the msdos.sys file that contains a copy of himem.sys?'


Hi, I just looked in my MSDOS.Sys and it wasn't there. (That doesn't mean that it shouldn't be there.)

What I as referring to in my advice was to type "msconfig' in the Start>Run menu and click OK. The click Config.sys, then look for the line that contains Himem.sys, then highlight the line, the click EDIT Then add a semi-colon in fhte very front of the line. The click OK, Save then restart.

MAKE A BACKUP COPY BEFORE YOU DO THIS BY CLICKING THE GENERAL TAB, THE CLICK 'MAKE BACKUP'

[silencio]

Originally posted by Orangeman
'Orangeman, isn't it the msdos.sys file that contains a copy of himem.sys?'


Hi, I just looked in my MSDOS.Sys and it wasn't there. (That doesn't mean that it shouldn't be there.)

Hehe. No, I mean that either command.com or msdos.sys has a copy of himem.sys built into the com or sys file. I think this started with win95 but it could have been 98.