Also I've realized that xpconv.exe doesn't patch the ISO fully, it patches system after setup. I was expecting it to patch Server 2003 to Workstation at the beginning. There's a list of ISOs I wanna have but actually it doesn't exist without hacking ISOs: Code: 5.1.2600.5512.xpsp.080413-2111 Datacenter Server 5.1.2600.5512.xpsp.080413-2111 Enteprrise Server 5.1.2600.5512.xpsp.080413-2111 Standard Server 5.1.2600.5512.xpsp.080413-2111 Web Server 5.2.3790.3959.srv03_sp2_rtm.070216-1710 Professional 5.2.3790.3959.srv03_sp2_rtm.070216-1710 Home Edition
@example12345678912345678 I will add conversion of Server 2003 Enterprise VL into Professional, as I posted in post #669. I don't see any benefits in your conversion ideas, only Enterprise to Professional to provide native 4GB+ RAM support. Other conversions are useless. Currently I have adapted code and now can be XP2ESD builded in 2 versions. 1) Windows 7 + 10 ISO = Most compatible image for older machines 2) Windows 8.0 ISO = Most compatible with newer machines Going to build XP2ESD with Windows 8.0 is for users who cannot boot Windows 7 installer on their machines. During adapting code to this option I found some problems when using patched ACPI.sys file as there is new way how XP2ESD handle it to speedup building process. Currently I'm fixing it as when it's done then is possible to deploy XP on B450 without problem. This option makes deploying on new machines really easy, I love it. If I got some time today, I will continue with UpdatePacks as I think all can be done in a day or two.
Yes, you can. I hope for XP2ESD v1.6 release in this week. All images needs to be rebuilded with upcoming version
I have no idea why it can happends, I can only tell you I have tested one insane 50 hours build and all 131 ISOs and nLite integration worked as expected.
No it's nLite related, should be also something with your host. Try for example manually integrate SP3 into SP2 setup to see if it will be successfull. I have this problem in past and host reinstall solved a problem
Is it normal that my .cmd windows stops at "Installing into VirtualBox"? Should I close it at this point?
You shouldn't close the windows until it creates the ISO. You can open VirtualBox to view Installation process.
Looks like it's working now, it integrated the updates. Now to re-run it with presets to remove Windows Desktop Search. Question regarding Office: can I just throw my Office XP/2003/2007 ISO into /setup and be done with it or..? Feature request: being able to remove components with nLite before installing updates.
No just sit a wait. VirtualMachine is silently created and system installed, after capturing image is created VirtualMachine destoyed
There is a saying in China that "slow work and fine work." At least we have the perfect upgrade package.