OEM Windows license
in [Dell]
|
Prev: nytimes: report says: Dell "very poor" in customer service (2008)
Next: Dell PA-12 / PA-10 laptop adapter repair / rebuild
From: Ben Myers on 21 May 2010 09:56 On 5/21/2010 6:27 AM, Brian K wrote: > "Ben Myers"<ben_myers(a)charter.net> wrote in message > news:ht4sgu$i1d$1(a)news.eternal-september.org... >> On 5/20/2010 8:30 PM, E wrote: >>> >> >> On the other hand, if I had replaced a 2400 motherboard (845 chipset) with >> a 3000 motherboard (865 chipset), booting the hard drive would result in a >> BSOD, when Windows tried to load the drivers for the old chipset. Without >> considerable handwaving and registry editing, a reinstall would be >> necessary. >> > > > Ben, > > We discussed the TeraByte OS Deployment Tool Script Pro last year. It's a > lot more sophisticated these days and also supports Win7. It only takes a > minute or two to get an OS booting after the first BSOD. You don't need to > use TeraByte software to restore the image to the new hardware. Any > image/restore app is fine. > > From the userguide.... > > "A typical scenario for using the script would be to first restore an image > of Windows to new/different hardware, and then run osdtool.tbs to make the > necessary changes so that the restored OS partition will boot and run > successfully. These changes are all made while the target Windows OS is not > running. > Changes needed to get a restored Windows OS to boot on new hardware can > include installing a storage driver for the boot device (hard drive > controller), as well as changing the HAL (hardware abstraction layer) and > the CPU type (AMD vs Intel). In some cases it may be necessary to first > remove all installed drivers, which osdtool.tbs can also do. " > > > > Brian, Thanks for the reminder. I do not get much demand for changing motherboard chipsets underneath a Windows install, but I may have to add the TeraByte OS Deployment Tool Script Pro to my set of sharp tools used for all manner of acts on Windows systems... Ben
From: Tony Harding on 23 May 2010 11:31 On 05/21/10 01:51, Christopher Muto wrote: > E wrote: >> Christopher Muto wrote: >> >> <snip> >> >>>> >>>> So the Dell OEM Windows XP license can be installed, activated, and >>>> receive updates, with a non-Dell motherboard in there? And it will >>>> work until MS stops supporting XP? >>>> >>>> It's just that they don't want you to, but will not try to stop it? >>>> >>>> Eddie >>> >>> you got two response telling you that technically you can indeed >>> install the dell oem windows xp cd on any pc that you wish. you will >>> have to activate it and windows oem cds require windows oem >>> activation codes so you will need the one that came with the >>> system/cd. the issue of legality is for you to figure out yourself, >>> but i find it at best ambiguous what they mean by the license being >>> tied to the machine... is the machine the processor, the motherboard, >>> the memory, the disk, the video card... the box?!? and when you >>> switch these components which component does the windows license >>> follow? if you change every part one by one because of no other >>> reason than system failure is it the same machine according to >>> microsoft? i don't think anyone honestly knows, not even microsoft. >>> there is an adage about george washington's axe where over the years >>> the head was replaces a couple of times and the handle four times, >>> yet it is still called george washington's axe. >>> bottom line is that the only difference between the retail edition of >>> windows xp with product ccode and the dell oem edition of windows xp >>> with product code is wording of the license. they function exactly >>> the same. >> >> Ok. I kept reading things about trying to use an OEM license on a PC >> that was not manufactured by said OEM. I guess there is much >> dis-information out there. They give the impression that it will halt >> sometime during the install, or it won't activate. >> >> This will knock ~110 off the total repair, since I can just use the >> original product key that shipped with it originally >> >> Your question, "what is the machine?" is funny. I have wondered the >> same thing. Since I was able to change several components in a home >> built PC and never had a problem with activation. The processor, hard >> drive, and dial-up modem, were the only things left in the box from >> the original build. >> >> I've never tried to use the same product key on more than one machine >> with WinXP. I assumed they would catch the second one when it tried to >> get an update. Here we are two operating systems later and I still >> don't know what would happen. . >> > >> Thanks >> Eddie > > regarding "reading things about trying to use an oem license on a pc > that was not manufactured by said oem..." i think what you may have > heard is that most oem windows cds are not full copies of windows like > dell has historically supplied but rather what are called recovery cds > that are an image of the original hard disk configuration for the > specific machine. this has its advantage, namely a simple to reload a > machine to its original 'factory fresh' state without having to install > any drivers or applications, but it has the disadvantage of only working > on a specific machine. some vendors that do offer full working versions > of windows had modified the installation routine to check the > manufacturer of the machine before proceeding (gateway was notorious for > this) but not all do. dell actually did this 'bios check' with windows > 2000 but there was a workaround for it by replacing a single file... > > as for using an activation code multiple times that would be a problem. > you can google tons of info about it. first time it activates online, > second time it might too, by the third time you have to call for > automated activation after typing in a ton of numbers, after that they > make you talk to someone to explain why you have installed it so many > times and though they state in their license agree that they will not > collect any identifiable information about you during the activation > process they actually ask you your name and phone number and refuse to > proceed if you don't give it. i learned this when a new machine when > through three disk failures in a row before it was determined that it > was a defective motherboard... the silly part is that after a certain > period of time the whole process is reset and online activation is > available again... research it if you really care to know the precise > details. 120 days, IIRC
From: Brian K on 24 May 2010 18:47
Ben, Maybe I shouldn't post this as it doesn't show using the TBOSDT Tool for simple tasks. The TBOSDT Tool is demonstrated in the second half of the video. It is heavy going. I don't understand most of it. The video is 9 MB. http://www.terabyteunlimited.com/videos/ifw/osdtool.wmv |