@George King XP-styled partition icons are almost done. Btw, the setup only uses the icons from the icon group. I just discovered that basically all you would have to do is put the respective XP icon's Icon Group from XP's shell32 to replace the vista icon's Icon Group by changing the number on the XP res to match the one from xpwizimg.dll. I thought it wouldn't work but it works because Icons rely on Icon Group to function, unlike bitmaps.
sorry i made a mistake what i meant is that the error comes to me everytime the guest os setup starts there is no errors from vitrualbox itself
Why does everything stop at Installing into Virtualbox while building XP2ESD? VirtualBox works, and XP was installed, but once the virtual machine shuts down, everything stays put
@George King Partition icons for the XP2ESD setup are done, I will send you the link for the resource file in private.
@George King Btw, keep in mind that I updated the Upgrade/CleanInstall icons to reflect XP's style, you can bring back the icons for the two buttons.
I tried to do that the first time I deployed using updated 1.6.3 but deploying two extra wim files in addition to XP's wim takes not only a lot of time but also a lot of disk space. Perhaps I wonder if you can add an option to select between only one newer-os wim image or two newer-os wim images to add on XP2ESD. I wonder if XP2ESD deploys the newer OS the same way POWIS does (in the sense that SDI and RunOnceEx are added on newer OS just like in POWIS). Regarding a true AIO experience, I don't know if an extra "LEGACYOSDEPLOY=No" option will be added that excludes XP ISO from being required to deploy (obviously skipping the XP's Auto-Sysprep phase), but that will make POWIS completely useless unless you're really planning to merge POWIS and XP2ESD into one AIO tool (maybe that's why you added POWIS launcher into XP2ESD, to provide backward compatibility with POWIS). If "LEGACYOSDEPLOY=Yes", then XP2ESD should deploy XP/2003 as if nothing was changed, the option should be enabled by default. Obviously, if "LEGACYOSDEPLOY=NO", then another function should be automatically set as Yes during builder to make XP2ESD launcher but with only newer OS wim instead (this may contradict XP2ESD's purpose, to deploy XP, but if you want an AIO experience, add this option, but this may mean that POWIS and XP2ESD may be merged once XP2ESD has all of POWIS' features).
Hello I created xp2esd using a windows 7 ISO and a windows 10 ISO, everything works perfectly, but if instead of XP2ESD SEUP, STANDARD WINDOWS SETUP is chosen, the installation starts but at a certain point it gives an error I only used OnePiece XP UpdatePacks v1.1.0, OnePiece_WinXP_Embedded_Post-SP3v1.0.2 is an alternative? or should it be used together with OnePiece XP UpdatePacks v1.1.0?
For installing XP you need to choose XP2ESD Setup. It's expected Standard Setup doesn't work for these custom images. Standard Setup is used only when you placed into your ISO/USB\sources folder another WIM / ESD. For example Windows 7.esd. Best is to use both packs. Embbedded ones is only addition with updates to 04-2019 that were relased only for XP Embedded, these updates have same branch and they are compible with XP. It's recommended to use both of them.
@jensonb You just grabbed drivers from Integral edition... XP2ESD already have these and more drivers created from scratch. I'm not interested in running XP PE these days. In XP2ESD ported driver collection you can find almost everything you need.
these single drivers are the same as in xp2esd, I ask someone to please integrate them into these 2 of my Live XP PE ISOs, I need them for some of my projects thank you
They are not same at all. Base files were probably same. This is XP2ESD related thread, no place for other custom projects. Best is to start research, adding drivers into related folders and needed registry entries is not hard. You can also scan your system before driver installation and compare it after. This way you get everything that needs to be touched.