True however the OP was clearly looking at the most "correct" route, which from my understanding is the indisputable choice, retail box, non-upgrade.
The reason why I'm sticking you with the whole issue of OEM vs Retail Upgrade is due to your specific comments on how to make it work which involves actual alteration of the product's code once it's installed (referring to the registry comment) and/or installing the Upgrade disc twice. We both agree that the hard truth behind the OEM deal is gray and not 100% crystal clear. For someone to install OEM Windows, it requires no alteration of the product for it to be used. I provided no hint of instruction on how to make it work, rather just a suggestion as an option. I read your post as almost an instruction on how to make something work illegally, which... correct me if I'm wrong but is in direct violation of this forum's policy.
You are incorrect here again (about what the forum rules are). Whether we like it or not we are not the EULA police. We can only do what I have been doing all along. Remind folks that they might not be 100% legit.
There is plenty of discussion on the board about Jailbreaking, Hackintosh, etc... What we (as mods) look for are specifically (w.r.t. the Windows on Mac forum): links to ISOs that do not come from Microsoft. (This is not to say that all ISOs are bad, I post the links to the "official" Digital River ISOs plenty to help folks through issues.), Detailied instruction on bypassing
activation and keygens as activation is really the main tool that Microsoft users against piracy.
This is why, both in this case and the other thread I am very careful about not saying anything about OEM until someone else has brought it up as being perfectly OK. The original posters in both threads came to their own conclusion that Full Retail Product was the right way to go and my first post in the thread was just to confirm that. It's downhill from there.
You'll find that most threads that start off "I torrented a copy of W7 and a keygen, and am having trouble with my mouse" fall on deaf ears around here.
I know what you're saying, I know what your intent is despite what you post. I'm just picking on you because it seems that you like to be very literal in some areas then in another post hints/tips as to how to circumvent the products intended application.
Re-read my first post in this thread and in the other one. What is my agenda? My insidious plan?
I never said policies made sense, as a normal user I could care less. However as a professional I have to look at where the gray areas are, assess the situation, consider if the risks are acceptable, if not research what isn't gray and stay within the crystal clear areas of any ToS, License, User Agreements, etc.
I would have no problem in vagabondforlife saying. "You could save a few bucks by using OEM, even though you are using it for personal/hobbyist use the risk of Microsoft doing anything about it is so tiny you won't get busted." However both he, you and others don't come out and say that it's a shade of gray. They say it's perfectly fine, "A-OK". It isn't so clear.
Personally, this is just me but I feel you'd do a better service by providing a contact number and having your readers find out from them directly. Putting links or quotes on a forum instigates discussion sometimes outright arguments/bickering and more interpretation by unqualified parties.
This is a major issue with shrink wrap licenses. The only person qualified to determine if they are in compliance with a license is the person entering the agreement. They just need to know what to look for.
As Ed Bott says, the folks on the other end of the line don't know either. It's the blind leading the blind. The licenses aren't written in a foreign language or impossible to decipher. This is why I post the links as well as the plain English "Licensing for Hobbyists" page and the Ed Bott article. Only you can decide if you think you qualify as a System Builder or can ignore that license (in which case who is the System Builder you derive that EULA from?) and only you can decide if something qualifies you for upgrade or student pricing, regardless of the intent.
Just as only you can decide if the Snow Leopard upgrade is for you even though you only have Tiger...
If they still haven't made up their mind at that point, they are free to call and get another opinion. However, most folks, will already have made up their mind. Either that they really want OEM (because everyone is doing it, and they wouldn't be swayed by Microsoft repeating the Q&A you posted from TechNet) or the really want full retail (because it is unequivocally the right thing to do).
I'm not singling out you nor is it my intent as I see this all the time everywhere, including MS Technet.
Were I not one of thick skin and a relatively even keel I might have reported some of your earlier posts as personal attacks. Credentials, and certs mean very little. I've seen my share of MCSE's stumped by things a good, but uncertified, admin can work around in 5 minutes. Things don't always go "by the book". Experience trumps training most of the time.
Off the record, any normal person who're not lawyers would think that if Microsoft is okay that their distributors are selling OEM Windows, would have to know that there's going to be those that aren't using it IAW the Licensing Terms and EULA, etc.
Just as a manufacturer of "Indoor Use Only" extension cords probably knows that someone will probably use them outside. All I can do is point out the license or indication and the risks and limitations.
FWIW Microsoft would probably do well to get folks off of their XP addiction if they offered Windows 7 upgrades with no support for $49. I bought all my copies of W7 (upgrades for existing XP or Vista installs when MS was offering 50% off at launch) yet, I have one machine I keep XP on and have the upgrade still in shrink wrap.
B
