To complete the needed "5 replies": I don`t want to start the setup-process when the imaging is done. I want the "boot.wim" to deploy the image and at next restart i want XP to start (not install). This is possible, i do this with WDS. I do this with 7, 8.1, 10 and 11 too. Just checking hardware and logged in as Administrator.
I don't think this captured WIM will work on real HW according to HALs and Kernels. I have improved Auto-Sysprep feature for this purpose for upcoming version. So when you create WIM on your own you just need to run Auto-Sysprep to create HAL and drivers independent image which will be able to run on any real machine. Or you can automate XP2ESD process with your previously customized XP ISO with turned off nLite touch in config.ini. Result is installable ISO. I have never tried XP2ESD deyploying from WHS. Would be great if you can try it after upcoming release.
I decided that this is really needed feature for v1.6. I did some tests and seems good. Now is possible to use "Dynamic drivers folder" for any system (5.1 - 11) deployed with Standard / XP2ESD setup engine using POWIS Launcher
I´m aware of this. Maybe i`ll change my mind in the future. Until now i`m not able to run XP2ESD without errors, i never got a working ISO. I´m german, so i used Win7, Win10 and XP DE. Maybe i`ll give it another try with all ISOs EN/US.
The "WindowsXPSyprep_DISK.VHD" is always created in "...\XP2ESD\auto-sysprep\VirtualBox". I put the folder "XP2ESD" in the root of drive "C:", i also tried other partitions. The path in "config.ini" is completly ignored, should be "VHDFile=V:\VIRTUALBOX\WindowsXPSyprep_DISK.VHD". VirtualBox installs XP and always ends in a BSOD.
@g-force I had the same problem with different Bsod on german XP SP3. Then I try VirtualBox-4.3.28-100309-Win.exe with Extensionspackage and all Bsods are gone Dietmar
I`m working on it - and i can tell you i got some effort. I had to change some things and lines in different CMD and it seems to run without failures (and even 10x faster). I will post all changes after some testing.
@g-force I make some tests more: By far the best version for to run everything under XP SP3 is Oracle VM vers. 4.2.20 with Extrapackage Dietmar
@diderius6 I´m running Win10 x64. The problems i found are not related to VirtualBox. It`s some settings in the scripts.
@George King These are changes i made: config.ini Code: ; VirtualBox setting for Sysprep VirtualBoxPath=C:\Program Files\Oracle\VirtualBox VirtualMachinePath=V:\VIRTUALBOX MachineName=WindowsXPSyprep OSType=WindowsXP RAM=2048 VRAM=64 HDDSize=10000 HDDType=VHD autosysprep.cmd Code: call :ReadINI VirtualBoxPath VirtualBoxPath call :ReadINI MachineName MachineName call :ReadINI VirtualMachinePath VirtualMachinePath call :ReadINI OSType OSType call :ReadINI RAM RAM call :ReadINI VRAM VRAM call :ReadINI HDDSize HDDSize call :ReadINI HDDType HDDType call :ReadINI HDDLabel HDDLabel call :ReadINI ASSIGNLETTER ASSIGNLETTER "%VirtualBoxPath%\VBoxManage.exe" modifyvm "%MachineName%" --ioapic off >nul 2>nul "%VirtualBoxPath%\VBoxManage.exe" modifyvm "%MachineName%" --pae on >nul 2>nul "%VirtualBoxPath%\VBoxManage.exe" modifyvm "%MachineName%" --memory "%RAM%" --vram "%VRAM%" >nul 2>nul "%VirtualBoxPath%\VBoxManage.exe" modifyvm "%MachineName%" --nic1 nat >nul 2>nul CaptureVHD.cmd Code: call :ReadINI VHDFile VHDFile call :ReadINI HDDLabel HDDLabel call :ReadINI ASSIGNLETTER ASSIGNLETTER call :ReadINI ImageName ImageName call :ReadINI ImageDescription ImageDescription call :ReadINI ImageFlag ImageFlag call :ReadINI USECHKDSK USECHKDSK call :ReadINI ADDDISM ADDDISM SUBST X: /D echo. echo [1] Mounting VHD
@George King ........I'm way out of touch. Does your new installer touch directx for XP on newer chipsets? Not that new anymore, the Intel 300 series on Asus B360M mobo. Direct3D doesn't run on my XP system. Found part of the problem, I am running Ge Force GT 1030 and there are no drivers yet, presumably. @diderius6...Where is all the XP modding going on? Wincert is 5 weeks old....no posts.
more than less: yes WindowsXP only needs this one primary extended partiton, formatted as ntfs. I didn´t test this configuration on real PC; just in VM on Oracle VirtualBOX with ISO from member g-force. credits go to g-force for his work on german Windows XP with install.esd
Current release status: I have changed and fixed probably everything I noted down. OOBE was most special to tweak it up. Now I'm fine with current state. Of course there will be things to improve in future as usual. I have now only few things for now that needs to be solved in future. TimeZone addon breaks OOBE TimeZone selection screen - nothing is listed even if it looks correctly and new TimeZones are available in system settings. There are 3 possible solutions 1) Use TimeZone.inf installation manually after setup finishes OOBE to get new TimeZone settings available in system 2) Find out why nothing is listed in OOBE selection screen after applying new TimeZones settings. I have inspected source code and there is nothing special I can found now about "GetAllTimeZones" functions tree 3) Write custom JavaScript / VBSscript function to query registry to <select> in OOBE I have burned some time to figure out 3) but It's not important now even I'm able to JS out needed lines, but it doesn't work in all possible scenarios. I hope community can hepl with finding needed solutions after 1.6 release Next steps before release are really small pieces in whole puzzle party. 1) Do few tests on real HW according to new Dynamic drivers folder support for 5.x in POWIS Launcher 2) Rewrite 1st post - I already have some mod from 07-2021 - This date drives me crazy, I hope I can have free time for my projects but real job and family eats a lot of my "free" time P.S. Comparing 1.5.6 vs 1.6 source tree is imposant, most of code and things are rewritten. More support and options and probably new bugs of course After release you must start from scratch - Only updatepacks / addons / setups can be used. I try will to describe it more during upcoming week. NOTE: XP2ESD is now powerfull like never before as we can now deploy XP - 11 from one setup media, preferably USB. Only things that needs to be sorted out are RunOnceEx system limits for installation different apps versions across OSes. And of course Dynamic drivers folder needs same / similar system check And finally for translators - here are current POWIS Launcher strings, please translate and post. Of course it will be better after release, but I think basic support can be added now. There will be probably another changes in launcher in future, but for now it's "final" for XP2ESD POWIS Launcher strings to translate Code: en-US.AvailableDriverPacks=DriverPacks available en-US.Selected=Selected en-US.Filename=Filename en-US.Size=Size en-US.Copying=Copying en-US.InstallationInProgress=Installation in progress en-US.WinREButton=Recovery Environment en-US.CMDButton=Command prompt en-US.StartButton=Start en-US.CheckAllButton=Check all en-US.UnCheckAllButton=Uncheck all en-US.SetupType=Setup type en-US.SetupFile=Setup file en-US.Unattended=Unattended configuration en-US.WithoutUnatteded=Without configuration en-US.XP2ESDSetup=XP2ESD Setup en-US.StandardSetup=Standard Windows Setup en-US.Options=Options en-US.DynamicDrivers=Dynamic drivers folder en-US.DynamicDriversTip=Integrate drivers from drivers folder on setup media into deployed system before first boot en-US.DefaultPartition=Custom partition ID en-US.DefaultPartitionTip=Specify custom boot partition ID for Windows XP / 2003, usefull for custom multi-boot installations en-US.PAEPatch=PAE Patch en-US.PAEPatchTip=Remove 4GB RAM limit on 32bit systems en-US.SkipOOBE=Skip OOBE en-US.SkipOOBETip=Boot directly to desktop under Administrator account en-US.NoReboot=Noreboot en-US.NoRebootTip=Do not reboot