The installation failed in the debug mode, but after the normal mode is installed, it can run normally in the debug mode
I did tests with booting WinXP 64-bit on 8 Gen mobo - to boot can be either boot debug or kernel debug for winload.efi 16497 with UefiSeven or FlashBoot bootdebug in bcdedit or DebuggerEnabled in BOOTICE debug in bcdedit or KernelDebuggerEnabled in BOOTICE Also tried EFI\Boot\bootx64.efi from Win8.1 or Win10 + winload.efi 16497 but then in WinDbg is BSOD 7E
So I wanted to note for some reason I can't mount the sysprep image as writeable on my system so I have to boot through macrium to replace the sfc_os.dll. When I attempt to mount it it just shows a ?. Not sure if being on Windows 11 is making that an issue or not.
@stan456 Read the guide carefully - sfc_os.dll you replace in the .vmdk file and not .mrimg: Do you do in MBR or GPT? In GPT WinXP Boot Manager entry is always added as the first on the list in Boot Menu: Code: echo: echo Adding WinXP Boot Manager to NVRAM boot menu, wait... echo: bcdedit /set {fwbootmgr} displayorder {bootmgr} /addfirst In MBR you need manually add WinXP Boot Manager entry to Boot Menu as first using BOOTICE. The mbr.cmd script displays information to do and automatically launches BOOTICE:
The issue is I have no way of mapping the drive as writeable. If I do, windows explorer just shows the drive letter with a question mark symbol on it so I though I'll create a backup image, open it on the host pc and replace the file in there and then restore the image. I've tried both MBR and GPT. Not sure if I need to mess with something in the BIOS to get this to work. I have an optiplex 3070 micro and an intel nuc I'm trying this out on.
I'll open diskpart, run clean on the internal drive and follow the directions as listed in the original post
@stan456 You had to be mistaken somewhere because the GPT.CMD script automatically adds an WinXP entry to the first place on the Boot menu list.
I've followed the exact directions and all it does now is say "starting windows xp in uefi" then just turns off. Testing this out in vmware, it just sits at that screen EDIT: loading this onto a real computer says the file \WINDOWS\system32\winload.efi might be missing or corrupt
Do you use the latest version sysprep_public.7z ? Do you choose from menu 1 Setup on clean disk or 2 Setup next to another OS ? Is the winload.efi file really on the disk in WINDOWS\system32 ? What is your real PC spec? If Intel 8 Gen or newer, have you tried to use the WinXP SP2 64-Bit UEFI bootdebug option? What version of VMware?
The system boots on the SATA disk, and there is no problem with the nvme driver, but once the nvme partition is started, the driver is incorrect. Whether it's Legacy (boot.ini) or EFI
I don't understand - "the nvme partition is started" ? Write detailed what errors appear, give a screenshot.
A problem has been detected and windows has been shut down to prevent damage to your computer. If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, fol1ow these steps: check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer. Technical information: STOP:0X0000007B (0xFFFFFAD9A24083C0,0xFFFFFFFFC0000034,0x0000000000000000,0 Co000000000000ooox