Leaderboard

Yep, but maybe the missing (or failing) driver is connected to *something* else. Try getting devcon from here: It should run in 8.1 (as Administrator). Open a command prompt navigate to where you put it (let's say C:\myfolder\ ) and in it run: devcon driverfiles *>driverfiles.txt (it will take some time to run) then run devcon hwids *>hwids.txt then compress to .zip the C:\myfolder\driverfiles.txt and C:\myfolder\hwids.txt and attach it to a reply. jaclaz

@HyperbolicEllipsoid Click on the field at the bottom of the page and type your reply, no need to quote every time, ffs! You will need a driver for that SD Host Controller. Also, research about "How to install XP on SD card". Your case should be almost identical.

Not necessarily. One thing is booting to XP (or to it setup) and another one is running it. All NT systems have a bootloader that loosely is made of two parts: 1) a "Real Mode" one (that needs BIOS services, provided by the CSM in your case) 2) a "Protected mode" one (that re-enumerates devices and starts the appropriate drivers) If a needed driver is missing you may be able to boot (and also to complete setup) but then the actual OS won't boot (or won't complete boot) and run. This ASUS TP200SA, what OS is it running now? You need to provide the Hardware ID of the controller PCI VEN & DEV, but if it is not in the driver pack it might be very difficult if not impossible to find a working one. I don't understand the reference you made to the Windows 10 disk.inf, the .inf is just a file needed to install a driver, not a driver. jaclaz

Some readers may not know what a broken record sounded like. In the days when music and other audio was sold on vinyl records, a crack or scratch often prevented the stylus (needle) from following the groove containing analog audio. In some cases the stylus skipped forward, but in a good many cases it skipped backward, causing the same passage to repeat over and over until someone intervened to break the cycle. I have seen many of your posts far and wide. Your preferred topic is always old Vista patches, but you seem to have an aversion to post-EOL patches (such as the one that was required to solve this thread), and you seem to believe that Firefox 52.9.0 is the only browser worthy of discussion. Your “broken record” analogy seems appropriate.

CSM (Compatibility Support Mode) is BIOS on EFI firmware. XP will work on both BIOS and CSM (they are the same thing). XP booted from EFI is also possible on MBR disks using some obscure Longhorn/Vista beta boot files: https://www.win-raid.com/t5438f45-Boot-WinXP-bit-bit-on-UEFI-bit-bit.html jaclaz

Steam verifications can be bypassed by placing a cfg near steam.exe it would seem , it would get rid of the checksum issue and stop redownloading everytime. Also used the Chromium 77 files from my Dec 2019 build and steam is still blank and steamhelper still crashes . steam.cfg

Open Device Manager, select View > Devices by connection, find the eMMC and check what is its parent device.