Azure Jane Lunatic (Azz) 🌺 (
azurelunatic) wrote2002-07-28 10:52 pm
this did *not* just happen.
My error message upon startup was this: "Missing or corrupt: \winnt\system32\drivers\isapnp.sys", and it told me I could repair the installation from the recovery console.
Upon hitting the product recovery CD, starting from it, however, I got the message that "filesetupdd.sys could not be loaded. The error code is 4. Cannot continue. Press any key to exit."
Exiting, of course, would start one into the missing or corrupt file error.
I managed to start her in safe mode, and called Dell. The nice guy on the other end of the phone sounded like he had a clue, and sounded happy to be talking to someone who was at least clueful enough to be writing down the problems.
We searched for the appropriate file on the w2k CD, but found no such thing. The Dell guy looked up the problem on the Microsoft website, but surprise of all surprises, the page wouldn't load for him! Naturally, lacking a cordless phone, this meant a bit of juggling around of cords and going and hanging up the red phone in my room. I kicked Votania off Enki, telling her that actually, this guy wasn't a Bastard Operator from Dell, he was a nice one.
The tech support guy told me, based on what was in the article, that we should replace said file. Only because evidently I'd installed a service pack at some point or other, my original product recovery CD might not work; the only way to fix that was to either remove the service pack so the original filesetupdd.sys would be current, or use an up-to-date w2k CD, like the one I'd gotten from DeVry.
I ran back to Tigereye to try starting in safe mode and attempting to follow some of the instructions in the Microsoft article. The phone hung up on the nice Dell guy, unfortunately. I made noises, then realized that Safe Mode with Command Prompt was not what I wanted. Enki closed my browser page with the article while I was away from him, when I went back to check my details. No one had touched him. Fortunately, I had written down the number, so it was only a few moments' work to look it up again. I set Tigereye to restart, and then had an inspiration.
Instead of attempting to expand isapnp.sy_ from the product recovery CD, I could just go and find an already expanded, working copy, on another machine running Windows 2000.
I had already backed up the current file of
ectogenesis when I discovered that Tigereye would start in safe mode; I was not worried about fucking up my computer.
ectogenesis is my only important file.
Enki is running Windows 2000 Professional.
I went over to Enki, floppy in hand, to get the file, found it, and copied it to floppy.
I returned to Tigereye.
I saw the "Login as administrator?" dialog box, the same one I saw every day logging in. I entered the password, then thought about the implications as I heard the "Microsoft sound" play.
It wasn't starting in safe mode. Tigereye was working again, for whatever unknown, unknowable reason.
Upon hitting the product recovery CD, starting from it, however, I got the message that "filesetupdd.sys could not be loaded. The error code is 4. Cannot continue. Press any key to exit."
Exiting, of course, would start one into the missing or corrupt file error.
I managed to start her in safe mode, and called Dell. The nice guy on the other end of the phone sounded like he had a clue, and sounded happy to be talking to someone who was at least clueful enough to be writing down the problems.
We searched for the appropriate file on the w2k CD, but found no such thing. The Dell guy looked up the problem on the Microsoft website, but surprise of all surprises, the page wouldn't load for him! Naturally, lacking a cordless phone, this meant a bit of juggling around of cords and going and hanging up the red phone in my room. I kicked Votania off Enki, telling her that actually, this guy wasn't a Bastard Operator from Dell, he was a nice one.
The tech support guy told me, based on what was in the article, that we should replace said file. Only because evidently I'd installed a service pack at some point or other, my original product recovery CD might not work; the only way to fix that was to either remove the service pack so the original filesetupdd.sys would be current, or use an up-to-date w2k CD, like the one I'd gotten from DeVry.
I ran back to Tigereye to try starting in safe mode and attempting to follow some of the instructions in the Microsoft article. The phone hung up on the nice Dell guy, unfortunately. I made noises, then realized that Safe Mode with Command Prompt was not what I wanted. Enki closed my browser page with the article while I was away from him, when I went back to check my details. No one had touched him. Fortunately, I had written down the number, so it was only a few moments' work to look it up again. I set Tigereye to restart, and then had an inspiration.
Instead of attempting to expand isapnp.sy_ from the product recovery CD, I could just go and find an already expanded, working copy, on another machine running Windows 2000.
I had already backed up the current file of
Enki is running Windows 2000 Professional.
I went over to Enki, floppy in hand, to get the file, found it, and copied it to floppy.
I returned to Tigereye.
I saw the "Login as administrator?" dialog box, the same one I saw every day logging in. I entered the password, then thought about the implications as I heard the "Microsoft sound" play.
It wasn't starting in safe mode. Tigereye was working again, for whatever unknown, unknowable reason.
