VOGONS


Matrox Mystique (MSI API Native) list

Topic actions

Reply 60 of 69, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

To be fair DD2 is not good, it works now, don't know what fixed it but this game is not very good.
Screamer/Screamer Rally are much better games than DD2, I have not tested these, all I can say is:
There is no matrox-tool to activate vesa2 compliant behavior on the mystique.

autoexec.bat (vbetsr+vbesetup) do no change anything on chasm and other games.
sdd5.3 (dos/winx) does offer lot's resolutions on chasm but does not help for "stargunner".

Stargunner is in fact really a great game and I would love to play it on vesa 320x240....more tests need to be done.

Retro-Gamer 😀 ...on different machines

Reply 61 of 69, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

Stargunner in plain dos with SDD 5.3 detects VESA2.0 but the game is still broken. The additional 40 lines (320x240) have weird colors and seem not to be part of the scrolling-gameplay.

Retro-Gamer 😀 ...on different machines

Reply 62 of 69, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

I am back on that machine for a nice multi boot setup. For those of you who have a machine with a mystique inside. What win95 driver are you using? I just figured out, that the driver I recommended (the very very late/last one from 1999) does not install, if I am using win95a, seems that it requires win95b, so I have to use a different driver.

UPDATES:
Stock 370 driver from the mga-cd has no working v-sync in ddraw as expected. if you want to try it (DX5 required) https://www.pouet.net/prod.php?which=8410
I have not tested the next two drivers, but I did that long ago and the only working driver was the very latest with files from 1999. Installing this driver over version 370 always crashes win95a on startup after reboot.

So in short. Either a third party tool that fixes vsync on ddraw on early drivers, or changing the OS to win95B and using the very latest driver.

Edit2:
Power-Strip and MGA-Tweak do not offer v-sync option. Beside some scene stuff, also JazzJackRabbit2 is affected, so...I am going back to the already fully tested and working setup. Win95b with the latest driver.

Retro-Gamer 😀 ...on different machines

Reply 63 of 69, by eliot_new

User metadata
Rank Member
Rank
Member

Hello Dr Zeissler, me too I ve a Mystique 220 4MB along with Diamond V1 4MB 3dfx on an Asus SP97XV with K6-2 400. I have a lot of issues running DOS games in SVGA or in 3dfx. Either it has to do with my Asus VS247HR or with the Matrox drivers or with the Matrox Diamond combination

DOS:P233MMX,64MB,ECS,SpeaMirageV7,3dfxV1,AWE64,ESS1868,PicoGUS,32GB
W98SE:K63/400,256MB,P5A,Verite2200AGP,3dfxV2,M3D,AWE64,ESS1938,PicoGUS,64GB
XP:P3-1G,512MB,CUSL2C,FX5600AGP,Audigy1,80GB

Reply 64 of 69, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

Can you describe what fails in more detail, perhaps I can help.

Retro-Gamer 😀 ...on different machines

Reply 65 of 69, by eliot_new

User metadata
Rank Member
Rank
Member

Hello Dr Zeisler,

Yesterday I switched the sdcard from the 1.PC Asus SP97XV K6-2 400 Matrox Mystique 220 4MB to 2. PC ECS P5HX-A P233MMX Spea Mirage Trio64 2MB

Result: after loading Univbe 6.7 in autoexec bat I could play Q1 in SVGA from 400x300 up to 1024x768

The same sdcard I utilized to boot on 1. PC: regardless what I do with Univbe, no SVGA

DOS:P233MMX,64MB,ECS,SpeaMirageV7,3dfxV1,AWE64,ESS1868,PicoGUS,32GB
W98SE:K63/400,256MB,P5A,Verite2200AGP,3dfxV2,M3D,AWE64,ESS1938,PicoGUS,64GB
XP:P3-1G,512MB,CUSL2C,FX5600AGP,Audigy1,80GB

Reply 66 of 69, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

What does UNIVBE 6.7 say to the myst-220 ? is it recognized, is sVGA not choosable or does the monitor stay black when choosing SVGA on mga-220?

Retro-Gamer 😀 ...on different machines

Reply 67 of 69, by eliot_new

User metadata
Rank Member
Rank
Member

