reboot12

@Dietmar I think that rom builded using efirom can work and CSMWrap will be able to use the legacy part from the loaded rom file. In uefi bios legacy VBIOS iGPU is in RAW area in CSMCORE module and CSMWrap not know where. But if you use loadpcirom legacy+uefi.rom your graphics card then maybe CSMwrap see legacy part using PCI I/O protocol same as use legacy rom from PCIe graphics card.

No, efirom.exe is Windows CMD executable: https://www.mediafire.com/file/luqx9gx86u9monv/EfiRom.zip/file After you build rom then posiible load it in UEFI Shell using command loadpcirom

@Dietmar Yea, possible load pci rom builded using efirom: UEFI Shell see efi rom but I don't know id CSMwrap see legacy part of rom

RAW OpROM (55 AA beginning) probably not but maybe after make efi rom image using efirom.exe tool possible - look at this: https://msfn.org/board/topic/178182-xp-pro-x64-os-boot-nvme/page/3/#comment-1227538

@Dietmar I test, test and test WinXP 32-bit SP2 with CSMWrap 1.2.1 on Asus B85M-E Config: iGPU Haswell, monitor connected over HDMI-HDMI cable (has both legacy and GOP VBIOS) PCIe AMD6450 in second PCIe slot x16 work at x4, same monitor connected over DP-HDMI (second HDMI port on monitor) (has both legacy on PCIe card chip and GOP VBIOS inserted to motherboard bios) Monitor THOMSON 1360x768 native resolution with 3 HDMI port input XP boot OK on vga.sys : on Haswell need set Primary Display iGPU in bios, work on bootmgr+BCD+winload.exe 5472 > boot on SeaVGABIOS from CSMWrap: XP desktop in 1024x768 32-bit on full monitor area if boot PC from bios Boot Menu then select HDD XP desktop in 640x480 32-bit on top left corner monitor area if PC auto boot from HDD not possible install Intel Haswell graphics driver - no free resources (yes there are Haswell iGPU drivers for XP and they work in normal legacy mode) on AMD need set Primary Display PCIE in bios, work on ntldr > boot on legacy VBIOS AMD6450 XP desktop in 1024x768 32-bit on full monitor area possible install AMD drivers and works 3D If I swap loaders: ntldr for Haswell iGPU then black screen and xp hangs but if set VGA Enable 1 before run CSMWrap (mm 0001003e 8 -pci) then boot OK but black screen winload.exe for PCIe AMD then stay on aurora boot screen but boot OK Running bios Boot Menu set GOP to 1024x768 then xp works in same resolution. Instead Boot Menu possible use u7.efi 1.31 with UefiSeven.ini set to 1024x768 without u7.original.efi to make error in U7 then fallback to UEFI Shell - I use startup.nsh @echo -off if exist fs0:\EFI\Boot\121.efi then set base "fs0:" endif if exist fs1:\EFI\Boot\121.efi then set base "fs1:" endif if exist fs2:\EFI\Boot\121.efi then set base "fs2:" endif if exist fs3:\EFI\Boot\121.efi then set base "fs3:" endif if exist fs4:\EFI\Boot\121.efi then set base "fs4:" endif if exist fs5:\EFI\Boot\121.efi then set base "fs5:" endif if exist fs6:\EFI\Boot\121.efi then set base "fs6:" endif if exist fs7:\EFI\Boot\121.efi then set base "fs7:" endif if exist fs8:\EFI\Boot\121.efi then set base "fs8:" endif if exist fs9:\EFI\Boot\121.efi then set base "fs9:" endif if exist fsa:\EFI\Boot\121.efi then set base "fsa:" endif if exist fsb:\EFI\Boot\121.efi then set base "fsb:" endif %base% u7.efi EFI\Boot\121.efi

Try change in bios Primary Display from Auto to PCIE if you use PCIe graphics card. If you have second monitor connected to iGPU disconnect it.

OK, but before you write on the forum about something new that you discovered, first write back to the previous post because it looks like you are ignoring which is very annoying

@Dietmar F..k, why don't you read carefully what I write I mean NVIdia GT 730 card

I don't believe it. I asked you to take a screenshot in xp in SlicTool Kit (slic.exe): https://www.mediafire.com/file/zuxxznjxjjnn3u1/memory_check.zip/file At the moment I'm not interested in whether the card works on ArrowLake with CSMwrap just whether it actually has VBIOS - connect card to other old motherboard run xp in legacy mode and please use slic tool kit.

It is impossible that such an old graphics card GT 730 does not have a Legacy vbios, after all, you booted the computer with this card in Legacy mode using CSMWrap - right? https://msfn.org/board/topic/186793-csmwrap-boot-csm-on-uefi-only-systems/page/10/#findComment-1280463 This is proof that it has vbios - show what the SLIC ToolKit memory dump at C0000 shows: https://msfn.org/board/topic/186793-csmwrap-boot-csm-on-uefi-only-systems/page/9/#findComment-1280402

@Dietmar I noticed an interesting thing - I did the xp32 tests with CSMWrap described in the last few posts on the original xp sp2 files including acpi.sys and there were no problems with acpi. Today I wanted to test something, I set CSM Enabled in the bios, I run the system without CSMWrap and there is BSOD A5. I replaced the acpi.sys outside of the running system with the ones from you - modded acpi.sys 5.2 and the system boots fine - but it seems to be related to the fact that I use winload.exe and it has a problem with the original acpi.sys - I seem to have written about it before (in 2019 and 2020) on BA about xp 64-bit + winload.exe: https://www.betaarchive.com/forum/viewtopic.php?p=445453&sid=c0c23f5574a1881384f2de47f5f59987#p445453 https://www.betaarchive.com/forum/viewtopic.php?p=447734&sid=c0c23f5574a1881384f2de47f5f59987#p447734 Very interesting that with CSMWrap work ok original acpi.sys + winload.exe

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