I want to install Windows XP 64-bit, but my hard drive is GPT. I tried using Hybrid MBR to get Legacy Boot to scan. I used XPISO:/AMD64/winnt32.exe with the command “winnt32.exe /syspart:C: /tempdrive:C: /makelocalsource” and followed the steps. After that, the hard drive became an XP Text-Mode Setup. When it loaded for a while, it encountered error 0x7B (INACCESSIBLE_BOOT_DEVICE). Then, I used Nlite to slipstream “Generic 64-bit Intel RST AHCI Driver by Fernando“. After re-installing the XP Text-Mode Setup to Hard Drive, I encountered another BSOD is 0xED (UNMOUNTABLE_BOOT_VOLUME). I consulted ChatGPT and knowing that Fernando’s Generic Intel RST AHCI driver only supports PCH AHCI controllers, not SoC controllers, I’m wondering if Fernando has created any customized versions of the Generic Intel AHCI driver? I hope Fernando can help!
Edit by Fernando: Thread moved into the “Windows XP” Category and title customized
@HPinES_Tech
Welcome to the Win-Raid Forum!
Maybe you will have to use another modded Intel AHCI driver (look >here<).
By the way - the BSOD error 0x7B indicates the usage of a not matching driver.
Which are the HardwareIDs of your on-board Intel SATA AHCI Controller? You can verify it by running any Windows OS, expanding the “IDE ATA/ATAPI Controllers” section of the Device Manager, doing a right-click onto the listed Intel SATA AHCI Controller and choosing the options “Properties” > “Details” > “Property” > “HardwareIDs”.
Bad screenshot (there seem to be some clothes over the monitor), but I guess, that the HardwareIDs are VEN_8086&DEV_22A3&CC_106. Tip: Press the “Alt”+“Print” keys simultaneously, run MS Paint and insert the screenshot.
To be able to solve your problem, I recommend to try the “Universal 64bit Intel RST(e) AHCI driver v13.2.8.1002 mod+signed by Fernando”.
Good luck!
@Fernando Approximately, the Hardware IDs are VEN_8086&DEV_22A3&CC_0106. However, version v13.2.8.1002 is too new to be compatible with XP; an older version is recommended!
@Fernando You previously stated that version v13.2.8.1002 requires Windows 7 or later in Generic Intel RST driver modded+signed by Fernando: “Supported are all Windows Operating Systems from Win7 up and all Intel SB/Chipset systems from ESB2/ICH7 up.”, and I extracted and checked the driver file packaged in the .rar file, and it’s not designed for Text-Mode Setup (there’s no txtsetup.oem file, and adding it with Nlite only provides support for PNP), further proving it doesn’t support XP. Could you please elaborate?
@HPinES_Tech
The 0xED BSOD error indicates, that your problem is not caused by a wrong/not matching AHCI driver.
If you want to know more, please watch >this< video.
@Fernando It wasn’t very helpful; I encountered error 0x7B before adding the AHCI driver, and after adding it, I got 0xED (BSOD right in Text-Mode Setup, not when the OS was installed and booted from the hard drive). This error could be due to a special SoC controller, Hybrid MBR on GPT, or an incompatible driver, etc.
@HPinES_Tech
The fact, that you got already a 0x7B BSOD before having integrated or loaded any AHCI driver, is the proof, that you had previously integrated/loaded another not matching textmode driver.
Because I was not sitting behind you while you prepared your customized XP image, I have no idea about the reason for your problem.
What about your in-use XP image? Has it been an original (untouched) one? Does its i386 or AMD64 folder contain a file named WINNT.SIF?
Yes, I understand. You mean this ISO file wasn’t downloaded from Microsoft, and the error is likely with the ISO itself rather than your driver, right? And it’s very difficult for me to obtain a genuine Windows XP (either CD or ISO) these days, so I can only get it from unofficial sources—that’s my limitation! Okay, if you have any solutions, ideas, or a better way to handle this, please reply.
@HPinES_Tech
No, I am rather unsure whether it is your downloaded ISO file, which is responsable for the BSODs you got. It may be your specific OS customization or a hardware/BIOS issue as well.
My support ends anyway, when I recognize, that the related user has violated the Copyright of any Company.
Good luck!
