New Win9x Driver: 5.52.015

[karlpeng]

New PowerDesk 5.52.015 for Win9x. http://www.matrox.com/mga/drivers/files/w9x_552.htm

[moprez]

The question is : will it work with Super7 boards?
I'll give it a try and post feedback.
I still use pd 5.30 for stability.


------------------
Moprez,
Technology Rules.
(K6-III 428MHz, 192M ram, FIC VA-503A, G400 D/H 32M, SB128 pci)

[karlpeng]

Hi,

I have no idea about Super7 M/B. I am using BX M/B(Asus P2B). I installed this newest driver and do some test. As I know so far ....
Its performance is almost as same as 5.50.010
according to 3D Mark 2000 Pro.(2589, 1024x768x16bit, TB)
Play some games and didn't see any difference.(USAF, WWII Fighter, EAW, Falcon4, Flanker 2, Unreal 1 ....) About the OPENGL ICD of 5.52.015, the FPS of Quake2 are about 90% compare with TurboGL Driver of 5.41.(62.4fps vs. 69fps, I only have Quake2 for OPENGL testing.)

After all, I found this newest driver do solve some bugs such as GDI error or wrong display within some 2D(DirectX) Game such as Talonsoft's West Front and East Front. That make me quite happy. 8-)

But this driver still have some texture problem with Apach Havoc(Direct3D Game). Just as same as 5.50.010.

I didn't run too much for test, that's all I know.

My system,

P3-550(Didn't O/C), G400 Max(Didn't O/C), 384MB PC-100 SDRAM, Asus P2B 1.04(BX).

[moprez]

My verdict : 0/5.
The test is simple. Launch Q3. Does it freeze your system (except the unfreezable hardware cursor!)? My answer is yes, since pd 5.41. With 5.30 everything is rock solid, but it's quite different with newer versions.
Does 5.52 work on an other system with similar config?
Maybe Matrox doesn't try their fresh new drivers with poor old K6.
Backyard compatibility isn't their priority. Or at least, doesn't seem to be.
I wish I'm wrong. Can anybody show me the opposite?

------------------
Moprez,
Technology Rules.
(K6-III 428MHz, 192M ram, FIC VA-503A, G400 D/H 32M, SB128 pci)

[Compton]

moprez, I have the Via Apollo Pro 133 chipset and I get the same problem on my G200. I don't see why they didn't call this driver a beta, cus from our perspective there certainly isn't any difference from the betas.

[Flip-Oh]

Hi,

Quake3 stops at the white screen before the intro movie on my system.
And I'm using a regular intel system.
Anyone have any suggestions? I already tried deleting the old drivers before installing the new ones, but that didn't do any good. TurboGL didn't help either...

Greets,
Jorg


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

[moprez]

My favorite combo (by default!) pd 5.30 + TurboGL 1.0.
It helps me wait until something stable from Matrox for "non Intel" (I mean Via) systems.
I always try the newest things, but in this case, newer isn't better.
I don't know why Matrox doesn't put this issue in their "known issues" in the README.

------------------
Moprez,
Technology Rules.
(K6-III 428MHz, 192M ram, FIC VA-503A, G400 D/H 32M, SB128 pci)

[diuby]

The last Matrox driver (5.52) fails in my system as 5.50 realese with any 3d games (at least with Direct 3d). It seems that the problem is with the hardware acceleration of G200. Blue screen of death!!
I think matrox don't test anymore their drivers with Super Socket 7 Systems. I'm very angry!!!
The last driver that run well with my system is 5.41 (5.30 blue screens!!!!).

[k6-III 400 - Via MVP3 Mainboard (Chaintech 5AGM2) - G200 8 Mb SDRAM - Logitech MouseMan USB - Windows 98 - DirectX 7 -]

[Rob G]

Complete arse with S7 once again. QuakeIII just freezes at start up with a blank (white) screen. I do wish they'd actually try and test these releases.

Back to 5.30

[DukeP]

Its a complete GO on my system. All the faults that I could find in the Beta, appear to have been fixed..


ABITBX6II PIII550 128MB SBLive G400MAX

[BADCHILD]

I tried 5.52 all morning and it just is not stable in direct 3d hardware acc. back to 5.41

of course i'm using a outdated via mvp3 board with an old! k6-2 300 so i guess it serves me
right not to be updating every two months. Thanks anyway matrox.

[OrbiT]

I didn't realise the G400 was so problematic on Super 7 set-ups! I am runing the following set-up:

K6-III/400 on ASUS P5A, 128 MB ram, G400 single head 16 MB, Creative SB128 PCI.

I have been doing powerdesk updates continually right up to the 5.50.010 beta that I'm using now, and each time things have actually IMPROVED.
It took me ages to get Direct X 7 working properly with these Beta drivers, but now that they do the system is rock solid. Admittedly I only play Quake 3, but I get none of the problems mentioned above...no problems at all in fact; I never have done with Quake 3 !

I'm sorry because I know this is going to annoy a lot of Super 7 users, and I do feel for you guys...all I can suggest is that you make sure you put Direct X 7 on BEFORE you install the powerdesk drivers...works for me

Please e-mail me if you want more info on my set-up...If my experiences can shed any light on this, then I am more tan happy to try and help...

[ElJay]

It's a no go with my G200 on a K6-2 300, DFI K6XV3+ (VIA MVP3 chipset).

I really wish matrox would let us poor Non-Intel folks know before we spend a half hour with their lame re/un/install crap.

I figured since this was a 'Final release' that it would work on my system. 'Guess not!

*GRR*

[bwhite33]

repost from other message

got this from dejanews and it did work with my Super socket 7 setup:
1) change to plain VGA driver; reboot

2) Do matrox PD un-install; DON'T reboot

3) find and delete (if there) pddata.bin, pdeskcmd.exe, pdkernal.dll

4) reboot and select 5.52

5) enjoy lack of hanging cursor and d3d pauses.

hope this helps

bryan

k6-3 450, tyan 1598s MB, SH g400 32 meg, 128 meg ram, vortex 2 card

[ElJay]

Thanks for trying to help, bwhite...

I still can't get 5.52 to work... so it's back to 5.30

The drivers work fine, until I run a game requires 3d stuff, then it dies.

I've tried them with the VIA AGP patch and without the VIA AGP patch but it doesn't work either way.