Obviously the term "OEM" is being used differently from factory-builds.
Grrrr!
I don't know why Microsoft insists on re-using identical terms in different ways.
Sometimes, OEM is used to denote Windows installed at the factory by major manufacturers. At other times, OEM is used to differentiate between Retail Windows licenses (which can be transferred to different hardware,) and Windows licenses sold to small builders and individual users who build their own systems. In this second context, OEM Windows licenses become "locked" permanently to the hardware where they are first installed and CANNOT be transferred to another machine. Typically, OEM licenses for system builders cost about half what a Retail license does; hence, their greater popularity.
SLIC Toolkit. . .
Now, we're getting into some real nuts-and-bolts stuff.
Systems from major manufacturers have three components that must be correct before Windows will activate: Product Key, Manufacturer's Software Certificate, and SLIC. SLIC, or System License Internal Code is flashed into the system's BIOS chips on the MotherBoard by the manufacturer. I rarely write about SLIC because it's not something most users alter.
But there are tools that enable users to manipulate their SLIC contents. The SLIC Toolkit is one of these tools. There's no harm in using the SLIC toolkit to examine your system's SLIC content, but I wouldn't recommend making changes.
Since Windows Vista uses SLIC version 2.0 and Windows 7 uses SLIC version 2.1 one could use SLIC Toolkit to determine if their system is Windows 7 ready. Not a big issue today, but in 2009, it was.
Note: One hack that Microsoft was unable to disable was people flashing SLIC 2.1 and installing Windows 7. Doing this produced a system that appeared to have a genuine Windows 7 installed by the manufacturer; hence, it would activate as if it was legitimate. (But do it wrong and you're replacing BIOS chips!)
Since Windows 10 doesn't use SLIC, the toolkit's becoming redundant.
Cheers, PW.
|
