Jump to content

Jakob99

Member
  • Posts

    354
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    0.00 USD 
  • Country

    United States

Jakob99 last won the day on October 5 2021

Jakob99 had the most liked content!

2 Followers

About Jakob99

  • Birthday 01/25/1999

Contact Methods

  • Website URL
    http://windowsenthusiasts1.epizy.com/

Profile Information

  • OS
    Windows 7 x64

Recent Profile Visitors

6,384 profile views

Jakob99's Achievements

75

Reputation

  1. 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!
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. Would it be possible for you to procure a copy of POSReady2009, install it, and try it?
  7. 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?
  8. 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?
  9. 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.
  10. Has anyone managed to backport the XP Haswell graphics driver to 2000 by chance?
  11. 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/
  12. 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.
  13. 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).
  14. @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!
×
×
  • Create New...