Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


mhyll

Member
  • Content Count

    32
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mhyll

  • Birthday 03/01/1983
  1. Once again, I wrote little batch file to slipstream language pack to Windows 7. For now, it's working on x86 system. To make it work on x64, just change "x86" in command paths to "x64". Note: You can slipstream x64 MUI to x64 DVD in x86 environment. Note 2: Starter edition is not in x64 Windows 7, so it's as in the batch-1. Requirements: Windows AIK for Windows 7 (RC version 7100 will work also - tested) Windows 7 RTM DVD Windows 7 MUI pack you want to install Create just this one CMD file: @echo Off echo Enter WAIK installation directory (default: C:\Program Files\Windows AIK): echo ========================================================================== set /p WAIK= echo. echo Enter path to mount point (ie: C:\WORK\MOUNT): echo ============================================== set /p WIM= echo. echo Enter Windows 7 DVD directory (ie: C:\WORK\DVD): echo ================================================ set /p WD= echo. echo Enter full path to MUI file (ie: C:\WORK\LP\lp.cab): echo ==================================================== set /p LP= echo. echo Enter temporary directory for extracted MUI (ie: C:\WORK\LPEXT): echo ================================================================ set /p ELP= echo. echo Enter MUI ID you're installing (ie: en-us): echo =========================================== set /p LANG= echo. echo Enter Windows Edition to modify (ie: 1): echo ======================================== echo LIST OF EDITIONS: echo 1 - STARTER echo 2 - HOMEBASIC echo 3 - HOMEPREMIUM echo 4 - PROFESSIONAL echo 5 - ULTIMATE echo ======================================== set /p EDITION= echo. "%WAIK%\Tools\x86\Servicing\dism.exe" /Mount-Wim /WimFile:"%WD%\Sources\install.wim" /index:%EDITION% /MountDir:"%WIM%" "%WAIK%\Tools\x86\Servicing\dism.exe" /image:%WIM% /Add-Package /PackagePath:"%LP%" "%WAIK%\Tools\x86\Servicing\dism.exe" /image:%WIM% /Gen-LangIni /Distribution:"%WD%" "%WAIK%\Tools\x86\Servicing\dism.exe" /image:%WIM% /Set-AllIntl:%LANG% "%WAIK%\Tools\x86\Servicing\dism.exe" /image:%WIM% /Set-TimeZone:"Central Europe Standard Time" "%WAIK%\Tools\x86\Servicing\dism.exe" /image:%WIM% /Set-SetupUILang:%LANG% /Distribution:"%WD%" "%WAIK%\Tools\x86\Servicing\dism.exe" /image:%WIM% /Gen-LangIni /Distribution:"%WD%" "%WAIK%\Tools\x86\Servicing\dism.exe" /image:%WIM% /Get-Packages /Format:Table "%WAIK%\Tools\x86\Servicing\dism.exe" /image:%WIM% /Get-Intl "%WAIK%\Tools\x86\Servicing\dism.exe" /Unmount-Wim /MountDir:"%WIM%" /commit rd /S /Q "%ELP%" mkdir "%ELP%" expand "%LP%" -f:* "%ELP%" xcopy "%ELP%\setup\sources\%LANG%\*" "%WD%\sources\%LANG%" /cherkyi xcopy "%ELP%\sources\license\%LANG%\*" "%WD%\sources\license\%LANG%" /cherkyi "%WAIK%\Tools\x86\Servicing\dism.exe" /Mount-Wim /WimFile:"%WD%\Sources\boot.wim" /index:2 /MountDir:"%WIM%" xcopy "%ELP%\setup\sources\%LANG%\*" "%WIM%\sources\%LANG%" /cherkyi xcopy "%ELP%\sources\license\%LANG%\*" "%WIM%\sources\license\%LANG%" /cherkyi copy "%WD%\sources\Lang.ini" "%WIM%\sources\Lang.ini" "%WAIK%\Tools\x86\Servicing\dism.exe" /Unmount-Wim /MountDir:"%WIM%" /commit rd /S /Q "%ELP%" mkdir "%ELP%" echo ======================================== echo === End of language pack integration === echo ======================================== pause Enjoy!!!
  2. mhyll

    vLite 1.1 beta - vBloat

    Thanks for sharing your knowledge. I am again a bit smarter.
  3. mhyll

    vLite 1.1 beta - vBloat

    no, read my post and you will know, which file is being installed when you run the update. PLS, can you explain GDR and QFE????
  4. mhyll

    vLite 1.1 beta - vBloat

    Ok...I installed the original Windows Vista and run through Windows Update. It's still the same. I don't know, what's happening. C:\WINDOWS\SYSTEM32\SHELL32.DLL -> ver. 6.0.6000.16513 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16386_none_69f268e21510dceb\SHELL32.DLL -> ver. 6.0.6000.16386 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16513_none_6a3b1b4414dac79d\SHELL32.DLL -> ver. 6.0.6000.16513 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20628_none_6abee9952dfc020b\SHELL32.DLL -> ver. 6.0.6000.20628 Any idea now???? It is situation AFTER REGULAR WINDOWS UPDATE!!! Is Windows using the newest one in WinSXS directory or what??? OK. EVERYTHING IS OOOOOK!!!! Looked into the _MANIFEST_.CIX.XML file in WINDOWS6.0-KB938979-X86.CAB. It contains BOTH versions, 16513 and 20628!!! Both SHELL32.DLL files are axactly tha same size!!! So probably, this are the same, but for different Vista editions. Here is the proof from that XML file. - <File id="108" name="x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20628_none_6abee9952dfc020b\shell32.dll" length="11315200" time="128273842777710000" attr="32"> <Hash alg="SHA1" value="a6dd82a2bb7b02b7efb6f6205e303cb87c9e38f0" /> - <Delta> - <Source type="PA30" name="42"> <Hash alg="SHA1" value="cab075ad886b13bf7db2da4b9c571cb06b70f83f" /> </Source> <Basis file="4" /> </Delta> </File> - <File id="107" name="x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16513_none_6a3b1b4414dac79d\shell32.dll" length="11315200" time="128273846077560000" attr="32"> <Hash alg="SHA1" value="22933024bd51ac73495a9884c93b35e4560ed7ec" /> - <Delta> - <Source type="PA30" name="43"> <Hash alg="SHA1" value="4dd27a5e3b3d97cef91866f2e0c65c856145da39" /> </Source> <Basis file="108" /> </Delta> </File> The same is also with other files packed in this hotfix. So hotfixes are fine, 16513 is the RIGHT version of the file. I am happy.....great work NUHI....but if it possible to somehow clean out those old versions, it would be great.
  5. mhyll

    vLite 1.1 beta - vBloat

    Ok...I installed the original Windows Vista and run through Windows Update. It's still the same. I don't know, what's happening. C:\WINDOWS\SYSTEM32\SHELL32.DLL -> ver. 6.0.6000.16513 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16386_none_69f268e21510dceb\SHELL32.DLL -> ver. 6.0.6000.16386 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16513_none_6a3b1b4414dac79d\SHELL32.DLL -> ver. 6.0.6000.16513 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20628_none_6abee9952dfc020b\SHELL32.DLL -> ver. 6.0.6000.20628 Any idea now???? It is situation AFTER REGULAR WINDOWS UPDATE!!! Is Windows using the newest one in WinSXS directory or what???
  6. mhyll

    vLite 1.1 beta - vBloat

    Can you explain more please? I've found more SHELL32.DLL files on my system: C:\WINDOWS\SYSTEM32\SHELL32.DLL -> 6.0.6000.16513 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16386_none_69f268e21510dceb\SHELL32.DLL -> 6.0.6000.16386 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16513_none_6a3b1b4414dac79d\SHELL32.DLL -> 6.0.6000.16513 C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20628_none_6abee9952dfc020b\SHELL32.DLL -> 6.0.6000.20628 Which one is system using????????? NUHI, can you do something with this??? I am thinking, that Windows is using the one in %WINDIR%\SYSTEM32 folder, so not using the newest version. Have tried integration with WUI 0.9.2.5 (Vista Update Integrator)...and it is the same. Starting VirtualPC and I am going to install clean original Vista, and then I will install the updates manually....I will post the report.
  7. mhyll

    Suggestion box (vLite)

    System Restore...not to remove it, but option to keep, but disable.... Disk defragmenting...disable automatic disk defragmenting Services...able to set services startup behavior (as in nLite)...I want to disable SuperFetch, but not to remove it (I hate it, because it does lot of hard drive trashing...and I don't see any performance differences)
  8. Just unpack it by using a tool like 7-zip or WinRar. By doing this you'll not get a CAB file, but more than 10.000 files included in Language Pack. You must run the EXE file, an it will create a temporary LP.CAB. This you must copy somewhere else.
  9. They have WAIK as prerequisite. I used it without WAIK.
  10. Hi Nuhi...me again. You maybe take a look on Vista Update Integrator 0.8.1.3 Beta. The're not using any of MS files (I cannot see them in install folder)...but it's working.
  11. First, see examples in batch. But to you: path for mount will be C:\VistaWork\Mount path for lp.cab should be exact, in your case C:\VistaWork\LP\lp.cab path for extracting..you're right, create C:\VistaWork\LPEXT lang id in your case is zh-HK (remind..lang id are alway first two letter small and second two with CAPITAL) For everyone example of the working directory structure: x:\VistaWork\DVD - here you copy Vista DVD x:\VistaWork\LP - here you copy lp.cab of your language pack x:\VistaWork\LPEXT - lp.cab will be extracted here during process x:\VistaWork\MOUNT - will be used for mounting WIM images I'm working on a script, that will create working structure itselfs independently on location, in the current directory of command file.
  12. Sure it is. I just wasn't looking on this. PEIMG and PKGMKR is the key.
×
×
  • Create New...