Thanks.

I assume you only need the latest one from what you mentioned earlier.

Yup. Thanks.

One more:

https://1drv.ms/u/s!As-dKk-N73dSmB3QiUBZJpnDKvyv?e=WOW0Ye
MD5: 5ca67ec423a77c10cf056917e188d93b

This should query mode Rendition VESA mode 120. For some reason Rendition DMATest uses the VESA call to get this instead of using any Rendition specific method (maybe there is none). Adding VESA function 0x4f00 makes DMA test return a different error.

[EDIT] I need the other bin file in the folder as well.
[EDIT2] Pretty much all the Rendition games query Rendition mode 0x0120).

i found setmode produces different output between windos(win) and Restart to DOS (rtd)
all my tests before only RTD

That's interesting. Under Win98 the V2200 the INT 1Ah call responds to the hardware ID of the V1000.

That must mean that Speedy3D games which are hardcoded for the V1000 must work under Windows but not DOS.

The mode info file wasn't created. I think I need an 8.3 filename,

yes speedy3d works under win98 on v2000 when on dos i must patch them by v2dosfix.exe which replace deviceid inside exe.
generally RTD adds performance, win and pure dos not. but pure dos faster than win.

performance priority.
RTD fast
DOS medium
WIN slow

https://1drv.ms/u/s!As-dKk-N73dSmB4sh5HK5VuL6IKD?e=ov0rz5
MD5: 1c254e9b5d58b246721a141a438d0eb0

This should dump the mode info for mode 120h.

Also all the other register reads are the same, the same port ID and memory mapped address.

vQuake is the only one I have which doesn't issue the VESA calls.

I think V_OpenVerite and V_ScreenBegin (at least that's the error messages called them) uses the VESA calls to switch mode, just like

1V_SetDisplayMode(vhandle, 640, 480, 16, 75)
2
3V_SetDisplayType(vhandle, V_FULLSCREEN_APP) 

on Windows.

I'm also willing to bet mode 120h is 640x480/16@75Hz.

i am unsure if vquake uses 75hz, coz there is no problem at all to capture vga output , as my Aver Media Game Capture HD can\t handle more than 60HZ refresh rates.

all files now created

This is what's reported:

VESA Mode info for Rendition mode 0x120

1Attribs 9b
2WinA Attribs 7
3WinB Attribs 0
4winGranularity 40
5winSize KB 40
6winASegment a000
7winBSegment 0
8winPos function pointerc0004eb4
9bytesPerScanline 1280
10// Optional for VESA 1.1+
11widthPelOrChars 320
12heightInPelsOrLines 240
13charWidthPels 8
14charHeightInPel 8
15numPlanes 1
16bitsPerPel 32
17numBanks 1
18memoryModelType 6
19bankSize 0
20numImagesPages 11
21reservedVBE 1
22redMask 8
23redPos 16
24greenMask 8
25greenPos 8
26blueMask 8
27bluePos 0
28reservedMaskSize 8
29reservedMaskPosSize 24
30directColourModeInfo 3
31linearAddress 8
32offscreenMemory 32
33offscreenMemorySize 2348810705

Despite what resolution being listed as 320x240 that's actually a 640x480 mode because the linebytes is 1280 (640x2 bytes per line, ).

[EDIT] I'm pretty sure that's not 320x4 (32 bit).

I think yes it should be 16 bit depth of color

yes i can confirm 320x200 and 320x240 actually reported as 640x480@60 by monitor, some of resolution can report as 800x600@60 and there is also some weird resolutions which actually 70hz and 75hz
the 512x384 resolution in game my monitor can show but can't define what is it, and it 75 hz.
if its neede i can make detailed report.

OK now that that call works in DOSBox, it turns out that actually was a 320x240x32 bit mode.

In fact because the call worked, it started querying all the available modes, one at a time, which makes sense:

https://1drv.ms/u/s!As-dKk-N73dSmB8NfU8X0z7bR042?e=b5PuXV
MD5: 77fbb0d2e720c481d1bc36afaea00edb

This should produce a whole lot of bin files, one per mode.

320x240 being reported as 640x480 is probably scan frequency related.

[EDIT] No, a detailed report won't be necessary. I'm sure Speedy3D doesn't go into scan frequencies.

DOS box/DMATest changes vid mode once that call started to work. So, progress! I'm hoping I can redirect to VL_OpenVerite instead of using Dosbox's setmode at some
point.

I need to plug in the rest of the stuff for all the modes. It's probably going to the wrong mode. V2000 has more modes than V1000. It would actually be interesting to see if it queries all the modes on your board or just the ones that're common.

Mode list for V1000 (47 modes):
120,121,122,123,124,100,101,125,126,103,105,127,107,10D,128,12B,12E,131,134,110,137,13A,113,116,13D,10E,129,12C,12F,132,135,111,138,13B,114,117,13E,10F,12A,12D,130,133,136,112,139,13C,115

For V2000 (61 modes):
11C,10D,10E,10F,11D,11E,11F,120,121,122,123,124,125,126,127,128,129,12A,12B,12C,100,12D,12E,12F,101,110,111,112,130,131,132,133,134,135,136,137,138,139,13A,13B,103,113,114,115,13C,13D,13E,13F,105,116,117,118,140,141,142,144,145,146,107,119,11A

BTW VESA BIOS calls (all through the standard Int 10h)

Call 0x4F00 doesn't change mode. It returns a list of available mode.

Call 0x4F01 It returns information about a mode.

The standard BIOS call function 0x0000 changes mode, just like on pretty much every single video adapter ranging from CGA and on all that.

done

Thanks. There's a VESA setMode function 0x4F02. I was wrong. The standard Int 10h setmode can't do modes higher than 0xFF.

Now DMATest returns a RISCReset failed. [EDIT] before it was board not detected[/EDIT]

I'll probably be stuck on this for a while.

In case anyone's interested in the mode details, I've attached it.

More to chew on tomorrow, unfortunately.