VOGONS


First post, by Cursed Derp

User metadata
Rank Oldbie
Rank
Oldbie

Heyyyyyyyyyyyyo,
I recently got a Dell Dimension 4100 as an upgrade from my previous Dell Dimension L1000R and it came with a TNT2 M64 AGP. As I soon discovered it was a pretty shifty card. So I decided to switch it out for my S3 Savage 4 PCI to see if performance improved. Well I set the drivers to Standard Pci graphics adapter, and removed the Nvidia inf files from windows/inf as well as from windows/inf/other. I removed the Nvidia card and inserted the savage 4. I set the primary video to pci in the BIOS and booted up the pc. I used LGR's savage 4 drivers from archive.org and while the card seemed to be installed when I looked at the display adapter settings in safe mode later on, normal mode Windows crashed after the windows 98 splash screen. I know the drivers for this card are historically janky but if anyone has any ideas, drivers, advice, or insight, that would be awesome.
Any help would be greatly appreciated.
Thanks

I am as smooth as a gravy train with flaming biscuit wheels.

Reply 1 of 3, by stamasd

User metadata
Rank l33t
Rank
l33t

It may be the card has a hardware fault. I have recently used a Savage4 on a Win98 machine with the exact same drivers, and that was after using a nvidia card (GF2GTS) on the system, and with the nvidia drivers still installed on it - and had no problems. Well except for the terrible performance of the savage4 of course. This was on a 440BX system with a coppermine CPU.

I/O, I/O,
It's off to disk I go,
With a bit and a byte
And a read and a write,
I/O, I/O

Reply 2 of 3, by Cursed Derp

User metadata
Rank Oldbie
Rank
Oldbie

So I should just switch it out?

Or get a better card cuz I only got shitty ones

I am as smooth as a gravy train with flaming biscuit wheels.

Reply 3 of 3, by ratfink

User metadata
Rank Oldbie
Rank
Oldbie

I tested my savage4 agp recently, it crashed windows on startup in one board (a slot A) but worked fine in a socket 7 - in both cases using windows 98. I could find no drivers that fixed it on the slot A - even phil's much-vaunted ones. I had had similar issues with other graphics cards in the slot A system (although in one case - not any more - I don't know why) - all I can think is some weird driver crud buildup that possibly I unknowingly cleared up at one point. That doesn'thelp you except to say try another card, or try the savage4 in another motherboard.