The $oem$ folder would need to be included in both source folders (one for x86 and one for x64). The project is very small so it wont take up that much room.
well, I went through this all thread some time ago and I would like to tell you Guardian and all collaborating others on this project BIG THANK YOU. I was really missing something as universal recovery media for my needs at work. If its PCs official at work they are covered by WDS, if its concerning the private laptops from my boss and above him, its hard. When hardware is OK, the laptops can be reinstalled from recovery partition with small overhead. When is damaged, its really annoying to get system back to good shape by hand. And try to tell big boss, you wont do it. So this is very good help + some drivers and Voila! Best regards K.
If this activation method fails, is it possible to make it use Windows Loader? If so, how do I add it?
You can add windows loader to scripts folder. Add a setupcomplete.cmd with code to install windows loader (instructions are in the readme file of windows loader by Daz).
I have other things already in the scripts folder... the code daz suggests is Code: @ECHO OFF %~dp0"Windows Loader.exe" /silent /preactivate cd %~dp0 attrib -R -A -S -H *.* SHUTDOWN /R /T 5 RMDIR /S /Q "%WINDIR%\Setup\Scripts" exit What part of his code should I remove so it don't conflict with my current stuff and where should I put his code? Code: @echo off wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2533552-x64.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2819745-x64-MultiPkg.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB947821-v34-x64.msu" /quiet /norestart /nobackup "%WINDIR%\Setup\Files\ChromeStandaloneSetup.exe" /silent /install "%WINDIR%\Setup\Files\driver_booster_setup.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP- "%WINDIR%\Setup\Files\MSEInstall.exe" /s /q /o /runwgacheck "%WINDIR%\Setup\Files\NDP46-KB3033091-x86-x64-AllOS-ENU.exe" /q /norestart wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2592687-x64.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2965788-x64.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2984976-x64.msu" /quiet /norestart /nobackup "%WINDIR%\Setup\Files\Windows-KB890830-x64-V5.24.exe" /q "%WINDIR%\Setup\Files\AdbeRdr11010_en_US.exe" /msi EULA_ACCEPT=YES /qn "%WINDIR%\Setup\Files\AdobeAIRInstaller.exe" -silent "%WINDIR%\Setup\Files\install_flash_player_17_active_x.exe" /qn /norestart "%WINDIR%\Setup\Files\install_flash_player_17_plugin.exe" /qn /norestart "%WINDIR%\Setup\Files\jre-8u45-windows-x64.exe" /s /qn ADDLOCAL=ALL IEXPLORER=1 MOZILLA=1 JAVAUPDATE=0 REBOOT=suppress "%WINDIR%\Setup\Files\spybotsd162.exe" /verysilent "%WINDIR%\Setup\Files\vlc-2.2.1-win64.exe" /L=1033 /S "%WINDIR%\Setup\Files\Silverlight_x64.exe" /q rd /q /s "%WINDIR%\Setup\Updates" rd /q /s "%WINDIR%\Setup\Files" del /q /f "%WINDIR%\Setup\Scripts\SetupComplete.cmd"
Think you should ask questions about his loader on his thread because this has nothing to do with the multi oem project. I would personally add it to the end of your script since it changes the working directory to where the script is located but you can always change it back. Its up to you. There is no reason to add the rmdir of scripts folder because the multi oem project does that on first login incase users want to install apps like yourself (it cant remove the scripts folder because the cmd file is being ran from it thus empty script folder will remain). Just some suggestions.
Thank you, I guess you are correct and I should post there instead... If anybody is curious this is the code I used and it seems to work Code: @echo off "%WINDIR%\Setup\Files\NDP46-KB3033091-x86-x64-AllOS-ENU.exe" /q /norestart wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2533552-x64.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2819745-x64-MultiPkg.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB947821-v34-x64.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2592687-x64.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2965788-x64.msu" /quiet /norestart /nobackup wusa.exe "%WINDIR%\Setup\Updates\Windows6.1-KB2984976-x64.msu" /quiet /norestart /nobackup "%WINDIR%\Setup\Files\Windows-KB890830-x64-V5.24.exe" /q "%WINDIR%\Setup\Files\Silverlight_x64.exe" /q "%WINDIR%\Setup\Files\ChromeStandaloneSetup.exe" /silent /install "%WINDIR%\Setup\Files\AdbeRdr11010_en_US.exe" /msi EULA_ACCEPT=YES /qn "%WINDIR%\Setup\Files\AdobeAIRInstaller.exe" -silent "%WINDIR%\Setup\Files\install_flash_player_17_active_x.exe" /qn /norestart "%WINDIR%\Setup\Files\install_flash_player_17_plugin.exe" /qn /norestart "%WINDIR%\Setup\Files\jre-8u45-windows-x64.exe" /s /qn ADDLOCAL=ALL IEXPLORER=1 MOZILLA=1 JAVAUPDATE=0 REBOOT=suppress "%WINDIR%\Setup\Files\vlc-2.2.1-win64.exe" /L=1033 /S "%WINDIR%\Setup\Files\MSEInstall.exe" /s /q /o /runwgacheck "%WINDIR%\Setup\Files\spybotsd162.exe" /verysilent "%WINDIR%\Setup\Files\driver_booster_setup.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP- rd /q /s "%WINDIR%\Setup\Updates" rd /q /s "%WINDIR%\Setup\Files" %~dp0"Windows Loader.exe" /silent /preactivate cd %~dp0 attrib -R -A -S -H *.* SHUTDOWN /R /T 5 del /q /f "%WINDIR%\Setup\Scripts\SetupComplete.cmd" If I did add it to the top portion, how do I switch the directory back to the current one tho? You seem to know a lot about the batch files? Again, thank you in advance
Change current directory by cd /d %windir%\ this would change the current directory to Windows folder...make sure to add the \ at the end or it fails.
Sorry to sound like a noob but before one does any editing is the windows included with these downloads or does one need to have an windows iso file/disk beforehand ? Thx
You need to get the ISO yourself then add this project ($oem$ folder) to the sources folder of the ISO.
That what I thought but I had to ask to be sure. Will it still work with an retail windows version ? thanks
To my knowledge any oem pack will work with Windows Vista - 10 no problem. The only issue is if the configuration of the setupcomplete is correct (and scripts there after). That being said Multi OEM will work without any issues After glancing at the coding for the Multi OEM Pack the coding is very tight. I see no issues here. Now I almost wish my vacation was longer lol
Ive used x64 and x86 version of OEM Dell Win7 and replaced the OEM folder ei.cfg removed. It works perfectly, just played inside VMware with modded bioses from another thread. The advantage which is really handy is multilang version without need the Ultimate. Thats for license reasons when recovery OEM hardware would be needed. Still there are many threads to study on this site, just why I didnt discover this forums bit earlier.... Very good well of knowledge of Microsoft recent systems. PS: The graphic themes are also really great even VMware one - just for this one Id need an KMS environment Perfect work
According to M$ system requirements for the new win 10, will use similar to win 8.x as far as oem activation so that is cool. Less work I have to do in the future. I expect the kms solution to change but not the oem activation.
The problem you'll face LOL I guess all of us, is OEM skus. Maybe it'll be very hard to find them because I assume M$ is going to push exotic editions just like in Win8.x
Yep will be similar to win8.x but given time they to will be available. Some things we have to learn patience with.