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

Well this is true and I agree with you and all my due respects to him, all the best for him.

 

You need to login to view this posts content.

 

Oh, could you do that, please? I can't believe this either. Let me tell you I didn't know him at all but his work is awesome and speaks by itself.

 

I'll see what I can do. Hopefully, I still have the number somewhere. Not promising anything tho.

 

Windows 8.1 with Update [CSL-Core-Pro AIO] x64 for OEM machines

I did my Windows 8.1 with Update [CSL-Core-Pro AIO] x64 dedicated for OEM machines (UEFI) with the following sku selection screen:
Windows 8.1 Single Language with Update
Windows 8.1 with Update
Windows 8.1 Pro with Update

ei.cfg file is the same used in this Multi-OEM project:

Code:

[EditionID]


[Channel]
OEM
[VL]
0

I am testing on VM for a first stage. The problem is with sku CSL, no OEM branding as expected as the other skus.

Any thoughts?

 

Can you tell me the actual name of win 8.1 single lang. from windows after you installed it. Like does it say Windows 8 Single Lang or something else from the information window? I don't have that ISO so I cant test....kinda guessing for now. Need to know what the actual name that version in windows to understand more. Thx.

If I cant tell from that info, could you possibly upload somewhere so I could test it in VMware...since I don't have that version. Would make it easier and faster to troubleshoot myself.

Just from what you said above it looks as if the script is breaking before the branding. Probably at the check version but not for sure. I'm shooting in the dark for I don't have that ISO to test.

 

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.