Service Pack 2 (sp2) woes.

[wef]

Okay, I managed to botch the first installation of service pack 2 with
the typical atapi.sys problem because of a program called Daemon
Tools. After I uninstalled this program, I found out that a typical
solution to get beyond the problem was to rename the file.
Unfortunately, I aborted the install by choosing not to continue so I
could reboot and try again later. This caused a lot of problems
mostly with crashes and detection of new hardware that didn't exist.
I finally managed to figure out that I had to boot into safe mode and
then click "no" so I could do a system restore back to the point
before I started applying service pack 2. Hopefully this will be a
solution to others who have similar problems with install sp2 and want
to back out for whatever reason.

However, I have a new problem now. When I boot up and login, I still
get the message that windows is searching for drivers for new
hardware. I have to click cancel three times as the dialogue box
appears three times before I can use my system normally. When I go
into Control Panel and then device manager, I see eight unknown
devices. Clicking on properties shows in the details tab that all
eight are related to either root\legacy_fastfat or
root\legacy_navex15. Looking in my registry, I see bogus looking
entries for each of these that look like this:

location:

My Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_NAVEX15

example subfolders:

$%&'(
$%&'()

etc...the characters keep building up one character at a time for a
while. The entry for fastfat looks similar. When I try to delete
this key or any of the weird subkeys, I get the error message "error
while deleting key". Attempts to rename to key give me "error while
renaming key". I am wondering if there is any way I can edit the
registry in other ways to get rid of garbage that regedit won't allow
me to remove. Most of the other "legacy_" keys only contain one
subfolder except for these two entries. Any help on this would be
greatly appreciated. I suppose I could either back out to service
pack 1 and have less security or continue to click cancel three times
until I upgrade my hardware and reload everything. But I'd appreciate
any input so I'm not counting down the days to when I reinstall
Windows XP and take this as a "lessons learned".

 

[Frankster]

Check with "root" in this newsgroup. He will tell you that there is nothing
wrong with SP2. It's all your fault! LOL.

 

[root]

Check with "root" in this newsgroup. He will tell you that there is nothing
wrong with SP2. It's all your fault! LOL.

This NG distills the 1 in 1000 that have a problem. Of those it's mostly a
minor problem. All the rest never even come here. A few sysadmin regulars
have reported things like 50 installed with no problem or one minor fix.

 

[Rock]

Check with "root" in this newsgroup. He will tell you that there is nothing
wrong with SP2. It's all your fault! LOL.

In fact it was the OP's fault, but I'm not trashing on him. He had
Deamon tools installed which interfered with the installation, then he
backed out of it the wrong way. There will be problems with some
installations, no way around that, but your suggestion, waiting for
weeks, will somehow change things, shows no understanding. People are
still having problems installing unpatched XP to a system, or SP1 and
now SP2. In fact the roll out has been very smooth.

 

[root]

People are
still having problems installing unpatched XP to a system, or SP1 and
now SP2. In fact the roll out has been very smooth.