tenthman
Topic Starter
Hello…I'm having a little difficulty using my floppy drive. I downloaded a program called ERUNT which lets me easily backup my entire Registry into a folder as well as onto a handy little USB flash drive. I wanted to do this because now I can turn off System Restore (I only have an 8 gig hard drive).
One of the ways to restore a corrupted registry using ERUNT is to boot into DOS and run the executable from there (you'd do it this way if you absolutely can't get your computer to boot into windows at all). Well, in as many words as possible, while trying to create a DOS boot disk, my computer shuts down with the BSOD and the error message is pointing towards a file called "fltmgr.sys". It's some sort of file manger program.
I have four copies of it on my computer…all are in the WINDOWS directory:
C:\WINDOWS\system32\drivers
C:\WINDOWS\ServicePackFiles\i386
C:\WINDOWS\$hf_mig$\KB914882\SP2QFE
C:\WINDOWS\$hf_mig$\KB922582\SP2QFE
The two highlighted in orange text were installed this past Tuesday as one of Microsoft's monthly Windows Updates.
I don't know if this problem existed before the Updates as I hardly ever use my floppy disks anymore. Of the two fltmgr.sys files downloaded during the Updates, I tried taking the older of the two and re-named with an .old extension to see if that would clear it up, and it didn't.
I was recently having a problem with an old anti-virus program file, so I ditched that AV program and got a free one instead. I no longer get the BSOD because of that file because it's gone…I wonder if the problem has just shifted to this file instead? Do you think my computer is getting ready to pack it in? The computer is about 5 years old. Or has anyone ever heard of this before? Is it possible to just delete those last two Update files and have everything be ok, or what?
Ok…hope someone can help…otherwise I'll probably start having to look for another box. I think I'm going to try a Mac this time tho.
One of the ways to restore a corrupted registry using ERUNT is to boot into DOS and run the executable from there (you'd do it this way if you absolutely can't get your computer to boot into windows at all). Well, in as many words as possible, while trying to create a DOS boot disk, my computer shuts down with the BSOD and the error message is pointing towards a file called "fltmgr.sys". It's some sort of file manger program.
I have four copies of it on my computer…all are in the WINDOWS directory:
C:\WINDOWS\system32\drivers
C:\WINDOWS\ServicePackFiles\i386
C:\WINDOWS\$hf_mig$\KB914882\SP2QFE
C:\WINDOWS\$hf_mig$\KB922582\SP2QFE
The two highlighted in orange text were installed this past Tuesday as one of Microsoft's monthly Windows Updates.
I don't know if this problem existed before the Updates as I hardly ever use my floppy disks anymore. Of the two fltmgr.sys files downloaded during the Updates, I tried taking the older of the two and re-named with an .old extension to see if that would clear it up, and it didn't.
I was recently having a problem with an old anti-virus program file, so I ditched that AV program and got a free one instead. I no longer get the BSOD because of that file because it's gone…I wonder if the problem has just shifted to this file instead? Do you think my computer is getting ready to pack it in? The computer is about 5 years old. Or has anyone ever heard of this before? Is it possible to just delete those last two Update files and have everything be ok, or what?
Ok…hope someone can help…otherwise I'll probably start having to look for another box. I think I'm going to try a Mac this time tho.