• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Windows7 OEM

Messages
143
Country
australia
Maybe too late but...

I ALWAYS go with the OEM versions. You get exactly the same OS except:
  • You have to choose whether it'll be 32-bit or 64-bit before you buy (check your hardware compatibility)
  • You don't get all that fancy packaging with a "look how wonderful Microsoft Windows is" booklet.

NewEgg has always treated me great. FAST deliveries... VERY good deals... No issues at all and I've been shopping there for years! They even beat TigerDirect with selection and prices on quite a few products!!

What exactly does OEM mean?:confused::confused:
 
Hmmmm Msoft OEM software has certain restrictions ...check the details on the newegg site

"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."

Just a heads up as you can have issues with the software later down the track
Around here most retailers/wholesalers wont sell you OEM software unless,you purchase system from them(once upon a time you could get around this by just buying a Harddrive not sure if thats still possible) or if you are a system builder with the msoft certification and documentation

Wozza
 
...Just a heads up as you can have issues with the software later down the track
Around here most retailers/wholesalers wont sell you OEM software unless,you purchase system from them(once upon a time you could get around this by just buying a Harddrive not sure if thats still possible) or if you are a system builder with the msoft certification and documentation

Wozza

Not nearly as often as it used to be, the "combo pack" you described was offered in the past but that has faded away for the most part. I purchased a few of those years ago. I've never have had an issue with the software nor legalities. As long as it's offered without having to provide proof of "certification" I have no problem continuing. Personally, I have no desire for their unnecessary packaging and a 32-bit DVD I will never use nor having to pay for it. If Microsoft chooses to come after me for purchasing and using an OEM product on my personal PCs, I'm fine with that. It's kind of like speeding... most of the time the only ones who get a citation are the gross offenders.

The "disclaimer and license agreement" is visible in the listings of the OS and it's ultimately the responsibility of the purchaser. Buy it, don't buy it... makes no difference to me. I offered my suggestion but it's always good to hear/read warnings and cautions...
 
And then there's the bit about "cannot be transferred to another computer once it is installed". Is that anything like what Power Spec does? If you change the Mobo or CPU the OS thinks it's in another computer and won't boot. Even MS can't register it.

Bob
 
OEM operating systems have always struck me as a grey area.

Reputable firms sell them but always with the disclaimer previously quoted - however note the words This software is intended for pre-installation on a new personal computer for resale." Yet Microsoft says OEMs should only be resold to another system builder - re-selling them otherwise is a breach of the terms of the licence under which Microsoft originally supplied them.

No matter which way it's looked at, I suggest there is a breach. That won't matter as long as Microsoft doesn't do anything about it. There must be a risk (probably small) that Microsoft may do so in the future, even if it hasn't in the past.
 
Yet Microsoft says OEMs should only be resold to another system builder

I think it depends on how you define 'system builder', I built my system so without a better definition I'm a 'system builder' and entitled to use OEM versions of software. If they get grumpy for accounting purposes I'll sell it to myself when it's finished.

Mind you there's a lot of stuff in EULA that wouldn't stand up in a court of law.
 
I think it depends on how you define 'system builder', I built my system so without a better definition I'm a 'system builder' and entitled to use OEM versions of software. If they get grumpy for accounting purposes I'll sell it to myself when it's finished.

Mind you there's a lot of stuff in EULA that wouldn't stand up in a court of law.

There is a better definition of System Builder - the one in Microsoft's OEM System Builder Agreement. The one you agree to on installation!

True, many EULAs wouldn't stand up in court - but should we really try to exploit loopholes in EULAs and, if so, should we exploit commercial FS add-on developer's EULAs too?
 
There is a better definition of System Builder - the one in Microsoft's OEM System Builder Agreement. The one you agree to on installation!

True, many EULAs wouldn't stand up in court - but should we really try to exploit loopholes in EULAs and, if so, should we exploit commercial FS add-on developer's EULAs too?

The MS definition of a System Builder, is probably sufficiently vague that you can get away with it:

“System Builder” means an original equipment manufacturer, an
assembler, a refurbisher, or a software preinstaller that sells the Customer System(s) to a
third-party.

