@George King I don't know if this is useful but perhaps multiple two boot.wim files inside ISO can be useful so you can boot from win7 PE or win10 PE using bcd. This is similar to the way XP2ESD launcher allows multiple wim images inside ISO. This way you can make an iso that's compatible with all types of hardware (old or new). The easier way to do this is to just basically copy modified boot.wim from win-7 based XP2ESD iso and add it to win10-based XP2ESD ISO (win 7 boot image renamed as boot7.wim and added duplicate entry on BCD pointing out to boot7.wim instead of boot.wim). Or add an optional string in config.ini (like ALLOWMULTIWINPE=Yes) that basically may allow XP2ESD to copy 2 boot.wim from both windows 7 and 10 ISOs and then repeat the same XP2ESD configurations of the first boot.wim to the second boot.wim. This may sound like a waste of time but since XP2ESD is supposed to be an AIO setup i was wondering if this can be an option. The other advantage of this is that it's easier to test two installers (one contains win10pe, the other win7pe) in one single iso. The disadvantage of this is that in order to apply the same settings in both boot wim files, you would have to edit the same file from each image individually in order to apply the change. If this won't be taken into consideration, I will understand but having the option to boot XP2ESD installer from win10pe or win7pe in one iso will allow more computers to use XP2ESD modern installer.
The activator isnt compatible with wxp mce x86? Becus when i build it it says its not activated when it installs on vbox & after installing from xp2esd iso. Also using the right key becus else the build install will error out.
after doing the process of creating the modern installer when testing it in virtualbox it says it does not detect SATA disks when it is in IDE if it detects it... now in VMWare it does detect SATA disks... when I proceed with the installation in virtualbox it says that it does not find a fileversion.vbs file.. but vmware proceeds with the installation without problems using SDI... any solution? It is as if it were that in virtualbox it did not copy the $oem$ files and that the drivers also conflict in virtualbox than in vmware
I tried some what every key and my own keys and xp mediacenter 2004 wont activate. Common problem with this edition of xp or is it becus the recommend update packs what causes this or something? Kinda out of ideas to fix it right now.
@rulman See again supported input ISO versions in first post. This screens mean you are not following guide. Also you haven’t posted logs…
tr_windows_7_ultimate_with_sp1_x86_dvd_u_677484.iso tr_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-74085.iso