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

Discussion in 'MDL Projects and Applications' started by searchengine, Jan 30, 2010.

Thread Status:
Not open for further replies.
Page 57 of 115
  1. rulman

    rulman MDL Member

    Jan 25, 2012
    103
    22
    10
    #1121 rulman, May 10, 2012
  2. noitamina

    noitamina MDL Novice

    May 11, 2012
    1
    0
    0
    #1122 noitamina, May 11, 2012
  3. searchengine

    searchengine Guest

    #1123 searchengine, May 11, 2012
    Last edited by a moderator: May 11, 2012
    (OP)
  4. hlmasterchief93

    hlmasterchief93 MDL Novice

    Jan 15, 2012
    10
    8
    0
    #1124 hlmasterchief93, May 15, 2012
    hello, can i use this on already installed computer ?
     
  5. Tito

    Tito Admin / Adviser
    Staff Member

    Nov 30, 2009
    19,012
    19,687
    340
    #1125 Tito, May 15, 2012
    Obviously... :)
     
  6. redroad

    redroad MDL Guru

    Dec 2, 2011
    5,326
    6,045
    180
    #1126 redroad, May 15, 2012
    Last edited: May 15, 2012
  7. hlmasterchief93

    hlmasterchief93 MDL Novice

    Jan 15, 2012
    10
    8
    0
    #1127 hlmasterchief93, May 16, 2012
    so how to use it ? just run OOBE.cmd within wins 7 ?
    thank you :)
     
  8. Tito

    Tito Admin / Adviser
    Staff Member

    Nov 30, 2009
    19,012
    19,687
    340
    #1128 Tito, May 16, 2012
    Last edited by a moderator: Apr 20, 2017
    No no.. slightly manual process :D

    Go to $oem$\$$\Setup\scripts\MultiBrand_OEM's\, choose your brand (for example ASUS), then paste the following files & folder in %WinDir%\system32\oobe\info

    Code:
    Backgrounds
