windows 98se behaves differently than win11
win98se changes irqs according to bios changes.
so they are the same in dos and win98se
unless of course they are not assigned in bios, than win98se assigns them of course.

My testing probably fried your hard drive. I don't think that's why the Rom bios dump failed.

If you could try @agentbsod's fix for f1. He says with the F1 drivers redline and verite in the F1 folder and v10003d.uc in windows/system F1 runs without the F1 wrapper. He also says you need verite. Vxd in the system folder. I believe the V2000 ref drivers already have that as an active driver.

Just give it a go. If it works there's yet another way to play F1 on V2000.

Need to be careful with your hardware. They don't make Verité boards anymore.

I remember one of those F1 wrapper tests took 6 hours.

Or you could relax 😀

Is regular rebel moon on rredline or cgl?

It was in your video of Rendition games.

Rebel Moon on Verite, speedy 3d, looks better than on rising engine.
Its just my very old hard drive.
All ok

Well I'm glad you got that sorted. I'll get you a fresh build tomorrow. There's something I need to test.

I don't know if I can call real mode software interrupts from dos32a. I found a link once which said it could through int31h. But I can't find any it anymore. Will persevere.I need protected mode to perform pokes into high address ranges.

[EDIT] Figured it out how to real mode calls from 32 bit protected mode.[/EDIT}

[EDIT] This is wrong. Ignore this. The ROM address has to be read through a BIOS call.

@Raven-05, here you go.

https://1drv.ms/u/s!As-dKk-N73dSmFFY1-qOeFqc8C_p?e=2AcR6E
MD5: 205896b3551b5f2276d4148d62737f02

Let's try dumping the BIOS again. Edit the run.bat file if you need to see console output. I've redirected it to a file. The ROM should be dumped again.

150th time lucky maybe.

This is a 32 bit app. Hope it works.

You can run it with run.bat. If you want to do it manually dos4gw fifo.

Fixed (h0pefull);

https://1drv.ms/u/s!As-dKk-N73dSmFIu_YsW43foCyda?e=Dyq71q
MD5: 8912f54a2a531fde5443c2fb7d2d3e6e

This should query the ROM extension address and dump it.

[EDIT] Same instructions as before [/EDIT]

002

1Rendition Segment 0000C000, Rendition Base 00000A2C
2Rendition ROM Address is 00000000
3Detected V2000 board
4Membase  : DE000000
5Portbase : D000
6RAM      : 4194304
7640x480/16 Mode Num is 0, granularity is 0 KB
8Error mode not found

001

1Rendition Segment 0000C000, Rendition Base 00000A2C
2Detected V2000 board
3Membase  : DE000000
4Portbase : D000
5RAM      : 4194304
6640x480/16 Mode Num is 0, granularity is 0 KB
7Error mode not found

Tested Formula1 with latest release, works ok, everything great.
Older FIFO's still produce 0xff or 0x00 filled files

Thanks. That real mode int 10h call from protected mode isn't working. I'll try and fix it. It gave me a lot of grief with dosbox but eventually managed to get it to work.

It's not working on real hardware.

i think you know pcem or 86box is a low level pc emulator where you can run dos as on real machine?
also i recall this https://github.com/86Box/86Box/discussions/1933 )

This won't work, but I need the output from it to see what's up:

https://1drv.ms/u/s!As-dKk-N73dSmFN4PsVdnAfo9QBz?e=TabOVe
MD5: a82a6dbbb9ec2c4b5a949d6515943fb9

RaVeN-05 wrote on 2024-03-17, 12:06:

i think you know pcem or 86box is a low level pc emulator where you can run dos as on real machine?
also i recall this https://github.com/86Box/86Box/discussions/1933 )

I am aware of pcem/86box. I have an installation on my machine with W98 at the moment. One of the guy(s?) working on it planned on adding Rendition emulation.

The BIOS address space for a ROM is 32 KB C000:000 C000:7FFF. The Rendition docs claims it has a 128 KB BIOS. It also says it's mapped into high address ranges.

