reboot12

On Dell Wyse 5070 in Win7, no eMMC driver works and the system causes the eMMC disk disappears from the BIOS and UEFI Shell: https://msfn.org/board/topic/186861-emmc-disk-in-winxp-3264-bit/#findComment-1281375

Maybe the @George King eMMC driver is good, but the XP does not see the disk just like the Realtek sound card https://msfn.org/board/topic/186847-winxp-sp2-64-bit-on-asus-j1800i-c-baytrail/#findComment-1281009 I am also trying to use the eMMC disk in Win7 but also does not see the disk. In addition, if I restart the computer from Win7, the eMMC disk disappears in the bios (EMMC Device: none) and UEFI Shell (no fs1: Ctrl device): To be visible, I have to close the system, disconnect the power cable for a few seconds, connect the cable back - I need cold start. Bios - EMMC Device: 16 GB, UEFI Shell: fs1: Ctrl device present:

I found information that for Windows 7 to support the eMMC disk you need to update the storport.sys file - Windows6.1-KB2732471-v2-x64.msu https://www.sevenforums.com/drivers/429158-how-do-i-run-windows-7-emmc-laptop-post3528065.html https://www.sevenforums.com/drivers/429158-how-do-i-run-windows-7-emmc-laptop-post3528072.html https://www.betaarchive.com/forum/viewtopic.php?p=480427#p480427 KB2732471-v2 update storport.sys is 6.1.7601.17956 I use WinXP x64 AHCI, NVMe ported drivers from @George King and storport.sys 6.1.7601.25735. If the version is newer, it means that it contains eMMC fix from 17956 ?

I have a Dell Wyse 5070 test machine with two disks - eMMC 16 GB and M2 SATA 128 GB I installed on M2 WinXP 64-bit in pure UEFI and the OS works well. I have ported eMMC drivers but the system does not see eMMC disk both on system drivers and on those ported. There is only an SD controller device in the Unknown section in the Device Manager: I added HW ID PCI\VEN_8086&DEV_31CC controller to the sdbus.inf file but nothing helps. eMMC_xp64.zip Installation of the KB934428 update does not help either. P.S. Same eMMC disk works OK in Win10:

Eh, everything is described in this forum - learn to look for before you write senseless posts https://msfn.org/board/topic/183956-asus-b85m-e-with-core-i5-4590-code-10-in-device-manager/ https://msfn.org/board/topic/176356-simple-xp-32bit-64gb-ram-true-pae-guide/page/10/#findComment-1280987

