Kris Steenhaut made noise to Bas Heijermans:

Hi Kris,

 BH> My problems have started after testing the Danis506.Add driver, not
 BH> before. Matrox has never given me problems whatsoever.

 KS> I don't think you can blame Dani's driver for that.

I have used one of the early Dani drivers and that one has screwed my desktop
totaly, after that happend I never touched or will touch that driver again.

 BH> Please don't twist my words, I have installed many Matrox'ses, it's
 BH> the best card arround for OS/2.

 KS> Maybe in the past, not for now anymore.

It still is, maybe if you stop messing arround so much in OS/2 your problems
would go away:-)

 BH>  Ati and S3-cards are really a pain in

 KS> The Ati and S3-Virge do work excellent now, with the latest
 KS> drivers. Especially the S3 with the latest 1.03.25 drivers.

Have you ever tried to work with the newer range of ATI, like the 128 series?
Well have fun! Ati is very un-cool in the OS/2 area.
The S3 cards are only good where it's the S3Trio series about, they are stable 
and well written, all the rest of them are unpredictable of the stability.

BH> the butt, drivers and stability. I suspect that de Dani drivers are
BH> the major problem with the Matrox problems we see arrise now.

 KS> No. The big problem with Matrox are the Matrox drivers.
 KS> These drivers don't cope too well with sharing IRQ. That's
 KS> the reason why the Matrox behave well on older systems, and
 KS> why they have problems on newer one's.

O please!
Do you have any idea what you are talking about?
Shared IRQ's has little to do with the drivers but all with the hardware
design of the cards used and/or the motherboard.
In case you don't know most motherboards can turn off or on the IRQ that can
be assigned to the videocard, it doesn't make much of a diverance either way.
I grant you that the Matrox 2.22 and the 2.23 drivers are not good in some
cases, but they certanly won't hog the CPU, they only hang the WPS.
The only thing software can do with IRQ's is clearing them (CLI instruction)
but to let that have much impact the CLI has to be looped, and I still have to 
see a programmer who is that stupid to use that in their driver.
And in case if they have done so it will lock your entire system (if even
possible with OS/2) that you would have to use the reset button to get out of
it, even ATL-CTRL-NUMLOCK-NUMLOCK won't work anymore, and that's something I
have never seen in any driver.

 BH> And for your information, Netscape is a piece of junk and gives 
 BH> problems on any system.

 KS> You are absolutely wrong about that. Comm404 behaved rather
 KS> well, the new comm461 is stable and works well.

If we take a vote on that here in the area you will lose big time:-)

 KS> It is on the contrary my impression, Netscape was (and is)
 KS> falsely blamed for problems caused by the Matrox drivers.

Well here in all of my systems NS give lots of problems, with dropped FTP's,
crashing randomly, leaving threads open after closing, refusing to start,
showing pages only after reloads and so on.
But only 1 out of the 3 systems has a Matrox card, the others have
WesternDigital 90C31 and a S3Trio64, the results are the same.
Even the OS/2 versions are diverend, one is Warp 4 US-fp10, the other Warp 4
US-fp9 and the last Warp Server Advanced 4 SMP-US-fp42.
Also 3 diverend machines, one is an AMD-K6-2-350 with 192MB ram, the other an
AMD 5x86-133 (overclocked to 160Mhz) with 48MB ram and the Server has 2x Intel 
PI-133 with 96MB.
I have tried NS202, 404 and the latest 4.61, all with the same problems.
The only program that's giving me big problems on all of them is NS, so why
should I be convinced that it has anything to do with Matrox??????
O and before I forget, I even tried the Win'95 version 4.6? (forgot the last
number:-) under Win'95 OSR2 and it has the same problems.
The only good versions of NS that I have seen so far are the ones for BeOS and 
Linux.
This brings me to the conclusion that NS is crap, allmost any version.

Warp3SMP,

Bas Heijermans.

 -=Team OS/2=- -=Computer.Repairs@VT4.Net=- 
--- timEd/2-B11