Jakob99

Alright, so I tried your driver, and Intel HID Event Filter driver installs successfully with no error! Unfortunately, the touchpad still does not work as the Intel Serial IO drivers do not want to install. I tried the ones here https://www.mediafire.com/file/23np1m85w5za00a/Serial_IO_7th_Gen%2B_Win_7.zip/file but when I install them, I get a Code 31 error (Windows cannot load the driver for this hardware) or whatever that error is called. These are Skylake Serial IO drivers modded to include my 8th Gen Serial IO. Idk why this Windows 7 Skylake Serial IO driver isn't working as the Windows 8.1 Skylake drivers I modded work just fine under 8.1, so theoretically, the linked drivers should work, too! This should be the last hurdle in getting the touchpad to work under 7. I appreciate anyone's help in getting those drivers to work without producing a Code 31 error. EDIT: PCI\VEN_8086&DEV_A368&SUBSYS_08311028&REV_10 and PCI\VEN_8086&DEV_A369&SUBSYS_08311028&REV_10 (Intel Serial IO A368 and A369). Forgot to include my Device ID's for reference.

Hi! I tried your modded DSDT table. The Intel HID Event Filter driver now shows up as an Unknown Device within Device Manager, however, I still get the 0x07E BSOD when attempting to install the driver. This happened with Snappy Driver Install, as well as the official Intel installer (which no longer throws "This computer does not meet the minimum requirements" when launching it). Below is what should be BSOD logs as well as the Intel driver, which is unmodded as it already supports my device and Windows 7 (as nothing has changed with the device from Skylake to 8th Gen Coffee Lake). And yes, I even tried the GeorgeKing thing, and no changes BSOD logs: https://www.mediafire.com/file/l9cpkpm0adh1k4c/73BSODEVENTFILTER.zip/file Intel HID Event Filter driver, unmodded: https://www.mediafire.com/file/7y8y4i36t71qtqr/HIDEventFilterDriver-1.1.1.318-Windows_RS1_Certified.zip/file Any help on figuring out why the driver still BSOD's even after using your modded DSDT is greatly appreciated!

Great! Idk why mine threw the message then.

Sorry for the late response. Got sidetracked by the 4th of July holiday. Anyhow, I have uploaded the ACPI table (dsdt.dsl and dsdt.aml) here: http://windowsenthusiasts1.epizy.com/Downloads/dsdt.zip There were dumped from the Windows 11 install on the same laptop (as opposed to the Windows 7 installation), but I see no reason these shouldn't work. If, for some reason, you need them dumped from the 7 install, please do let me know and I will do so. EDIT: If you get a "File not downloaded, potential security risk" message when downloading this, just ignore it and allow the download to continue. Idk if Chrome will throw this error, but Firefox can/will.

I may be closer to solving this problem! It appears that the issue is this: https://winraid.level1techs.com/t/win-7-64-not-working-touchpad/94960/19?u=moline I can gather that the check on this laptop checks if you have Windows 8.1 or above, and if you do, the touchpad will be enabled and allow successful installation of the HID Event Filter Driver, and thus, the Serial IO drivers. If you have Windows 7, the check will fail and disable the touchpad entirely, meaning Windows 7 won't know it exists, and one of two things will happen when you try to install the HID Event Filter driver: 1. The setup.exe will tell you your computer doesn't meet the requirements (This computer does not meet the minimum requirements for installing this software), which is expected as the OS, and thus the app, do not know that the touchpad exists, or 2. you get a 7E BSOD with IntelHidEventFilter.sys identified in the stop screen when you try to install it over a HID driver from an external device, like USB Wireless Mouse. To fix it, the following will need to be done: https://winraid.level1techs.com/t/win-7-64-not-working-touchpad/94960/33?u=moline I'm still working on deciphering this. Basically, if the DSDT table is extracted, we can modify the check so that Windows 7 will pass and allow the touchpad to be seen within the OS, and allow it to function after installing the aforementioned drivers. The way to do this is commonly used for Hackintosh installs as Macintosh will fail the check no matter the version, meaning you'd have to edit the check so that Darwin (Macintosh) pass and allow the touchpad to work under it; since I'm not dealing with Hackintosh, we just have to adapt the tutorial for Windows use. I'll report back later.

I'd ask over at win-raid. They do BIOS modding over there, and may have a modded BIOS that brings up the Advanced Options.

What is your laptop? Acer Aspire E1-531, something else?