But doesn't say which address range. There's a PCI register marked ROM extension, which is what I'm trying to read, but it's coming out as all 0s. By ROM extension do they mean an add on extra ROM or the built in ROM?

If we succeed at Speedy3D maybe the PCem/86Box team will get free Rendition support running native drivers. (y)

You only one working on Rendition support for now

For now.

Bit beat. Need to get some sleep. WIll probably get back to it sometime tomorow.

You have plenty of time to run fifogw3 before then.😀

RaVeN-05 wrote on 2024-03-16, 17:57:

Rebel Moon on Verite, speedy 3d, looks better than on rising engine.

rising engine works in 1600x1200

verite has texture filtering and colored lightning, other graphics effects)
!no matter! i like verite more , period dot dot !DOT!
______________________________________________________
no comments anymore.
__________________
i really tired and live in war.
_____________________
Keep good mood here, there is not right topic to discuss best ever rebel moon version!
___________________________

@sharangad under windows its creates fifo.txt , under dos its hangups after standard messages of dos4gw.

1Rendition Segment 0000C000, Rendition Base 00000A2C
2ROM port 00
3ROM port 00
4ROM port 00
5ROM port 00
6Rendition ROM Address is 00000000
7Successfuly read VESA block
8Signature:"VESA"
9Version:200
10OEM name:"9Qt
11f9AuìÀtèZ[Ã"
12Capabilties:0002
13RAM: 4096 (KB) (4.000000 MB)
14oemVersion: 00
15Vendor:"Null"
16Product:"Null"
17Revision:"Null"
18Accelerator Caps: 00
19Supported VESA & OEM modes :023f:c00046f5
20
21Supported VESA (Accelerated) modes :023f:00000000
22F9E,C9,465,70,16,60B,465,70,465,70,FF54,F000,8008,F000,E7FF,F000,00,D000,28,60B,EF6F,F000,EF6F,F000,EF6F,F000,EF6F,F000,9A,60B,465,70,07,D070,F84D,F000,F841,F000,24D7,FD64,E739,F000,7273,10BC,42D,70,A28,375,E7A4,F000,2F,6CC,FE6E,F000,1168,10BC,1D,D000,F0A4,F000,522,00,58B2,C000,FA8,C9,445,7B8,314,A15,1188,10BC,118C,10BC,FBC,C9,FC6,C9,FD0,C9,106C,C9,466,70,5B4,375,106C,C9,106C,C9,106C,C9,162,A15,1CC,A16,E4EA,C90F,E700,F000,106C,C9,01,896,106C,C9,106C,C9,106C,C9,106C,C9,106C,C9,106C,C9,106C,C9,106C,C9,106C,C9,106C,C9,106C,C9,106C,C9,EC59,F000,EFD5,F000,F065,F000,5CB2,C000,E7FF,F000,E7FF,F000,EFE5,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,2637,FD4E,E7FF,F000,E7FF,F000,E7FF,F000,4FC,70,EF6F,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,0D,8A3,E7FF,F000,E7FF,F000,E7FF,F000,00,00,00,00,00,00,00,00,00,00,00,00,00,00,40,897,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,E7FF,F000,5DE,C000,E7FF,F000,E7FF,F000,35,60B,ECF3,F000,EF6F,F000,EF6F,F000,E2,60B,F0FC,F000,FA,60B,112,60B,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,22,2EB7,FCC6,202,
23Detected V2000 board
24Membase  : DE000000
25Portbase : D000
26RAM      : 4194304
27640x480/16 Mode Num is 0, granularity is 0 KB
28Error mode not found

OK. I see the problem. Let me see if I can fix it.

BTW you've done a lot pushing for Rendition support. Let's hope we can get Speedy3d running soon.

Dos allocated pointers don't seem to be accessible in protected mode.

sharangad, isn't this the bios you are trying to get?
Re: Rendition Verite Thread