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

You need to login to view this posts content.

 

Update: I have learned a lot doing this test for csl iso's....conclusion is the oem folder with the oobe.cmd, setupcomplete.cmd and firstlogon.cmd doesn't work with the csl iso's. There is nothing wrong with the oobe.cmd script...it works just not on csl iso's. Don't blame searchengine's project but blame M$. Sorry but these are the facts.

You can try yourself by creating all three .cmd files and placing them in oem folder. Just echo something to show followed by pause...you will see it is never ran. The install doesn't see the .cmd files in the oem folder.

Update 2: I tried using the leaked version from MSDN with same neg. results...
MICROSOFT.WINDOWS.8.1.SINGLE.LANGUAGE.RTM.X64.ENGLISH.DVD-WZT
RELEASE DATE: 08/21/2013
BUILD: 6.3.9600.16384.WINBLUE_RTM.130821-1623
FILE: 9600.16384.130821-1623_x64fre_Client_SingleLanguage_EN-US-IRM_CSLA_DV5.ISO
SIZE: 3,838,724,096 byte
SHA-1: 10F0288681BF56D22D9ADC58E27BEE2D781E6A1D
MD5: 22B42364D905BD6EC9C2F143BC9A8F8E
NOTE: this is original M$ image.
by WZT

The Only Workaround: If you are syspreping a computer and using audit mode, you could run it manually while in audit mode before syspreping the computer to capture recovery image. I say this since you work on pc's Mister X. I only do custom recovery's personally and this is how I would do it if I had to. Now if needing to install apps during like the usual way using setupcomplete or firstlogon commands you then need to set a reg entry to install those apps during run after login while in audit mode before capturing recovery image. I think you know how to do that if needed, if not, here is the reg entry path to enter and run your cmd file.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce

 

I am getting all kinds of pm's about this project not working on csl iso's....contact M$ and complain.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Ok thanks for all !
I integrate OEM project with Windows Loader in all my Iso of Windows to repair the computers

 

I have successfully created an x86 and x64 OEM DVD and they work perfectly. I am making an x86/x64 AIO DVD. Do I put the OEM folder in both the sources folder and the source64 folder or just in one or the other? Also should the ei.cfg file be removed from sources folder and the source64 folder? Thanks

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

This project of yours would be just impressive xinso. Why don't you PM cerberus8855, I assume his a close friend of searchengine, and tell your intentions?

 

EDIT: OK. I quit. Thanks.

 

Correct, I am not searchengine but I think as long as you give credit to searchengine for his work, I don't think it would be a problem. Personally I don't need the hooker in oobe.cmd file for I use audit mode if needed to do activations so not to have to worry about backing up tokens.

 

Thanks, cerberus8855.

Would you mind givin' me more hint for "use audit mode if needed to do activations"?

Thanks.

 

You need to login to view this posts content.

 

Hi. Tried to install fresh windows with oem folder added to iso. But nothing happened. No logos no certs no key. Seems like your scrypt does not work with my laptop. Checked query tool and it does not find slic 2.1 in my bios, despite slictoolkit. Could you tell where manually I need to put files of logos and sertificates for my Compaq laptop?

 

Is your bios slic 2.1 ?

 

It should work on any edition of Windows 7 and Windows 8.x except for Single Language edition, you won't get neither oem branding nor oem activation.

 

Need more info....export what slic tookit said and post it in code tags. Post what the query tool said in code tags as well. Also what OS are you trying to install? Did you mod your bios with slic 2.1? There are a lot of factors.

 

The instructions don't say it has to be a multi language edition. Nor do you have to use any script commands unless you want an unattended install.
Isn't moving the $OEM$ folder all that's required?