Normally the same as in the PCIe HD graphics card, e.g. AMD HD7450: Audio output from Intel CPU is over HDMI, DP or DVI (DVI only if in bios is function Audio over DVI and you need DVI > DP or DVI > HDMI cable:

I tried this on my Dell Wyse 5070 GeminiLake but Win7 installer still not see eMMC disk. My disk ID: PCI\VEN_8086&DEV_31CC I tried also replace some Vendor Device e.g. TED PCI\VEN_1679&DEV_3000 to PCI\VEN_8086&DEV_31CC in sdbus.inf but still not help: dism /mount-wim /wimfile:boot.wim /index:2 /mountdir:mount dism /image:mount /add-driver /forceunsigned /driver:eMMC dism /image:mount /add-package /packagepath:Windows6.1-KB2732471-v2-x64.msu dism /unmount-wim /mountdir:mount /commit I run installer pressing F8 then select Disable Driver Signature Enforcement

@Dietmar Yea, I found solution: extract devcon.exe tool from XP ISO > SUPPORT\TOOLS\SUPPORT.CAB to %windir% press Win+R and run gpedit.msc in Device Manager check Device ID MS UAA device - mine has DEV_0F04 go to Local Computer Policy > Computer Configuration > Windows Settings > Scripts (Startup/Shutdown) and open Startup click Show Files and using Windows notepad make script re_UAA.cmd (use yours MS UAA Device ID) @echo off devcon disable *DEV_0F04 devcon enable *DEV_0F04 click Add... > Browse... - select created script and click OK then close gpedit window restart WinXP after the restart, the system's starting sound is not heard and no speaker icon in tray but when the system starts fully, in device manager is OK and Realtek sound card works P.S. devcon.exe version must be same architecture - best from same ISO as installed OS because 32-bit version cannot disable/enable device in the 64-bit OS !!!

@Dietmar Yeeeeeeeeaaaaaaaaaa - it works After disabling and enabling Microsoft UAA Bus Driver for High Definition Audio, WinXP finds 2 new sound devices - Realtek and Intel. I have drivers for Realtek so I can install them now and the sound works Thanks a lot Dietmar, I would never think of disabling then enabling UAA can help detect audio devices I need to add a script to the autostart which restarts the MS UAA driver and should be ok.

Can you read with understanding? I do not have a dedicated card, both are integrated - one of the Realtek motherboard and the other with the Intel processor and both work OK in Win7, Win10. The point is that in WinXP they are not visible in the device manager so I can't install the drivers. And no, in the bios it is impossible to disable the Intel card integrated with the processor, you can only disable the Realtek card integrated with the motherboard but I do not want to disable because I have drivers to it and I would like to use it in WinXP:

@Dietmar What double ??? I don't use CSMWrap because the motherboard has native CSM These are two completely different sound cards - one is a Realtek 10EC 0887 integrated with the motherboard and the other Intel integrated with the CPU 8086 2882

BIOS UEFI 64-bit but CSM available. Hi. I installed WinXP (Legacy) but in the Device Manager I can't see any (?) Unknown device or (?) Multimedia device for sound card (Realtek or Intel). On Win7 and Win10 there is no problem with that and both sound cards available:

Unfortunately, after a few days of testing, there is still a problem with the lag on Haswell machine. I changed OS to my favorite - WinXP 64-bit - everything works ok and I have full access to RAM P.S. I wanted to add a RAM patch to my project on MDL - WinXP 32-bit on a modern PC (ISO boot.wim + install.wim) but since it works unstable, I will probably give up Maybe I will add as an alternative in the boot.ini and BCD file but not as default.

@Dietmar Please extract bios from this: https://dl.dell.com/FOLDER13218127M/1/Wyse_5070_1.37.0.exe

@Karla Sleutel Supermium 126.0.6478.254 64-bit, XP64-bit - works in PL

@Dietmar A CSMWrap version has been released, which allows you to use the BIOS video from the disk from EFI\Boot\vgabios.bin https://github.com/FlyGoat/CSMWrap/issues/37#issuecomment-3030297746 Compiled bins: https://github.com/FlyGoat/CSMWrap/actions/runs/16040013218 Thanks to this, WinXP boot OK on iGPU using ntldr as on a normal Legacy machine - I tested CoffeeLake, Haswell, SandyBridge: CSM Disabled, iGPU VBIOS extracted from motherboard bios. Now - I don't have to use SeaVGABIOS and Longhorn bootmgr 5472 loader.

WinXPPAE 3.5 can't patch any SP2 hal version: Patching halmacpi.dll (ACPI Multiprocessor PC HAL)... Invalid file!

I don't know, but if you compare patched kernel files 5.1.2600.6368 in a hex editor and are changed exactly the same bytes in the same offsets, it means that they work the same. You must first patch using a patcher v3.5 kernel file 5.1.2600.6368 ntkrnlpa.exe 5.1.2600.6368 > https://catalog.update.microsoft.com/Search.aspx?q=2813170 WinXPPAE.bat script default patch all RAM: WinXPPAE.exe /M:ALL /NOBACKUP so, put ntkrnlpa.exe (GDR version) and WinXPPAE.exe in same folder then patch as above: winxppae /M:ALL Windows XP PAE Patcher 3.0 by daniel_k | HAL patches by <Mov AX, 0xDEAD> PAE will be enabled using all available RAM. Patching ntkrnlpa.exe (Uniprocessor PAE Kernel)... OK! File ntkrpamp.exe (Multiprocessor PAE Kernel) was not found. File hal.dll (Standard PC/Standard PC w/ C-Step i486 HAL) was not found. File halaacpi.dll (ACPI Uniprocessor PC HAL) was not found. File halacpi.dll (ACPI PC HAL) was not found. File halapic.dll (MPS Uniprocessor PC HAL) was not found. File halmacpi.dll (ACPI Multiprocessor PC HAL) was not found. File halmps.dll (MPS Multiprocessor PC HAL) was not found. No, this is not simple to compare - too big differences :-( Probably ntkl64g.exe is compiled from source code. org vs v35 differ only in 11 bytes: Search for differences 1. org_ntkrnlpa.exe: 2 070 016 bytes 2. 35_ntkrnlpa.exe: 2 070 016 bytes Offsets: hexadec. 138: C2 04 139: FF 03 13A: 1F 20 16B632: 07 00 16B637: 01 02 1703C2: 74 EB 1BE554: 10 00 1BE555: 00 02 1BE56A: 1B 00 1BE572: FC F8 1BE576: 01 02 11 difference(s) found.

This is not impressive - simply this is patched ntkrpamp.exe for multi CPU/multi core use: Modern computers have multi-core processors and the use of RAM patch on old PC does not make sense because old computers with a single-core processor do not support a large amount of RAM and a patch is not needed. Therefore, the 64G patch does not contain other kernal and hal files.

@Ascii2 I make big tests: using Macrium Reflect clone OS to other HDD - still problem replace RAM modules - still problem use only 2GB RAM 1+1 - still problem using Macrium Reflect make disk image, then restore on other PC - Haswell 8GB RAM (4+4 Dual Channel), OS boot, find new devices, I install drivers. I test and it looks like there is no problem and WinXPPAE 3.5 works well :-) I use exactly same patched files and settings: ntkrnl2.exe SP2 5.1.2600.2180 + hal2.dll SP3 5.1.2600.5512, noexecute=optin I have to use the system for some time to make sure 100% that there is no problem. It seems that the problem is only on SandyBridge machines.

