- Messages
- 2,156
Here is a link concerning the new OEM System Builder license. (Edit: Perhaps I should have emphasized originally that I am talking about the OEM System Builder [Personal Use] License even though that is what I linked to). Below is a snip of, to me, its key provision, although there are other important provisions allowing use on a second machine and sale to a another individual. MS always seems to muddy the water when it comes to the OEM System Builder license. Ignoring the VM possibility, the way I read the snip is that 8 can be used, for example, as one of the operating systems of a dual boot given installation on a separate partition. Do you think that this literal interpretation is what MS means. Why would a dual boot, for example, be required? And, why wouldn't one be able to install on a second drive--not just a separate partition?
OK fine, even if my literal interpretation is correct, then I, for one, am up for buying a Win7 computer, partitioning it, and going for the OEM system builder dual boot--thus extricating myself from the clutches of MS, my computer manufacturer, and crapware. Also, why not just buy a new Win8 machine and obliterate everything there--starting over with UEFI, if desired, and doing the dual boot.
My understanding is that MS is being pretty loose, at least informally, in interpreting its OEM System Builder license. I doubt that even, for example, the dual boot thing is an operational requirement. What would be the point?
I am interested in anything you have to say about the interpretation given above and about the MS operational interpretation of it OEM System Builder license.
OK fine, even if my literal interpretation is correct, then I, for one, am up for buying a Win7 computer, partitioning it, and going for the OEM system builder dual boot--thus extricating myself from the clutches of MS, my computer manufacturer, and crapware. Also, why not just buy a new Win8 machine and obliterate everything there--starting over with UEFI, if desired, and doing the dual boot.
My understanding is that MS is being pretty loose, at least informally, in interpreting its OEM System Builder license. I doubt that even, for example, the dual boot thing is an operational requirement. What would be the point?
I am interested in anything you have to say about the interpretation given above and about the MS operational interpretation of it OEM System Builder license.
Attachments
Last edited:
My Computer
System One
-
- OS
- Win7 Ult on DIY; Win8 Pro on MBP/Parallels; Win7 Ult on MBP/Boot Camp; Win7 Ult/Win8 Pro on HP
- Computer type
- PC/Desktop
- System Manufacturer/Model
- DIY Rig; MacBook Pro (MBP)/Parallels/Boot Camp; HP Pavilion dv6500t Laptop
- CPU
- Intel i7-2600K (sometimes OC'd to 4.8 GHz)
- Motherboard
- ASUS P8P67 Deluxe Rev B3
- Memory
- 16 GB Corsair Vengeance
- Graphics Card(s)
- EVGA 570 SC
- Monitor(s) Displays
- Gateway
- Hard Drives
- Dual Boot:
Win7 Ult RAID 0 on OCZ Revo x2 and
Win7 Ult RAID 0 on Caviar Black SATA 3's
- PSU
- Cooler Master Silent Pro 1000W
- Case
- Cooler Master 932 HAF
- Cooling
- Zalman CNPS9900MAX-B CPU Fan
- Keyboard
- Logitech Cordless Desktop MX 5500
- Mouse
- Logitech Cordless Desktop MX 5500
- Internet Speed
- 20 Mbps Download/2+ Mbps Upload
- Other Info
- Pioneer Blu-ray Burner/DVD Burner