Intel Gma 965 Modded Drivers
Marcelo Eichel
Meanwhile, although Intel is distributing unlocked drivers, they are being cautious about it, at least initially. At the very top of the driver description, before anything else, is the following warning text.
A friend and I are trying to play modded minecraft together, however whenever he installs mods onto his minecraft it causes some massive visual bugs, his entire screen goes a ton of different colors as he looks around, entire chunks become a solid color, and mobs turn pitch black. It only happens when a mod is installed but it doesn't matter what the mod is.
I know asking for display drivers for win98 is probably the most yawn-inspiring question asked, and I wouldn't ask if I didn't think it weren't remotely possible, given some of the genius work I've seen here!
Sometime last year I built a 386 and had a play with mini98 on it, and in the course of searching for a matching case cover, I ended up with an Intel G31 mainboard with an E8600, after a bit of fun and failure, I built a P4/NVS280/AWE32 for win98/dos use, though the E8600/NVS280/(no sound) was considerably faster. However, given the E8600 is a good match for max-speed win98, and the HDA audio is working (thanks guys, legendary!), the next thing I was looking at was the onboard intel G31 graphics. Boring, yes, but given w9x modded-driver supported video cards are not quite so cheap/available anymore, they should provide enough grunt for w9x gaming backed by an e8600. The other was that I saw, on retro systems revival, a w98 driver was posted that supports i945, which was what gave me (probably false) hope as i noticed that driver used ialmnt5.sys rather than ialm.vxd used in the latest official w98 supported intel graphics drivers. Unfortunately I don't have a i945 graphics chipset to test that driver with.
Anyway, I exhausted most avenues of inf-modding the G31 registry entries into the 945 (and last official w9x supported intel) driver inf, and about as much file swapping as I could think of, even ran kernelex in case the newer NT binaries checked the G31 registry entries. The furthest I got in w9x or ME was 'display not configured correctly' on startup, with bootlog showing that miniVDD couldn't start. I was kinda hoping that the driver architecture was the same, and it was just a matter of configuration stored in the registry, with the driver implementing that config.
There aren't any "modded" graphic card drivers for 9x. They just involve editing INF files and putting files from different available versions of the released drivers for the best combination (which is how GeForce 7000 series work on 9x). The only real mod is the Radeon 9500 softmod that was very popular back in the day, but this was also done for XP and Radeon 9000 series was always officially compatible with 9x anyways.
I've been trying to install the Intel USB 3.0 eXtensible Host Controller Driver (version 3.0.0.16 as supplied by the Asus web site) but it balks when it gets to the PCI bus. At this point the entire system freezes for about 30 seconds and then a generic message is returned saying the install failed and some devices were not installed. If I try to install the PCI bus driver manually via the Device Manager (updating from the stock Microsoft driver and pointing it to the directory where the Intel USB3 drivers reside) It fails saying "The parameter is incorrect". Something has occurred in this process though, because the Device Manager is now listing the driver as Intel, version 3.0.0.16. Rebooting at this stage causes a BSOD while loading windows, requiring a repair boot and System Restore to recover.
I also tried simply adding two lines into the inf file (since it already contains all the necessary instructions, they just disabled them), but the it becomes unsigned, so now I need to find a way to install unsigned drivers.
First you should use the free devmanview tool from NirSoft to check that you have the correct PnP vendor string. I know that you already have the string, but just to make sure that there is no mistake. Then you need to ensure that you have NDIS68 drivers, previous versions will not work. Then you need to patch the corresponding inf to move the lines with your vendor string from the Windows 10 section to the Windows Server section, it seems that this part is also ok in your case.
You can check with devmanview if the driver shows up with your NICs. Then you can set testsigning to off again and re-enable secure boot (if applicable). I also installed the PROSet Adapter Configuration Utility from Intel to check the adapter settings and verify the hardware and cabling. If you have multiple NICs beware that the numbering on the device is not the same as in the drivers. The number 1 adapter was the physical port 2 in my case. If you plug your cable to another port Windows will complain that there is no active network adapter.
In the Device Manager, update the drivers for the Ethernet Connection and 'Browse my computer for driver software'. Choose 'Let me pick from a list of available drivers', then selecting the PRO1000/Winx64/NDIS68 folder and selecting any of the .inf files in there. One of the following devices should show up, use one of these:
Already drivers for Intel HD4000 I take from Lenovo page to this model G500 and it's for win8.1 it works, and for AMD 8570m from G510 which is from 2015. And it works, but with that I'm losing any power efficient on battery, because as I saw dedicated graphics works all the time not just switching when needed. There it works or not. Mostly get ERROR CODE 43 with any new driver.
Windows XP:
- Intel 7 series (Ivy Bridge) is the last chipset with official support, though it's limited and I know only a few motherboards that have XP drivers and none of them are mini-ITX. Intel 6 series (Sandy Bridge) has wide XP support and probably has mini-ITX boards with XP drivers. No idea about AMD boards
- NVIDIA GTX 960 is the last NVIDIA card with official XP drivers, though from what I've read it's easy to modify the drivers to make 970/980/980 Ti work too. Again no idea about AMD cards
Windows 7:
- Wikipedia says Intel Broadwell is the last chipset officially supported by Microsoft, but you can find up to Intel 200 series (Kaby Lake) motherboards with Windows 7 drivers
- Looks like even NVIDIA RTX 30 series has Windows 7 drivers, I think they've been more like security releases so don't know do RTX cards work just as well as the earlier GTX cards.
If you aren't set on building two mini-ITX PCs, you could build one midi tower for both XP and 7 with Ivy Bridge board that has XP drivers and that GTX 980 of yours. Would have space for a nice PCI/PCIe sound card too.
The last AMD Radeon supporting WinXP was the Radeon HD 8xxx series (codenamed "Sea Islands"). Its successor, the R5/7/9 2xx series (codenamed "Volcanic Islands") dropped official WinXP support, although I'm not sure about tweaked/modded drivers.
I wonder if graphics cards from late Windows 7 era suffer from similar compatibility problems in Windows XP as GeForce cards newer than FX5xxx do in Windows 98 due to having to use drivers that are too new.
I have no idea about Windows XP and current/modern hardware, but I am still using Windows 7 64 as my daily driver on an X570 chipset based ITX motherboard. Also using a Ryzen 5000 series CPU, 32GB DDR4 RAM and a PCIe Gen 4.0 NVMe. It's absolutely incredible performance, BUT I did have to jump through a few hoops to get it all running smoothly. The X570 chipset may be the very last chipset to support Windows 7 64 and even that statement is not completely accurate. To get the X570 chipset to work with Windows 7 64 you have to use AMD's X470 chipset driver package. Works well. I don't see the X670 chipset being as agreeable to this scenario, but I could be completely wrong and only time will tell. Hopefully, someone will test that out eventually. You also have to use modified USB driver packages to get USB 3.x ports to work properly in Windows 7 64. This becomes a problem during the installation of Windows 7 and it is preferable that you have a motherboard with a PS/2 port (many modern boards still have one) so you can use the mouse and keyboard until the proper USB 3.x drivers are installed. Otherwise, you have to go to the trouble of slipstreaming your Windows 7 install package with the updated/modded USB drivers and the Windows 7 64 NVMe driver which Microsoft so kindly removed from their site. Luckily, you can find it elsewhere. As far as video cards, as others have said here, NVidia GeForce 30 series cards are the top. So a 3090 Ti and below will work just fine. NVidia still updates their Windows 7 64 drivers, but almost strictly for security patches at this point. I think the latest was back in August of this year.
Edit: I should also point out if you do get an X470 or X570 chipset motherboard you will most certainly need to replace the M.2 WiFi card if it has one. I use the 'Intel Dual Band Wireless-AC 8265' as a replacement which has plenty of bandwidth for me at 866Mbps max. Some of the X470 boards have a LAN port that is compatible with Windows 7 64 and some don't. None of the X570 boards I've come across have LAN drivers for Windows 7 64. So check what network chipsets they have. You may be stuck using a third party network card or using a USB LAN dongle that has WIndows 7 64 drivers. All of the integrated audio chips on both the X470 and X570 boards I've used have Windows 7 drivers available.
I found the intel Graphics drivers with 3rd gen Ivy Bridge support, to be somewhat troublesome in game compatibility. Whilst 2nd gen Sandy Bridge ones are completely fine. So I reverted back to v6.14.10.5384 of 10-9-2011 when possible.
Edit: New test result: I could not find such issues with the new intel graphics driver on a H67 desktop board with ivy bridge CPU. So the issues with newer drivers were somehow particular to the earlier test system: HM65-chipset laptop with Sandy Bridge (mobile) CPU.