UsefulAGKHelper

By errors I can also mean things not working they way they should like the display freezing but the OS still loading. Btw, I am only talking about XP x64 on UEFI x64.

@reboot12 Regarding your solution of always using vga.sys at first deployment, you can also change the service in your video driver by changing the Service string to the name of VgaSave from Vga inside the enum key, to the key that matches that hardware ID of the driver (change permissions in the Enum key to edit the contents inside the Enum key). If the installation of any driver has removed the service needed by that driver (due to inf errors etc), the keys can be added to the key matching your hardware ID (assuming that the service was present but didn't integrate properly in the driver's enumeration entry) to prevent future errors in the respective driver (as you see in your enum key, the keys match the hardware IDs of the driver you're looking for). For example, I use vbemp legacy vga driver (as the VgaSave service instead of the ms vgasave) and it's always loaded on the device manager without errors. I disabled pnp vbemp (to prevent delay at bootscreen) and I used only the non-pnp vbemp driver that is named vga.sys.

I don't understand why I kept receiving infinite boot delay with this acpi.sys. The problem was fixed after using the previous acpi.sys that I had used.

Thank you so much!

@Mov AX, 0xDEAD @Dietmar Can you guys please give me the download link of the latest V8 WIP 2.0 acpi.sys that you have?

Btw I realized that in the vgapnp.sys and VGA.sys windows 7 generic drivers, they're still the same because the vgapnp.sys (from win 7) I have for XP has vga.sys as internal filename and has same size as the vga.sys file.

Instead of deleting the display.inf file, rename it to display.inf.old to prevent the installation. I prefer methods that only disable and do not remove the files and services in case of problems (for backup purposes).

Thank you for adding StartAllBack Canary, the system tray is back!

@Dietmar I would like to know how to debug individual drivers (sys files etc) on the same computer. How do you do it?

@Mov AX, 0xDEAD Is there a problem with the upcoming workarounds for ACPI 2.0? Is that why are you delaying?

Oh, that's terrible. How can this be fixed in Canary?

@Tihiy This bug isn't supposed to happen... What happened to the system tray and the clock, why it's gone? When I disable StartAllBack's taskbar, the system tray and the clock show from Windows 11's default taskbar. When I try to use the start menu's search bar, the screen is covered in the Mica effect, as shown in the second screenshot. Please fix this! I am using Windows 11 25931.1000 Insider Preview.

@Mov AX, 0xDEAD@Dietmar Can you please tell me the current progress of the ACPI 2.0 driver?

Since July 10 (made public since July 11) I have managed to run Windows XP x64 SP2 (built using XP2ESD) from UEFI Class 3 on Coffee Lake Windows 11 laptop on winload.efi 16497 using FlashBoot 3.3n bootmgfw.efi and Windows 7 generic VGA drivers by modifying the contents of mounted devices and enum key. I have used the XP2ESD build which contains the backported generic drivers and ACPI 2.0 drivers (from here) to get this to work. So far I tested acpibit64crack.sys from Dietmar. The fact that I managed to boot XP on such new hardware means that the ACPI 2.0 worked! Touchpad doesn't work because there aren't any working XP drivers for Intel Serial IO I2C Host Controller (9DE8 and 9DE9 in my case) to get the Elan1200 I2C Hid device to install using the backported generic touchpad driver from windows 8. USB XHCI controller and USB 3.0 root hub work without problems so I can use external mouse (for the cursor) and USB wireless adapter (for internet). I don't know if it's caused by ACPI incompatibility but I have tried to backport the Intel Serial IO I2C Host Controller from Windows 7 and it still wouldn't work even with Mov's ntoskrnl emu extender files! I have provided the device manager entries of my XP installation (from the enum key) so you can see the information on the drivers installed in my working XP OS.Useful's-XP-device-manager-entries.txt

My point still stands. Btw we should stop going off-topic here.