reboot12

GOP not from this one but from a similar HD7450 Did you read this post? I described on betaarchive.com with pictures: https://msfn.org/board/topic/186793-csmwrap-boot-csm-on-uefi-only-systems/page/9/#findComment-1280411 Insert .ffs file using UEFITool: https://www.mediafire.com/file/hdkw8v22lhixv8c/AMD-GOP.zip/file Instruction step-by-step on other example driver: https://github.com/pbatard/efifs/wiki/Adding-a-driver-to-a-UEFI-firmware Read tutorial from Adding the module to the firmware

Why clover? CSMWrap 1.2.1 normal load VBIOS from my AMD6450 - but in motherboard bios I have amd-gop inserted.

This is normal because CSM Disabled = pure UEFI and this requires GOP. Your AMD6450 card not have GOP - only Legacy VBIOS

@Dietmar Yes, VGA Enable 1 help boot xp32 on iGPU using normal ntldr - black screen but OS works - I have Remote Administrator installed and OS works in 640x480 4-bit (Memory Remap Enabled or Disabled): 00 01 00 - bridge to which the graphics card iGPU is connected 00 02 00 - iGPU No need set I/O acces and Bus master 'Command (4)' for iGPU because is default set to 7 - only VGA Enable for bridge: mm 0001003e 8 -pci CSMWrap121.efi If VGA Enable is 0 then OS hang for some minutes (about ~3) and in WinDbg BSOD 0x4000008a: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Opened \\.\com3 Waiting to reconnect... Connected to Windows XP 2600 x86 compatible target at (Fri Jun 6 15:34:42.574 2025 (UTC + 2:00)), ptr64 FALSE Kernel Debugger connection established. Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe - Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible Built by: 2600.xpsp_sp2_rtm.040803-2158 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 System Uptime: not available watchdog!WdUpdateRecoveryState: Recovery enabled. *** Fatal System Error: 0x4000008a (0x89ECE990,0xB9D7DA60,0x00000000,0x00000000) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe - ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4000008A, {89ece990, b9d7da60, 0, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** ERROR: Symbol file could not be found. Defaulted to export symbols for halmacpi.dll - *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : ntkrpamp.exe ( nt!KeRegisterBugCheckReasonCallback+77c ) Followup: MachineOwner --------- nt!DbgBreakPointWithStatus+0x4: 8052a5d8 cc int 3 I tried install Haswell iGPU driver, install OK but after reboot and VGA Enable is error Code 12 (not free resources) and still works on 4-bit: But if use bootmgr+winload.exe+BCD+vga.sys (haswell iGPU uninstalled) no need set VGA Enable 1 then OS boot in e.g. 800x600 32-bit VGA Enable is only helpful for ntldr loader

@Dietmar I need to remember and practice because I don't remember exactly. pci - list all PCI devices For graphics card you need set register Command (4): 0007 mm xxyyzz04 7 -pci For PCI Bridge you need set register VGA Enable in Bridge Control (3E) (the bridge to which the graphics card is connected) mm xxyyzz3E 8 -pci xxyyzz is PCI bus dev func of PCI Bridge device https://forums.macrumors.com/threads/win7-x64-booting-natively-via-efi-no-bios-emulation.696523/post-14778765 https://forums.macrumors.com/threads/win7-x64-booting-natively-via-efi-no-bios-emulation.696523/post-14776170 This is example in my PC: 00 1C 04 - PCI bridge to which the graphics card is connected 04 00 00 - PCIe graphics card mm 001c043e 8 -pci VGA Enable mm 04000004 7 -pci I/O acces and Bus master For check changes: pci -i 00 1c 04 -b pci -i 04 00 00 -b To check bridge to which the graphics card is connected use: devtree -b and dh handle_number

Try set VGA Enable in UEFI Shell before run CSMWrap: https://www.betaarchive.com/forum/viewtopic.php?p=434759#p434759

@roytam1 github problem if try use @

@Dietmar You tried other cards? Best I use is AMD HD7450 with GOP+VBIOS or AMD HD6450 only VBIOS but I insert GOP to motherboard bios and now card works also in pure UEFI https://www.betaarchive.com/forum/viewtopic.php?p=471154#p471154 With this cards works all - passthrough in VMware ESXi or virt-manager QEMU KVM, XP 64-bit in pure UEFI, XP 32-bit with CSMWrap

With a PCIe Radeon R5 card you also have an XP desktop in 4-bit? How VBIOS is then used - check, for example, with SLIC ToolKit > C0000 memory dump. This is my radeon VBIOS when boot using CSMWrap:

What is the native resolution of the monitor connected to the graphics card? I noticed interesting things when we change the GOP resolution before running CSMWrap. You can change the resolution, for example, using UefiSeven 1.31 in the UefiSeven.ini file and boot the u7 without the .original.efi file - then the u7 will boot at the set resolution and return to the UEFI Shell because it does not find the original.efi file Now run CSMWrap runs at the same resolution as set by U7 (SeaBIOS probably also). I tested with winload.exe and in XP it boot in 800x600 but in the screen settings there are different resolutions to choose from - different depending on what resolution you set in U7. Unfortunately, changing the resolution restarts the computer.

NTFS partition must be created using diskpart from Win7 or newer for bootmgr load or change bootsector in WinPE: bootsect /nt60 C:\ or change in Bootice: @Dietmar Read also this: https://github.com/FlyGoat/CSMWrap/issues/46

@Dietmar I sent to email.

For the serial port to work you need to load the pciserial.efi and terminal.efi drivers in the UEFI Shell: load pciserial.efi terminal.efi Try my patched Longhorn 5472 winload.exe + bootmgr + BCD - the necessary files I seem to have already sent you. You need also fix BCD using bootice.exe https://msfn.org/board/topic/186793-csmwrap-boot-csm-on-uefi-only-systems/page/2/#findComment-1280116

I have but the old version: https://github.com/FlyGoat/CSMWrap/issues/14#issuecomment-2889051446

Yes, these drivers work 100% - I tested both 32-bit in XP 32-bit and 64-bit in XP 64-bit The same drivers also work in Win7

In that case, look for a support to the problem from the system manufacturer - good luck I don't want to post a tutorial on a forum that will disappear from the web in a moment like reboot.pro

@Klemper I have a question - is registration not working on the MDL forum? I don't want to explain once again what and how because that's how everything is described: https://forums.mydigitallife.net/threads/usb-3-xhci-driver-stack-for-windows-7.81934/page-18#post-1861262 My drivers work OK and tested on many computers. First time I've heard of drivers "killing the mobo"

@roytam1 Best USB3 drivers for XP - AMD by daniel fixed by me - I use them in my XP 32 and 64-bit tutorials on MDL. Also works fixed by me from George King 6.2.9200.21180 - I used them in tutorials before but they have a slight problem: https://forums.mydigitallife.net/threads/winxp-64-bit-on-a-modern-pc-iso-boot-wim-install-wim.88435/page-7#post-1868985 Everything is on MDL in my tutorials and other topics - just register.

What problem to make an account?

@roytam1 https://forums.mydigitallife.net/threads/winxp-32-bit-on-a-modern-pc-iso-boot-wim-install-wim.88834/

No

@Dietmar Have you checked if there is any debug information in Putty via COM port after load drivers pciserial.efi & terminal.efi ?

@Dietmar No, links not works but as far as I know DUET is a UEFI bios and there is no such file because it doesn't make sense - to run UEFI bios on UEFI bios

I wonder if every UEFI no-CSM bios is missing table for all the legacy Interrups?

Wait, wait, wait - after all, OVMF_CODE-pure-efi.fd bios doesn't have these modules and CSMWrap works