No. /PAE switch load Ntkrnlpa.exe I use only like this and PAE works: /noexecute=optin /fastdetect /kernel=ntkrnl2.exe /hal=hal2.dll Enabling PAE Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP The PAE kernel can be enabled automatically without the /PAE switch present in the boot entry if the system has DEP enabled (/NOEXECUTE switch is present) or the system processor supports hardware-enforced DEP. Presence of the /NOEXECUTE switch on a system with a processor that supports hardware-enforced DEP implies the /PAE switch. If the system processor is capable of hardware-enforced DEP and the /NOEXECUTE switch is not present in the boot entry, Windows assumes /NOEXECUTE=optin by default and enables PAE mode. You need use /NOPAE because default (optin) is enabled: https://web.archive.org/web/20060313135704/http://support.microsoft.com/kb/900524/

Yea, I use SP2: ntkrnl2.exe SP2 5.1.2600.2180 (patched by WinXPPAE 3.5 on SP2 OS) + hal2.dll SP3 5.1.2600.5512 (patched by WinXPPAE 3.5 on SP3 OS because the patcher cannot patches the hal.dll SP2 version) ntkrnl3.exe SP3 5.1.2600.5512 + hal3.dll SP3 5.1.2600.5512 - both patched by WinXPPAE 3.5 on SP3 OS ntkl64g.exe SP3 5.1.2600.6368 + hal64g.dll SP3 5.1.2600.5512 - files from @Dave-H 64 GB of RAM patch.zip I test (for a short time) my XP SP2 on other machines and probably no lag issue but this is fresh installed OS - no any drivers, apps. maybe lag issue is only on my SandyBridge machine recently I changed 2x4GB RAM - maybe they cause the problem? my OS has all drivers and many applications installed - maybe some application or driver works badly with a RAM patcher? I have to test the patch for a long time on other computers + all drivers installed. boot.ini [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="RAM v3.5" /noexecute=optin /fastdetect /kernel=ntkrnl2.exe /hal=hal2.dll multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="WinXP" /noexecute=optin /fastdetect This is my table when DEP/PAE works on WinXP SP2 depending on the setting of the noexecute option in boot.ini So, I do not have to use boot.ini switch /PAE because noexecute=optin is enough.

@Dietmar @Mov AX, 0xDEAD I use the WinXPPAE 3.5 patch for a week and I noticed a problem with disk operations - the same is for the 64G version: Video when ram patch is used - lags: https://files.catbox.moe/ericzb.zip Video when no ram patch: https://www.sendspace.com/file/17e170 Testing config: Asus P8H61-M LE R2.0 RAM 2x4GB DDR3-1600 Dual-Channel CPU Intel Core i3-2120 WinXP SP2 Pro HDD: SATA in AHCI mode

@Karla Sleutel Site work normal for me on Supermium 126.0.6478.254 64-bit What OS?

Windows Boot Manager 5472 test: https://github.com/FlyGoat/CSMWrap/issues/39#issuecomment-3014504946