Re: Stolen Legitimate XP pro disk.



On Mon, 25 Jun 2007 07:21:01 -0700, nucklebone

My disk was unfortunately nicked. Is there a way to make a recovery disk

For some OEM installations, maybe - tho it will typically be a more
destructive installation tool than a real generic OS disk.

Else, prolly no. Look for an \i386 file set.

find the product key from my computer?

I use Nirsoft's ProduKey tool from www.nirsoft.net, i.e.

http://www.nirsoft.net/utils/product_cd_key_viewer.html

As time progresses and you upgrade your components on the
computer, it is better to re-format your hard drive

False, though it is debatable (and often debated).

If you have the usual useless duhfault out-the-box installed state,
you have nothing to lose but your patches. The more work you put into
improving your install, the less keen you will be on "just" formatting
and starting over. A new motherboard may require a "repair install",
which needs a bootable OS disk (dunno if a raw \i386 can be enough);
any other hardware change should not require even that.

Even so, you should always have an installation disk, and a
custom-installable one at that (so that you can do things like
Recovery Console boot, repair install, etc.). Large OEMs deny users
these tools, yet MS still considers their crippled OS "recovery" disk
(or lack of any disks at all) as "Genuine Advantage".

Makes you drink, doesn't it?

(so i have been told), how can this be done without having to buy another
disk?

Find an exact matching disk and clone it, or order a replacement disk
(no license, just the disk, should be cheap) from MS or your OEM.

By "matching", I mean:
- same edition, i.e. Starter / Home / Media Center / Pro
- same code base, i.e. 32-bit / 64-bit
- same license, i.e. retail / upgrade / royalty-OEM / OEM / etc.
- (same SP level)

Actually, "same SP level" isn't a biggie, as there won't be a product
key issue across SP versions AFAIK (as there will be across editions
and license types). But if HD > 137G, the SP level must be at least
SP1, ideally SP2; "Gold" (SP0) is unsafe for installation or use over
137G, and SP1 is not 100% safe to use > 137G (OK to install).



------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
------------ ----- ---- --- -- - - - -
.



Relevant Pages

  • Re: OEM and Standard windows - What are the differences?
    ... for most OEM`s I think the best course would be to create a totally new disk with the customer/friends own OEM bundled recovery disk. ... installation media, it is not the source media itself but the license that is the clincher, if they have a license to use the software who gives a rip where the software is installed from? ... we can legally install Windows or other MS products from a network location or we can restore an OS from any number of backup facilities available. ...
    (microsoft.public.windowsxp.general)
  • Re: OEM XP Reinstall
    ... PK doesn't work with your disk -- it belongs to the volume license, ... System Properties shows Win XP HOME OEM and the OEM type key. ... So, it isn't/wasn't an Upgrade, it was a dual-boot. ... and I also ran Belarc Advisor which got the install key ...
    (microsoft.public.windowsxp.general)
  • Re: Cannot boot to Safe Mode or otherwise.
    ... It sounds like I'll be able to make a disk that will work. ... You can also either boot off a rescue CD ... But you might still need to perform a Clean Install in the end. ... But you can also create an installation CD for him (and make it an OEM ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: OEM Licence woe (again)
    ... > preinstalled, service pack 2 + hotfixes, OEM Home Windows XP disk to ... > repair a clients PC with. ... > XP OEM install with my clients serial number to repair his/her PC. ... > windows install disk and the PC. ...
    (microsoft.public.windowsxp.general)
  • Re: Upgrades and OEM
    ... new disk, I installed XP using the old disk (another OEM XP disk) ... remnants of an old install to screw up a new install. ... OR simply change the product key on the computer to the valid one that came ...
    (microsoft.public.windowsxp.setup_deployment)