Can "orphaned" registry keys be deleted? (sysprep related)

[Steve Maser]

I'm having a specific problem when I try to move a sysprepped XP SP2
created on an Intel machine to an AMD machine.

Microsoft references this here:

http://support.microsoft.com/kb/888372

Their resolution works -- if I could boot the system in "safe" mode.

But if I run the "mini-setup" part of sysprep, I can't get into Safe
mode.


So, I'm wondering if I could safely *purge* the entire key on my Intel
machine before sysprepping it.


Does Microsoft defined "orphaned" as a left-over key that's no longer
used by *anything*? Or is it only "orphaned" when noticed by my AMD
machine, but would still be seen by my Intel machine if I removed it?


Thanks!

- Steve

 

[Adam Leinss]

Does Microsoft defined "orphaned" as a left-over key that's no
longer used by *anything*? Or is it only "orphaned" when noticed
by my AMD machine, but would still be seen by my Intel machine if
I removed it?

From a quick lookup, it appears Windows XP uses processr.sys or
amdk7.sys if you are using an AMD processor and Intelppm.sys if you are
using an Intel one. It appears it has something to do with the power
management features of the CPU. If you don't plan to use this on Intel
hardware anymore, I don't see why you cannot get rid of the key.

You'll likely have to create two images: one for Intel hardware and one
for AMD hardware. BTW, is there not a way to standardize all your
hardware to one CPU platform?

Adam

 

[Steve Maser]

You'll likely have to create two images: one for Intel hardware and one
for AMD hardware. BTW, is there not a way to standardize all your
hardware to one CPU platform?

Adam

Hah.

No.

I work in a University. Faculty members buy whatever they want.

Surprisingly, though, this was the first AMD machine we've tried to put
our sysprepped XP loadset on in the 3+ years we've had this loadset.


Rather than doing this:

2.
Click Start, click Run, type regedit, and then click OK.
3.
Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Intelppm
4.
In the right pane, right-click the Start entry, and then click Modify.
5.
In the Value data box, type 4, and then click OK.


I just tried *removing* the "Start" entry entirely (as it's "orphaned"
as MS defines it) -- rather than deleting the whole key.

This did not affect the boot/mini-setup of my Intel boxes and
completely bypassed the BSOD I was getting on the AMD laptop.


I'm hoping that "orphaned" means that it's a key that's completely
ignored. If so, this is now a non-issue.


I'm willing to be convinced otherwise that it was a bad idea to delete
this key entry, though...

- Steve

 

[aleinss]

This did not affect the boot/mini-setup of my Intel boxes and
completely bypassed the BSOD I was getting on the AMD laptop.

I'm guessing then that the only "problem" you might see is on laptops.
Newer ones "clock down" to save battery life. That's probably what
intelppm.sys is used for. See
http://support.microsoft.com/?kbid=832885.

Adam

 

[Steve Maser]

I'm guessing then that the only "problem" you might see is on laptops.
Newer ones "clock down" to save battery life. That's probably what
intelppm.sys is used for. See
http://support.microsoft.com/?kbid=832885.

Adam

Possibly. All I ended up removing was the "Start" entry of that key.

I'll have to keep an eye on it.

- Steve