Good luck, first don't call that dual-boot as it's not dual boot, just autorun with custom deyploy from live system.
Feel free to do your own research and post results here. I have priority on important things. Polishing boot screen design is not important at all.
Actually it is dual boot because not only it will install on any other partition but also because it will add the entry on the live OS' BCD which is by definition dual-boot. If it's not on a different partition of the same drive then it's a different story. I will call this Live deploy for now, thanks for the suggestion.
Well, ISO is still not dual-boot, thats what I mean. If you boot from your ISO there will be only one boot option (if you not duplicate default entry with another boot.wim). Adding another boot option to installed system BCD is only "multi-boot support" from installer. And this setup.cmd already does as I told you before. Good luck with trying to achieve same result that you get from current WinPe (boot.wim) based setup. Much better will be to find out how to enable "upgrade" to XP from any non UEFI installed system. Windows 8.0 setup engine would be great to start research as it's last one that can be launcher under XP. And still running POWIS Laucher from installed OS gives you all coded option and real time changing them as settings.ini is used only for default choice. Yes, setup.cmd can read settings.ini too. But everything can be called by parameters, thats how POWIS Laucher do that
wdym mean “from any non UEFI installed system”? as in which os? all of them? (this sentence is relocated from bottom due to off-topic-ish things) could then there would be upgrade enable for vista2esd if xp2esd upgrade’s possible? (in other words keep the classic in place upgrade option that enables if you run from valid xp version or valid vista version or at least enable performing a so called “upgrade” while keeping powis launcher) UNRELATED MESSAGE the vista2esd project is all i keep thinking about every day and every night. just thinking of the method to integrate updates (judging from older messages on thread, it’s dism script that’s kinda like integrate7 but for vista and with all updates in one ready to download + auto sysprep to install updates that can’t be integrated/make them installed status) i will try to be a tester for vista2esd once it releases depending on how burdening school is. i’m gonna get a laptop that supports vista soon so i can eventually test the future project on real (supported) hardware and there once it releases and try to report bugs. thank you for the amazing works @George King
Server 2003 test session is in progress! I think everything is solved now. Few ISO images needs manual fix before processing. Server 2003 is different game. I need really prepare instructions "How to prepare input ISOs" for Server 2003. I will also provide SVF patches to make it easy with English version, as problematic ISOs are probably only in English. Code: en_win_srv_2003_enterprise_with_sp2.iso en_win_srv_2003_enterprise_with_sp2_vl.iso en_win_srv_2003_r2_datacenter_with_sp2_vl.iso en_win_srv_2003_r2_datacenter_x64_with_sp2_vl.iso en_win_srv_2003_r2_enterprise_kn_with_sp2.iso en_win_srv_2003_r2_enterprise_kn_with_sp2_vl.iso en_win_srv_2003_r2_enterprise_with_sp2.iso en_win_srv_2003_r2_enterprise_with_sp2_vl.iso en_win_srv_2003_r2_enterprise_x64_with_sp2.iso en_win_srv_2003_r2_enterprise_x64_with_sp2_vl.iso en_win_srv_2003_r2_sbs_with_sp2.iso en_win_srv_2003_r2_standard_kn_with_sp2.iso en_win_srv_2003_r2_standard_kn_with_sp2_vl.iso en_win_srv_2003_r2_standard_with_sp2.iso en_win_srv_2003_r2_standard_with_sp2_vl.iso en_win_srv_2003_r2_standard_x64_with_sp2.iso en_win_srv_2003_r2_standard_x64_with_sp2_vl.iso en_win_srv_2003_web_with_sp2.iso en_win_srv_2003_web_with_sp2_vl.iso en_win_srv_2003_whs_with_sp2_pp3.iso en_win_srv_2003_whs_with_sp2_pp3_oem.iso en_win_srv_2003_whs_with_sp2_pp3_vl.iso
I found out earlier that copying everything from sources folder (inside boot.wim) to the sources folder of installation media will allow setup to run but it can only run on host os that windows 10 setup engine supports. It's not perfect, gives prompts similar to the first time you tried to implement windows 10's setup engine on XP. In order for the upgrade option to work properly, you need to also borrow upgrade files from windows 10 setup engine, windows server 2008 R2 setup engine and windows 7 engine (specifically the ones referencing XP and server 2003). Borrowing upgrade files from windows server 2008 R2 setup engine can add upgrade support for windows server 2003.
Thats, why Windows 8.0 must be used to support this "upgrade", maybe in future I can investigate. My next goal will be Updating UpdatePacks and 2003 UpdatePacks re-creation. Probably meanwhile I will review setup engine patching mechanism as I need to let setup remove created PageFile to add full support for Quibble in automated way.
@MilkChan I will try it, most of Server 2003 there are my uploads, instead of missing ones Only one bad thing is lack of x64 localized UpdatePacks
Mostly important is grab all possible x86 ISO images. x64 can be supported only in English for now. I have plan how to bring localization into English x64 5.2 systems without using MUI, but it needs time and can be done maybe somewhe in future.
Seems like 2003 process is polished as much as possible for now. As there are still needed some time consuming tests in upcoming release. I'm going to try to fully localize Windows XP x64 without using MUI meanwhile.