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

You need to login to view this posts content.

 

Hi, Everyone I made a w7 multi-oem iso using the files on this page. everything works fine,
but when i look in personalize the screensaver has a red circle and line threw it with the word none under it.
but the strange thing is the screensaver works?

thanks in advance for any help.

 

hi there, i wonder if it's possible run this project on a system already installed? and if so, how can do it?
Thanks for the effort and support.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Great! It Works like a charm

 

Creat work keep ON

 

Thank you very much
exactly what I need

 

Unfortunately, searchengine turned in his user status.
If you are good at modding, you can find the hardware ids and such and make the extra folders and stuff for newer manufacturers though...
Then you just copy the various filenames and formats for the images.

 

I am going to look into this to see if I can get it working with win 10...cant do anything about the tool but I can update the oobe.cmd file.

 

Very much appreciated my friend.

 

I agree !

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

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.