D
Dan
Validate Product Key against i386
Disclaimer: It's hard to pose this question without sounding like
someone trying to scam the xp validation scheme, but here goes.
I'm working on a friends computer and it's fairly riddled with viruses.
It's an OEM system, so there is no XP CD. I've been able to build up
a bootable CD from the i386 directory that the OEM left in a recovery
folder. I'm about to do a system repair (boot CD, enter to enter setup
and not recovery console, highlight partition and hit 'R' for repair),
when it dawns on me that I need his product key. I bit searching finds
it stickered to the back on an MS hologram. Being paranoid, I checked
it against the key that the current copy was licensed with, and turns
out they are different. This isn't a big surprise since the oem
probably installed from an image.
So now, I need to figure out (before I start setup) if either of these
product keys match the i386 folder in the recovery directory. If they
don't match, I get half way through setup and can't get the product key
to recognize in setup. This would destroy the repair process and I
would have to resort to fdisk-format-reinstall. I'm hoping to keep all
his application settings and data (hence the choice of the repair
path).
Thoughts on a LEGAL way to do this without violating the terms of the
MS license.
-Dan
Disclaimer: It's hard to pose this question without sounding like
someone trying to scam the xp validation scheme, but here goes.
I'm working on a friends computer and it's fairly riddled with viruses.
It's an OEM system, so there is no XP CD. I've been able to build up
a bootable CD from the i386 directory that the OEM left in a recovery
folder. I'm about to do a system repair (boot CD, enter to enter setup
and not recovery console, highlight partition and hit 'R' for repair),
when it dawns on me that I need his product key. I bit searching finds
it stickered to the back on an MS hologram. Being paranoid, I checked
it against the key that the current copy was licensed with, and turns
out they are different. This isn't a big surprise since the oem
probably installed from an image.
So now, I need to figure out (before I start setup) if either of these
product keys match the i386 folder in the recovery directory. If they
don't match, I get half way through setup and can't get the product key
to recognize in setup. This would destroy the repair process and I
would have to resort to fdisk-format-reinstall. I'm hoping to keep all
his application settings and data (hence the choice of the repair
path).
Thoughts on a LEGAL way to do this without violating the terms of the
MS license.
-Dan