Just a guess, but likely some VGA driver stuff included in the UEFI crap isn't handed over to the proper driver. A similar scenario was frequent in the good old W9x days when you may face some devices listed twice (one for the MSDOS/Bios drivers and one for the proper Win32 ones). At the time deleting both devices from dev manager and rebooting fixed the problem, not sure if the approach could work in your case
To clarify to you, I boot XP x64 SP2 on UEFI Class 3 real hardware (windows 11 capable laptop) using winload 16497 (through EFI BCD) and FlashBootPro 3.3n bootmgfw.efi using the XP x64 SP2 installation generated by XP2ESD installer. Now that you know, I want to remind you that actually in my case, there's only one monitor (the laptop's built-in monitor obviously), one graphics adapter, and a windows 7's standard VGA graphics adapter driver (I reinstalled XP's VGA graphics adapter driver by fixing the enum entries in registry) for the display (vgasave is only supposed to be start in safe mode, not simultaneously on normal mode with the vgapnp driver). I have the proper mounted devices installed, and a videoprt service (service set to boot, group set to video, error control set to normal) to force videoprt to boot, so If I uninstall the Standard VGA driver from device manager, XP will reinstall it on real hardware after reboot just like in VirtualBox on Legacy mode. When I uninstalled the vbemp driver, I didn't do it from device manager, I did it from registry, I modified the VGA driver enum to point to the Standard VGA driver instead of vbemp, I deleted the vbemp service, inf and sys files, I also removed the entry key of the vbemp driver's VideoID containing the resolution. But XP still recreates the driver in this way. I also did a reinstallation of the VGA driver again but this time from device manager and I overwritten the VGA sys files with the ones from Windows 7, so XP x64 SP2 could boot from safe mode on UEFI Class 3, but still, the problem of two "monitors" being present persists and being enabled simultaneously causes glitches so that's why I disabled the second one.
That's was (and still is) a pretty common "problem" on physical machines. HDAudio is just a family not a single implementation, there are a zillion of different combinations of codec chips and chipset implementations, some of them aren't managed properly by the generic driver not even in W10/11, but obviously the older is the OS the greater percentage of unsupported/not working combinations you find. So saying that a HDAUDIO works in VBox and not in VMware means basically nothing other than they are emulating two different audio cards. In vmware just use the realtek drivers or change the audio device from hdaudio to SB16 or SB PCI
@George King I think I know why FlashBoot 3.3n bootmgfw.efi file works on XP for me. I used Windows 7's VGA files vga.sys and vgapnp.sys (they're designed to also offer the minimum screen resolution supported by uefi and have a higher maximum resolution than XP's vga drivers). Without Windows 7's two vga files, no display shows on FlashBoot 3.3n on XP. You need to include windows 7's vga.sys and vgapnp.sys files into XP2ESD's apps folder (the 2 vga files have no missing imports). Not only that, but it also improves display on safe mode so it's not restricted to 640x480.
Do you still have the install ISO for XP that works on UEFI Class 3 hardware, and would you be willing to send me it?
Just so you know, it works with the ISO generated by XP2ESD Builder (because it has the needed files and drivers needed). Remember that I had to install XP on VirtualBox (I configured the VM to use AHCI and NVMe controller, the same processor type and cores as my host, 2GB Ram, KVM paravirtualization enabled, TPM 2.0 enabled, USB 3.0/XHCI enabled) using the XP2ESD installer to skip through the Sysprep process. I changed the drivers to standard in the device manager. I shut down the VM, mounted it, put the contents of the XP installation into a WIM image, put the XP image onto an extra partition on my HDD (I created with partition wizard), created the needed BCD entries, created an EFI boot entry pointing to flashboot 3.3n bootmgfw.efi, I used Windows 7's generic VGA drivers, Dietmar's acpi64bitcrack.sys, created a service to videoprt, set the controller on my host hardware to AHCI mode and now XP boots only from FlashBoot on UEFI Class 3). I already explained how I did this: https://forums.mydigitallife.net/th...-installer-v1-6-2.82935/page-127#post-1796741
Hi everyone, while you'r here please have a quick look at this post Some future ideas that may or may not pan out, but for starter, we try to collect all files first.
@George King ; C:\XP2ESD\plugins\setup\dotNetFx_AIO_x86.exe C:\XP2ESD\plugins\setup\dotNetFx_AIO_x86.txt (dotNetFx_AIO_x86.exe /ai /gm2) C:\XP2ESD\plugins\setup\K-Lite_Codec_Pack_1385_Full.exe C:\XP2ESD\plugins\setup\K-Lite_Codec_Pack_1385_Full.txt (K-Lite_Codec_Pack_1385_Full.exe /verysilent) txt files do not work. Why is the new version not used? Resource Hacker Version 5.1.7 Last updated: 3 January 2019 7-Zip 23.01 (2023-06-20) Snappy Driver Installer Origin Version 1.12.14
Will check how its done, we have disccussed it already few months back over PMs. It should use Longhorn 4074 drivers detection mechanism, same should be with sysprep. Also winload should be used by default to support it. For example adding few more files to XP WIM open doors to different patching scenario for setup engine. I’m fine with current method. Im interested only in that kind of sysprep. He worked on that more than 15 years, hope it will work..
I’m finishing my work on upcoming 1.7 release. Drivers collection is growing. New compiled GenAhci 6.3 based on WDK 8.1 source sample. I found also few more interested samples code accross different betas of WDK and DDK. Mostly I’m working now on MultiLanguage support. For example XP x64 MUIs as addons with ability to build it automatically.