Lets try not to quote the entire first post please. It takes too much space in the thread. Thank you.
It might be useful to provide download links for: Query Tool v4.x Only: Project xx-xx-2015 with Query Tool v4.x: [Complete Project] Project xx-xx-2015 with Query Tool v4.x (Without Certificates & OEM’s) This would be a much smaller download option since the Certificates & OEM’s folder contents do not change often…
Certificates data can be detailed in 'oemscan.ini' and appropriate certificate|s written from oobe.cmd, thus eliminating 'Certificates' folder.
Certs take 592kb so that isn't even worth eliminating. I am leaving it as it is. Its the images that take up the space, nothing else. The project isn't big by no means and only takes a few mins to download. If I split the oem project up into sections to be put together others will complain since not everyone feels comfortable piecing it together. Nothing is going to change in this area, end of discussion. If you edit your own then don't bother asking me to troubleshoot it. Question: Why is everyone wanting to adjust script and layout when it finally works, to save 592kb of space? lol If it isn't broken, why fix it? Like the old saying goes. Maybe this is why searchengine didn't share the source....to keep ppl out of it. hmmmm Think I might end up doing the same since these types of questions have only arose since it became open source. Seems we have too many hands in the cookie jar and that wasn't the purpose of making it open source. The purpose was if I or some else leaves or gets bored of it, someone else with experience could pick it up.
Nobody was complaining, merely offering an alternative suggestion that certificate data could be added to the 'oemscan.ini' as it is already the central file that contains all the main activation data... thus Certificates folder containing @200 tiny individual files could be removed (cosmetic change more than practical).
I just don't understand the method is all. If you know how to implement this new method I would be eager to learn.
Ok, that even made me more confused. lol What 4 bytes is he talking about (where in rw everything can I find this info) and then how to apply it? Interesting reading but seems some other tools were used which he reversed in order to read bios so I have little info to compare it too. He basically made a fork of this project for win 7 and I like the method but I don't know it. Would have to be adjusted for slic 2.0, 2.2 and 2.3 which is included in this project also. I posted a message for him asking if he could or wanted to share the info with me. I have more questions then answers at this point. lol I do see what some are talking about now...I just don't know how to implement it. Damn, and I thought I could take a break from this. lol Update: The marker as he calls it is what is listed in the ini file for bios id if I am not mistaken. So if I am understanding this correctly we only need the oobe to create the cert with marker (bios id) info only or is the whole key needed? Yep, its official....I'm a noob again. lol
Must click thanks button in order to show download link on first post. @skolar I see what you mean now. I will add the info but will take some time for starting tomorrow my life gets busy again. Thanks for the examples. I knew how to add to oobe but didn't quite understand the ini until now. I see what you mean. Just give me some time to play and test it. When posted I will add your username to credits on first post. Thanks again. Update: Think I can shorten oobe activation part so it isn't so long.
@The_Guardian Attached 'oem.7z' file contains your 'OOBE.cmd' & 'oemscan.ini' files edited as per previous example. Feel free to use, or not use, no credits necessary. I done a couple of VMware test installs for HP and Toshiba with slic 2.1... both installs activated. Yeah, the code can most likely be shortened for the 'OOBE.cmd', and I may look into that later, but at the moment it does the job, and eliminates the need for Cert folder & contents. Edit: 'oem.7z' attachment received (link removed)
First post updated. Below is the change log for 01-02-2015... Spoiler Change log 01-02-2015: -Removed Certificates folder, oobe.cmd now creates needed certs through the .ini file. (Thanks skolar) -Corrected error in query tool if UEFI is not present. (Thanks abbodi1406) -Changed output in query tool from Percent to % sign when scanning. (Thanks abbodi1406) -Version freeze in effect until further notice.
I have an Asus ROG Laptop with Windows 8.1 “Core” [OEMM] / Prod Key embedded in BIOS… Is the Multi OEM Project able to use this [OEMM] / Prod Key with Windows 8.1 Pro, Windows 8.1 ProWMC or Windows 7 installations?
No. But is not the project itself the problem, problem is that embedded key is for Core edition and for that specific OEM machine solely, in other words that key is tied to that hardware/edition configuration.
The project will extract and dump oem-dm key and then apply it if correct win oem version (most are core). As far as others if key not in bios then you will need to use kms activation which if needed can be added to setupcomplete.cmd file. In other words if oem-dm key in bios is for windows core edition....you must install core edition for key to activate. If another edition, of course it will fail and kms activation will be needed. Run the query tool before doing a install so you will know where you stand.
@The_Guardian Re: OEM Query tool The 'Rw.exe' icons brief toolbar flashing can be eliminated by small edit of 'OEM-CD.cmd'. From... Code: Rw.exe /Min /NoLogo /command="ACPI Dump MSDM";"RwExit" /logfile=".\MSDM.txt" Rw.exe /Min /NoLogo /command="ACPI Dump SLIC";"RwExit" /logfile=".\SLIC.txt" To... Code: Rw.exe /STDOUT /NoLogo /command="ACPI Dump MSDM;RwExit" >".\MSDM.txt" Rw.exe /STDOUT /NoLogo /command="ACPI Dump SLIC;RwExit" >".\SLIC.txt" optional delete reg entries created by 'Rw.exe'... reg delete "HKCU\Software\Rw.exe" /f >nul reg delete "HKCU\Software\RW-Everything" /f >nul 'RwExit' appears at end of MSDM & SLIC data on saved 'Results.txt' Edit: attached file received (thus link removed)