Major graphical glitches with ATI Graphics Pro Turbo on ASUS P55T2P4

[eddman]

Windows 10 host
PCem v17
Windows 98 SE, built-in drivers

The glitches are only present in the windows environment and when using anything higher than 16 colors mode. In 256 mode the main visible glitch is the mouse cursor being black, however in 16-bit and 24-bit modes the entire output is glitched.

Also, when I use the offered restart option when changing to/from 16 colors mode, sometimes I get a "Windows Protection Error" message.

That card works fine on other socket 7 boards (haven't tried Epox), and the Super 7 and Slot 1 boards.

Can anyone confirm this behavior with that board?

Screenshot 2022-11-20 224056.png (40.33 KiB) Viewed 1059 times

[unreal9010]

It works for me in Windows 95 in 16-bit mode (800x600), however, whenever I exit any fullscreen DOS application running under Windows, cursor turns black and there are black artifacts all over the screen. Currently, the only workaround is to change resolution, refresh rate or bit-depth. Happens under any compatible Mach64 bios or drivers.

[eddman]

It works for me in Windows 95 in 16-bit mode (800x600), however, whenever I exit any fullscreen DOS application running under Windows, cursor turns black and there are black artifacts all over the screen. Currently, the only workaround is to change resolution, refresh rate or bit-depth. Happens under any compatible Mach64 bios or drivers.

Are you using that ASUS board? For me windows 95 behaves the same way as I see on 98.

I want to confirm the problem on that board+card combination before opening an issue on github.

[unreal9010]

It works for me in Windows 95 in 16-bit mode (800x600), however, whenever I exit any fullscreen DOS application running under Windows, cursor turns black and there are black artifacts all over the screen. Currently, the only workaround is to change resolution, refresh rate or bit-depth. Happens under any compatible Mach64 bios or drivers.

Are you using that ASUS board? For me windows 95 behaves the same way as I see on 98.

I want to confirm the problem on that board+card combination before opening an issue on github.

The issue described above occurs with with any board, emulated CPU, operating system, bios or drivers so it's definitely a PCem bug.
I recall this one being present since at least 2016 when I started to regularly use PCem.

[eddman]

If you can, please test with that specific board and card, and in windows environment only, no DOS programs. It's probably all related, but I want to confirm that specific case only.