Tried this version the driver problem on the HDD was solved perfectly. I don't understand why, if in "config.ini" Code: ; Integrate Windows 8 Dism into XP host ADDDISM=Yes with "capturevhd.com" it crashes here Code: C:\Windows\system32>if "Yes" == "Yes" ( REM Adding Windows 8 DISM xcopy "C:\XP2ESD\apps\dism\*.*" "X:\WINDOWS\system32" /i 1>nul if exist "C:\XP2ESD\apps\dism\it-IT" (xcopy "C:\XP2ESD\apps\dism\it-IT" "X:\WINDOWS\system32\it-IT" /i /s 1>nul ) else (xcopy "C:\XP2ESD\apps\dism\en-us" "X:\WINDOWS\system32\en-us" /i /s 1>nul ) ) last thing, why does it repack the sp3.cab file at the end of the installation if I have more than 4GB? thank you
You need to run script after editing config.ini. These settings are readed only when script starts. Because we need to avoid SFC file replacement. Even with patched SFC I encountered file restore from SP3.cab. Thats why is repacking needed.
Hi! Great tool! Success with v1.5.2 "renamed" for me. I'm using english ISOs and would like to change my timezone, locale and keyboard during setup, if possible. Would like to skip oobe with locale already set. In old days I was using winnt.sif for my unattended iso. Where and what to change? Thanks in advance!
According to input setup language I created automated settings for TimeZone and Keyboard. You can do it after setup in control panel. In standard OOBE these settings are locked, so I unlocked it to be able change these settings very comfortable during last part of setup and also it's same as newer Windows have it. But If you want to build your image in different TimeZone and Keyboard, just locate this part of code in Auto-Sysprep.cmd and for reference look into _docs folder Code: REM Set LanguageGroup and TimeZone if !Language! == "0401" set LanguageGroup=13 && set TimeZone=158 if !Language! == "0404" set LanguageGroup=9 && set TimeZone=210 if !Language! == "0405" set LanguageGroup=2 && set TimeZone=095 if !Language! == "0406" set LanguageGroup=1 && set TimeZone=105 if !Language! == "0407" set LanguageGroup=1 && set TimeZone=110 if !Language! == "0408" set LanguageGroup=4 && set TimeZone=145 if !Language! == "0409" set LanguageGroup=1 && set TimeZone=004 if !Language! == "040b" set LanguageGroup=1 && set TimeZone=110 if !Language! == "040B" set LanguageGroup=1 && set TimeZone=110 if !Language! == "040c" set LanguageGroup=1 && set TimeZone=105 if !Language! == "040C" set LanguageGroup=1 && set TimeZone=105 if !Language! == "040d" set LanguageGroup=12 && set TimeZone=135 if !Language! == "040D" set LanguageGroup=12 && set TimeZone=135 if !Language! == "040e" set LanguageGroup=2 && set TimeZone=095 if !Language! == "040E" set LanguageGroup=2 && set TimeZone=095 if !Language! == "0410" set LanguageGroup=1 && set TimeZone=110 if !Language! == "0411" set LanguageGroup=7 && set TimeZone=235 if !Language! == "0412" set LanguageGroup=8 && set TimeZone=230 if !Language! == "0413" set LanguageGroup=1 && set TimeZone=100 if !Language! == "0414" set LanguageGroup=1 && set TimeZone=100 if !Language! == "0415" set LanguageGroup=2 && set TimeZone=100 if !Language! == "0416" set LanguageGroup=1 && set TimeZone=065 if !Language! == "0419" set LanguageGroup=5 && set TimeZone=145 if !Language! == "041d" set LanguageGroup=1 && set TimeZone=110 if !Language! == "041D" set LanguageGroup=1 && set TimeZone=110 if !Language! == "041f" set LanguageGroup=6 && set TimeZone=130 if !Language! == "041F" set LanguageGroup=6 && set TimeZone=130 if !Language! == "0804" set LanguageGroup=10 && set TimeZone=210 if !Language! == "0816" set LanguageGroup=1 && set TimeZone=085 if !Language! == "0c0a" set LanguageGroup=1 && set TimeZone=105 if !Language! == "0C0A" set LanguageGroup=1 && set TimeZone=105 In my opinion, is best to do it during OOBE
Tool updated to v1.5.3 Added some new info, until I rebuild all UpdatePacks Q: UpdatePack was skipped during nLite integration, why? How to solve it? A: This is caused by forcelang attribute in entries.ini in UpdatePack itself, just remove this line and repack UpdatePack, then try it again. These packs will be repacked soon to avoid this problem! Code: 11.04.2021 - v1.5.3 - Fixed detecting default system language for FIN, FRA, HEB, HUN, SVE, TRK, ESN with these system you should encountered bug as UpdatePacks was not integrated as they have language depency - Fixed reading ISOs in repository folder as reading search pattern was case-sensitive - Fixed Volume License detection for ISO name - Added automated Administrator account name detection. Now should be Auto-Sysprep without errors, for example on Spanish Windows is "Administrador" not "Administrator" @jiafei2427 @SunLion @ederfernandez @Gustavox10 Please me know how it goes on your side. I hope all problems caused by language mapping should be gone now.
As your's instruction, the whole installation work. Device driver listed Intel ich7 family. Will try on nforce and ati chipset.
Good afternoon everyone! I am on a trip visiting my sister in another region of Brazil. I will return home on the 15th and then I will do the tests and return the results. You can count on me!
Tested on nforce and ati(Amd) chipset in ahci mode working,ram size 4gb. Using another computer: Dism to capture image after installation complete. Restore the image and on first boot there after display is blank also no hard disk activity. Would it be better using winpe to restore the capture installed image.
You can’t use captured XP on different HW. System created by XP2ESD create install.wim that works on any HW, but simply capturing and restoring will never work. NT 5.x was not designed for it. Whats your goal?
I have a strange issue. I am using this with official ISOs and all prerequisites but am getting lots of 'file not found' errors.
Noted the reply. Rather then going thru the new installation every time,better to capture and restore the same image.Thanks for your good work
Installing from ISO builded by XP2ESD is like restoring as image is already captured in install.wim. Also this setup is like 1000% quicker compared to original method
Please see previous pages how others posted info for debuging. I would like to fix all possible scenarios. @exe csrss Are you on Windows 7?
Tested it normal on Win7 Until the [5] stage .[6]An error was encountered,I think it is a DISM version issue and I will try to replace the system version. Finally, I will give this a full report.
@jiafei2427 DISM is called from apps folder as it's latest version that can run on XP and first that support capturing. I will try it on 7 too today. I have builded my perfect 7 AIO so it's time for new testing. During upcoming weekend I would like to create new script, that should create multiboot XP / 7 setup ISO (thats why I renamed drivers folder to driverpacks). I hope it can be done easily. Then I will continue in testing my unreleased Windows 6.1 Kitchen and maybe release it to public soon. EDIT: Confirmed, on Windows 7 is doesn't work. I'm going to find solution. EDIT2: I tried it 3 times, on last try It was successfull. Thats so weird as nothing was changed! I only tried before 2 and 3 launch dism from apps folder in cmd. But I noticed something about VHD driver install in 1 or 2 XP2ESD session. Any ideas? EDIT3: Maybe it's related to VHD mounting process. I'm going to grab VHDMount from Virtual Server 2005 R2 SP1 thats also reason why I requested them EDIT4: I'm going to perform Windows 7 x86 clean install and switch mounting to VHDMount, I hope it will work @exe csrss Can you try it too multiple times?