Kris Steenhaut made noise to Bas Heijermans:

Hi Kris,

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

 KS> You can't be blamed for having an open mind. Well, I'm going
 KS> to play the "it's only you" trick myself: yoy are the only
 KS> one now having problems with Dani's drivers..

I don't think so, I have seen lot's more messages of people who had the same
problem with that driver.
And BTW the speed of the normal driver is about the same as here driver.

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

 KS> I'm no messing around: that ONE problem on my system has
 KS> beel pinpointed to the Matrox Drivers. And not by me, btw,
 KS> but by someone having the same amount of knowledge about
 KS> these things as Sam Detweiler.
 KS> And I take the liberty to believe her instead of you,
 KS> because what she says match _exactly_ what is happening on
 KS> my system.

Believe what you want.

 BH> Have you ever tried to work with the newer range of ATI, like the 128
 BH> series?

 KS> No, I'm talking about stuff you wery well know who has
 KS> installed it. 

But those are old dated and not supported anymore.

 BH>  Well have fun! Ati is very un-cool in the OS/2 area. The S3
 BH> cards are only good where it's the S3Trio series about, they are
 BH> stable and well written, all the rest of them are unpredictable of the
 BH> stability.

 KS> I wasn't talking about the at128, but about Mach64, wich you
 KS> do know very well. I do know, unlike the newer Matrox, the
 KS> S3Savega4 works excellent, even with S3 propriatary drivers.

I don't use those anymore, the display speed is too low and the Mach64 can't
be compared to the Matrox G200 and up cards.

 BH> O please!
 BH> Do you have any idea what you are talking about?
 BH> Shared IRQ's has little to do with the drivers but all with the
 BH> hardware design of the cards used and/or the motherboard. In case you
 BH> don't know most motherboards can turn off or on the IRQ that can be
 BH> assigned to the videocard, it doesn't make much of a diverance either
 BH> way.

 KS> YOU don't knwo what you are talking about! The Aopen AX59PRO
 KS> has no possibility to reassign the video-IRQ. Look at my
 KS> previous message, look at the fucking manual (it's in
 KS> Spanish, you sure are able to read): the video-irq is ALWAYS
 KS> bouns to the same one as the mass-controler.

Well if you look in your BIOS (I have 2.24) in the section PNP/PCI
Configuration you can set any IRQ to any PCI slot, so you are able to take
them apart.

 BH>  I grant you that the Matrox 2.22 and the 2.23 drivers are not
 BH> good in some cases, but they certanly won't hog the CPU, they only
 BH> hang the WPS.

 KS> Wich is _exactly_ the case here. Not only with 2.22 - 2.23
 KS> but 2.22 @ 2.31 GA. 

Have you tried to install the one's on the CDrom?
They should work fine.

 BH>  The only thing software can do with IRQ's is clearing
 BH> them (CLI instruction) but to let that have much impact the CLI has
 BH> to
 BH> be looped, and I still have to see a programmer who is that stupid to
 BH> use that in their driver. And in case if they have done so it will
 BH> lock your entire system (if even possible with OS/2) that you would
 BH> have to use the reset button to get out of it, even
 BH> ATL-CTRL-NUMLOCK-NUMLOCK won't work anymore, and that's something I
 BH> have never seen in any driver.

 KS> _EXACTLY_ what happens here on my system and other fellows I
 KS> had a mail with. 

I think you have a BIOS settings problem, because a driver can't lockup the
ALT-CTRL-NUM-NUM feature, when you have that you have managed to halt the CPU
with the OS/2 Kernal.
To get into this state you have a few options, the CPU stopped because of
overheating, the ram/cache isn't working at the correct speed and so on.
I have seen the transfer problem with SCSI and locking the system with an
AX59Pro, but that problem was caused by a BIOS setting.
You problems are beginnging to sound the same as that person had, you should
try to find a way that you can recreate the problem every time, when you are
there you should start changing the BIOS in the Chipset section.
I'm convinced you will be able to solve your problem there.
It's not the IRQ's, you don't have to worry about them, they are not the
problem.

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

 KS> Do take a test: switch the Matrox drivers by the SDD, and
 KS> you'll see the difference. There is a new beta7 out since
 KS> yesterday, btw, will install them within a few houres.

I won't try them, the 2.20.060 drivers are working fine here.
Your problem are not the drivers, install first the normal VGA drivers with
SETVGA, then look into your config.sys for any drivers that left in there and
shouldn't be in there, reboot and install the Matrox drivers from the CDrom
that came with the Matrox.
If you still have locking or transfer problems, start changing the BIOS, you
will find that there will be the answer to your problems.

 BH> and it has the same problems. The only good versions of NS that I have
 BH> seen so far are the ones for BeOS and Linux. This brings me to the
 BH> conclusion that NS is crap, allmost any version.

 KS> Even with Matrox drivers  loaded, the NS461 behaves well.
 KS> Nearly all of the problems are gone, except for the
 KS> Alzheimer-bug: NS went down a few times since I had it
 KS> installed. But the FTP-http- and other files transports are
 KS> fine and well: last night I downloaded the 4 Mg SDD drivers
 KS> withhout a hitch at 4.3 kb, and days before I had the same
 KS> experience with even larger files. 

Then NS must have speed problems, because I have ISDN and the rates are upto 9 
kb.
I'm still looking to solve to solve it:-)

Warp3SMP,

Bas Heijermans.

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