The selling it to a third-party bit is virtually irrelevant, unless you think Dell have to buy their computers from someone else. If you're really worried sell it to a friend for £1 and then buy it back off them for refurbishment.

Reference the legality of EULAs, I wasn't referring to loopholes as such more the bits which fail under fair contract law or trying to remove statutory rights*. If someone writes a EULA that tries to take away my legal rights then they've got no one to blame but themselves as it can't be legally binding.

*Note this varies by jurisdiction, I'd have to look up the details but my understanding is based on UK law.
 
The definition you give isn't what the Microsoft OEM System Builder Licence states. Also Microsoft states:

There is a growing market for "do-it-yourself" home PC hobbyists who assemble PCs from components for their own use. Microsoft retail software licenses are the appropriate licenses for the do-it-yourself market. OEM System Builder software is not intended for this use, unless the PC that is assembled is being resold to another party. ​​​​​​​​​​​​​​​​​​​​​​

http://www.microsoft.com/oem/en/licensing/sblicensing/pages/licensing_for_hobbyists.aspx

I am not disputing anyone's statutory rights or indeed their right to protction from unfair clauses. I do dispute anyone's right to accept the terms of an agreement and then seek to wriggle out of it. Retail Licences are sold under one set of terms and OEM licences under another. If you can't accept the OEM terms then don't use it.

EDIT
In this context 3rd Party isn't "virtually irrelevant." It means someone who isn't Microsoft or the System Builder (the first two parties).
 
Last edited:
Link to the bit of the Microsoft empire that gave the definition I used, if they can't be internally consistent they've pretty much lost already.

http://oem.microsoft.com/public/worldwide/licensing/opccomm_retail_and_coem.pdf

By saying the 3rd party was virtually irrelevant I meant that as it could be anyone but MS or the builder it's trivial to sell the computer to a trusted 3rd party for £1 and then use the PC you've just put together. My mother now appears to have three computers at my house that she never uses...

The main issue with OEM licenses is that you have no right to technical support from MS, other than that everything else is FUD on their part.
 
By saying the 3rd party was virtually irrelevant I meant that as it could be anyone but MS or the builder it's trivial to sell the computer to a trusted 3rd party for £1 and then use the PC you've just put together.
That isn't permitted by the Microsoft OEM System Builder Licence, which is really what matters because you accepted its terms when you installed an OEM version.
 
The license also states that the buyer must be unrelated to the seller. I'm not sure it's worth all the confusion, tip-toeing about and hassle.

Bob
 
That isn't permitted by the Microsoft OEM System Builder Licence, which is really what matters because you accepted its terms when you installed an OEM version.

That's kind of my point, and I need to confirm with someone I know who's just covered this aspect in their OU law degree, I don't think the system builder license is legally enforceable. My main main reason for thinking this is the incredibly weak wording of this bit:

There is a growing market for "do-it-yourself" home PC hobbyists who assemble PCs from components for their own use. Microsoft retail software licenses are the appropriate licenses for the do-it-yourself market. OEM System Builder software is not intended for this use, unless the PC that is assembled is being resold to another party. ​​​​​​​​​​​​​​​​​​​​​​

If it was legally enforceable they'd use far more robust language, i.e. they'd say it was 'forbidden' rather than 'not intended'. Now it may be in the license that you agree to but if it's not legally enforceable then MS are trying to impose conditions beyond those they're allowed to.
Imagine Ford sold you a car and in the small print it said you could only fill up at Shell fuel stations, would you go along with that despite it being illegal for them to make that a condition of sale? Under UK law at least that'd be considered an unfair contract and wouldn't be binding. What I'm a bit unsure of is whether that negates the entire contract or just those bits, it's been almost two decades since I studied this and it was mostly to do with selling boats!

Interesting read http://www.lawiki.org/lawwiki/Shrink-wrapped_licence_agreements:_the_UK_legal_position which concludes that EULA have limited enforceability in UK law, it would also seem to imply you'd need the entire EULA written on the box for it to have a chance of standing up in court which would mean we're going to need much bigger boxes...
 
Last edited:
Oem

Here's the part I don't get.......if Microsoft stocks NewEgg with OEM pkgs, could it even be remotely possible that they think "commercial" system builders would be going online to newegg to buy an OS? Does DELL get their OS's from some online vendor? I doubt it..............

