Well, I took MGATweak to 1.5x like ya'll said. It didn't like that at all. I could do 166 but 175 crashed hard.
Then I tried 2.0x, guess what, maxxed out at 190Mhz, 195 died, 200 died. Probably would do 192 or something.
Just wish I had some 5ns SGRAM, or 4.3 or 3ns.......heh heh.
3DMark 99 MAX Pro...2x
1024x768x32bit
160/200/160=4986
175/175/175=4687
185/185/185=4821
190/190/190=4971
Fillrate =186.6
Fillrate w/ multi=214.2
I believe the reason 160/200/160 is faster is due to serious memory bandwidth limitations. There are no SGRAM timing changes in the above results, and Vsync is off.
My system:
P3-558 L2 Cache Latency 4
192MB RAM, Cas 2, 124MHz
Matrox Millenium G400 32MB Vanilla DH\
Creative SBLive Value
Quantum Fireball Plus KA 13.6
Quantum Fireball ST 4.3
3Com Fast Etherlink XL
Toshiba 6X/32X DVD
Sony CDU928E CDR
Then I tried 2.0x, guess what, maxxed out at 190Mhz, 195 died, 200 died. Probably would do 192 or something.
Just wish I had some 5ns SGRAM, or 4.3 or 3ns.......heh heh.
3DMark 99 MAX Pro...2x
1024x768x32bit
160/200/160=4986
175/175/175=4687
185/185/185=4821
190/190/190=4971
Fillrate =186.6
Fillrate w/ multi=214.2
I believe the reason 160/200/160 is faster is due to serious memory bandwidth limitations. There are no SGRAM timing changes in the above results, and Vsync is off.
My system:
P3-558 L2 Cache Latency 4
192MB RAM, Cas 2, 124MHz
Matrox Millenium G400 32MB Vanilla DH\
Creative SBLive Value
Quantum Fireball Plus KA 13.6
Quantum Fireball ST 4.3
3Com Fast Etherlink XL
Toshiba 6X/32X DVD
Sony CDU928E CDR
Comment