Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
My computer says its HIMEM.SYS file is missing. How do I replace it?
This message came up while I was trying to undo some damage I caused my computer -- tried to delete malware and unnecessary files while not really knowing what I was doing. The computer shuts itself down when I try to start it up.
Through the help of some good folks here on this board, I've successfully replaced the wininit.exe file -- one which I knew I'd deleted by mistake. But then when I tried to reboot, I learned this other file is missing also.
I searched the site for this problem (himem.sys) but the messages were so old that I thought I'd better post a new one.
My post on the initial problem is titled "shuts down during startup."
Thanks for any help!
It's better to reference a previous post by number rather than title:
Himem.sys is missing or Corrupted
Is it really missing? Try entering:
dir c:\windows\himem.sys
Drop the last year into the silent limbo of the past. Let it go, for it was imperfect, and thank God that it can go.
0 
Ah! Sorry about that. I'll use the number next time.
Good tip about checking the directory. It is indeed listed there, at 33,191 bytes. So why does it give me the message that it is missing? I'm baffled.
Btw, I like your signature. More good advice, especially at this time of year. :-)
Rhonda
0
No problem, it's just hard to keep track of messages without the numbering system.
Well, it may be that even though the file exists, it's become corrupted (although the file size appears to be correct) - you could try extracting a fresh copy from your CD or copy it from another machine or bootdisk with Win98.
Some more on the subject here
Ah, yes - the quote is by the late Times theatre critic Brooks Atkinson, and seemed appropriate
Drop the last year into the silent limbo of the past. Let it go, for it was imperfect, and thank God that it can go.
0
Aha, just found you again (I just posted on your previous link).
We have the same OS so I can send you any old "original" file you like. Shout if you want to try himem.sys which is original.
Have doubts though because normally when a file is corrupted it will usually at least cause one byte to be added or subtracted. You may be the exception though.
On the previous link I mentioned Windows overlay in passing. Probably best leave that on the back burner for now, to use if we are forced into it.
Still rather suspect some malware or virus is lurking but I might be wrong.
Have you a W98SE CD?
Derek.W
0
No CD limits us a bit.
I'll send file, nothing lost by trying but I rather doubt it is the problem somehow.
Derek.W
0
Hi Derek!
Yes, I think you're right -- something else must be at play here. I copied to floppy the himem.sys file you sent and used it to overwrite whatever elusive form of himem.sys file that was hiding in there.
Once more, I got the message "file is missing. Make sure it is in your windows directory." ::sigh::
In case one problem could be as simple as I am... After overwriting the file and getting the c: prompt again, I then typed "win" to restart. Is that at least correct?
Thanks so much for your help.
0
Derek!
Part of the problem WAS as simple as I am. I wondered, "Hmmmm, maybe I should just restart it and see..."
Two ctr-alt-deletes later, I am posting from my very own computer!
Only hitch is that I did get the message "A required .DLL file, USERENV.DLL, was not found." Can you help with that?
I'm going to heat up my Adaware as you recommended and see if anything good happens. If my luck doesn't hold out, I'll update you from another computer tomorrow.
A THOUSAND THANKS!!!!
Rhonda
0
The file USERENV.DLL is not usually provided on W98 (W2k/XP file). I happen to have a copy of it so I could send it. More likely it is asking for it for some reason although it is not really required. Sometime malware uses valid file names, so perhaps it was infected and has now been removed.
When you run all your malware/virus stuff if this error persists (and it probably will) then it's a case of finding out what is calling it.
Type msconfig in the Run box and look in the StartUp tab. Examine each line carefully and let me know if you find USERENV.DLL mentioned. You could also look in the Autoexec.bat tab too. If you can't find it then it is probably the registry calling it up. There are other ways of dealing with this but to avoid information overload I'll leave it at that for now.
Derek.W
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
