K
Kernel
Since the OEM version is 'bios locked' and can not be installed on any other
machine, will it activate automatically if reinstalled in less than 120
days?
machine, will it activate automatically if reinstalled in less than 120
days?
machine, will it activate automatically if reinstalled in less than 120
days?
Thee Chicago Wolf said:OEM doesn't mean BIOS locked. OEM can be a customized OS install CD by
a vendor, an OEM CD you bought from a vendor like Newegg (which you
are only allowed to install on 1 PC, ever), or what Dell does to the
"OEM" CD you got when you bought your system: it will only install on
a Dell. I don't think it will automatically install in 120 days. If
you entered a valid install key, it will continue to work but go into
reduced functionality (nag) mode after a period of time. After which
you'll have to activate via Internet or other methods.
- Thee Chicago Wolf [MVP]
Kernel said:Since the OEM version is 'bios locked' and can not be installed on
any other machine, will it activate automatically if reinstalled in
less than 120 days?
Thee said:OEM can be a customized OS install CD by
a vendor, an OEM CD you bought from a vendor like Newegg (which you
are only allowed to install on 1 PC, ever)
Daave said:Not enough information, Kernel.
Which OEM version? (That little tidbit of info would help tremendously!)
If you are referring to certain branded-OEM versions like Dell that have
Sytem-Locked Preactivation integrated into the CD and matching data
hard-coded to the motherboard's CMOS chip, then yes, you could say your
version is BIOS-locked and you would *never* have to activate XP -- no
matter how many times or how often you install it (since it is
automatically in a perpetually pre-activated state).
Otherwise...
Kernel said:XP Pro OEM Version 2002 Part No. X-14-72249. I installed that one
in a laptop. That CD will not install with any product code except
the one that came with it. I tried to use that CD and the product
code with an OEM CD that had a couple of corrupted files...it
wouldn't accept any of the codes. So I talked to Microsoft and they
replaced the defective CD.
I have other OEM CDs, and they too will only install with the code
that came with the CD. I'm surprised that Cheng Heng was able to mix
up the OEM CDs and product codes. I installed an OEM CD in the new
computer that I built, and would like to wipe it and make a cleaner
installation, but I'm a few weeks shy of the 120 day magic deadline. I
don't care much for trying to insert 50 digits from an automated
female, or talking to employees in India, and Okinawa, who I can
barely understand.
Daave said:If this is a generic-OEM installation, there is no BIOS-locked routine and
you would have to reactivate if you don't wait the full 120 days.
If you want to avoid that scenario in the future, simply create an image
of your hard drive once the OS is installed (actually, you should continue
to create incremental images -- but definitely save your early images!).
Then you won't ever have a need to reinstall XP.
Thee Chicago Wolf said:I used the phrase often used in this newsgroup regarding OEM
versions...'bios locked'. Never cared much for that phrase myself, but used
it to simplify my query. An advanced google search for 'bios locked' in
this newsgroup brought up 1,910 entries; so I guess it's a rather common
term.
Thee said:How does that work? Or, are you not allowed, but still can?
Thee Chicago Wolf said:Since I've always bought retail installs of my CDs and never an OEM, I
can't say with 100% certainty. You are legally tying that OEM install
to that PC only. Even if you uninstall and wipe the HD you can't
install that OEM license to a new system. You can do this (legally)
with a retail copy. Dig around the MS site to see the difference
between an OEM copy and retail if you feel like it.
- Thee Chicago Wolf [MVP]
How does that work? Or, are you not allowed, but still can?
Kernel said:But, always seeking perfection, I like to create a new installation of
the OS to tweak one thing or another. So the only way to have the
best of both worlds is to activate and make the clone right after the
XP Bliss screen appears, and that requires all my programs to be
reinstalled; that won't work for me.
Daave said:And create other images while you're are it:
- Clean Install plus SP3 and all subsequent security patches
- Clean Install plus SP3 and all subsequent security patches
with your customizations
- Clean Install plus SP3 and all subsequent security patches
with your customizations and with all your programs
Keep these image archives in a safe place. Make copies of them
-- hard drive space is cheap these days.
Alias said:MS says you *may* not. The reality is that if you wait 120 days, you can
install a generic XP OEM on another computer and it will activate on line
and become genuine.
John Doe said:Macrium Reflect is excellent for that. I also include a category/copy
for hardware drivers.
Kernel said:I'll try Macrium Reflect, looks like it's free. How can it
image when the OS is running? I've used only Drive Image 2002
since, well, 2002, for cloning (in Caldera DOS).
John said:I recall being told that uses something called "shadow copy".
Apparently it works without problems, but I usually take my hands
off the keyboard/mouse when it is copying.
It also compresses the images. I have been using it with an SSD
drive as primary for over a year. I even used it to move to a new
motherboard and (if I recall correctly) also from a conventional
hard drive to my SSD drive. Yes, the copies happen from within
Windows and quick. The restore from the free version boot CD takes
forever (here anyway), but if you have to restore Windows
frequently, something is wrong with your operation. So, during a
restore, I find something else to do.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.