reboot12

@UsefulAGKHelper I used a Dell 3040 to test the eMMC driver and it worked, but the computer has poor parameters to use it for anything specific , so I don't care about I2C support. I'm basically not interested in laptops and unusual mini-computers. Besides, my goal was to add UEFI, NVMe, USB3 and ACPI support to WinXP 64-bit and I managed to achieve it, so overall the goal was achieved. I think I've had enough and don't want to continue patching - anyway, there's a lack of testers and too little interest I've done a lot anyway: I added UEFI boot support I added basic UEFI NVRAM Boot Menu editing support I added restart from OS to UEFI firmware I patched kdcom.dll and bootvid.dll to easy debugging I patched hal.dll for restart working I successfully tested booting from the eMMC disk I have my favorite modern desktop WinXP 64-bit computer with all working devices (full drivers) - 8 Gen CPU, 16 GB RAM, an NVMe drive from which it boots in 18 seconds + PCIe graphics card with working 3D and a large 2K monitor, sound, network. The motherboard in this computer does not limit me like a laptop or some unusual mini-computer with soldered CPU, RAM or eMMC disk: I decide which keyboard and mouse I will use - PS/2 or USB I decide whether I will use a SATA or NVMe drive I decide which graphics, sound and network card I will use - PCI or PCIe I decide what processor and how much RAM I will use I have COM ports for debugging

@Tech Stuff I managed to start a Bridged network connection You need to replace four 64-bit drivers from version VMware 10.0.7 in WINDOWS\system32\drivers vmnet.sys vmnetadapter.sys vmnetbridge.sys vmnetuserif.sys Thank you again for the patched version of VMware Workstation 11.1.4

You are writing nonsense opinions you have heard WinXP 64-bit is a stable system - I know what I'm writing because I have been using it for a long time and it works great Besides, before you write something, check if it works. I checked it and it works OK on WinXP 64-bit @Tech Stuff actually did a good job - his patched version works. Thanks for you

@Tech Stuff OK, after installing vcredist x86/x64 (Microsoft Visual C++ 2008 Redistributable - 9.0.30729.6161) VMware Workstation 11.1.4 works on WinXP 64-bit Is it possible to activate the network somehow? I can install VMware Bridge Protocol but I cannot add a Bridged connection: Cannot change network to bridged: There are no un-bridged host network adapters Other VMware connections do not appear in the network connections window in the WinXP control panel

At the end of the installation I get an error: Setup failed to generate the SSL keys necessary to run VMware Server. Click OK to cancel this installation.

Oh, maybe my screenshots are from C64 or MS-DOS Guy probably use one-core-api-base with patched kernel32.dll

I tried replace VMware folder and drivers from system32\drivers but errors: VMware 12.0.0 VMware 11.1.4

@UsefulAGKHelper Still no Realtek I2S device detected. Do these drivers work and get the job done on your Asus laptop? Do they initialize devices connected via I2C?

https://pastebin.com/kNtEgwaX - i2cctrl.log from WinXP Screenshots from Win8.1 before and after installing I2C driver:

@UsefulAGKHelper Yes, now there is no BSOD 50 anymore, but your drivers probably don't do the job because I still can't install the sound driver:

Sorry, but if you publish a driver, e.g. on github, you should first test it on at least several computers. I'm not interested in your Asus x509FA laptop. I would like to use I2C drivers on other computers.

@UsefulAGKHelper I'm sorry, but I have to wrote your attention: do not quote the entire post, select only important lines using e.g. ... ... do not quote entire logs or other things, e.g. what AI wrote - select important lines from them test your drivers before posting public if you need to post the entire log, use sites designed for this purpose, e.g. pastebin.com

@UsefulAGKHelper Your latest i2cctrl driver install OK but after about some seconds BSOD 50 appears:

uartctrl.log [21/06/2026, 09:13 AM] AddDevice: PDO=FFFFFADFD0B5E060 [21/06/2026, 09:13 AM] AddDevice: checking HWID 'ACPI\8086228A' [21/06/2026, 09:13 AM] AddDevice: checking HWID '*8086228A' [21/06/2026, 09:13 AM] AddDevice: no supported HWID matched i2cctrl.log [21/06/2026, 09:11 AM] DriverEntry begin [21/06/2026, 09:11 AM] DriverEntry complete (mask=0x00000009) [21/06/2026, 09:11 AM] AddDevice: begin [21/06/2026, 09:11 AM] AddDevice: scanning HWIDs for controller match [21/06/2026, 09:11 AM] AddDevice: HWID candidate: ACPI\808622C1 [21/06/2026, 09:11 AM] AddDevice: HWID candidate: *808622C1 [21/06/2026, 09:11 AM] AddDevice: unsupported controller, skipping [21/06/2026, 09:21 AM] DriverEntry begin [21/06/2026, 09:21 AM] DriverEntry complete (mask=0x00000009) [21/06/2026, 09:21 AM] AddDevice: begin [21/06/2026, 09:21 AM] AddDevice: scanning HWIDs for controller match [21/06/2026, 09:21 AM] AddDevice: HWID candidate: ACPI\808622C1 [21/06/2026, 09:21 AM] AddDevice: HWID candidate: *808622C1 [21/06/2026, 09:21 AM] AddDevice: unsupported controller, skipping

@UsefulAGKHelper I tried your drivers - all using force because no compatible ID's and only GPIO install OK. I2C or UART - errors Code 31 (cannot load drivers...) setupapi.log #I163 Device not started: Device has problem: 0x1f: CM_PROB_FAILED_ADD.