Has anyone used a supported PCI-express video card under Windows 9X, without motherboard PCI-E port drivers installed? Would be nice to know especially with newer AM3+ motherboards (I've never heard anyone mention generic drivers for unsupported mobo's), or perhaps other boards that absolutely don't have chipset drivers for Windows 9x.
I agree and I did have Asrock 775-DualVSTA mobo but that got stolen. Even had a nice Philips AMD interwave based GUS sound card (had the cleanest sound I've heard from an ISA sound card), K6-3+ @ 600mhz and a Voodoo 4 4500 PCI system. All that stuff was stolen.
Download Driver Motherboard Bulldozer H55
Download File 🔥 https://urllio.com/2yGaAR 🔥
My only option is to have everything in one PC since I don't have space (or money) for multiple machines ATM. And I think it'd be a good contribution to gain interest in porting generic chipset drivers for recent mobo's, to Win 9X.
Ummm...Win9x doesn't support ANYTHING that fits in PCI-e slot because it doesn't support the technology at all. You're wasting your time looking for Win9x drivers for PCI-e cards because there aren't going to be any.
98 definitely doesn't support multicore, even the P4 HT processers confuse it. Slightly smarter Windows 2000 sees cores as a physical CPU (causing all sorts of other issues) But you really need XP/2003 for the OS to understand multicore CPUS
Maybe there will be enough speed to brute force ok speeds in 9x but it'll be more problems then its worth I'd think. No harm in playing though ?
SOLVED:
PCI express port drivers are NOT required. PCX 5750 does indeed work. Tested directx9 acceleration via dxdiag and every test passed. Had to use the unofficial 82.69 drivers since nvidia's official drivers didn't detect the card (go figure). Despite not having chipset drivers available for my AM3 mobo, Nvidia control panel shows what speed my pci-e express port is running (4X pci-express; reserving 16x slot for current gpu's). No conflicts whatsoever... Only thing with yellow ? marks in device manager is unrecognized usb3.0 ports.
For the record, Win 9x is stable despite using 16GB of ram and a piledriver CPU. Sound Blaster Live! 5.1 gives me the best hardware sound support I've ever had (can load 1.6+gigabyte soundfonts in 64-bit Linux; needs 2GB DMA bus patch however). Beats the heck out of my onboard sound anyday (and Live!5.1 still does spdif output so maybe I won't be limited to 48khz 16-bit sound and it's SNR, but I don't care); but for some reason, SB16 emulation causes BSOD and realmode-dos sb16 driver stays silent despite loading succesfully (maybe my mobo doesn't have ddma and nmi?). Not bad for 16 year old hardware-software.
The 6 series cards were the first "native" PCI-E cards from NVIDIA. But there were PCI-e versions of the FX 5300, 5700, and 5900 series cards (using the BR02 AGP to PCI-E bridge). The "oldest" PCI-E NVIDIA Card is actually the PCX4300 which is basically an MX4000 (ie not a real GeForce4) bridged to PCI-E.
For the record, FastVid is working great and still haven't had any problems. Recommend to use UMBPCI.SYS, HIRAM.EXE, and HIMEMX.EXE (DEVICEHIGH) in config.sys; FastVid, VBEPLUS (high?) in autoexec.bat. Been playing Final Fantasy VII, Eternal Doom (DOS), Mortal kombat 1 & 2 CD (this version of MK1 seems pretty rare and it's the best arcade port IMO; way better than floppy version) on this Win98SE setup and it's wonderful! Yamaha XG 70 software midi @ 44khz (bundled with black FFVII discs) and awe32/64 soundfont midi in FFVII both sound superb on Live! value.
Only problem I have is Mortal Kombat Trilogy shows corrupt color pallete (even with vbemp loaded and custom bios version of univbe.drv). If anyone could help with Mortal Kombat Trilogy that'd be great! Before I make a thread somewhere ? ...
Even though the PCX5750 runs (and it seems to run stable), it is damn slow. Perhaps due to missing pci-e port drivers (chipset drivers) (my particular AM3+ mobo is GA-970A-UD3)... Has the same issue however, in Windows 7 64-bit and the card runs even worse there believe it or not (totally unstable and crashes a lot; using vista 64-bit drivers though since there are no 7 drivers. Yeah...). Speed reminds me of an older 8mb directx 6 GPU in 98SE at times (don't remember Vodoo 4 4500 PCI dropping to 10 FPS @ 1024x768 in Half Life; I can bump the resolution without speed loss however and it can run smooth more than less). The card smokes in Linux with 64-bit Legacy Nvidia binary drivers (get 100-300 FPS in gzdoom at 1280x960; occasional drops to 90FPS with many light sources and spikes of 400-500FPS) so I'm pretty sure it's lack of pci-e chipset drivers for 98SE. The card is stable in 98SE but it's definitely not running how it should (it's like it's running off a 33mhz PCI bus with memory paging issues despite using a 16XPCIE slot @ 4X speed).
Also, univbe doesn't like the PCX5750. I can startup Mortal Kombat Trilogy in pure dos but the game locks up during the intro Dragon Logo (before the intro text shows). Game also crashes in Windows 98 with windows version. DOS version still doesn't work when running in Windows 98 DOS shell (game will actually show the intro text and let you start a fight (and runs hella fast; silky smooth compared to Windows XP), but the pallette is completely corrupt and player sprites are missing). Tried custom univbe.drv bios driver, updated univbe to latest version, and tried vbetemp with same results in all cases (also tried nolfblim and nolfb).
Build engine games such as Blood like real-mode DOS. Resolutions beyond 640x480 show graphics corruption and looks similar to video memory running out in 98SE Dos shell (even realmode DOS has problems at times). Also, even if you run the game at 640x480 or lower, the cutscenes become corrupt in Windows 98SE DOS shell. You can work around it by hitting windows key or alt-tabbing to the desktop, and clicking back into the game; you have to change resolution in-game after cutscene ends (screen gets distorted) to make screen normal however. Really annoying. Tried VBETEMP and FASTVID but problems persisted in all cases. NOLFB did seem to make corruption non-existent in high resolutions (e.g. 1600X1200), but game slowed to about 30FPS (think cutscenes still had problems in 98SE DOS shell).
Only good thing I can say about the PCX5750, is it's actually a tad faster than the original FX 5800 (5800 ULTRA too?), despite having a gimped chip (it's clocked faster which is why I believe). It doesn't even use a blow dryer; has a tiny single slot 55MM chipset cooler with fan on it. It also doesn't use external power and overclocks a lot BTW. Yes the 5950 Ultra is faster but that thing needs a dual slot blow dryer and molex power connector. If you need an FX series card in a PCI-E slot for Windows 2000/XP, this might suit your needs (you might have goodluck with Windows 9X if your particular PCI-E chipset has drivers for it; in my case it didn't. If so, you might want to try forcware 66.xx drivers which officially support this in Win 9X).
Going to try an ATI Rage 128 VR 32MB PCI card and see how that handles all the legacy problems I've encountered with this thing. Could really use something with GOOD legacy support for DOS, and acceleration for older Direct3D titles in 98SE without problems (FFVII, Resident Evil 1, etc.; most newer Direct X 7 titles seem fine in Windows 7 BTW).
My OS install for my main Desktop is going on 6 years now. Since it's advent, it has undergone a slew of changes. Off the top of my head, I know it started on an HDD, moved to an SSD with the system reserved partition on an HDD beside it, then both partitions moved to another SSD. Tangentially, it started on a Phenom, moved to a Bulldozer, then a Vishera, and now a Ryzen. Along the way, it has flirted with at least 4 different motherboards, courted half a dozen GPUs, and snorted a metric shitload of drivers and applications, leading to countless near-death experiences.
I spent some time this week refreshing the build. I moved to a Ryzen 7 1800x Processor, an MSI x370 Platinum Motherboard, 32GB of Corsair Dominator Platinum DDR4 RAM, mucho RGB, and a new hard-line liquid-cooling loop to boot.
The first hurdle was that Windows 7 has no native support for XHCI and, since my previous motherboard didn't have XHCI, I'd never installed the drivers. Foresight would have led to me doing this preemptively, but I'm an idiot. Not having these drivers meant that USB was broken and, you guessed it, so were my peripherals.
I walked around the corner, picked up an old PS/2 keyboard. With this, I managed to pull old chipset drivers, install the XHCI drivers, and throw on some other drivers which were provided with the hardware.
While installing drivers, I ran into install issues. Those lead me to realize that the boot loader had been put into Selective Startup mode, which allows the OS to boot without many critical services. Naturally, I flipped this off, rebooted, and quickly realized my mistake.
Something was out of whack between the chipset and the OS, and that somehow caused the BCD to get corrupted. I still don't know what corrupted it! This conjured the selective startup issue. Fixing it conjured a new issue, where Windows was complaining about not being able to find required devices for boot.
Naturally, I continued to startup repair. Except, as it turns out, my Windows 7 USB didn't have a repair option (more on that later), so I had to make a new one. That ended up bricking my Windows 10 machine due to a bad disk mounting driver, but that's off-topic.
After fixing my Windows 10 machine and getting a new USB made, I booted into startup repair, applied fixes and... got an error. Now, when trying to boot the OS, I got a blue screen. Not a Blue Screen of Death. A blank, light-colored, empty blue screen. What in the world?
It's at this point I had a realization: Windows 7 Repair suffered from the same XHCI USB issue. When trying to repair either the MBR, BCD, or both, the repair application attempted to access a template on the USB, failed, and errored out (this is possible because USB worked in the BIOS, but broke upon loading of CLASSPNP.SYS). 152ee80cbc