reboot12

Yes, when I check what and how, I will add the eMMC driver to my guide on MDL

I haven't tested 32-bit drivers because I don't have where or how. I used the 64-bit George King Generic_SD+MMC_6.2.8056.0 from DP_Ported_DriversCollection_v46.7z (x86/x64) drivers that he recently shared a few posts ago. I only modified the sdbus.inf and sdstor.inf files a bit, but the driver will probably work without any modifications. This is my 64-bit driver for PCI Mode: https://www.mediafire.com/folder/oegoaaxeyy8cp/5_eMMC My inf files is 99% copy/paste from Win8.1 but: changed NTamd64 to NTamd64.5.2 added ID PCI\VEN_8086&DEV_2294 changed start services mode Start=3 to Start=0 changed Group type from System Bus Extender to Boot Bus Extender - not tested is this really nedded no localization strings - only english But if the eMMC controller works in PCI mode, the standard PCI\cc_080500 or PCI\cc_080501 matching ID should be enough.

@Dietmar Yeeeeeeeeeeeeeeeeeeeeeeaaaaaaaaaaaaaaaaaaa. For the first time in the world, WinXP 64-bit in pure UEFI from an eMMC disk !!! same acpi.sys 5.2.3790.7777 built by: ddi2 as I use in my modern WinXP tutorial eMMC driver from @George King modded .inf by me eMMC disk size is 8 GB and my WinXP occupies only 1.22 GB all size (I tested installation Win8.1 Lite but occupies 90% disk space) for install I use USB with Win8.1 installer because this support eMMC I had to remove the original sdbus.sys and sffdisk.sys drivers from the system (also from the Driver Cache), need change in hidden bios settings eMMC mode from ACPI to PCI Mode and add Intel eMMC controller Device ID 2294 to critical list devices in regedit: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase I've been waiting for this for a long time. P.S. Now I will also try on Dell Wyse 5070 Gemini Lake on eMMC - maybe I will also succeed ???

@Dietmar Yeeeeeeeeeeeeeeeeeaaaaaaaaaaaaaaaaaaaaaaa I fixed code bootvid - now support: auto detect memory address graphics card auto detect many popular resolutions // Walidator rozdzielczosci BOOLEAN IsValidRes(ULONG w, ULONG h) { if (w >= 800 && w <= 3840 && h >= 600 && h <= 2160) { if ((w == 800 && h == 600) || (w == 1024 && h == 768) || (w == 1152 && h == 864) || (w == 1280 && h == 720) || (w == 1280 && h == 800) || (w == 1280 && h == 1024) || (w == 1360 && h == 768) || (w == 1366 && h == 768) || (w == 1440 && h == 900) || (w == 1600 && h == 900) || (w == 1600 && h == 1200) || (w == 1680 && h == 1050) || (w == 1920 && h == 1080) || (w == 1920 && h == 1200) || (w == 2560 && h == 1080) || (w == 2560 && h == 1440) || (w == 3440 && h == 1440) || (w == 3840 && h == 2160)) { return TRUE; } } return FALSE; } BSOD is displayed always centered screen is not cleared before BSOD detected resolution is displayed in bottom right screen corner

@Dietmar Yeaaaaaaaaa - I make new versions bootvid.dll for BSOD - auto find graphics card and no clear screen: top left centered Now, when testing drivers under WinXP UEFI, I see a BSOD on the screen This is very helpful if I cannot debug in WinDbg via COM or LAN port e.g. on my Dell Wyse 3040 little PC. @Dietmar Problably BSOD be same as in WinPE 3.1 when you tried patched before.

@Dietmar Yeeeeeeeeeeeaaaaaaaaa I built from scratch a bootvid.dll driver (hardcoded version) for WinXP 64-bit that can display a BSOD on the screen if OS boot in UEFI mode It only needs to hardcode the current graphics card memory address and the native resolution of the monitor: I also built a version that automatically finds the address of the graphics card but cannot read the current resolution and uses hardcoded resolution and displays the BSOD only well in hardcoded resolution. On any other resolution BSOD it is corrupt: But of course possible compile bootvid.dll auto-scan memory addres and use hardcoded any custom resolution e.g. popular 1920x1080

WOW, please give me source code or compile for me WinXP 64-bit driver to test.

CLOVER on Legacy or UEFI? For UEFI try like this: on USB FAT32 stick put clover files: EFI\CLOVER\ACPI\patched\DSDT.aml EFI\CLOVER\ACPI\origin EFI\CLOVER\cloverx64.efi EFI\CLOVER\config.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Name</key> <string>DSDT.aml</string> </dict> </dict> </dict> </plist> boot to UEFI Shell and run cloverx64.efi table should be loaded if you press F5 now then table should be writen to origin\DSDT-0.aml but after load Windows - I tried Win 8.1 DSDT table is original - not patched ??? You might also try ACPIPatcher.efi > https://github.com/jslegendre/ACPIPatcher For WinXP 64-bit I tested registry override with asl.exe and works - no BSOD: acpidump -b -n DSDT -z iasl -d dsdt.dat edit dsdt.dsl and save as e.g. dsdt_fix.dsl iasl dsdt_fix.dsl asl -loadtable dsdt_fix.aml Now table is in registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ACPI\Parameters I use: asl.exe 64-bit 6.3.9600.16384 from WinDDK 8.1 iasl-win-20180105.zip - this is latest version working on WinXP (I don't know why these tools are only in the 32-bit version, but they work OK on WinXP 64-bit)

@Dietmar Apparently acpidump.exe reads the table from RAM AIDA64 reads from the bios If I use asl.exe, which inserts a table into the registry, acpidump.exe reads it, which means that the overwriting probably works correctly.

@Dietmar Have you ever tried patching the DSDT table and override e.g. using CLOVER or asl -loadtable dsdt_fix.aml it? I tested override using asl and work on WinXP - this add table to registry. CLOVER replace also in UEFI Shell but on Win 8.1 DSDT is back oryginal.

@Dietmar v12 v13

@Dietmar v10 v11

@Dietmar

@Dietmar

@Dietmar AI wrote to patch acpi.sys you need find KeBugCheckEx and change CALL to NOP (90). This function is in offset 0x4A1E8