Jakob99

This thread is for the discussion of Windows XP drivers that do not currently work or are broken under 2000, even with the Extended Kernel/Core, and there are many. While several XP drivers have been made to work (e.g. Intel Ethernet, Broadcomm Ethernet, USB3, etc, etc), a lot do not work, or do, but are broken in some fashion. I'm gonna list off the ones that I know for sure do not work or are broken: Not working: *Intel Centrino WiFi cards *Broadcomm WiFi cards *Realtek WiFi cards (like the 8188 and so on) *IDT audio (most commonly seen in Dell Latitude laptops from 2010 or so to 2014 or so. Without this, no sound output on laptops like Latitude E6530). *Intel HD Graphics for Intel Haswell (but the XP driver is broken. If it could be fixed, I see no reason why it wouldn't also work on Broadwell a la Skylake graphics working on Kabylake to Comet Lake) Broken: *Qualcomm Atheros AR5B125 and related WiFi cards (It works, but whenever I have it enabled, the computer lags severely due to an increase in CPU usage caused by @blackwingcat's driver) I'm not really concerned about getting the Atheros AR5B125 card working properly as it has issues with the Windows XP One-core API (I have a multi-boot of 2000, XP-64, Vista, and 7 on Aspire E1-531). Realtek, on the other hand, does not have issues with ocapi, so I would appreciate it if we could get such cards like the 8188 and 8179 working under 2000 (both of which I have). These seem like they would be easier to mod than the Intel Centrino cards, but, when I changed NTx86.5.1 to NTx86.5.0, 2k still tells me there is no compatible driver. Even leaving it as 5.1 produces the same message. If there are any other essential drivers not working or are working, but broken, please do feel free to post em!

Cool! I don't need those as in Windows 7 and earlier, the touchpad is picked up as PS/2 (Only in Windows 8 and later is it I2C). The problem is, Windows XP isn't detecting my PS/2 touchpad, so I have to use USB mouse.

Hi! Using a modded ACPI.sys from @K4sum1, which I think came from here, I was able to get XP 64-bit to install on my Dell Inspiron 3542 laptop with Intel Haswell, but with one glaring exception; The touchpad is not detected at all. Like, I cannot use it and need to use USB mouse. Looking at the touchpad properties in device manager under 7 (where it works fine), shows ACPI something something under hardware/compatible IDs, meaning, something in the modded ACPI.sys or whatever is not telling the computer to activate the touchpad under XP. The touchpad is Synaptics, and it works on Windows 7 and later just fine. I should note that in 7, it is registered as a PS/2 touchpad, but in 8 and later, it is registered as I2C touchpad, with no setting in the BIOS to change the touchpad mode (unlike other laptops such as Acer). No way XP is trying to register it as an I2C touchpad, lol. I was wondering if anybody here had a solution in getting the touchpad detected (I don't care about the Synaptics driver right now, only the basic Microsoft PS/2 driver). I should also note that it tells me to plug my laptop into the charger, even though it is. This also does not happen under 7 and later.

I noticed a side-effect when using Windows XP 64-bit on my Dell Inspiron 3542 after using the modded ACPI.sys @K4sum1 gave me; The mouse doesn't work, and is not detected at all, and it tells me to plug my laptop into a charger, even though it is. These problems do not happen on Windows 7 and later. One thing I also noticed is that this touchpad is an I2C/PS2 combo touchpad, but, this one is different than later ones. Usually, when you have a touchpad like this, there would be a setting in the BIOS to switch between I2C and PS/2 (so, for Acer's, it would be Advance for I2C and Basic for PS/2), but, for this Dell, there is no setting in the BIOS and it is dependent on the OS installed. For example, XP 64-bit has no mouse detected whatsoever, Windows 7, it is PS/2, and Windows 8 and later, it is I2C. I have not even tried Vista on this due to the Haswell bugs, but I wouldn't mind trying that if a fix is found for that. I'm gonna also post this in the ACPI thread as well to see if a solution can be found.

VESA will work fine with 32-bit, I can confirm, however, when I tried it with 64-bit, it did not work. Yeah, you do need to copy a file into System32 manually, as apparently the inf does not tell Windows to copy it over, but despite that, it still Code 10.

Would it be possible for you to procure a copy of POSReady2009, install it, and try it?

I am reading this now! Thank you for sharing! Ahh. I wasn't sure if POSReady 2009 would have a few extra dependencies added in to facilitate the the POS features. Has anyone actually installed POSReady 2009 to a consumer computer. If so, were these same BSOD's present as well?

You'd have to ask @K4sum1 for the version he is using. I wonder... Are there any dependencies in POSReady 2009 that aren't in normal XP?

Let's try this again: https://msfn.org/board/topic/170950-windows-2000-on-haswell/ Now it works. Idk why it wouldn't work with the embedded link.

Test

Has anyone managed to backport the XP Haswell graphics driver to 2000 by chance?

I've used the 32-bit XP on Haswell as well as its graphics driver, and I got the same thing. These BSOD's are why @blackwingcat has not ported the driver over to W2K yet. If these could be fixed for all Haswell's, and then made to work with Broadwell as well (since it is based upon Haswell), then it could then be backported to 2K, allowing for a graphics driver for 2K under Haswell and Broadwell without needing a modded AMD/Nvidia graphics card in there also. See also this for valuable information: https://msfn.org/board/topic/170950-windows-2000-on-haswell/

Hi! Me and @K4sum1 have a Dell Inspiron 3542 (Mine. laptop with Haswell) and a Dell Latitude E7250 (K4sum1's. laptop with Broadwell). We both got Windows XP 64-bit installed to it, but can't get the Intel graphics to work without a BSOD. On my 3542 (Haswell), it asks me to restart, but upon restart, I get a SystemServicesException 3B BSOD, forcing me to go into Safe Mode to revert the driver back to the Standard VGA. If I'm remembering correctly, when I tried this on my Inspiron 3847 (Desktop with Haswell), I got Page_Fault_In_Nonpaged_Area, which would be a different BSOD if I'm correct. Unfortunately, I have since sold that tower. K4sum1 thinks, and I agree, that the XP Haswell driver could work on Broadwell, since Broadwell is based upon Haswell, but when he tried it on his E7250 (Broadwell), he got the Page_Fault_In_Nonpaged_Area BSOD. We both agree that the driver is botched, but aren't sure exactly how it is botched. If this issue could be fixed for both the 32 and 64-bit driver (both have this issue), then the Haswell driver would thus work under my 3542, then K4sum1 could then work on getting it compatible with Broadwell. If both go well, then @blackwingcat could backport it to 2000, which would give us a 2k compatible graphics driver for both Haswell and Broadwell. Is there anyone out there who could potentially fix the BSOD problems me and K4sum1 face when trying to use this driver? I'll upload screenshots of our respective BSOD's to Imgur as well. TIA for your help! https://imgur.com/gallery/windows-xp-64-bit-bsod-after-installing-haswell-graphics-driver-on-haswell-broadwell-systems-49YBBJc Device ID for Intel Haswell HD Graphics - GT1ULT: PCI\VEN_8086&DEV_0A16&SUBSYS_06511028&REV_01 K4sum1 will post his Broadwell Graphics ID later.

I got this error on a Dell Inspiron 15 3542 laptop with Haswell, even with modded ACPI. The ACPI.sys I tried was given to me by K4sum1, and I know it works properly, as I've used this successfully on my Acer Aspire A315-21 (long gone). The BIOS is American MegaTrends APTIO Setup Utility. UEFI is disabled, Fastboot is disabled, USB is plugged into USB2 port... I know XP works perfectly on Haswell as I've gotten it to install with no ACPI mods needed on my long-gone Inspiron 3847 desktop tower (I'm wondering if a few of those were originally made with Ivy Bridge before they stuck Haswell in them. I know they have a few with AMD inside).

@win32 How close are we to being able to use Windows 7 WiFi/Ethernet drivers with the Vista Extended Kernel? A friend of mine wants to know as his Intel WiFi/Ethernet support 7 at a minimum, not Vista. TIA!

Weird that I can post here, but not in his XP UEFI Class 3 thread... I keep getting 403 Forbidden when I try to reply. Anyhow, I'm gonna take this and the XP one and port them both to my website if that is ok. MSFN has been finicky as of late, and I do not want these to be lost!

Tried it and it didn't work

That's weird... I thought 8.0 (6.2) supported eMMC's out of box?

Virtualization features. You need these enabled to use VirtualBox or VMWare.

IntelPEP.sys must be deleted, otherwise the BSOD will keep happening. Updating the OS will cause the file, and thus, the BSOD to return, but it can be fixed again by simply deleting the file again. The INACCESSIBLE_BOOT_DEVICE BSOD that you are getting could be the result of the drive mode. Most newer Intel laptop's default to VMD mode, which is only compatible with Windows 10 and 11. You will need to pop open the BIOS and switch it from VMD to SATA mode. This will fix the BSOD, although, how you got 8.1 to detect and install to the drive (if it's set to VMD mode), I do not know. Maybe it's not set to VMD mode. Who knows.

I had whitebear do that and there was nothing. I had him disable a few things like Parallel and Serial ports (in case those were erroneously being picked up as a floppy drive, like with Windows 2000 on InsydeH2O BIOS), Intel Turbo and Fastboot, TPM, and even USB3. I did give him my WinXP 64-bit ISO on the off chance the ISO he was using is somehow corrupted.

I'll delete that part, then. Forgot about that rule.

I have an Acer Aspire A315-21 and I decided to mess around with Windows Vista, and with the help of @K4sum1, got the AMD graphics to work wonderfully after installing @win32's Extended Kernel (I also got XP 64-bit to install). Laptop Specs: AMD Radeon 9220e Radeon R4 5 compute cores 2C+3G 1.60 GHz. 8GB of ram (can be upgraded to 12, but allegedly can be upgraded to 20 by putting a 16 in there, but this is untested by me, and I offer no guarantees!) Acer Aspire A315-21 with Ethernet, USB3 port on the left, below the Ethernet, and two USB2 ports below the power supply plug. AMD Radeon R4 Stoney Ridge Graphics. 1TB SSD (for this test only. The actual product will ship with a 256GB SSD that has Windows 10 Home Edition). What I got working: Realtek Audio Realtek Ethernet Elan Touchpad The entire AMD Chipset including USB3 and SATA except for AMD Serial IO AMD Graphics. Realtek Card Reader. What didn't work: Qualcomm Atheros QCA9377 WiFi (unsupported card, needs to be swapped out with a Vista capable card, Ethernet used, or USB WiFi carried in). Qualcomm Atheros QCA9377 Bluetooth (although you can get rid of its Unknown Device by installing the Generic Microsoft Bluetooth Device). AMD Trusted Platform Module 2.0 (this caused a BSOD upon installing it if I'm remembering correctly). Untested: NVMe (I could never get the NVMe slot in this laptop to work with any of my drives. Maybe they are the wrong type, who knows). Known Issues: There's nothing show-stopping here. Does not suffer from the Haswell bugs obviously, but more importantly, it does not suffer from the Ryzen BSOD bugs! The perfect platform for running Vista on 2019 hardware! Properties: Device Manager: AMD Radeon R4 Stoney Ridge Graphics: AMD PSP 2.0 Device: AMD SATA Controller: AMD USB 3.0 Host Controller: Qualcomm Atheros QCA9377 (unsupported on Vista): Enjoy! EDIT: Yes, this topic was inspired by @Carlos S. M.'s topic on running Windows 7 on Alder Lake. You can tell by the format of this thread being very similar to his, lol.

Hi @UsefulAGKHelper! I have Coffee Lake as well, but inside a Dell Precision 7530! It is also UEFI Class 3, like yours (although it does contain a Legacy Mode that cannot boot internal devices such as hard drives, only external devices like USBs). I did not think it was even possible to install XP on machines like ours, so I'm gonna have to try this out and see what happens! As for the Intel Serial IO I2C Host Controller, I have never gotten the Skylake driver to work under Coffee Lake and Windows 7, even after modding my Device ID, and others, into it! I don't know why exactly it doesn't work. If I use Opencore to load specific DSDT tables, I can get the Intel HID-Event Filter driver to show itself within 7's DM (it's hidden in normal boot due to how the DSDT is programed to dole out devices based on the OS requirements for said device), but this has no effect on the Serial IO drivers. If it doesn't work under 7, it won't work under Vista, let alone XP. It does, however, work just fine under 8.1, so there is something in that OS that it wants that would need to be backported, but I have not figured out what this is. Also, I'm surprised the DM exposed the Serial IO drivers from the get-go. I'm surprised there isn't a version check on those in the DSDT tables that blocks them from being seen within XP/Vista. I do wonder, if AMD Serial IO drivers could be forced to work under an Intel board... In the Windows 7 on the Intel Alder Lake Z690 thread, @Carlos S. M. managed to force the AMD XHCI driver to work despite it being an Intel USB board, so that's why I'm wondering if AMD Serial IO drivers could be forced. I'm gonna try that soon as well.

Your best bet is to hook into Ethernet (whether it be Broadcomm, Realtek, or Intel, those drivers are eays to find) and then run Snappy Driver Installer Origin. This should pick up the WiFi driver, after whic you can discard Ethernet. For some reason, Windows XP and Vista Centrino drivers are insanely hard to find! Only Windows 7 and later seem easy to find (as you can find them on the computer manufacturers website).