Jakob99
Content Type
Profiles
Forums
Events
Posts posted by Jakob99
-
-
8 hours ago, TSNH said:
Apparently someone has modified those drivers for Windows 7 and the are supposed to work on 8.1 too.
I know nothing about them so use on your own risk.
I can confirm that these work with 8.1. You will need to disable driver signature enforcement for these to work, however, and, at least in my case, the drivers will sometimes revert to the Microsoft Basic Display Adapter randomly, but your experience may differ of course!
0 -
1 hour ago, mina7601 said:
You're welcome!
It works!
3 -
9 minutes ago, mina7601 said:
https://ftp.mozilla.org/pub/firefox/nightly/2023/09/2023-09-26-09-27-49-mozilla-central/ (this is the latest, at the time of this writing)
From the above link, choose win64.zip version.
Cool! Thank you for the link!
1 -
On 9/24/2023 at 4:01 AM, yoltboy01 said:
Currently, Windows 8.1 can run the latest version (119). Since 120 Nightly will be released tomorrow, I think it will run as well. It‘s going to be the fifth post-EOL version to run on 8.1
I can confirm 119 works under 8.1. I did not see 120 in the Mozilla FTP, so I couldn't try that yet.
0 -
I am here today to show you off my website called Windows Enthusiasts. There are 18 tutorials on the website as of now. It also has an external links page that links to various threads from here, a downloads page containing some items used in the tutorials, a news archive containing all the post entries I made from the prior months, etc, etc. There is a mobile site link, but that is very incomplete. The site itself is nearing two years old, which it will hit on November 4th. You can view the website here: http://windowsenthusiasts1.epizy.com/?i=1
0 -
If you are running Windows 7 on a modern-ish laptop that supports 7 (e.g. Skylake, Kabylake, Coffee Lake, and later AMD and Nvidia), and the touchpad isn't working and you can't get its drivers installed, please save the following thread. Hopefully @George King can get the 8.0 I2C driver working under 7! Couple this with the Extended Kernel (if/when the driver is ported) and you'll have a sturdy Windows 7 laptop!
0 -
3 hours ago, George King said:
@Jakob99 I will check that file. I think I have ported one for XP (Generic_Touchpad_6.2.9200.16384), but have not tried it real machine. Will check it soon, as your not alone who searching for Generic_Touchpad driver solution.
I will check 6.3 driver to see missing imports and if we can get needed code for missing imports..
Awesome! I do not know if this file is also present in any 8.0 builds or if it was introduced only in 8.1. Also, the Intel Serial IO drivers will need to be made to work, too, from my understanding. I tried these (linked below), but I get a Code 37 if I install these after booting Windows 7 via Opencore (By booting 7 this way, it causes Intel HID Event Filter driver to show itself within DM). Maybe I should try installing those by booting Windows 7 normally (that is, not through Opencore).
EDIT: My Intel Serial IO device ID's are A368 and A369. A369 is the most important one as it is that one that allows the touchpad to function under 8.1. Another thing, the touchpad also does not function under 8.0 as the Serial IO drivers Code 37 there as well. For reference, Code 37 is "Windows cannot initialize this device (Code 37)"
0 -
Dell Precision 7530, Intel UHD630 graphics, Intel 8th Generation, Windows 11, 8.1, and 7.
As you'll know, Windows 8.1 contains a generic I2C HID Device Driver. This doesn't show up in device manager until after the Intel Serial IO drivers are installed. Intel Serial IO drivers do have drivers for Windows 7, however, as far as I know, there is no generic I2C driver, meaning you would need to install touchpad drivers before the touchpad works. This isn't a problem when installing on machines that support 7 like Skylake as either everything works or you can flip into PS/2 emulation mode in the BIOS.
When installing onto an unsupported machine like Kaby Lake or Coffee Lake, that's where things get dicey. For Windows 8.1, you can just install the chipset, restart into startup options, disable driver signature enforcement, mod the Skylake Serial IO driver to include your device (i.e. A368 and A369), and then install both to get a working driver, no Elan, Synaptics, or ALPS (Dell Touchpad primarily) drivers needed.
For Windows 7, it is not as clear cut! For instance, the Intel HID Event Filter driver, despite being unchanged since Skylake, will most likely not show itself within DM. This can be fixed by using Opencore to load a modded DSDT table and subsequently boot Windows 7 with it. Even then, the standard Windows 7 driver may BSOD upon installing (although, this may most likely be due to not having KB3125574, which brings in many stuff, including WdfLdr.sys driver that it relies in). This driver does not appear to be needed for the Serial IO drivers to work,
Now, if you load Windows 7 without the modded DSDT, installing the Serial IO driver will throw a Code 31 error and not work. If you use the modded DSDT, this will switch to Code 37 (after reinstalling the drivers of course). Even if we get the drivers to work, there would still be most likely no mouse function as there is no generic driver in the form of I2C HID, like in Windows 8.1. This would mean the touchpad driver (whether it be ALPS, Synaptics, or Elan) would have to be installed, but people have reported problems doing so, likely because they added in new HID touchpad devices since Skylake.
To get around this I2C HID (hidi2c.inf) from Windows 8.1 would have to be backported. This would introduce a basic I2C touchpad driver, like in Windows 8.1. While you wouldn't have access to the touchpad settings provided by ALPS (Dell Touchpad), Elan, or Synaptics, you would still be able to control it from the Windows Control Panel.
Now, the question is, how can we backport hidi2c.inf from Windows 8.1 to 7? I wonder if @George King has any ideas here. This is currently the only device not working under Windows 7 on my Dell Precision 7530. Not only would this help me, but it would help several other users who may be in the same boat as me.
0 -
Under the Intel Serial IO A368 and A369 devices (currently labeled Intel Device), I found this under "Parent" in the DM: ACPI\PNP0A08\0
This is also present under the Unknown Device. Updating this turns it into the Dell Free Fall sensor, but with a yellow mark (idr the exact error code I get when I updated it last). This suggests whatever that ID is tied to is "broken" and that getting it working will result in all three aforementioned devices working (I don't care about the Free Fall sensor, I just happened to see that it has the same "Parent" as the Serial IO devices).EDIT: This id is also shared by the already working UHD630, meaning, this may not be the issue.
0 -
Hi @blackwingcat! I keep forgetting to tell you this. Basically, your modded Qualcomm Atheros AR5B125 WiFi driver works under Windows 2000, however, I notice that when the driver is enabled, the computer becomes INSANELY slow, and I don't know why. If I disable the card, the slowness goes away and the computer is speedy once again. It's almost as if it is hogging all the resources, but idk. Any help on fixing this greatly appreciated!
0 -
4 hours ago, MaruKorea said:
didn't work. i need modded driver.
Even after adding your device id? Rats! You may be out of luck, unfortunately.
0 -
Try these. They should work. If not, you'll need to mod your device ID into these.
0 -
Main Article:
If you read that post, you'll see that @kar1 appears to needs KMDF from Windows 8.1 backported to Windows 7 to make my Intel Serial IO A368/A369 work under 7. This already works under 8.1 with no mods needed except to a Skylake Serial IO driver inf. On Windows 7, it has become more complicated and after days of back and forth with kar1, come to the conclusion that KMDF 1.13 is needed on Windows 7. So, my question is, can this be backported to 7? kar1 has said this has been done before when people backported KMDF 1.11 from 8.0 to XP (it was also released to Vista and 7 as an update), so I'd think backporting 1.13 from 8.1 to 7 wouldn't be impossible. Any help on this is greatly appreciated!
0 -
24 minutes ago, kar1 said:
I managed to finally create a .inf file for ACPIEx that makes it bind to a virtual ACPI device.
I took Microsoft's loopback network adapter .inf file (msloop.inf) as example to write a new one.After boot the event log no longer shows that the driver couldn't load due to unavailable hardware.
However it just silently fails to load, even if I bind it to a valid ACPI HWID (ACPI_HAL\PNP0C08).ACPI_HAL\PNP0C08 is the ACPI HWID that the normal 'Microsoft ACPI-Compliant System Device' is bound to.
And acpiapic is the one that the computer itself uses, but acpiapic doesn't use need driver to work.I thought that adding a new legacy device with the Device Manager and giving it a new .inf that uses the same ACPI HWID could work.
However the driver still not loading seems to hint at a bigger issue, which is that we will need to backport KMDF 1.13 to Windows 7.This has been done in the past with KMDF when Windows 7's KMDF 1.11 was backported to Windows XP.
We have to essentially backport KMDF 1.13 to Windows 7, by finding out where all its files are on a Windows 8.1 OS.For registering the new KMDF 1.13 with Windows 7, we can make a clean Windows 7 SP1 install, then make a snapshot of before & after the official KMDF 1.11 update is installed.
This will reveal in which places of the registry we need to register a new unofficial version, and which kind of data we need to write.For the current ACPIEx driver it's uploaded here, but it still doesn't work:
https://www.udrop.com/KqcD/ACPIEx___SpbCx-Win7-testing.zip (md5: a9367f0922e9f95a5ae1b14aca75ec58)
Interesting. Idk where the KMDF files would be stored at on a Windows 8.1 and 7 installation. Maybe someone here could help out.
0 -
Here is the Computer tab opened up. The "Dell Inc. Precision 7530" driver does not show up under 8.1 or 7 (and nothing is affected by its absence on the former and latter). I am not seeing a device called "System Board" under System Devices unfortunately.
0 -
3 hours ago, kar1 said:
@Jakob99 The ACPIEx.sys driver when I tried it myself didn't run at boot because it has no HWID to bind itself to.
I don't know which HWID it's supposed to be installed for on a real Windows 8.1 system (e.g. ACPI_HAL\PNP0C08).Can you boot your computer into a Windows 8.1 or newer WinPE and share screenshots of the Device Manager's ACPI x64-based PC device?
It will also help to share more screenshots about a System Device named 'System board' from the Device Manager.It's for the 'Parent' property and potentially some other device properties.
But in any case, I think the only remaining part to be modified for the ACPIEx driver is the ACPIEx.inf file.
If it gets correctly rewritten with a real Windows 8.1 HWID for ACPi, then the SpbCx driver will be able to run.And since Intel Serial IO drivers require the SpbCx driver as a dependency, this will make them work too.
I got a Code 37 (Windows cannot initialize the device driver for this hardware) upon installing your Serial IO drivers. I followed the steps in the provided ReadMe, too.
I found this Device ID in Windows 11's Device Manager (found by clicking on Serial IO A369, Details, and Parent): ACPI\PNP0A08\0, but idk if it's the correct one for ACPIex. If it's not, what would ACPIex be known as in the Device Manager?
0 -
13 hours ago, kar1 said:
I looked it up deeper and the driver fails to load likely because of the lack of a KB3125574 Windows update:
- https://www.catalog.update.microsoft.com/Search.aspx?q=KB3125574This update brings a WdfLdr.sys driver that the Intel HID Event Filter relies on.
However it should work without the KB3125574 update by taking it from a Windows 8.1 system.I took your Intel HID Event Filter drivers and modified them, the list is as follows:
- Removed all invalid INF comment prefixes // and replaced them with ; instead
- Added my compiled ntoskrn8.sys & WdfLdr.sys from Windows 8.1 to the INF files section
-
For HidEventFilter.sys & WdfLdr.sys I modified the EXE/SYS file headers to use MajorVersion 6 & MinorVersion 1
Because it was MajorVersion 10 & MinorVersion 0 (6.1 vs. 10.0 for Win10) - Modified the import filename in both HidEventFilter.sys & WdfLdr.sys from ntoskrnl.exe to ntoskrn8.sys
- Modified the __security_cookie in both SYS files & bypassed the security cookie check in driver code as well
- Removed the Security Directory information from EXE/SYS headers for both HidEventFilter.sys & WdfLdr.sys
- Updated all the EXE/SYS file checksums in the headers for all files
- Created a new unsigned HidEventFilter.cat file with '6.1' OS attribute (verifies all .sys files & the .inf file)
- Included dpinst64.exe from Microsoft (version 2009 for Windows 7 64-bit)
Prior to installing the modified drivers, you need to remove all the previous Intel HID Event Filter drivers with DriverStore Explorer:
- https://github.com/lostindark/DriverStoreExplorerThis allows for removing old drivers that otherwise get reinstalled again instead of the newest modified drivers.
The modified Intel HID Event Filter drivers (version 3):
- https://www.udrop.com/KopH/HidEventFilter-Win7-testing-3.zip (md5: 765c950f421cd7a9b7a353e8e980487c)For the 0x0000007E BSOD error code, it doesn't actually mean much other than 'Windows had a trouble while running this program/driver'.
It's a generic Windows error code rather than one that actually gets sent by the Intel HID Event Filter itself.Try the modified version after having removed all previous ones with DriverStore Explorer, I think it should work.
You can also enable testsigning & easily self-sign the drivers yourself with Driver Signature Enforcement Overrider:
- https://www.softpedia.com/get/Tweak/Video-Tweak/Driver-Signature-Enforcement-Overrider.shtmlJust sign the HidEventFilter.cat file only if needed.
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.
0 -
On 7/19/2023 at 1:19 PM, kar1 said:
There's a DSDT & SSDT editor (IDE) on Github for this purpose:
https://github.com/ic005k/Xiasl (block it in the firewall to prevent its Internet check)Another older DSDT Editor:
http://web.archive.org/web/20161108180259if_/http://olarila.com/dsdt/DSDTEditor_Linux_Windows.zipYou should then be able to edit your SSDT/DSDT and load patched versions using a boot-time loader:
https://github.com/jslegendre/ACPIPatcherOr you can also use Clover, OpenCore, or other loader of choice.
Some quick tips:
- CondRefOf function is also used to verify the return of _OSI
- "Windows 2009" is Windows 7 & "Windows 2013" is Windows 8.1
- Lookup "If (_OSI" or "If ((_OSI" to quickly locate the blocks that have a system check
- WIN7 is a constant that cans also be searched
- ACOS & ACSE variables seem to matter, they have to also be modified
- OSYS is the variable that gets checked the most in the OS installed locks
- Vista is named with the WLG constant
- There's a DRS3 variable but only set for Windows 10 RS3 & later
I made a patched version of your DSDT that makes Windows 2006 & 2009 (Vista & 7) behave as if it was Windows 8.1 (2013).
It also returns Windows 8.1's OSYS value for Vista & 7 which will be able to unlock more ACPI objects.
https://www.udrop.com/Kn0y/dsdt-patched.zip (md5: 4d22eb9bedc63efb618aaeef84ffb9db)Try using the normal version and if any problem then the 'no-optimization' one.
I also compiled GeorgeK1ng's version of NTOSKRNL_Emu incase you need to mod the Intel HID driver.
https://www.udrop.com/Kn0H/NTOSKRNL_Emu-GeorgeK1ng-version.zip (md5: a054a8ba9d05e587f3ac0f409d9e25e5)dsdt-patched.zip 423.82 kB · 1 download NTOSKRNL_Emu-GeorgeK1ng-version.zip 83.56 kB · 1 download
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!
1 -
5 hours ago, mina7601 said:
Hello, on my testing with downloading this file Chrome and Firefox, I didn't get that error message when downloading it on Chrome nor Firefox.
Great! Idk why mine threw the message then.
1 -
On 6/24/2023 at 6:41 AM, ExtremeXT said:
Dump your ACPI tables with acpidump from iASL and send them in a zip. Changing _OSI values to allow unsupported OSes is easy enough. Then the modified table will have to be injected with something like OpenCore which can be used for Windows as well.
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.
0 -
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.
1 -
2 hours ago, SkyKuker said:
HP Pavilion 17 (e117-dx).
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.
0 -
21 hours ago, SkyKuker said:
Oops, nevermind.
Looks like you have an Insyde BIOS, just like me. This is why installation does be hanging. So, as I see, the remedy is patched BIOS?
What is your laptop? Acer Aspire E1-531, something else?
0 -
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.
0
Windows 2000 on Haswell?
in Windows 2000/2003/NT4
Posted
Yeah, you need to fix USB2 for it to work within setup as it is broken. It's either that or use a PCI-E PS/2 expansion card (if your computer supports such dongles) with PS/2 mouse/keyboard to get through setup and then fixing the USB drivers within Device Manager, as noted here: http://windowsenthusiasts1.epizy.com/USB2Issues.html