CkRtech wrote on 2026-02-28, 20:14:

I am up to doing this as I am still messing with this video card if you have the interest and the time. […]
Show full quote

Mumak wrote on 2025-11-09, 18:25:

Well, I guess I will have to get such a card and run tests...
The only alternate way would be to create a special HWiNFO version which would require a key press prior to each VGA chip test (HWiNFO displays at the bottom of screen which chip is tested) so you could capture the moment when it goes wrong..

I am up to doing this as I am still messing with this video card if you have the interest and the time.

The last line in the debug file was:
Checking: AT&T DEB

I know that it could be we were several steps ahead of the last item logged at the time the error occurred, but stopping before each test with a list of which test is about to be active would hopefully help us narrow things down.

OK, I have created a special build that requires a key-press after each status row displayed by HWiNFO. This should help to pin-point the exact place where it goes wrong.
Please try this build and let me know what was the last message displayed before the display went off.

Ok. Launched. Pressed spacebar through some init. Selected video info.

Saw “checking matrox…” and pressed space.
Saw “checking S-MOS,” pressed space, and then… screen corrupted.

CkRtech wrote on 2026-02-28, 22:50:

Ok. Launched. Pressed spacebar through some init. Selected video info.

Saw “checking matrox…” and pressed space.
Saw “checking S-MOS,” pressed space, and then… screen corrupted.

Thank you!
Please try the attached version and let me know if it fixes the problem.

Alas, it appears to still have the same problem.

OK, I have put again the key-pressing to check further. Please try this build and let me know.

OK. Now we are talking.

"Checking: Weitek" gave a momentary flash of just a few scanlines near the bottom quarter of the screen. Everything continued to work fine. Standard fare for when hardware is detected by software in my opinion.

And of course the Power 9000 chip on this Diamond Viper VLB is made by Weitek, so perhaps it managed to communicate with it.

I passed through a few other items until "Checking: Oak." I pressed spacebar after that and BOOM. Corruption.

Oak is, of course, the base VGA chip on the card used for handling text and low res modes. The P9000 is accessed for VESA modes.

CkRtech wrote on Yesterday, 17:59:

OK. Now we are talking. […]
Show full quote

OK. Now we are talking.

"Checking: Weitek" gave a momentary flash of just a few scanlines near the bottom quarter of the screen. Everything continued to work fine. Standard fare for when hardware is detected by software in my opinion.

And of course the Power 9000 chip on this Diamond Viper VLB is made by Weitek, so perhaps it managed to communicate with it.

I passed through a few other items until "Checking: Oak." I pressed spacebar after that and BOOM. Corruption.

Oak is, of course, the base VGA chip on the card used for handling text and low res modes. The P9000 is accessed for VESA modes.

Thanks. Please try the attached build and let me know.

Bingo.

No TSR:

With Diamond VESA driver loaded:

CkRtech wrote on Yesterday, 19:01:

Bingo. […]
Show full quote

Bingo.

No TSR:

The attachment IMG_6083.jpeg is no longer available

With Diamond VESA driver loaded:

The attachment IMG_6084.jpeg is no longer available

The attachment IMG_6085.jpeg is no longer available

Perfect 😀 Thanks for you help!
I will release a new version with this and a few other fixes.

Mumak wrote on Yesterday, 19:05:

Perfect 😀 Thanks for you help!
I will release a new version with this and a few other fixes.

Happy to help!

Version 6.2.7 released. Details and download in OP.