Tweet
Well, I got tired of waiting on Matrox and went out and bought a Prophet II 32 MB.
I made a clean install of w2k with ACPI disabled, then installed Via's 4in1422, rebooted and installed AGP 4.03. After rebooting again and verifying all was well in the system listing of DM, I installed the drivers (3.8.4, from the CD) for the GTS2, (and later, the 5.2.2 drivers).
I rebooted, and guess what?? 3dmark2000 runs to completion, as does the Q3A demo bm and Final Reality. In Q3A at default settings I get 125 +/- fps, and about 4400 in 3dmar2000.
For comparison, in W98 (not SE), I get about 6000 in 3Dmark2000 and 115 fps in Q3A. This is all without any overclocking of either the cpu or GTS2 with a k7-800 on a KA7.
Some interesting observations:
In the tunnel test for textures in 3dmark2000, the walls have a true 3D texture which I never saw with the G400Max (when I got it to run that far).
Also, when I set the memory bus to 133 with two 128MB Corsair hd modules, I saw random white squares on the terrain in the helicopter tests if the I/O voltage was above 3.3 volts (that wasn't there with either module used alone), and it had a tendency to crash.
In the radial color test of FR, random pixels were left behind as the colors changed (under the same conditions). I found that by changing the AGP drive level adjustment in the KA7_42 BIOS, I could get rid of these anomolies.
Now, just to vindicate Matrox to some degree, 3Dmark2000 will not run to completion with either Athlon opts or 3Dnow! opts selected. With the GTS2 however, there is a new D3D hardware opt selection available, and it runs great with that setting. At this point it does appear the problems with 3Dmark2000 and the KX-133 lies with either Via or writers of the bm itself (of course, Matrox's drivers may still not work when, and if, the basic incompatibilities are fixed).
JohnT
I made a clean install of w2k with ACPI disabled, then installed Via's 4in1422, rebooted and installed AGP 4.03. After rebooting again and verifying all was well in the system listing of DM, I installed the drivers (3.8.4, from the CD) for the GTS2, (and later, the 5.2.2 drivers).
I rebooted, and guess what?? 3dmark2000 runs to completion, as does the Q3A demo bm and Final Reality. In Q3A at default settings I get 125 +/- fps, and about 4400 in 3dmar2000.
For comparison, in W98 (not SE), I get about 6000 in 3Dmark2000 and 115 fps in Q3A. This is all without any overclocking of either the cpu or GTS2 with a k7-800 on a KA7.
Some interesting observations:
In the tunnel test for textures in 3dmark2000, the walls have a true 3D texture which I never saw with the G400Max (when I got it to run that far).
Also, when I set the memory bus to 133 with two 128MB Corsair hd modules, I saw random white squares on the terrain in the helicopter tests if the I/O voltage was above 3.3 volts (that wasn't there with either module used alone), and it had a tendency to crash.
In the radial color test of FR, random pixels were left behind as the colors changed (under the same conditions). I found that by changing the AGP drive level adjustment in the KA7_42 BIOS, I could get rid of these anomolies.
Now, just to vindicate Matrox to some degree, 3Dmark2000 will not run to completion with either Athlon opts or 3Dnow! opts selected. With the GTS2 however, there is a new D3D hardware opt selection available, and it runs great with that setting. At this point it does appear the problems with 3Dmark2000 and the KX-133 lies with either Via or writers of the bm itself (of course, Matrox's drivers may still not work when, and if, the basic incompatibilities are fixed).
JohnT
Comment