Fun with CGL (Creative Graphics Library) on 3D Blaster

Reply 260 of 270, by sharangad

Posted on 2026-05-03, 17:56

sharangad Offline

Rank l33t

Rank: l33t
Posts: 2680
Joined: 2023-07-01, 11:02
Location: Colombo

RaVeN-05 wrote on 2026-05-03, 17:36:
Well I tried v2100 as "closest" to v1000. Used Rebel Moon : Unpatched: init_gfx: about to cglLoad […]
Show full quote

Well I tried v2100 as "closest" to v1000.
Used Rebel Moon :
Unpatched:
init_gfx: about to cglLoad

init_gfx() : CGL Load Failed error - - 0
Patched: (xor eax, eax)
init_gfx: about to cglLoad
About to cglQueryScreeb
Failure: Query Screen returned - 122
No CGL Found!!!!!! Using VESA driver.

We need to try to test on non Creative v1000 card owners. I am sure owners here.

What if cglQueryScreen is patched out in exactly the same way as cglboard present?

This is at offset 0x10551. Will give it a go tomorrow, it's time for bed here.

Also the mode numbers might be embedded into the driver. Will check tomorrow.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda\
https://patreon.com/Rready

Reply 261 of 270, by sharangad

Posted on 2026-05-03, 20:07

sharangad Offline

Rank l33t

Rank: l33t
Posts: 2680
Joined: 2023-07-01, 11:02
Location: Colombo

Here's the modified CGL file.

https://nirvtek.com/downloads/VRITB170.V2000.20260504.001.7z
MD5: 80cbef55870aafb41999f52557aef4cb

Unzip and place in game directory. I've put my V1000 board back in and don't really fancy swapping cards at 1 AM.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda\
https://patreon.com/Rready

Reply 262 of 270, by sharangad

Posted on 2026-05-03, 21:05

sharangad Offline

Rank l33t

Rank: l33t
Posts: 2680
Joined: 2023-07-01, 11:02
Location: Colombo

The full function pointers for VRITE170.CGL (Pointer offset is 0xF17C):

