Jakob99
Content Type
Profiles
Forums
Events
Posts posted by Jakob99
-
-
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!
0 -
5 hours ago, superleiw said:
Found some Windows 7 drivers : Have you already tried any of these eMMC drivers by any chance ?
https://board.eclipse.cx/download/file.php?id=272
The W7 Braswell drivers from 2015 might be compatible with your laptop.
Tried it and it didn't work
0 -
10 hours ago, superleiw said:
Not sure if this is useful as it would need to be backported but Microsoft had released a eMMC Hotfix for W8.1
The hotfix can be downloaded from here :
https://thehotfixshare.net/board/index.php?/files/file/20824-windows81-kb3078919-x64msu/ (64bit)
https://thehotfixshare.net/board/index.php?/files/file/20825-windows81-kb3078919-x86msu/ (32bit)
Contains dumpsd.sys and sdbus.sys and sdbus.inf fileversion 6.3.9600.17931 from July 2015
That's weird... I thought 8.0 (6.2) supported eMMC's out of box?
0 -
12 hours ago, johnelmer227 said:
Yes i did but however VMD doesn't exist in BIOS it only has Intel VTX and VTD idk what are those about
Virtualization features. You need these enabled to use VirtualBox or VMWare.
0 -
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.
0 -
21 hours ago, K4sum1 said:
I was able to fix this by disabling the Nvidia GPU, running only on the integrated Intel iGPU. After Windows was installed, it seemed to work with the dGPU enabled, although no drivers made it mostly useless.
However I have a friend with a Broadwell laptop, E5450, and they get this with the ACPI. No dGPU to disable, going to have them look through the BIOS to see if they can find anything.
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.
0 -
5 hours ago, NotHereToPlayGames said:
This is strictly forbidden here at MSFN. See Rule #13.
I'll delete that part, then. Forgot about that rule.
0 -
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.
0 -
On 7/24/2023 at 3:26 AM, UsefulAGKHelper said:
Since July 10 (made public since July 11) I have managed to run Windows XP x64 SP2 (built using XP2ESD) from UEFI Class 3 on Coffee Lake Windows 11 laptop on winload.efi 16497 using FlashBoot 3.3n bootmgfw.efi and Windows 7 generic VGA drivers by modifying the contents of mounted devices and enum key.
I have used the XP2ESD build which contains the backported generic drivers and ACPI 2.0 drivers (from here) to get this to work.
So far I tested acpibit64crack.sys from Dietmar.
The fact that I managed to boot XP on such new hardware means that the ACPI 2.0 worked! Touchpad doesn't work because there aren't any working XP drivers for Intel Serial IO I2C Host Controller (9DE8 and 9DE9 in my case) to get the Elan1200 I2C Hid device to install using the backported generic touchpad driver from windows 8.
USB XHCI controller and USB 3.0 root hub work without problems so I can use external mouse (for the cursor) and USB wireless adapter (for internet).
I don't know if it's caused by ACPI incompatibility but I have tried to backport the Intel Serial IO I2C Host Controller from Windows 7 and it still wouldn't work even with Mov's ntoskrnl emu extender files!
I have provided the device manager entries of my XP installation (from the enum key) so you can see the information on the drivers installed in my working XP OS.Useful's-XP-device-manager-entries.txt
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.
0 -
On 6/20/2023 at 12:01 AM, trancer03 said:
Need Vista driver for Intel Centrino Wireles-N 100 (PCI\VEN_8086&DEV_08AE&SUBSYS_10058086&REV_00)!
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).
0 -
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
0 -
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
[WIP] Windows Vista Extended Kernel
in Windows Vista
Posted
@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!