|Trial by GeForce4
||[Friday 13th May 2005 at 6:32 pm]
The saga of my lone stand against the den of malice that is the computer|
Warning: contains heavy technical content. All ye who click have been warned.
System: Epox 8KTA2 motherboard (VIA KT133 686B), GeForce 4 Ti4600, Promise Ultra133 TX2, Windows 2000.
Well, the old graphics problem is back (I was hoping that the windows reinstall would get rid of it). Googling turns up this as being a rare but not unheard-of problem with my particular chipset, and throws up a bunch of tricks to try to fix this.
One is to remove the ACPI support, and make Windows 2000 think that the computer is a non-ACPI one. I'm just trying this, and it seems to have resulted in a complete hardware redetect of everything up to and including the floppy drive (probably because all the IRQs have shifted - ACPI works by using one IRQ, usually 11, as a gateway to a whole bunch of logical ones). I never did like the idea of IRQ sharing - it always seemed to be asking for trouble.
Anyway, it's just finished installing a mountain of drivers for everything except the network card, owing to the floppy drive vanishing along with the rest of the hardware. Now to get dualview going again, and then test it to see if it works now.
...and it works on the primary display, which seems to have lost its Direct3D acceleration, but when I try the secondary display the thing locks on me. Hmm.
Next thing I'm trying is suffling cards around. Seeing if it's caused by cards sharing IRQs and not behaving. I'll shift the IDE card, as that's sharing with the onboard sound (according to the BIOS). Of course, this means Windows will do another minor hardware redetect, but that's what you get for using an IDE controller.
Hmm, that's cured a sound stuttering problem. But has it fixed my graphics card? *fires up dxdiag*
Now, I *could* reinstall older nVidia drivers, but that'd be too easy. And besides, I'm learning by doing this. And I've managed to fix another problem along the way.
So, what's there left that I could do? Monkey around with AGP driving settings, drop the AGP acceleration leve, monkey around with system voltages... actually, I think I won't do the last one. I don't need a new keyring pendant. I'll try the AGP acceleration, as come to think of it it worked fine when there was no Direct3D acceleration. I can drop the AGP arpeture size as well - apparently too-large settings can cause problems.
*reboots* Start > Run > dxdiag.exe
It is nice having a freshly-installed Windows setup - everything runs so fast. Still, it's only a matter of time before it will be overcome with all the software I use on a day-to-day basis (and more besides).
Back to the story - that didn't work either. Some more digging seems to point fingers in the direction of VIA's AGP driver (as well as everywhere else). So I've uninstalled that, and once the graphics drivers are reinstalled I'll give that a try.
Nope, didn't work. Oddly enough it works perfectly fine without Dualview installed, or with Dualview but without Direct3D acceleration. Ah well. I give up for now. The older drivers worked, so I'll cope with them.