Hello Dr. Zeisser, I m sorry 4 answering that late. I only just managed to get around to testing it. The Matrox Mystique 220 is not at fault; it works perfectly (100%) in SVGA mode with this hardware: ECS P5HX-A, P233MMX, 64MB EDO RAM, and a 32GB SD card (configured for multiboot with MS-DOS 6.22 and Win98SE). Thanks to UniVBE 6.7—which I call from my autoexec.bat—I can even run Quake 1 v1.01 at resolutions up to 1280x1024 in software mode. It is therefore clear that the issue lies either with the Asus SP97-XV motherboard or its CPU, an AMD K6-2 400. The board is running a BIOS by Jan Steunebrink, and I have configured it with the most aggressive settings. I plan to test all my other PCI graphics cards in this system to see if they also result in a black screen when using SVGA. Furthermore, I intend to install my slowest CPU, a Pentium P150, for additional testing. I would also like to apologize to the Vogons community if I gave the impression that the Matrox Mystique 220 was the cause of the problem; it is, in fact, a fantastic card.

DOS:P233MMX,64MB,ECS,SpeaMirageV7,3dfxV1,AWE64,ESS1868,PicoGUS,32GB
W98SE:K63/400,256MB,P5A,Verite2200AGP,3dfxV2,M3D,AWE64,ESS1938,PicoGUS,64GB
XP:P3-1G,512MB,CUSL2C,FX5600AGP,Audigy1,80GB

Reply 68 of 69, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

Interesting, thx for sharing that info. I don't have a clue what's wrong though.

Retro-Gamer 😀 ...on different machines

Reply 69 of 69, by eliot_new

User metadata
Rank Member
Rank
Member
dr.zeissler wrote on Today, 15:12:

Interesting, thx for sharing that info. I don't have a clue what's wrong though.

I tested exactly 6 graphics cards on my Asus SP97-XV motherboard with an AMD K6-2 400 processor and 128MB of SDRAM, running MS-DOS 6.22.
The tests were performed using 3dbench2 and Quake 1 (at resolutions of 320x200 and 800x600).
UniVBE 6.7 is enabled in the autoexec.bat file. Here are the test results.

1. Tseng ET4000W32p:
=> Q1 800x600 = yes,
=> 3dbench 259.0 fps;
=> Q1 320x200 = 56.6 fps
2. ARK2000 Hercules Stingray 64:
=> Q1 800x600 = yes,
=> 3dbench 307.9 fps;
=> Q1 320x200 = 57.0 fps
3. V3-3k PCI:
=> Q1 800x600 = yes,
=> 3dbench 307.9 fps;
=> Q1 320x200 = 57.0 fps
4. S3 Trio 64:
=> Q1 800x600 = yes,
=>3dbench 306 fps;
=> Q1 320x200 = 56.0 fps
5. Matrox G450: (what a miracle, regardless all warnings in internet, it works with a non_intel chipset mainboard Asus SP97-XV @ SiS 5582
=> Q1 800x600 = yes,
=> 3dbench 271 fps;
=>Q1 320x200 = 57.1 fps
6. Matrox 220 with 4MB RAM:
=>800x600 = no (blank screen at all SVGA resolutions regardless what Hz is set by unirefresh or unicentre),
=>3dbench 305 fps;
=>Q1 320x200 = 57.1 fps
6: I even tried connecting it to a 2009 Sony HD-ready TV via VGA; the result in SVGA was the same: a blank screen.

EDIT:

I seem to be overworked as I had completely forgotten, that at the beginning of november I had a K6-233 ANR on the Asus SP97-XV with no K6-init loaded and then the Matrox Mystique 220 worked on the Asus SP97-XV:

Quake1 software mode 640x480, 800x600 (not) possible although same graphics card, but different boards?

Conclusion: it must be K6-2 400 and K6init which enables write combining but causes a problem with the Matrox Mystique 220. Furthermore you should avoid Asus EyeCare 23" monitors as only my Asus VS247HR worked with the Mystique in SVGA resolutions.

DOS:P233MMX,64MB,ECS,SpeaMirageV7,3dfxV1,AWE64,ESS1868,PicoGUS,32GB
W98SE:K63/400,256MB,P5A,Verite2200AGP,3dfxV2,M3D,AWE64,ESS1938,PicoGUS,64GB
XP:P3-1G,512MB,CUSL2C,FX5600AGP,Audigy1,80GB