New Parhelia drivers 1.06.00.99

[Sisyfos]

ftp://ftp.matrox.com/pub/mga/archive/2kxp/2004/

Kim

[GNEP]

Oooh - so who's gonna try them out for me then?

[SaTaN^666]

I tried them guys. dont bother. very ... buggy.. they turned me into a wallhacker in q3, lots of flickering screens during gameplay if u go into game menus and back in game. I would stick with teh 1.5s drivers

[lecter]

They seem to have fixed the green Windows Media bug, which had been fixed before but reappeared in the recent releases...

[K6-III]

No new OpenGL extensions as compared to the prior 1.06 beta...

[GNEP]

So does anyone fancy trying them with KOTOR?

[KeiFront]

No real improvements noticed so far. No improvements in Kotor you still have to disable the movies, etc. Alt+tabbing still causes problems in quake3 based games, etc.

And offcourse we still have to guess what's fixed with this driver release (again no release notes).

[K6-III]

Looks like most of the bugfixes in this release are for Premiere Pro...

[leech]

Why have matrox stopped putting out release notes for their drivers? It can't really take all that long to write one.....

Leech

[stcynic]

Originally posted by leech
Why have matrox stopped putting out release notes for their drivers? It can't really take all that long to write one.....

Leech

It does if you are not keeping good track of what bug fixes are in a release. I do not know about Matrox, but you would be surprised at how many software shops do _not_ keep track of these things well ("Hey Bubba! What bugs did you fix? I am writing up the release notes.").

If they were using a decent bug-tracking system, you are correct--it is very easy. Most of them will create the damn thing for you automatically.

The only other excuse for not doing it, that I can think of, is if you are trying to disguise quality problems by preventing people from know what kind of and how many bugs you are fixing.

So I assert: there is no good reason for Matrox to not produce release notes.

[bsdgeek]

Any good reason to get these over 1.06b? Feelin' lazy...

[KeiFront]

Originally posted by bsdgeek
Any good reason to get these over 1.06b? Feelin' lazy...

Yes the 1.06beta gave me some problems in one particular game (BSOD ) these don't .

Originally posted by stcynic
If they were using a decent bug-tracking system, you are correct--it is very easy. Most of them will create the damn thing for you automatically.

The only other excuse for not doing it, that I can think of, is if you are trying to disguise quality problems by preventing people from know what kind of and how many bugs you are fixing.

So I assert: there is no good reason for Matrox to not produce release notes.

I'll second that, it's damn easy to keep track of bug fixes. any decent source mangment and bug tracking software can help you with this.

[Joel]

I'll second that, it's damn easy to keep track of bug fixes. any decent source mangment and bug tracking software can help you with this.

Plus you have to remember that Matrox no longer has any outside beta testing going on. Everything is done internally on lab test machines instead of real world everyday use machines.

Joel

[Che Guevara]

Is anyone else than SaTaN^666 having problems with the new drivers (which don't appeared in the last ones)?
In some q3a based games like et for example?

And does FAA with game specific settings work again (remember the 1.06 beta...)?


Greetz
Che

[Sisyfos]

Seems there's a 2kxp_106_00_se.exe now that doesn't require .NET.

From Setup.ini:
[SETUP]
PackageName = Matrox Powerdesk SE
InstallPowerDeskVisible = false
InstallPowerDesk = true
.NETRequired = FALSE
IniFormatVersion=2.0

[VHEAD]
DUALPARH.inf
DuALG400.inf
DUALG550.inf

[FAMILY]
mtxparh.inf = Matrox Parhelia & Millennium P650/P750
G550.inf = Matrox G550 Series
G450.inf = Matrox G450 Series
G450MMS.inf = Matrox G450MMS
G400.inf = Matrox G400 Series
G200.inf = Matrox G200 Series
G200MMS.inf = Matrox G200MMS

[Powerdesk]
PowerDeskInstallCommand = msiexec /I PDeskSE.msi /q



Haven't tried them though

Kim