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

OOBE.cmd (incorrect entry)

Code:

%RQR1% | findstr /I "\<WINDOWS\>" | findstr /I "\<10\>" >nul&&%INL% SET WINVER=10&goto :BIOS

Manufacturer theme is applied despite this error, because of entries:

Code:

IF NOT DEFINED WINVER GOTO :BRANDING
IF NOT DEFINED EDITION GOTO :BRANDING
IF /I "%WINVER%"=="VISTA" goto :TRANSFER3
IF /I "%WINVER%"=="7" goto :TRANSFER3

 

You are correct and wrong at the same time...let me explain.

The reason behind not using technical preview is because its just a preview not the actual final OS so I added the above line to be ready for win 10 when final is released.

This is why it applies regardless which is correct also for it is still a not defined windows version so it goes to branding where it will check for oem-dm key in bios (which doesn't exist yet for it is technical preview only) and if exist applies oem-dm key. This might not work in win 10 final depending if they keep the same scheme for oem activation or not. No way to test this yet in a technical preview.

This replaces the if /I not "%winver%"=="8" goto :TRANSFER3 because it is needed for win 10 as well but not for vista or win 7 so it goes to :TRANSFER3 for those.

I knew a few out there would complain but now maybe you see why I did it the way I did (its made for future FINAL win 10 when released).

 

I understand your logic.

OOBE.cmd :TRANSFER3
aero.theme is temporarily renamed to theme3.theme

OEM-Sync.exe
has function to return theme3.theme to original theme name, but only after it checks if system is Win8x.
has function to apply OEM-DM key, but only after it checks if system is Win8x.

 

I think you are misunderstanding the default windows theme...the only time windows theme will be installed is if the machine has No oem match (this is the same for vista, win 7, win 8.x and win 10 when released). If oem machine found then it will apply that theme and info thus making backups like for example your theme3.theme (aero). I have done nothing to the script in this area...its still original. The oem-sync.exe has nothing to do with the themes being applied, only info for slic table and oem-dm key info and apply if found. There was only small changes made for it to work with windows 10...compare it to the original and you will see.

 

I understand you changed nothing on OOBE.cmd :TRANSFER2 section, but if Manufacturer brand discovered, then the script renames aero.theme to theme3.theme, and names the discovered Manufacturer theme as aero.theme, thus Windows shows Manufacturer theme as default theme at first desktop view. The OEM-Sync.exe initiates a runonce instruction to rename theme3.theme back to aero.theme, and rename the Manufacturer theme to $OEM$.theme on first reboot, thus correcting file names whilst keeping Manufacturer theme applied. It will not do this last part as it does not check for Windows 10.

 

The oem-sync.exe does nothing with themes or images just looks for oem-dm key in bios and if exist applies the key....that is all the oem-sync.exe does period. Everything else is done by the script. Remember you are probably using win 10 technical preview which is called windows technical preview thus why it doesn't find "10" and defaults to undefined version. I am not adjusting the script just for technical preview but for final windows 10 when released. Do you understand? The script runs exactly as it should for right now...might need more adjusting once windows 10 final is released.

 

Thank you thank you thank you
Please don't abandon this beautiful project...

 

First off its not my project but I just picked it up since no one was working on this anymore. I will do what I can. Take care Mr. X.

 

I know actually this is not your project, it's searchengine's project. What I meant in my previous post is due you've been contributing in the past to it, I know that just by making observations and comments to searchengine, please re-take it and keep it up my friend. Take care you too.

 

If you install Win8x, and look in your Windows folder, before you reboot, you will find W82THM.cmd and if you look in registry you will see a runonce instruction to run this cmd file.

Instructions on cmd file:

Code:

@echo off 
 
if exist "C:\Windows\Resources\Themes\theme3.theme" ( 
   takeown /F "C:\Windows\Resources\Themes\*.theme" >nul 
   ICACLS "C:\Windows\Resources\Themes\*.theme" /reset /T /Q >nul 
   ICACLS "C:\Windows\Resources\Themes\*.theme" /grant:r "C:\Windows\Resources\Themes\*.theme:(OI)(CI)F" 2>nul 
   REN "C:\Windows\Resources\Themes\aero.theme" "$OEM$.theme" >nul 
   MOVE /Y "C:\Windows\Resources\Themes\theme3.theme" "C:\Windows\Resources\Themes\aero.theme" >nul 
) 
 
del /F /Q "C:\Windows\W82THM.cmd" >nul

OEM-Sync.exe responsible for this action, and also performs a similar action if Vista installed to rectify img24.

 

You need to login to view this posts content.

 

Does anyone have valid links to the files from post #1? Need to do some "research". Thanks in advance.

 

I will upload tomorrow if no one else beats me to it. lol

In the future I will post an updated version of this project that will not use oem-sync but instead be ran from oobe script. There is no hurry for now for windows 10 is only technical preview which is time bombed. I am not really concerned with this as of yet but when it becomes final I will update the project myself if no one objects. Searchengine done a fantastic job and I wish he was still here but that isn't the case. He will truly be missed. With that being said, I don't want to offend anyone here but I cant see this project just being dropped and no one else wanting to pick it up.

 

You need to login to view this posts content.

 

Script and oem-sync works as it should...why all the questions? I am sure since nothing else is in the scripts folder with only a blank oobe file he put in place a method if something didn't exist do something which is probably why you are seeing the other cmd file...this is a guess though because the theme is transferred in the original oobe.cmd file so that is redundant. He was and is a smart scripter and is highly missed. There is no use in asking anymore questions regarding the oem-sync for he is the creator of that exe and only he can answer your questions. Script works and that is what counts. I will not reply to these questions anymore for I cant answer them, nor can anyone else here. The source was never released before his leaving.

 

Sorry, wasn't trying to ask any questions, was trying to point out that OEM-Sync.exe performs some runonce instructions for various OS's with some self deleting batch files, that return some file names back to normal [previously altered by OOBE.cmd to apply themes], and that Win10 would have no such instructions built-in to OEM-Sync.exe.

 

Depends on how he wrote it. Technical Preview isn't in the list I know for a fact, nor in the oobe.cmd so if it didn't work (regarding themes which is the main point of your questions, I am more concerned with activation method personally, I can make the script transfer themes but activation is another story) I would have had normal windows theme applied. See either way it works but I am more concerned about the oem activations....images we can figure out easy, IF there ever is a true issue with it.

You are only seeing some of the files used for the oem-sync for it is a compiled project into one exe....who knows maybe autoit....the main point is there are more instructions then what you are catching. I will leave it at that and say good night.

 

I have decided to get rid of the oem-sync for two reasons..obviously no source code was shared but more importantly, oem-sync showed as virus on some AV's (this is a false positive of course but noobs still freak out, lol). I have decided to go with getwin8key.exe and dll or just Rw.exe instead which are both clean on virus total results. Then it will apply key if needed. Everything will be open source so if I decide to drop this project someone else can pick it up. Its all about sharing info. I will be re-creating the tool also just to let everyone know (open source as well). Nothing will be hidden thus why I call it open source.

Special thanks goes out to xinso for all his help. Two brains are better then one.


If anyone has any new oem images that they would like to share for this project now is the time to share them before I compile the new oem project (I will be posting in the next few weeks).

 

I am having one issue that I cant figure out....how do I output max screen resolution to a txt file? I cant use wmic for it is disabled. I need another method...

I remember searchengine saying he had issues of the same a while back and he found a solution but did not share it...I think he used autoit to resolve it but I don't want to use that or else the exe will show as virus on some AV's. That's the reason I am looking for a alt. method.

Update: Ok, I finally got a vbs file to work that checks for max screen resolution and outputs to a text file so it can be used in script to apply correct size images. I know searchengine used rweverything but why did he dump a slic for win 8.x machines? There is no slic for win 8.x, key is in msdm dump....hummmmm. I really do believe the oem-sync was used for something else as well. I just noticed the same with the tool...it shouldn't dump the slic for no table exist. Anyways, this is old news but caught my eye.
Its all coming together now.