Reply 20 of 27, by retro games 100
- Rank
- l33t
Mystery update: 😉
Well I just tried the FX5950 Ultra in a different mobo, an Abit KT7A. The RAM stick in this board is a different stick to the previous set up, and I removed the only other card from the other set up which was a basic soundcard. The CPU is different too. In fact the only thing which is being reused from the previous Gigabyte test mobo is the Corsair 450W PSU. ...And I get the same problem running Duke Nukem 3D - that is, strange graphical glitches seen on the screen. So, it's either the FX graphics card, the PSU, the nVidia drivers (77.72), or my messed up win98 HDD installation. Which one should I try changing first? 😀
Edit: I'm sorry that this thread has temporarily changed in to "what's wrong with my FX5950 gfx card?". I will remove this card soon, and retry the Radeon XT inside the "new" Abit testing mobo.
But quickly back to this FX card - I tried a few different nVidia drivers, and I still get a strange graphical glitch on Duke Nukem 3D, and also Shadow Warrior (another 3DRealms game), but this problem disappears if I chose to "restart in MS-DOS mode". So, I guess it's a driver glitch?
Edit 2: I DL'd the 61.76 nVidia drivers from the gigabyte website for the FX card, and when I run dxdiag.exe, it freezes on one of the D3D tests - the one with the bouncing white square in full screen mode.
Edit 3: I tried reinstalling DX9, and also the unofficial SP for win98. The full screen D3D test still freezes. Then I changed the PSU. Unfortunately, I've only got a spair 350W PSU, but it's a good one made by Nexus. But that D3D test still freezes. Then I changed the nVidia drivers again, to 71.84, but that D3D test still freezes. But then I fixed it - and the solution was really weird. The CD-ROM yellow ribbon cable was badly twisted. I threw it away, and replaced it with a boring grey one. And just by doing that, the D3D demo now works. Weird. But I'm still having problems with Duke Nukem 3D, but at least I solved the dxdiag problem.