Kenman My First Post !!
Posts: 1
(4/9/02 9:43 pm) Reply
IFSMGR is not managing jack squat
Dunno what did it, but something grabbed my pc by the cojones and ripped it apart.
I used Ad-Aware to remove lots of ad components, and then I went to add/remv programs and removed GoZilla, and at that instant, BAM!!! All hell broke loose...
The first indication was my SFP warnings- I hacked my registry awhile back to turn the SFP warnings on.....(if you don't know, what happens when SystemFileProtection is enabled, it monitors your system files, and anytime a program changes/modifies/deletes a protected system file, it pops up a notification). Well, after removing GoZilla, I had about 15 notifications warn me that "telnet.exe has been modified to version 0.0.0" and "command.com has been modified to version 0.0.0" and so forth......and then it automatically rebooted!
Upon reboot, I get "invalid system disk... please insert disk and hit blah blah" just like if I had a floppy in the A:, but I didn't.
I used ME's restore, going back one day, but that didn't help. I then tried the other 2 points to no avail....
Using a system disk, I get a BSOD right as Win starts loading the registry and then an error concerning IFSHLP.SYS and IFSMGR.SYS, and then, in it's own fancy rhetoric, I get "System Halted." (actual error msg: "While initializing device IFSMGR -- The Microsoft Installable File System Manager cannot find the helper driver. -- Please ensure that IFSHLP.SYS has been installed. System halted.")
I located a SFP log, and it lists all of the files that alerted me to a change....all were from win\command dir......I double checked them, and even re-extracted them, but still no go.
FDISK /MBR (to restore master boot record) ran normally, but didn't help anything.
All DOS files are intact and list correct boot dir's.
All of the documented startup files I should need look to be OK.
Every solution that I could find in the WinKB @ support.microsoft.com has been exhausted.
A scandisk with the surface scan on turned up no HD errors.
So I just try to reinstall ME, and it tells me that setup requires Windows.... STUPID POS, THAT'S WHAT I'M TRYING TO INSTALL!!! Before that it says that I have a compressed drive, which is BS also.
I haven't formatted yet in hopes of saving what's left on that HD.....but going w/o the net, or any pc at home at all, is killing me!
It's now been a week!!! AAAAhhhhhhh!!!!!!!!
My will is fading....
Any help would be appreciated!
I'm fairly competent with computers, but this one is getting the best of me. I don't believe in that "you must reinstall windows" theory, at least not yet. Maybe I'm a hopeless techie...
nfo: WinME, Dell system, EZ-BIOS to boot 2 physical drives, anything else just ask
Re: IFSMGR is not managing jack squat
I'll check the IO.SYS when I get home, not sure offhand.
Yes, when I tried to reinstall Win I started w/the ME disk, and I tried using all 3 options.... start pc w/CD, start pc w/o CD, and minimal.
I even tried to install from win\opts\cabs, win\opts\install, and then off of the ME CD... nopers.
On a side note, I noticed that my backup Win98 cabs (in win\opts\cabs) were renamed with an extension *.cbk, is this normal? The ME cabs in the win\opts\install folder are normal *.cab.
Re: IFSMGR is not managing jack squat
I couldn't find IO.SYS anywhere in C . I searched using all of the avail switches, including /ah, /as, /ar, and /aa.
I went out to the bar last night, and so I didn't have time to do much else trouble-shooting...
Does this sounds suspicious of a virus? ...or of malicious ad-ware?
I ran f-prot and it found a couple of "suspected" virii, but nothing concrete.
wish i had a little more knowledge on the workings of windows o/s so i could provide more help.. but i've been having a similar problem (jacked ifsmgr.vxd) and was wondering if you've by any chance installed any "windows updates" off their update site. there may be subtle differences, but from what i gather win98/Me are pretty close to one another. (currently running 98se, not winMe).. i've reinstalled win several times now, everything seems to work fine...then i use windows update and it causes a bsod when i try to update device drivers. DUN 1.4 upgrade just flat killed my machine. anyway, was just a theory that it may have been caused by a recent update. some say i'm paranoid, but personally i think m$ is intentionally doing all they can to kill older systems in order to force people into their less than wonderful newer versions. best of luck.