Moderators: Flying Fox, Ryu Connor
Use of this OEM System Builder Channel software is subject to the terms of the Microsoft OEM System Builder License. This software is intended for pre-installation on a new personal computer for resale. This OEM System Builder Channel software requires the assembler to provide end user support for the Windows software and cannot be transferred to another computer once it is installed. To acquire Windows software with support provided by Microsoft please see our full package "Retail" product offerings.
MadManOriginal wrote:I wouldn't worry about it too much. Worst case is you have to call MS to activate. 'Have you installed this license on any other computers?' 'Nope.' 'OK, then here's your activation code...' I've only had to do that once in 10+ years of activated MS OSes and that was for Win XP OEM (which had much more strict hardware change tolerances) when I was forced to reinstall multiple times in less than a week because of dodgy hardware.
Forge wrote:I have a feeling it's Vista 2.0, and we're going to get Windows 9 much, much sooner than anyone expected.
Forge wrote:Edit: In reviewing my post, I realized I'm not really on-topic. I apologize. Since I originally had a more on-topic intent, but the info seems useful here, I'll leave it.
Forge wrote:MadManOriginal wrote:I wouldn't worry about it too much. Worst case is you have to call MS to activate. 'Have you installed this license on any other computers?' 'Nope.' 'OK, then here's your activation code...' I've only had to do that once in 10+ years of activated MS OSes and that was for Win XP OEM (which had much more strict hardware change tolerances) when I was forced to reinstall multiple times in less than a week because of dodgy hardware.
Funny, I had to do it twice in 3 weeks of Windows 8 usage on my laptop. It kept updating drivers silently right after install. I called, reactivated, all good. A week and a half later, Lenovo kicked out a firmware update that resolved a UEFI bug I was having. Despite it being a laptop with pretty much no removable/replaceable parts, I got to make the phone call again!
Even better? Two weeks after that (a week and change ago), my Win8 install just suddenly decided to make itself unusable. Not sure what happened, just got a new-style BSOD every boot. Used System Restore three times, with a further-back point each time, then attempted the "refresh my Windows" thing, only to have it fail with an obscure message relating to my original upgrade install.
Guess what? The disk image I made just before trying out Win8 got used. Laptop is in perfect working order again, despite Windows 8 providing a multitude of BSODs, including some specifically telling me I had failing hardware.
I am now officially giving Windows 8 a miss for this go-round. I have a feeling it's Vista 2.0, and we're going to get Windows 9 much, much sooner than anyone expected. It'll actually be Windows 8.1, just like how we got the "all new" Windows 7 right after Vista shipped, which was in reality nothing more than a big service pack rollup and some UI tweaks/changes.
Edit: In reviewing my post, I realized I'm not really on-topic. I apologize. Since I originally had a more on-topic intent, but the info seems useful here, I'll leave it.
Ryu Connor wrote:How the hell did a thread I answered fully in the second post end up this long?
Ryu Connor wrote:How the hell did a thread I answered fully in the second post end up this long?
Ed Bott wrote:If you purchase the software separately, in a package or as a download, the rules are much more liberal. Note that the text for the following rules is identical for retail upgrades and for System Builder software that you install on a PC you build yourself, or in a virtual machine, or on a separate partition. Emphasis in the following sections is in the original:EULA wrote:You may transfer the software to another computer that belongs to you. … You may not transfer the software to share licenses between computers.
In other words, you can remove the Windows 8 upgrade from an original PC and then install it on another PC, assuming the new PC has a license that qualifies it for an upgrade. Likewise, you can completely remove the PUL System Builder software from a self-built PC, a VM, or a partition and then install it in a new physical or virtual PC.
There is no limit on the number of times you may do this type of transfer, providing you follow the rules I describe later in this section. That means hobbyists who like to tinker with PCs can relax. If you buy a System Builder copy, you can move (not share) that license from an old PC to a new one
MadManOriginal wrote:That link is not linked from either the Ars article or the Ed Bott article to which Ars links as far as I can see, hence the confusion.
Users browsing this forum: Bing [Bot] and 2 guests