Besides, the dog across the street("REX") is going to be purchasing this system,
 
Last edited:
As I keep saying, what matters is what the Microsoft OEM System Builder Licence actually states - what's said elsewhere is irrelevant.

Your point about shrink-wrap validity is misconceived. All the reputable sellers (Amazon Fry, Newegg) make it clear on their sites that their OEM Windows are sold subject to the conditions of Microsoft's OEM System Builder Licence. Buyers can't claim they didn't know. If they choose to buy without reading that licence that's their problem - it's available on Microsoft's site. Quibbling about validity of shrink-wrap licences is irrelevant. (Incidentally, the only UK court to consider their validity ruled that a shrink-wrap licence was enforceable - Beta Computers v Adobe Systems.

What is unfair about Microsoft offering a cheaper licence to genuine System Builders in return for not having to provide support? Companies do that all the time. Would you expect to be able to buy your Ford car cheaply under the same agreement as that between Ford and its dealers?
 
As I keep saying, what matters is what the Microsoft OEM System Builder Licence actually states - what's said elsewhere is irrelevant.

Only if it's legally enforceable which is questionable and has never been tested in a court of law. You can write anything you want in a Licence but it won't trump the national law of the country in which the transaction takes place.

Incidentally, the only UK court to consider their validity ruled that a shrink-wrap licence was enforceable - Beta Computers v Adobe Systems.

Which if you read the link I posted is regarded as a questionable judgement at best, and the willingness of both parties to accept it is probably tied to Adobe also being in the business of writing some dubious EULA.

What is unfair about Microsoft offering a cheaper licence to genuine System Builders in return for not having to provide support?

Nothing, but why should I be stopped from buying a cheaper license if I don't want Microsoft's support? Especially when I have to provide that support to anyone else I build a computer for if I put an OEM install on it which even MS license terms let me do.

Would you expect to be able to buy your Ford car cheaply under the same agreement as that between Ford and its dealers?

No, but I expect the Ford dealers don't pay the full retail price for any cars they buy and in this situation I'm in the position of being a dealer as I can buy the OEM software and put it on a computer I've assembled. MS will even let you buy a single license if you just want to put out one computer, if I felt like complying with their license terms I could then sell it to my mate for £1 and then he could generously gift it to me after I treat him to a drink in the pub.
 
What is legally unforceable about the Microsoft OEM System Builder Licence and which national laws trump it? Remember as you said "I'm in the position of being a dealer " so consumer protection laws don't apply to you. You've already accepted the licence itself is not unfair. To paraphrase your argument "why should I be stopped from buying a cheaper Ford car if I don't want the wheels?" That's a matter of terms of trade, not rights.

"if I felt like complying with their license terms... rather gives the game away. It appears you believe you don't have to comply with licence terms if they are inconvenient to you.
 
"if I felt like complying with their license terms... rather gives the game away. It appears you believe you don't have to comply with licence terms if they are inconvenient to you.

You don't have to comply with them if they're not legally enforceable, this isn't to say they can't then refuse to do business with you.

To paraphrase your argument "why should I be stopped from buying a cheaper Ford car if I don't want the wheels?"

Because as far as I'm aware that's not an option, you can however get a cheaper one if you don't choose the alloy wheels and the metallic paint.

Of course having now bothered to read the OEM System Builder License the only restriction on use it places is that you sell the Customer System(s) to a third party. It doesn't define a third party, or set a minimum price which as I've already demonstrated makes it trivial to work round by selling it to a trusted third party for a nominal sum. Which incidentally is accepted commercial practice, Raytheon once sold a weapon system to the Royal Navy for £1 so it could be trialled on a warship, although they seemed to take it back rather quickly come September the twelfth...
 
If they are not legally enforceable I suggest you demonstrate why they are not, as I've asked several times.

You missed out the part in the licence which refers to when a Customer System leaves your control.

It's very revealing that you decided that the Agreement wasn't applicable without bothering to read it. - " having now bothered to read the OEM System Builder License."

What Raytheon may or may not have done is another irrelevance. It wasn't operating under a licencing agreement.
 
Back
Top