G400, UT, and Win2k Problems...

[SoRnMaN]

Anyone have any suggestions? I bought and loaded up UT earlier today, and played thru real quick just fine, running it in dx... Then tonight I was looking to get into it a bit more, and every time I play, it will lock up on me after a 4-5 minutes. Just lock up, the sounds still plays on, but I have to hard reboot out of the game.. Just wondering if anyone is having the same problems and if anyone had any suggestions... Note: I picked up quake3arena today at the store.. it plays fine... so i will be trying ut in opengl mode to test it...

[This message has been edited by SoRnMaN (edited 04 December 1999).]

[dwinter3]

I am running the 4.9 g400 drivers on w2k 2183, and I can only get UT to run in a window. Did you have that problem?

[jorsmith]

I'm also getting lockups a few minutes into the games. The Direct3D titles I have tested are Falcon4 and Fly! The sound keeps on playing and my HD keeps on working for a little bit till all tasks are completed --- and my system is locked down so firmly that the reset button is the only way out.

Sort of relieved to hear I'm not the only one with this problem (ie.; an issue for the driver developers...)

Build 2083, P2 450 dual, Asus P2BDS, 256 mb ram, Cheetah 9.2 u2w, g400max.

Regards,
Jørgen

[SoRnMaN]

well, it looks like it may be win2k that is creating the problems, rc2 is supposed to not include dx7 support from what other people have told me. so that may be the problem, but i don't see how it locks up 5 or so minutes into the game if there is no dx7 support. ohh well, still in search of answers. q3a is nice, but i think unreal tournament is better.

[TDS]

I'm running W2K 2183 (RC3), with Matrox 5.0 Drivers. According to W2K's DXDIAG program, DX7 is installed, and still ALL Direct3D programs lock up on the G400. Have also tried with my old Permedia 2, and, although slow, it runs stable. This gives me the idea that matrox has done it again, and given us a non-functional set of drivers. WAY TO GO, MATROX (My next card will NOT use mga drivers.....)


------------------
System Information
------------------
Time of this report: 12/7/1999, 17:43:31
Machine name: SIRIUS
Operating System: Microsoft Windows 2000 Professional (5.0, Build 2183)
Language: English (Regional Setting: Norwegian)
Processor: Intel Celeron, MMX (2 CPUs), 433MHz
Memory: 256MB RAM
Page File: 61MB used, 556MB available
DirectX Version: DirectX 7.0 (4.07.00.0700)
DX Setup Parameters: Not found
DxDiag Version: 5.00.2136.0001

[Flip-Oh]

What are you whining about?!?!
These are BETA drivers!! They don't have full functionality YET and Matrox isn't saying they have full functionality either. So stop your stupid whining and use win98!

------------------
______________________
I am the Jorg, resistance is futile.
© StarTrek: First Contact

[TDS]

Yeah. '98.......

Trust me, I'd rather be running NT, and my old trustworthy V2/SLI's.... Didn't you notice the SMP part in my config?

-TDS

[djohnson]

Installed RC3 last night and the beta drivers. UT and all D3D games run fine. I did have to turn off bus mastering though. Have not had any problems installing software or running games. In fact, some glitches that I had in UT graphics are gone now.

[TDS]

Hmmmm You say it works quite nice?

What's the specs on your machine? Could it be that it is the SMP part that messes up?

I only wonder, since the other guy with the same problems as me also was running a dual-cpu system.

-TDS

[djohnson]

I have the following:

Epox mvp3g-m
AMD K6-3 450
256mb ram
G400 32mb dualhead
10GB EIDE IBM
SB Live Value
Netgear 100mb

[TDS]

From what I can gather, and take into account that I'm not very familiar with super-7 MBs, your mainboard does not support AGP-2x. Neighter are you running SMP, and natrually not APIC-IO.

This gives me a few leads to theorize on the driver problems.

As someone has pointed out earlier, this kind of problem was known on the Powerdesk 4 releases of the Win9x driver, and could be avoided by disabling the AGP2x support. This would probably be an indication that eighter the card itself, or the driver development utilities Matrox are using, are buggy. Since historically Matrox has delivered state-of-the-art hardware, and state-of-crap drivers, I believe this has something to do in the drivers dept.

Since you also mention the bust-master point, it may have something to to with APIC-IO to do. It may well be that the Firmware/Driver does not handle IRQ's above 15.....

Since I also noticed that jorsmith, who (from what I see) has the same problems as me, It may be related to the Asus P2B-DS mainboard. Asus has a poor track-record when it comes to admitting faults in their mainboard, for those of you who remember, The P2L97 series had great problems with power-intensive agp-cards, such as the TNTs. So, this may aswell be part of an ASUS fault.

-TDS

tds@powertech.no

[zsadecki]

same problem here, except it locks after about 30 seconds. running bp6, 2x550 celerons, PCI128, g200.

[TDS]

Could you other guys with G-X00 problems under W2K pls. check what IRQ your card is running on? Since APIC-IO boards give you plenty more IRQs, we may have found the Busmaster bug there. My board now works perfectly in non-busmaster mode, but the drivers create an SMP spinlock in busmaster mode.
-TDS