I keep coming back to these two stupid INT call for more data. Tracing back from the Rendition Verite not found always leads back to the int call on each path. Now I need the carry flags from these. The carry flag shouldn't be set on return from an int call, but with DOS box I get somthing back possibly.
So any Rendition board under DOS should be fine. No crashes or anything. Just need the console output.
I just realized some of the results I get are different depending on if the CPU is in protected mode or not (EMM386 vs UMBPCI). Don't know if this makes much of a difference here, if any. It didn't change that register you were noting on the previous results though. I think I've been using them under EMM386 the whole time but I can't remember.
Anyway, here's the V1000 for the new one. Don't know if you even need mine but I did it anyway.
Pentium MMX 233 | 64MB | FIC PA-2013 | Matrox Mystique 220 | SB Pro 2 | Music Quest MPU Clone | Windows 95B
MT-32 | SC-55mkII, 88Pro, 8820 | SB16 CT2230
3DFX Voodoo 1&2 | S3 ViRGE GX2 | PowerVR PCX1&2 | Rendition Vérité V1000 | ATI 3D Rage Pro
It shouldn't make a difference in theory because thd int calls run in virtual 8086 mode.
The only notable difference between RaVeN-05's and your results are in CX. Flags is the onky other thing that worries me, but an int call should preserve the flags register. I'll knock up one final version in a bit, to see if the call alters stuff on the stack.
Thanks! That second Int1A call is very useful. By altering what it returns the error code returned by Speedy3D apps with Verite board not detected changes.