1Driver: C:\DOS\CGL\CGL Drivers\VRITE170.CGL
2File size is 102174 (00018F1E)
3File version 170.84 (Build #16)
4File header offset 115, type [2] at offset 119
5Name table read: current offset 126 (0x0000007E)
6************************************************
7CGL Driver Type: float operands with register based parameters passing
8************************************************
9File offset is now 05C5
10Function cgltfr: pointer 2032C, file offset 2F4A8
11Function cglVersionControl_: pointer 2350, file offset 114CC
12Function cglSendStream_: pointer 2434, file offset 115B0
13Function cglGetPixel_: pointer 3484, file offset 12600
14Function cglPutPixel_: pointer 3390, file offset 1250C
15Function cglInitScreen_: pointer 1878, file offset 109F4
16Function cglQueryScreen_: pointer 1674, file offset 107F0
17Function cglClearScreen_: pointer 3958, file offset 12AD4
18Function cglCloseScreen_: pointer 1F34, file offset 110B0
19Function cglSetWindowClip_: pointer 39F0, file offset 12B6C
20Function cglInitPan_: pointer 2040, file offset 111BC
21Function cglPanPos_: pointer 21CC, file offset 11348
22Function cglSetLineStyle_: pointer 314C, file offset 122C8
23Function cglSetFillPattern_: pointer 315C, file offset 122D8
24Function cglSetStipplePattern_: pointer 32B8, file offset 12434
25Function cglSetDepthMode_: pointer 30CC, file offset 12248
26Function cglSetStencilMode_: pointer 337C, file offset 124F8
27Function cglSetLogicalOpsMode_: pointer 31AC, file offset 12328
28Function cglSetDepthCueColor_: pointer 307C, file offset 121F8
29Function cglSetDitherMode_: pointer 3060, file offset 121DC
30Function cglLoadTextureMap_: pointer 4E60, file offset 13FDC
31Function cglSelectRenderBuffer_: pointer 3CEC, file offset 12E68
32Function cglCopyDisplayBuffer_: pointer 3E58, file offset 12FD4
33Function cglLockBuffer_: pointer 3FE8, file offset 13164
34Function cglClearBuffer_: pointer 3AF0, file offset 12C6C
35Function cglSetConstant_: pointer 3770, file offset 128EC
36Function cglSwapBuffer_: pointer 3C64, file offset 12DE0
37Function cglUpLoad_: pointer 482C, file offset 139A8
38Function cglDownLoad_: pointer 4140, file offset 132BC
39Function cglSetPalette_: pointer 36E0, file offset 1285C
40Function cglGetPalette_: pointer 373C, file offset 128B8
41Function cglSetPickRegion_: pointer 7270, file offset 163EC
42Function cglGetPickResult_: pointer 7270, file offset 163EC
43Function cglSetExtent_: pointer 7270, file offset 163EC
44Function cglGetExtentResult_: pointer 7270, file offset 163EC
45Function cglGetConfig_: pointer 1F7C, file offset 110F8
46Function cglSetCursor_: pointer 6FCC, file offset 16148
47Function cglSetCursorPos_: pointer 6F00, file offset 1607C
48Function cglSetupInterrupt_: pointer 2360, file offset 114DC
49Function cglReleaseInterrupt_: pointer 23A8, file offset 11524
50Function cglBoardPresent_: pointer 22A4, file offset 11420
51Function cglQueryFeature_: pointer 729C, file offset 16418
52Function cglEventRegister_: pointer 7330, file offset 164AC
53Function cglEventDeregister_: pointer 73A4, file offset 16520
54Number of functions 44

and there was a bug with the VRITB170 pointers. The correct set is available here
(Pointer offset 0xEEDD):

1Driver: C:\DOS\CGL\CGL Drivers\VRITB170.CGL
2File size is 99399 (00018447)
3File version 170.84 (Build #16)
4File header offset 115, type [0] at offset 119
5Name table read: current offset 126 (0x0000007E)
6************************************************
7CGL Driver Type: integer operands with register based parameters passing
8************************************************
9File offset is now 05C5
10Function cgltir: pointer 2032C, file offset 2F209
11Function cglVersionControl_: pointer 2350, file offset 1122D
12Function cglSendStream_: pointer 2434, file offset 11311
13Function cglGetPixel_: pointer 3444, file offset 12321
14Function cglPutPixel_: pointer 3390, file offset 1226D
15Function cglInitScreen_: pointer 1878, file offset 10755
16Function cglQueryScreen_: pointer 1674, file offset 10551
17Function cglClearScreen_: pointer 38C8, file offset 127A5
18Function cglCloseScreen_: pointer 1F34, file offset 10E11
19Function cglSetWindowClip_: pointer 3960, file offset 1283D
20Function cglInitPan_: pointer 2040, file offset 10F1D
21Function cglPanPos_: pointer 21CC, file offset 110A9
22Function cglSetLineStyle_: pointer 314C, file offset 12029
23Function cglSetFillPattern_: pointer 315C, file offset 12039
24Function cglSetStipplePattern_: pointer 32B8, file offset 12195
25Function cglSetDepthMode_: pointer 30CC, file offset 11FA9
26Function cglSetStencilMode_: pointer 337C, file offset 12259
27Function cglSetLogicalOpsMode_: pointer 31AC, file offset 12089
28Function cglSetDepthCueColor_: pointer 307C, file offset 11F59
29Function cglSetDitherMode_: pointer 3060, file offset 11F3D
30Function cglLoadTextureMap_: pointer 4DD0, file offset 13CAD
31Function cglSelectRenderBuffer_: pointer 3C5C, file offset 12B39
32Function cglCopyDisplayBuffer_: pointer 3DC8, file offset 12CA5
33Function cglLockBuffer_: pointer 3F58, file offset 12E35
34Function cglClearBuffer_: pointer 3A60, file offset 1293D
35Function cglSetConstant_: pointer 36E0, file offset 125BD
36Function cglSwapBuffer_: pointer 3BD4, file offset 12AB1
37Function cglUpLoad_: pointer 479C, file offset 13679
38Function cglDownLoad_: pointer 40B0, file offset 12F8D
39Function cglSetPalette_: pointer 3650, file offset 1252D
40Function cglGetPalette_: pointer 36AC, file offset 12589
41Function cglSetPickRegion_: pointer 6B10, file offset 159ED
42Function cglGetPickResult_: pointer 6B10, file offset 159ED
43Function cglSetExtent_: pointer 6B10, file offset 159ED
44Function cglGetExtentResult_: pointer 6B10, file offset 159ED
45Function cglGetConfig_: pointer 1F7C, file offset 10E59
46Function cglSetCursor_: pointer 686C, file offset 15749
47Function cglSetCursorPos_: pointer 67A0, file offset 1567D
48Function cglSetupInterrupt_: pointer 2360, file offset 1123D
49Function cglReleaseInterrupt_: pointer 23A8, file offset 11285
50Function cglBoardPresent_: pointer 22A4, file offset 11181
51Function cglQueryFeature_: pointer 6B3C, file offset 15A19
52Function cglEventRegister_: pointer 6BD0, file offset 15AAD
53Function cglEventDeregister_: pointer 6C44, file offset 15B21
54Number of functions 44

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda\
https://patreon.com/Rready

Reply 263 of 270, by sharangad

Posted on 2026-05-03, 21:51

sharangad Offline

Rank l33t

Rank: l33t
Posts: 2680
Joined: 2023-07-01, 11:02
Location: Colombo

The utility for dumping the CGL listings is available here:
https://nirvtek.com/downloads/CGLLOad.20260504.001.7z
MD5: 2135554607f137bb2f5ca0bb3f61a8b6

Run it with the CGL filename to dump contents
cglload <filename>

OR pass two filename for two files to compare
cgload <file1> <file2>

THe source is here. It's very rough and originally AI generated.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda\
https://patreon.com/Rready

Reply 264 of 270, by RaVeN-05

Posted on 2026-05-04, 13:04

RaVeN-05 Offline

Rank Oldbie

Rank: Oldbie
Posts: 1054
Joined: 2009-12-30, 13:32
Location: Ukraine

looks like 0 zero is always good sign, and later game crashes, so v2100 and probably v2200 soon of all are no go.
maybe v1000 non creative can work

https://www.youtube.com/user/whitemagicraven
https://go.twitch.tv/whitemagicraventv

Reply 265 of 270, by sharangad

Posted on 2026-05-04, 14:38

sharangad Offline

Rank l33t

Rank: l33t
Posts: 2680
Joined: 2023-07-01, 11:02
Location: Colombo

RaVeN-05 wrote on 2026-05-04, 13:04:

looks like 0 zero is always good sign, and later game crashes, so v2100 and probably v2200 soon of all are no go.
maybe v1000 non creative can work

It does look like it! Thanks RaVeN!

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda\
https://patreon.com/Rready

Reply 266 of 270, by sharangad

Posted on Yesterday, 16:00

sharangad Offline

Rank l33t

Rank: l33t
Posts: 2680
Joined: 2023-07-01, 11:02
Location: Colombo

RaVeN-05 wrote on 2026-05-04, 13:04:

looks like 0 zero is always good sign, and later game crashes, so v2100 and probably v2200 soon of all are no go.
maybe v1000 non creative can work

I plugged some of the cglQueryScreen code into an Ai. It seems to suggest that it's looking for a specific non-verité chip (conexant) , but it's probably wrong. The 3db pci is a bigger card than the v2100 I have (stealth ii s220) with more chips, though that might be due better integration on the newer card.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda\
https://patreon.com/Rready

Reply 267 of 270, by RaVeN-05

Posted on Yesterday, 20:18

RaVeN-05 Offline

Rank Oldbie

Rank: Oldbie
Posts: 1054
Joined: 2009-12-30, 13:32
Location: Ukraine

Tech process evolution?

https://www.youtube.com/user/whitemagicraven
https://go.twitch.tv/whitemagicraventv

Reply 268 of 270, by sharangad

Posted on Today, 02:35

sharangad Offline

Rank l33t

Rank: l33t
Posts: 2680
Joined: 2023-07-01, 11:02
Location: Colombo

RaVeN-05 wrote on Yesterday, 20:18:

Tech process evolution?

That's what I thought. It seems unlikely they put in a secret glint chip in there:)

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda\
https://patreon.com/Rready

Reply 269 of 270, by RaVeN-05

Posted on Today, 11:35

RaVeN-05 Offline

Rank Oldbie

Rank: Oldbie
Posts: 1054
Joined: 2009-12-30, 13:32
Location: Ukraine

so i need look closer to card, it could be GLINT at same board where Verite chip, or even unified? that was if true very ridiculous.

https://www.youtube.com/user/whitemagicraven
https://go.twitch.tv/whitemagicraventv

Reply 270 of 270, by sharangad

Posted on Today, 11:43

sharangad Offline

Rank l33t

Rank: l33t
Posts: 2680
Joined: 2023-07-01, 11:02
Location: Colombo

RaVeN-05 wrote on Today, 11:35:

so i need look closer to card, it could be GLINT at same board where Verite chip, or even unified? that was if true very ridiculous.

That's a pretty stupid idea. I tried to get DeepSeek to disassemble the functions from vritb170 with the offsets and it gave give complete and utter garbage. On manual inspection, It does look for 0x1163 (Creative/Rendition) and 0x001 (V1000) in a BIOS call int 1A from protected mode through the extenders Int 31 dispatcher. It could be looking for something in the ROM BIOS, something unique to the card. I'll look into this once I've got a basic wrapper working.

I had a few problems with that. The function offsets are correct, but for some reason Dosbox mangles the machine code for some instructions, various bytes at random offsets are corrupted. I don't know whether my patching is broken, ICR23 widescreen support is corrupting something OR dosbox's instruction parser (happens with every single type of core) is messing things up.

Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda\
https://patreon.com/Rready

Main menu