Where does the OEM license leave someone who builds PCs for other people like I have? Do I have to be registered as an OEM system builder or VAT registered company to be able to also purchase an OEM copy of XP to give them or ... something else?
The PCs I've built have generally been complete builds with the exception of the keyboard, mouse and monitor but otherwise everything else that makes up a PC including a case is new. Where do I stand continuing to do this? I know you can't really answer this but it'd be nice if you could get an answer out of your contact at Microsoft.
Also as an extension of the above can I also not simply be my own vendor and supply and install a OEM copy of Windows installed on the new PC I built for myself with the same lack of new monitor, keyboard and mouse?
I know what you mean. I recently built a complete system up for someone at work. Complete with screen, keyboard, mouse, printer etc. I bought an OEM copy of XP Home and installed that on it. It still needed activating and everything else. Now that's a new PC so is it legal to put OEM Windows on it?
---
Silence propagates itself, and the longer talk has been suspended, the more difficult it is to find anything to say.
And yet if I'd installed say, Linux on there, given him the PC then a week later he'd wiped Linux, bought OEM XP and installed it then, it would have violated the license agreement. :|
---
Silence propagates itself, and the longer talk has been suspended, the more difficult it is to find anything to say.
I really think that OEM licenses should only be available to OEM certified organisations. To be fair, it's even a minefield for me and I'm supposed to have expertise in this field and as I said earlier, it's a minefield for MS as even their top guys don't know which hardware can constitute a 'new PC'.
I like work where we're a University and have a simple campus agreement whereby XP Pro can be installed on all PCs. Also, we're allowed Office Pro on staff home machines legally. First legal copy of Office I've had since Office 95 incidentally :)
---
Silence propagates itself, and the longer talk has been suspended, the more difficult it is to find anything to say.
Personally, I object to Serg's suggestion, as this is POST 100, and if we strip out the unnecessary posts it will no longer be able to make that auspicious claim
They are blithering idiots who seem to believe that an API should do everything for them, including enforcing business logic specific to their project. Not that it matters. The world's ending soon anyway.
Heh. This week I've been moved onto a new high-priority project, and seem to be in a similar situation of people not having a clue how to do an API. Or structure a simple CMS-integrated webapp. Or use source control properly. Or write useful specs. And so on. :(
If you feel like advancing your career and learning CFML, there's a couple of open spaces on the team - would be good to have a second person with functioning brain cells... :)
(that's probably a bit harsh; it's more likely the fault of it being stupidly rushed that it's badly setup/etc, but it's still awfully frustrating)