demonized999 wrote on 2024-01-10, 12:24:

Do you still need something to be run on V1000?
I have miroCrystal VRX here.

This

Could you try this as well? (On a single card)

https://1drv.ms/u/s!As-dKk-N73dSlw8Mo-Zu9Ad0nTvO
MD5: 4cd999b10c26e7293cecfa7c2280da8f

I need the redirected console output and the other txt file it creates. I'll also need a dump of your video bios (segment c000:0000). It has to be the bios the test app ran against.

[EDIT] I haven't got any results from a V1000 yet.

Sorry - I had some other stuff to finish yesterday 😀
Here are the results attached alongside the video BIOS of the card

Thanks demonised.

The V1000 is the same as the V2100 and V2200.

The specific address is different because it has a different bios location for the id string.

That's good I suppose?

Yes it is. That pretty much guarantees the address returned always points to a some sort of identifier and some other data in the BIOS terminated by a 'y' character.

Now it's a matter of seeing what this data is used for. So far all I know is it counts how many characters there are until it hits the 'y'.

vQuake uses paging to access the BIOS using a different address, that threw me off for a while. But even there it searching a a 'y' character and counting.

In all the Verite BIOSs I've looked at at the returned address there're a couple of bytes followed by "Rendition Reference Board" more bytes, some of which could be strings. The boards I've looked at a Steal II, nameless V2200, and your MIRO V1000 all return a pointer to that block in the BIOS as an offset in register CX and a segment in DX.

It's what gets done with afterwards that doesn't make any sense either that or my assembler is really really terrible (probably is).

Was it tested with Indycar Racing 2 W95 build? people at the icr2 community would jump in sheer happiness if this is working on it.

Win95 build? Is that rredline?

If it is I was unaware of that.

Will test and see. If it isn't rredline speedy3d support is needed and that's nowhere near ready yet.

My large text file viewer is almost done. Should be able to jump right back into working on dos support.

sharangad wrote on 2024-01-30, 01:10:

Win95 build? Is that rredline? […]
Show full quote

Win95 build? Is that rredline?

If it is I was unaware of that.

Will test and see. If it isn't rredline speedy3d support is needed and that's nowhere near ready yet.

My large text file viewer is almost done. Should be able to jump right back into working on dos support.

race sim central guys have more info on it
https://racesimcentral.net/indycar-racing-ii- … ion-experience/

Deffnator wrote on 2024-01-30, 12:54:

sharangad wrote on 2024-01-30, 01:10:

Win95 build? Is that rredline? […]
Show full quote

Win95 build? Is that rredline?

If it is I was unaware of that.

Will test and see. If it isn't rredline speedy3d support is needed and that's nowhere near ready yet.

My large text file viewer is almost done. Should be able to jump right back into working on dos support.

race sim central guys have more info on it
https://racesimcentral.net/indycar-racing-ii- … ion-experience/

I *think* that's the DOS version that has Rendition support. If there's a Windows version with Rendition (RRedline on Windows) then the game would already be running.

sharangad wrote on 2024-01-30, 13:01:

Deffnator wrote on 2024-01-30, 12:54:

sharangad wrote on 2024-01-30, 01:10:

Win95 build? Is that rredline? […]
Show full quote

Win95 build? Is that rredline?

If it is I was unaware of that.

Will test and see. If it isn't rredline speedy3d support is needed and that's nowhere near ready yet.

My large text file viewer is almost done. Should be able to jump right back into working on dos support.

race sim central guys have more info on it
https://racesimcentral.net/indycar-racing-ii- … ion-experience/

I *think* that's the DOS version that has Rendition support. If there's a Windows version with Rendition (RRedline on Windows) then the game would already be running.

There's no RRedline IndyCar Racing 2

The quest for DOS support will resume soon.

Back on the job:

I just realised SetMode left out a critical bit of info. The stack pointer. This is critical because I don't know whether any extra parameters were passed on the stack:

https://1drv.ms/u/s!As-dKk-N73dSlzcMo-Zu9Ad0nTvO
MD5: 5371fed7181333a8abe948069c7d91a3

V1000/V2000. What I really need is the console output from the app.

Thanks guys.

Haven't watched this thread in a little bit. Here's results from the last post. Let me know if you need me to run any of the earlier ones.

V1000

Thanks @Agent of the BSoD.

That's al I need, for now.

V2200
Say please if v2100 needed also?

RaVeN-05 wrote on 2024-02-09, 13:23:

V2200
Say please if v2100 needed also?

No. This should be enough. Thanks Raven.

Once more with feeling:

https://1drv.ms/u/s!As-dKk-N73dSlzsMo-Zu9Ad0nTvO
MD5: eb772a4a880b99942b3c58b04fc67cff

[EDIT]. SetMode again.

on v2200

Thanks Raven.