I can't believe I haven't posted this here yet, but K4sum1 managed to get AMD Radeon Graphics drivers, for use with AMD hardware such as Stoney Ridge, working under Vista, meaning we get Aero Glass now! This also opens up much newer laptops such as Acer Aspire A315-21 from around 2017-2019, meaning you don't have to go Ivy Bridge or 2015 AMD. All of the AMD Chipset drivers will work (you will need the latest one that supports Vista), but you will need to mod each INF to include your device ID, and you will also get many unsigned driver warnings, but they all work from AMD SATA to AMD USB 3.0. The AMD TPM 2.0 driver causes a BSOD (PSP 2.0 does not), so do not try to install it. The WiFi card and Bluetooth adapter will also not support Vista, so you'll either need to use USB WiFi, Realtek Ethernet, or swap out the WiFi card for a vista capable one. Out of curiosity, everything even works under XP except for the WiFi/Bluetooth driver as well as the graphics driver. You will, however, need a modded ACPI file. And a sidenote, I've never been able to get the VESA graphics driver to work on my Aspire A315-21, even with copying that one file manually. I do not know why it won't work despite doing it all seemingly correctly.

Ah, ok. I thought there was an option for thread creators to delete their own posts. Welp, they can go ahead and delete this since this thread is pointless now.

I guess I completely overlooked that. I will remove this now.

Removed due to the forum rules.

Ah. Does Aero rely on Direct3D9?

Interesting. I don't think I have quite the expertise to do this, but I know someone who may. Would this also apply to post-Ivy Bridge Intel graphics drivers such as for Haswell and later?

Couldn't the BIOS in this computer be modded to add in Legacy Mode? SP1 uses Ivy Bridge if I'm not mistaken, so it should be possible.

Anyone know if it's possible to get this Realtek 8821CE WiFi card working with Windows Vista? Thanks in advance for your help!

Yeah, but regardless, it shouldn't be there as the IA-64 version was never released to the public, only to those specific testers like Fujitsu-Siemens, as you mentioned.

There is nothing wrong with selecting an operating system from within Edit Profile, that works as intended, however, I think there is a mistake with it as one of the choices you can select is Windows 2000 x64 Datacenter, which, from my understanding did not exist outside of the planning stages and a few banners found within Windows "Whistler" XP (alongside the Windows 2000 Personal x64 banner). Hoping for some clarification here.

Do you have a link to your portable version of Office 2010 as well as the steps needed to pull this off?

http://win2k.org/cgi-bin/dl.cgi?file=iata76_cd2ke.cab&lang=en Try these. You can integrate all the SATA drivers as W2K should pick the correct one.

What's your Intel SATA driver device ID (you can find this under IDE ATA/ATAPI controllers).

We already have @blackwingcat for that, and he does an amazing job! If it weren't for him, W2K would not be working on Intel Sandy or Ivy Bridge.

Sorry for the double post, but I just wanted to say thank you to blackwingcat for all the amazing work he has done in getting Windows 2000 to work on modern hardware such as Sandy Bridge, Ivy Bridge, and even Haswell. Thanks also goes to Realtek for keeping 2k support for their audio and Ethernet (whether they forgot about it or they really do not change much when they "update" the driver for a new Windows release) and also to ALPS Touchpad for allowing the drivers to be installed onto 2k with a simple INF mod, and also to the good folks at win-raid for supplying me with the modded BIOS that made my installation possible! I do have a few bug reports, however. After installing the Atheros driver, the CPU usage increases. This was not problem prior to driver installation. I think I found a temporarily fix for this, which is to disable the network adapter unless I need to browse the web with MyPal until hopefully a more viable solution can be found. And there is also a weird caveat with audio drivers. You MUST install any audio drivers before installing Extended Kernel/Core. This includes: Realtek audio to even USB Bluetooth (make sure to sync your Bluetooth audio device after installation so the Bluetooth audio drivers can install. I think you'll be fine if you connect to a different audio device after installing the Kernel/Core, but, this has not been tested/proven as I only have one Bluetooth Audio device that I use) and other audio devices that install drivers. If you attempt to set any of this up after setting up Extended Kernel v31 and Extended Core 16b, it will not work even though the drivers do not throw any error codes (such as code 10) in the device manager. Realtek audio stops working (the computer reverts to the no audio driver installed beep when dialog boxes pop up) as does Bluetooth audio as well as Intel Display audio (this, afaik, can only be installed after kernel/core and will always cause this error until it is fixed). Idk why this happens. I'm hoping blackwingcat can figure out a solution. In short, audio drivers such as Realtek and Bluetooth audio installed prior to Kernel/Core will work, and will continue to work even after you install the kernel/core, just don't install the Intel Display Audio until bwc finds a solution and releases a kernel update for it.

I can confirm officially that MyPal 68 works splendidly under Windows 2000 as I am replying to this from that! Thanks to windows2 for this suggestion!

Edit: It works! No more procedure entry point error!

THE DRIVER WORKED!!!! THANK YOU SO MUCH!!!! With working WiFi, I can finally ditch Ethernet! Now time to find an internet browser that renders properly as not even Google Chrome does.