Jakob99

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.