WALLPAPER.jpg
ASUS_BADGE.png
ASUS_MCE_LOGO.png
ASUS_BADGE.bmp
ASUS_BAR.bmp
USER.bmp
    Also copy ASUS.theme to %WinDir%\Resources\Themes; edit ASUS.reg by Notepad to add your system model etc & merge it.

    :)
     
  9. SteveDun777

    SteveDun777 MDL Novice

    May 16, 2012
    2
    0
    0
    #1129 SteveDun777, May 16, 2012
    Last edited: May 16, 2012
    I am new here to this forum but luv all the info here. I have found a bug in vista oem activation.....I tested vista with your addon $oem$ folder and when at desktop at end of installation it show background pic but if you reboot or right click on desktop and choose personalize to open display info it doesnt show the installed background pic. Even if you just close the personalize display info window\Background it will kick out the theme or background pic that your script installs. Does this on vista only and with all oem and custom themes. Win7 installs correctly. Any suggestions would be great. Thanks for the hard work u have shared.

    Fix: If I apply the theme manually in display options then it will stay installed. Guess Vista is temperamental. Sorry for buggin ya.
     
  10. searchengine

    searchengine Guest

    #1130 searchengine, May 16, 2012
    Last edited by a moderator: May 20, 2012
    (OP)
    it's not a bug as such, it's more of a workaround... Vista themeing|activation is more problematic than Windows 7 (from $oem$ install method), because Microsoft have disabled customization features in Vista, that are enabled in Windows 7. Activation for Vista is done by using 'setupcomplete.cmd' to use slmgr to install specific serial and certificate, because Microsoft disabled ability to run slmgr to apply activation during oobe.cmd process. Themeing in Windows 7 is easy because registry can be edited to apply specific brand or custom theme as default, but registry edits to do the same in Vista don't work. The themeing 'workaround' for Vista is that oobe.cmd renames img24.jpg (Vista Default Wallpaper image) to img24.bak and puts a copy of the brand or custom 'Wallpaper' in it's place, therefore when you logon for first time, the brand or custom 'Wallpaper' is displayed as default, at the same time Display.exe deletes the img24.jpg and renames img24.bak to img24.jpg., thus returning Vista default Wallpaper. Display.exe then silently applies the brand or custom 'Wallpaper' as your preferred desktop background. Your brand or custom theme is available from dropdown selection, as is original Vista default theme.
     
  11. SteveDun777

    SteveDun777 MDL Novice

    May 16, 2012
    2
    0
    0
    #1131 SteveDun777, May 16, 2012
    Thank you for explaining this in detail to me. I understand now. I choose the theme manually from display options and it applied. Thanks for the hard work you put into this.
     
  12. wish-master

    wish-master MDL Novice

    Dec 15, 2011
    3
    0
    0
    #1132 wish-master, May 17, 2012
    Last edited: May 17, 2012
    You downloaded the file several times
    And using many of the browsers
    The file error 889
    Hash does not match
    Is it possible to remove the file again to download the latest center
    Or on the torrent
     
  13. Tito

    Tito Admin / Adviser
    Staff Member

    Nov 30, 2009
    19,012
    19,687
    340
    #1133 Tito, May 17, 2012
  14. wish-master

    wish-master MDL Novice

    Dec 15, 2011
    3
    0
    0
    #1134 wish-master, May 17, 2012
  15. wish-master

    wish-master MDL Novice

    Dec 15, 2011
    3
    0
    0
    #1135 wish-master, May 17, 2012
    The file error hash
    File is corrupt
    :worthy:
     
  16. tcntad

    tcntad MDL Guru

    Oct 26, 2009
    4,694
    1,704
    150
    #1136 tcntad, May 17, 2012
    No it isnt, my CRC32/MD5/SHA1 checks matches the file..

    Instead of just coming here when it mismatches, download and try again, if it does download on another computer.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. HALIKUS

    HALIKUS MDL Addicted

    Jul 29, 2009
    526
    372
    30
    #1137 HALIKUS, May 22, 2012
    Great package that i have been using for what seems like a few years now. I have noticed though that lately there are more and more GPT\UEFI combos (my motherboard included) and that the Daz loader will freeze the installation when run as it is incompatable with GPT\UEFI (Win7), Enterprise (Win7), and Windows 8. Is there any code we can add to SetupComplete.cmd that will check the OS and drive partitioning so that it only runs on Win7\Vista\etc MBR\BIOS? I know in autoit i can use a command such as

    If @OSVersion <> "WIN_7" Then
    MsgBox(48, "Windows 7", "This will only work on Windows 7", 1)
    Exit
    EndIf

    ...to close if it is not Win7. Is there a cmd equivalent, and a command to check the partitioning? Then it will be a truly universal $OEM$ folder and i won't have to delete the loader before installing the incompatible OS's from my install.wim.
     
  18. searchengine

    searchengine Guest

    #1138 searchengine, May 24, 2012
    Last edited by a moderator: May 24, 2012
    (OP)
  19. HALIKUS

    HALIKUS MDL Addicted

    Jul 29, 2009
    526
    372
    30
    #1139 HALIKUS, May 24, 2012
    Last edited: May 24, 2012
    @searchengine, your assumptions were right about silent mode, and the only way to close it is a reset; the loader locks the system during setupcomplete.cmd. That script may be exactly what im looking for (or at least a piece of the puzzle), i just don't have the time to do any VM tests for a day or so. My other workaround i was considering was to have setupcomplete run an autoit exe (that i am more familiar with) to run the loader and decide whether or not to run it.

    I currently use a Winbuilder PE (x86 mainly, x64 for EFI) to install with, and have a custom gui. The boot.wim has an X: ramdrive, so in my gui, if i select Win7 (or Win 8) it extracts the proper sources dir (depending on the PE arch) to x:\sources, and i already have an $OEM$ folder in x:\sources\$OEM$, along with $OEM$w7x86, $OEM$w7x64, $OEM$w8x86, and $OEM$w8x64. It will copy the x86 $OEM$ folder to $OEM$, and then run x:\sources\start.exe with an autounattend and my gui adds a proper key to the xml. I have modded start.exe and autorun.dll so that i can rename start.exe to (ie : ) w7x86.exe where i have a corresponding file in the same directory as install.wim (i have 4 exe's, boot.wim, and install.wim in DVD\sources) so i can install Win7\8 x86\x64. It also runs a few autoit scripts that look for $winRoot\WinPEpge.sys and then copies the $OEM$ to $winRoot\$Windows.~LS\Sources\$OEM$. If its Win8, it deletes Daz loader. If its x64 im installing, it looks for $winRoot\Windows\SysWOW64 and it copies the x64 $OEM$ folder to $winRoot\$Windows.~LS\Sources\$OEM$. The install goes fine, it runs the loader, but if its GPT or enterprise the loader hangs. The script you supplied can maybe be run during the $OEM$ copy to check for GPT and will delete the loader.
     
  20. searchengine

    searchengine Guest

    #1140 searchengine, May 25, 2012
    Last edited by a moderator: Apr 20, 2017
    (OP)
    @HALIKUS...

    I think the ideal solution would be if when 'Windows Loader.exe' is ran in 'silent' mode from 'SetupComplete.cmd', that it self aborted, and self closed when 'unsupported OS, or incompatibility' is encountered, resulting in no 'freeze', no harm; thus allowing remainder of setup to continue.

    however, the following example 'SetupComplete.cmd', may workaround your difficulties.

    SetupComplete.cmd - example
    Code:
    @echo off

::clear
SET INL=
SET RQR1=
SET RQR2=
::begin
SET INL=IF NOT ERRORLEVEL 1
SET RQR1=REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "ProductName"
SET RQR2=REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "EditionId"

:CHECK1
::check activation status
WMIC /NAMESPACE:\\root\CIMV2 PATH SoftwareLicensingProduct WHERE LicenseStatus=1 GET LicenseStatus | findstr "1" >nul
%INL% goto :SKIP

:CHECK2
::check Windows OS -> '8'
%RQR1% | findstr /I "WINDOWS" | findstr /I "8" >nul
%INL% goto :SKIP
::check Windows Edition -> 'Enterprise'
%RQR2% | findstr /I "ENTERPRISE" >nul
%INL% goto :SKIP

:CHECK3
::check for 'efisys' in list volume function -> If it finds it -> check status & if 'healthy' -> goto :SKIP
setlocal enabledelayedexpansion
echo list volume > %windir%\Setup\scripts\listvol.tmp
cd /d %windir%\Setup\scripts\ >nul
for /F "tokens=6-9 delims= " %%G IN ('diskpart /s listvol.tmp') DO IF /I %%G==efisys set mounted=%%J
del /F /Q listvol.tmp >nul
if '%mounted%'=='Healthy' goto :SKIP
endlocal

:LOADER
::run loader, cleanup, reboot
%~dp0"Windows Loader.exe" /silent /preactivate
cd %~dp0
attrib -R -A -S -H *.*
SHUTDOWN /R /T 5
Del /S /F /Q "%windir%\Setup\scripts\*.*" >nul
RMDIR /S /Q "%windir%\Setup\scripts" >nul
Del /F /Q %0% >nul
exit

:SKIP
::executed to 'Skip' running loader, cleanup -> from CHECK1,2,or3
Del /S /F /Q "%windir%\Setup\scripts\*.*" >nul
RMDIR /S /Q "%windir%\Setup\scripts" >nul
Del /F /Q %0% >nul
exit
    Summary
    :CHECK1
    if activated, go directly to :SKIP
    :CHECK2
    if OS is Windows 8, or Edition Enterprise, go directly to :SKIP
    :CHECK3
    if 'efisys' detected, go directly to :SKIP
    :LOADER
    run 'Windows Loader.exe', cleanup, and reboot
    :SKIP
    by-pass running loader, and cleanup
     
Page 57 of 115