VOGONS


Reply 560 of 1740, by Agent of the BSoD

User metadata
Rank Member
Rank
Member

Here's mine on your latest one.

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

Reply 561 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

Thanks agent.

Apart from the WinPosFunc* and some reserved mask changes everything's identical (except for modes supported only by V2000, which are missing).

*VGA boards back in the 90s under real mode only allowed access to 64 KB of VRAM at a time. This was know as the current page. By using the WinPosFunc (or by writing to manufacturer/model specific registers on the board, the page could be changed in 64 KB offsets to access any part of VRAM. At that point most newer boards supported linear addressing (in 32-bit protected mode), where the whole of VRAM could be directly accessed at a higher 32 bit memory location eliminated paging.

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

Reply 562 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

Oh and the detailed mode list for the V1000 in case anyone would like to take a peek.

The winpos func is different on the V2000 and V1000 because the BIOS location where the function lives is different on the two board.

I think @Demonized999's Mirvo V1k which has somewhat different BIOS (non-reference) BIOS will have also have a very different location for this.

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

Reply 563 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

Yet another test:
https://1drv.ms/u/s!As-dKk-N73dSmCBa69zZWGx-1Rq4?e=NPU4NO
MD5: d7d4fb050e75914c99e891c4518166cd

This should hopefully reset the Rendition board. I only need SetMode.txt. The *.bin files are unnecessary.

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

Reply 564 of 1740, by Agent of the BSoD

User metadata
Rank Member
Rank
Member

After this finished, the text on screen underwent corruption. DOS was still usable but I couldn't read anything. Also seems to have changed the resolution to 640x480. Guess that's a result of resetting the card. A dir command looks like this.

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

Reply 565 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

Oh wow!

Well at least that worked. I think I need to do a set mode to mode 3 or something.

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

Reply 566 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

DMATest now produces:
D:\DMA>dmatest
DOS/4GW Protected Mode Run-time Version 1.97
Copyright (c) Rational Systems, Inc. 1990-1994
Microcode load failed
Failed to access Verite board, error code 0x270a06.
Errors have been found.

But there're port reads now. Expect another SetMode shortly.

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

Reply 567 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

This carries out the first step in loading the microcode. It won't actually load anything. Just a tentative register read.

It also just *might* switch back to a standard resolution.

https://1drv.ms/u/s!As-dKk-N73dSmCH7UCVmHZcKUFuM?e=zoTb1c
MD5: 0da04dbb3ec6977480a8046d687eacef

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

Reply 568 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

The register it's reading is actually the VESA mode reigster internal to the chip.

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

Reply 570 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

https://1drv.ms/u/s!As-dKk-N73dSmCLyu7y_AW4HIdra?e=UeCTa8
MD5: 06963258ab7f3887278d4c2d049e1924

I've put it into mode 3, which is allegedly the default 80x25 DOS mode. I guess it's not the right mode.

Rendition DMATest now failed with RISCStart failed.

So get me the results of this binary, please.

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

Reply 572 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

I actually made a mistake there es:Di probably points to the firmware in RAM. Will load the firmware into ram and try again. I'll be delayed for around 30 mins.

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

Reply 573 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

OK, ES:DI is duff, it's actually poking it into VRAM.

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

Reply 574 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

I seem to have hit an impasse.

I can't upload the firmware into RAM without going into protected mode.

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

Reply 575 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

https://1drv.ms/u/s!As-dKk-N73dSmCQKZaFXarpHrm28?e=yTZCB6
MD5: e32da5823234cd3c370c753d32e1ba5e

This won't upload the firmware, but it should allow me to read the register values for success (I hope).

Last edited by sharangad on 2024-03-06, 12:16. Edited 1 time in total.

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

Reply 576 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

The current state of DMA Test is:
D:\DMA>dmatest
DOS/4GW Protected Mode Run-time Version 1.97
Copyright (c) Rational Systems, Inc. 1990-1994
Microcode not responding
Failed to access Verite board, error code 0x2708.
Errors have been found.

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

Reply 577 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

Microcode not responding is because register reads from ports 43, 42, 41, 44 are 0 (in DOSBox-Rendition)after poking the microcode into RAM. It actually runs around a loop reading this and gives up after a while.

Actual hardware will return something different.

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

Reply 578 of 1740, by sharangad

User metadata
Rank Oldbie
Rank
Oldbie

These ports appear to be:

0x40 0x20040 FIFOInFree Free entries in RISC input FIFO (b4:b0). Byte register. Read only.
0x41 0x20041 FIFOOutValid Valid entries (b2:b0) for RISC output FIFO. Byte register. Read only.
0x42 0x20042 Comm Communication register between host and RISC. Byte register. Read/write.
0x43 0x20043 MemEndian Select byte swapping on memory accesses. Byte register. Read/write.
0x44 0x20044 Intr Interrupt register. 16-bit register. Read/write

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