I experienced the same problem. My machine is Asus M409BA. CPU AMD A4 9125 Radeon R3 iGPU NVMe & SATA HDD It manages to deploy install.wim onto partition, but failed to boot after aurora bootscreen (winload.efi). I tried enabling csm, booting into bootlog, use usb 2.0 slot, but all that didn't solve the problem. Also, this is out of topic, but how did you manage to integrate uefiseven? I tried to use it with win7 aio simplixed iso but i couldn't manage to enter the installation process. I lack fundamental understanding on how uefiseven works.
But do you boot in Legacy? Enabling CSM does not mean that Legacy mode is automatically used - you need to start a computer from USB for install and from disk after install in Legacy mode. If there is a CSM option in the bios, it can work in several modes: pure UEFI (CSM Disabled) - Bios UEFI (GOP) video is used and the Windows uses loader bootmgfw.efi - there are only UEFI items in Boot Menu UEFI + CSM (CSM Enabled) - boot option UEFI & Legacy - there are both UEFI and Legacy items in Boot Menu. Windows can use loader bootmgfw.efi when you selecting from Boot Menu UEFI or loader in MBR and bootmgr if you choose Boot Menu item Legacy. Bios Legacy video is used. Legacy only (CSM Enabled) - boot option Legacy only - there are only Legacy items in Boot Menu. Windows uses only MBR & bootmgr. Bios Legacy video is used Some old PC - when UEFI was just coming in, do not have a CSM option switch and BIOS always operate in UEFI+CSM mode - e.g. ThinkPad X220 - this laptop does not have a GOP video bios - it only has a Legacy video bios. Still others PC have only pure UEFI without CSM - this is UEFI class 3
I updated the tutorial - in Win7 (and probably 8, 10 and 11) instead of using a full Administrator account, can be used account with administrator's permissions but you need to disable UAC and restart the system.
I fix sysprep.inf because the USB keyboard and mouse not yet operate at stage Welcome & License: Code: [Unattended] OemSkipEula=Yes ... [GuiUnattended] OemSkipWelcome=1 USB devices (e.g. keyboard & mouse) only work after this step - when the progress bar exceeds half: Also replaced MS Paint to IrfanView 64-bit (iv.exe) in boot.wim & install.wim files.7z and sysprep.7z updated
files.7z updated added new tool to detect boot mode UEFI or Legacy - thanks to this, in Legacy mode, I skipped selected parts of the code required only in UEFI mode cosmetic changes in main script new screenshots in first post
Came back to revisit the project and its working so well now thanks for everything! I am running into an issue though during the install. For some reason I have to re-enter the windows xp key, language etc until it logs me in for the first time.
I have changed it a long time ago - now the xp key, organization and regional options are introduced during installation (mini-setup) - see Spoiler Screenshots mini-setup at the end of the first post in this topic. Do you use updated files.7z and sysprep.7z files? Do not use a sealed system again! This is why there is a step in the tutorial to create a copy of sysprep.vmdk to the vanilla_sfc.vmdk file after installation and SFC replacement to start tutorial from that moment. If you have not made a copy of the sysprep.vmdk file, you need to install the system from the beginning. If in the tutorial I share a new version of sysprep.7z, you always have to do it: delete current sysprep.vmdk copy a previously made backup vanilla_sfc.vmdk as sysprep.vmdk boot VM WinXP then use sysprep.iso from sysprep.7z
One disadvantage is that Windows XP 64-bit is not technically Windows XP at all, it’s a desktop version of Windows Server 2003 64-bit. But the main disadvantage is that 16-bit programs and 32-bit drivers no longer work. So, if you have relatively exotic devices or programs they won’t run anymore. There are only three main issues with XP x64: 1) Driver Support - A lot of lowly manufacturers do not have XP x64 drivers. 2) Application Support - XP x64 has zero support for 16-bit applications. If you have any old 16-bit games or programs, they will no longer function. 3) Installer Blacklisting - Some idiot installation developers have added operating system checks to the installers which blacklist any operating system not explicitly defined in the installer. Basically, that means the installer will refuse to install the software on XP x64 even though it works fine on XP x64. You can work around this one by installing the application on a operating system that isn't black listed and then copy the files over to your XP x64 computer. copied.
Small edit for future users if you'd like to update the original post, tell folks where disable the page file, system restore, automatic updates set Never search Windows Update for drivers set Ignore - Install the software anyway and don't ask for my approval is within xp. Also for testing on a VM, what should people set the OS type to? Windows 7 x64? 10 x64? etc
@stan456 All these settings are under the System Properties - right click on My computer > Properties Testing in a virtual machine is really just for me to check if the startnet.cmd script works well and whether USB3 and SATA drivers work. In a virtual machine, you can always install the original WinXP. I did the guide to install the system on a real (modern) computer
In my case, WinXP X64 with USB 3.0 installed ok. Restart is normal, and, if usb mouse is connected on usb 3.0 port, in Device manager, USB driver have yellow exclamation mark. USB 2.0 are working fine. Controller is TI, This problem applies only on usb 3.0 ports. No patched ACPI driver, normal boot on mbr.
@un user USB3 drivers require patched acpi.sys because without it is a yellow exclamation mark with an error Code10 USB 3 ported driver fo WinXP 64-bit Code 10 > missing patched acpi.sys Code 24 > wrong LoadOrderGroup Code 39 > missing usbd.sys file