Hello Mike,
donderdag 16 september 1999 20.55, Mike Roark wrote to Kris Steenhaut:


 MR> No, but you are the only one that continuously complains. And it does
 MR> get boring.

Nope.

 KS>> I would it could be thrue. But a good nap will not fix the
 KS>> sucking Matrox 2.21-2.22-2.23 drivers. And these drivers are
 KS>> genuine GA. So, the only one to blame is Matrox.

 MR> BZZZZT! Wrong answer.. Mine work just fine. Obviously George's do to.
 MR> And a lot of other folks say the same thing. When asked what card to
 MR> recommend, a lot of people say Matrox.

Even the guru who sold me the card has admitted now he has problems. A lot of
people did buy coz it was recommended, a lot of people are complaining now.
No, it's not only me.


 MR> Obviously something is wrong with YOUR system.

Again the "it's only you trick". No, I do compare the Matrox with a simple
S3-Virge onto the same Mobo, for instance. The S3 is stable, the Matrox
unstable. It is definitely the Matrox.

 MR>  But you continuously
 MR> blame Matrox because you can't find the problem with YOUR system. You
 MR> state that you have 3 systems with OS/2 on them. Are they identical
 MR> except for the video drivers? I'd bet not. It's often the little
 MR> things that go unnoticed that make it appear that something is wrong
 MR> with a part. How large are the os2.ini and the os2sys.ini files? Are
 MR> they corrupt? Have you re-built them? How many times have you changed
 MR> video cards? Are you sure that everything was done correctly? Perhaps
 MR> missed a step? No one is perfect, and missing something that is
 MR> important can happen to anyone.

If "it was only me", you could have a point. But know I know it is about the
Matrox. Moreover, the Matrox problem has been a diagnostic of the Matrox
problem, and the problem is the BMGAX64.DLL.
The behaviour of this driver is erratic: on some systems no problems,  on
other systems problems and/or severe problems.

You want to know more? Mail to:


***  Internet: dani@ngrt.de
     Fidonet: 2:2490/2576

 MR> That's a lot of questions. Let's see if there is a civilized answer
 MR> to
 MR> any of them.

BTW: I switched the Matrox drivers for the SDD beta, did that too. And all
problems were gone. One more prove it is about the Matrox drivers. Sadly, the
SDD drivers are still beta, and do have some problems with the Acrobatic
reader. And while I was busy, I could see the BMGAX64.DLL does have weird
behaviour indeed. It stays locked for ever, even is there isn't any entry in
the config.sys nor the *.ini's. Even Matrox own "uninstall˙clean" isn't able
to delete the file.


    Groeten uit Gent,
    Regards/2

      Kris

--- GoldED/2 3.0.1  FMail/2 1.48/g
633/260