Win 8.x • Win 7 • Vista - 'Multi-OEM' ISO Project

@ kronflux, I have noticed quite a few times on this forum problems with corrupt ISO files MagicISO is usually the culprit UltraISO and PowerISO are problem free. As for WinRAR using it with ISO files can cause confusion for some users especially if they have WinRAR set a default program for ISO files people unpack the ISO's and then burn this files to cd/dvd them wonder why it is not bootable.

 

You need to login to view this posts content.

 

...ANYWAY... I went ahead, and did what I said in the last post.... I can post the oobe.cmd, but for legal reasons I can't post the keys.ini (can you spell DCMA?), so, if searchengine wants to give me a way to get ahold of him, I got a present that everyone might like ; otherwise, it will have to wait for some other soul to *randomily and unexpectedly* write the exact same code and upload it to some file sharing service

 

You can PM searchengine.

 

You need to login to view this posts content.

 

I'm going to PM you a link to download the current versions of both -before my vista mods and after my vista mods

 

I think I can one up that ;-) how about a oembios.ini....
i'm thinking something like:

Code:

;;certname=biosstring1 biosstring2 biosstring3; or more ;-P
acer=ACER AcerSystem TravelMate;
;;^acer->corresponds with the file in the certs directory - if it doesn't activate oobe will search for acer2, then acer3, and so on
advent=DSGLTD ADVENT;
alienware=ALWARE ALIENWARE;

bios strings will contain all possible bios strings...
Then we could process all the manufacturers in a couple lines of code, and make it easy to maintain!!!
certname will be the cert file ex: acer.xrm-ms (- extension)
if we have more than one cert for *ANY* of the included biosstrings it will be xxxx2.xrm-ms or xxxx3.xrm-ms
this way if any of the certs for the strings for that manufacturer fail; it will just continue along until we activate
now of course when we have certs like HP-PROLIANT-FOXC(we only have keys for HP!!) ..... we would put all of those strings in the biosstring. now for ones like EMAC-GATEWAY-GATEWAY2 (since we have product keys for emachines and gateway-and even if they are the same cert I doubt it will stay that way in the future) we would copy the cert to "emachines" and "gateway" and then properly add the emachines strings to the emachines cert and the gateway tags to the gateway biosstring....

But that's not it!!! If I am correct, *ANY* valid slic bios with *MATCHING* cert will activate with *ANY* valid OEM key(for the edition you installed).. so in the keys.ini we setup a defaultoemkeys manufacturer with all the generic keys(that are used 3-20 times repeatedly in our keys.ini). Then if no matching PIDKEY is found, but a valid biosstring+cert exist, we will simply use the defaultoemkeys. if everything does exist then we use the PROPER key for that specific oem.

this way we can really clean up the oobe.cmd and make it easily updatable, and clean up that serious mess of product keys.... (oh yeah, i like that reverse style keys.ini - kind of like DAZ's.. I think I need to fix that too, then we could *AH HUM* "borrow"(or more likely copy) keys back and forth between windows loader and this project.

now for the toshiba series ie: toshiba, tosa, tosac, tosi, and tosq we would check %MAN% after the cert lookup, and create the duplicate directory - this way we can still save space - maybe I should even do a duplicate file check on the vista and 7 certs - we could use a "either" directory for certs if they are the same between versions; if the cert isn't found in the windowsversion directory it would check the either directory..

well, I am off to mess with it a little before I crash, Probably try to finish it up tomorrow or monday night. #WINNING!!

 

I do have to say, I liked the previous versions of the dell wallpaper, and the acer wallpaper. I wish those ones were in the multiple sizes so I could replace the new ones. the new ones are ugly, in my opinion. less professional looking.

 

You need to login to view this posts content.

 

Thank you everyone. I was able to build an img that appears to work in virtual box just fine. Although, aside from using JoshCell's tools, I haven't done much like this before. Can somebody verify a few things for me?

The setupcomplete.cmd and loader files all go here? \sources\$oem$\$$\Setup\scripts

Since my img had both x86 and x64 install folders, I placed the oem, loader, and setupcomplete.cmd in both the \sources\ and \source64\ folders. Was this necessary?

Thanks again.

 

well, since then We implemented a bios.ini, and it searches it with one loop.
But I think(I'll have to try) we can read the output from wmic into a enivromental variable(with SET /P=<filename)..but we can output to a file and search that!!
that would clean up the repeative WMIC calls....(It would still run FINDSTR on every check until it finds the string..)
as For the keys; I removed all the duplicate ones

anyway, if you have a better way to do it I would love to see it!!

I need to verify this: but if i Run the following:

Code:

WMIC BIOS GET VERSION >bios.tmp
WMIC COMPUTERSYSTEM GET *manufacturer* >cs.tmp  ---still not sure about which string to get
WMIC CSPRODUCT GET *vendor* >csp.tmp  ---- or which one here

we could just extract what we need....
and I could search that against the bios.ini instead of the opposite way around(like it is now)

that would reduce a lot of overhead(if it works properly)!!!!!

 

Alphawaves did that with his 7Toolkit. But now he has a new tool to that. Biosversion its called.

 

Worked very fine............ one question can i switch to windows default theme..................