!!! LET'S START AN OFFENSIVE AGAINST THE VIA-MATROX - CONFLICT !!!

[Surfwienix]

i remember that my soundcard (terratec dmx) makes a double entry in the device-manager every time i installed it. that could be. my soundcard has another strange behaviour: bios says (pci device-listing): soundcard irq 5 - windows says: soundcard irq 9. ???

we'll see tomorrow when i have a new vga.drv. i go to bed now. my pc kills me one day because i get no sleep with all these problems here....

[Alfie]

Sounds like a windows problem!
Let's start an offensive against windows
Why don't you have the win98 cab files on your hard drive?
Perhaps a fresh install is in order here!
Kruzin are you editing out there???

[EchoWars]

Krusin- I am like Surfwienix, thought this was a well-known problem. I have been building and selling PIII's, G400's, and Tyan Trinity 400 (133A chipset, but you knew that...) to the tune of about 20 machines now. Anything newer than 5.41 crashes immediately in Q3 (although performance is decent enough at 1024x768). Have never been able to use TurboGL. Have been reading about a lot of others on this forum with same problems for months. I don't think it is related to anything but Matrox's drivers and VIA's drivers (or hardware implementation).

Gurm-
Was not really comparing the G200 to the TNT2U performance-wise. It's not a big mystery that the G200 is pretty unacceptable for Q3 play. Especially after you play it with a G400 Max and a PIII 800. It's time had come...(stifles a tear). Kinda was more a 1x/2x comparison (hardware), and a 'does the newest available driver work correctly?' thing. Just a measure. To me, it's kinda nice to see a system work really well with new drivers without crashing or looking for FAQ's or checking a forum to see if everybody else is having the same problem...etc. That, in itself, is difficult to put a value on. (not like I don't mind hanging out here, tho...)

[The PIT]

Have you done what Kruzin has asked you to do yet. Also how about clocking back that processor. Get everything stable at 400 then bring the speed up until things go wrong again. Then knock it back at notch.

[This message has been edited by The PIT (edited 26 May 2000).]

[cadwal]

My version of the tests (I didn't bother to try older versions):

P3V4X + G400MAX + P3600EB (no overclocking)
BIOS 1003: AGP 4x, 256MB apert

W98: 4in120 + AGP4.02 + INF1.02 PD5.52, TGL1.3 -> AGP 4x, apert>64MB

W2K: INF1.02 PD5.03 -> AGP 2x, apert<=64MB

W98 ICD: GLQuake ok, Q2 ok, Q3 white screen
W98 TGL: GLQ black screen, Q2 black screen, Q3 white screen
W2K: GLQ ok without sound, Q2 ok (visual artifacts ?), Q3 white screen

So TGL with this PD is a complete failure for me. Notable is that the black screen looked like complete lockups but the white ones were not. In W2K I could kill Q3 and in W98 it had locked the keyboard but hitting the on/off button gave an orderly shutdown of W98.

AGP support in W2K seems not so good either.

(Odd things noticed: Fighting Steel (D3D) but nothing else (yet anyway) gives me huge temp spikes (>75C) in PCProbe, MBM etc)

[Surfwienix]

0 Systemzeitgeber
1 Standard (101/102 Tasten) oder Microsoft Natural Keyboard
2 Programmierbarer Interrupt-Controller
3 Realtek RTL8019 Plug & Play LAN-Adapter oder kompatibles Gerät
4 (frei)
5 DMX Device Manager
5 IRQ-Holder für PCI-Steuerung
6 Standard-Diskettenlaufwerk-Controller
7 (frei)
8 CMOS-/Echtzeitsystemuhr
9 Creatix V.90 HaM
9 IRQ-Holder für PCI-Steuerung
10 IRQ-Holder für PCI-Steuerung
10 VIA Tech 3038 PCI/USB Universal Host Controller
11 IRQ-Holder für PCI-Steuerung
11 Matrox Millennium G400 DualHead - Deutsch
12 PS2 (PS/2)
13 Numerischer Coprozessor
14 Erster IDE Controller (Dual FIFO)
14 VIA Bus Master PCI IDE Controller
15 Zweiter IDE Controller (Dual FIFO)
15 VIA Bus Master PCI IDE Controller

solved this double irq thing. d'you think the irq's are ok now ?

[The PIT]

Yep thats better whats happening now then?
Also have you clocked that processor back?

[Surfwienix]

i can't clock my cpu back. it doesn't run @400 since i've overclocked it (around 1 month). i must run @450, but i will try to set a lower voltage. i heard that this would go when it runs for a while. now it is set to 2.9V (!!!), and is getting very hot. but i have no crashes or other unnormal errors, runs very fine @450, only a bit hotter than normal (50-58°C) and the via-problems were there before, too.

[The PIT]

let me get this striaght. If clock the processor back to it's default settings it won't run at all?

[Gurm]

Wow... um... you CAN'T clock it back?

In that case you blew something up... or have something set VERY wrong on the motherboard.

Time to tear it down and put it back together from scratch...

- Gurm

------------------
Listen up, you primitive screwheads! See this? This is my BOOMSTICK! Etc. etc.

[Alfie]

With the epox board there's only two jumpers to set.One is for bus speed,set it to 100mhz.
The other is for the multiplier.Set it to 4x.
After setting these jumpers you must reconfigure the bios to match the jumper settings.
Once you have done these things the cpu should reset to 400mhz.
Once this is done,get back with your problems and we can go on from there.
The voltage setting and temperature is too high.The temperature alone can be causing problems!Not to mention the voltage.(make sure you set the voltage correctly via the dip switches on the mobo.
So before faulting Matrox and/or Via,clean your own house and then when things don't work,start complaining!

[Surfwienix]

I SAID THAT THESE VIA-MATROX PROBLEMS HAVE APPEARED BEFORE I OVERCLOCKED MY CPU !!!

SO, THE VIA-MATROX PROBLEMS HAVE ABSOLUTELY NOTHING TO TO WITH MY O/C CPU !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[This message has been edited by Surfwienix (edited 28 May 2000).]

[The PIT]

Stop bloody shouting. The fact that you say that the Cpu can't be clocked back indicates either a problem with the motherboard or your Cpu is buggered. I suggest you start looking at that rather than blaming Matrox. Yep the problems were there before you overclocked which indicates a slightly unstable system so why overclock before you got it stable?

[HollyBerri]

Errr.... let me see if I have this all correct...

"The VIA-Matrox problems started before I overclocked my CPU(!!!!)"

Ummmm... and when was that exactly, that you overclocked your CPU?

Seems to me that there's one of 2 answers:[list=1][*] You overclocked your CPU less than oh, 6 days ago, when the most recent VIA .inf file was released (to say nothing of the most recent BIOS release or any other applicable files-- such as Windows Updates, DirectX releases, etc.).

In that case, you do have some cause to complain, since you had the most recent versions of everything and it didn't work correctly, although why you would then OC under those conditions eludes me... and further, if you had OC'd so recently and already blown your CPU's ability to clock back, you've got bigger problems in your system than a "driver conflict".
[*] You OC'd some time ago and your problems occurred before later revisions of various software, which you may or may not have installed.

And so this is Matrox's fault how? Both they and VIA have updated drivers several times, Windows has released small fixes, and I'm sure Epox has updated their BIOS. You may have heard that subsequent releases and patches are designed to solve such conflicts and the like. After all, I have a MAX and I use PD 5.52, whereas you state that you're using 5.30 (presumably because of the SS7?) If you had old drivers (that were not working right at the time), OC'd your machine and screwed something up further (evidenced by the fact that you can't clock back), then updated your drivers, I don't see how you would expect it to work <u>now</u>. And I certainly don't see how Matrox and/or VIA are to blame.[/list=a]

Is it just me? Maybe I should be quiet and offer you some cheese to go with your whine...

---------------------
Holly



[This message has been edited by HollyBerri (edited 29 May 2000).]

[Alfie]

The Super7 platform has come to an end.
Those of us still using it must realize this,Via has geared its newer drivers for it's 133 chipset,Matrox keeps trying,but it's concern must lie with the newer designs.(I think).
I'm still annoyed that my g400 won't work on this 486 I've got kicking around.
The SS7 was a stop gap for Via and AMD.
The only way they could compete with Intel.
It was a marvelous time,but the party may be over regarding 3d applications and SS7.
Until we upgrade our systems,all we SS7 users can do is seek workarounds and hope the next drivers work better!
No sense kicking a dying horse!