To copy files you make cd isos or you edit the hd image directly, if it works.

With the DLLs from Formula1.RedlineVerite.20231016.002 stuck in the F1 folder and redline.dll and verite.dll from the heavy gear driver stuck in Windows\system on
a Win98SE system (without a Rendition board) I get this:
Is the Windows\system folder called something else in French? I use the GetSystemDirectory call to get it, so it's not hardcoded and should work everywhere..

The sequence I get makes sense. V_EnumVeriteBoards fails because I haven't got a Verite board so the app shuts down.

The name is the same in french. I'll check in PCem later to see what happens.

chuky wrote on 2023-10-17, 09:48:

The name is the same in french. I'll check in PCem later to see what happens.

You had a win95 osr 2 box 2 days ago and today you have a win 98 machine.
[edit]
Could've sworn you said you had w98 box.

You dual booting? 95b and win98 shouldn't make a difference.

I had Windows 95 on the computer, then I upgraded it to Windows 98.

In Pcem it logs fine with the same Windows 95 and the same Rendition Vérité dlls that I had. I guess I'll have to format and reinstall.

I did more tests. I formatted and installed Windows 98 SE and the wrapper still isn't logging the results.

Then I removed the Rendition V2100 and put an S3 Virge instead, without installing any driver, and the wrapper logs the results.

Logs with the S3 Virge and version 2023-10-17.003 say:
V2K.RReady.Redline.txt

1Loaded system\redline.DLL library
2VL_OpenVerite_

V2K.RReady.Verite.txt (it doesn't say it loads verite.dll)

1V_EnumVeriteBoards
2Callng base function

But it's with the S3 Virge.

I tried putting the Rendition Vérité in a different pci slot and it was the same, logs were empty.
I tried reinstalling the same driver version but overwriting mfc42.dll and msvcrt.dll (I was keeping my files before) and it was the same. When the driver installs, it says these 2 files are older in the driver than what I have and it's recommended to keep them. So it's the same if I keep them or overwrite them.
I tried using just system\verite.dll and system\redline.dll from another driver, version 110 instead of 106, but it was the same. Actually version 110 can't install because it looks for french files, so I installed version 106. I also had version 106 before, when Windows 95 and 98 were installed before I formatted and reinstalled everything.
I tried using reference drivers for the V2x00 but it was the same. I tried versions 2.3 and 3.0 beta5. The readme says it's for the V2x00 but the driver itself calls the card a V2200 with it (while it's a V2100).

I think I'll try compiling the older version that output logs. Maybe I'll have more ideas for tests in the meantime.

edit: Here's where I got my drivers:
Diamond s220
http://www.vogonsdrivers.com/getfile.php?fileid=321
Reference Drivers
http://www.vogonsdrivers.com/getfile.php?fileid=1537

edit2: the bios is version 1.31 while 1.35 and 1.36 are available in this driver.

I think the logging actually screws things up. I'll get you another build sometime today with some tweaks.

I'm also preserving registers, that could have something to do with it. With RReady, some functions don't like it.

Would be handy if you could debug it. It could also be that the log file isn't being flushed before crashing.

Today's build:
(Now with log flushing)
DLLs: https://1drv.ms/u/s!As-dKk-N73dSljMZNyuV2p_4eBap?e=Xk2gKC
MD5: 741e37373936125aae8dcd24fb50ab2b

Source:
https://1drv.ms/u/s!As-dKk-N73dSljQuHjcnxzfqP402?e=GRMWO8
MD5: 0678edf8b55a0ac377cae3950b19a987

It'll be interesting to see if this produces anything. You may get a warning popup about a missing logging function, just click OK and it'll continue OR you might not.

This version puts things in the logs. There's a crash message and reports from Windows but no other message.

V2k.RReady.Redline.txt

12023/10/18 06:24:12.720 Started logging

V2k.RReady.Verite.txt

12023/10/18 06:24:12.720 Started logging
206:24:12.770 Loaded system\Verite.dll library
306:24:12.770 V_EnumVeriteBoards
406:24:12.770 Calling base function
506:24:12.940 V_CreateCmdBuffer entry

chuky wrote on 2023-10-18, 04:34:

This version puts things in the logs. There's a crash message and reports from Windows but no other message. […]
Show full quote

This version puts things in the logs. There's a crash message and reports from Windows but no other message.

V2k.RReady.Redline.txt

Copy code to clipboard

12023/10/18 06:24:12.720 Started logging

V2k.RReady.Verite.txt

Copy code to clipboard

12023/10/18 06:24:12.720 Started logging
206:24:12.770 Loaded system\Verite.dll library
306:24:12.770 V_EnumVeriteBoards
406:24:12.770 Calling base function
506:24:12.940 V_CreateCmdBuffer entry

So it looks like it crashed while creating the command buffer.

sharangad wrote on 2023-10-18, 06:33:

chuky wrote on 2023-10-18, 04:34:

This version puts things in the logs. There's a crash message and reports from Windows but no other message. […]
Show full quote

This version puts things in the logs. There's a crash message and reports from Windows but no other message.

V2k.RReady.Redline.txt

Copy code to clipboard

12023/10/18 06:24:12.720 Started logging

V2k.RReady.Verite.txt

Copy code to clipboard

12023/10/18 06:24:12.720 Started logging
206:24:12.770 Loaded system\Verite.dll library
306:24:12.770 V_EnumVeriteBoards
406:24:12.770 Calling base function
506:24:12.940 V_CreateCmdBuffer entry

So it looks like it crashed while creating the command buffer.

This should hopefully crash somewhere else. In the unlikely event it does actually run it'll be slow because of the logging.

Binaries:
https://1drv.ms/u/s!As-dKk-N73dSljazekC0fcldViCC?e=fNY7TC
MD5: b8d1370f339d1634e68856c343702d62

Source:
https://1drv.ms/u/s!As-dKk-N73dSljXyYh2h_ISXu--P?e=0qZ6sk
MD5: fe4a88dd4b21bf203b88c83c6e5bb445

I use Win98 + Rendition Verite v2200 4mb agp, unnamed card 1999
i see startup screen , loading screen, then music plays and crash.

RaVeN-05 wrote on 2023-10-18, 15:13:

I use Win98 + Rendition Verite v2200 4mb agp, unnamed card 1999
i see startup screen , loading screen, then music plays and crash.

Try this:
https://1drv.ms/u/s!As-dKk-N73dSljekm22Td2Ns6qxL?e=cbSd4d
MD5: d3938cb9615517851e9905bc37f087ed

See how far it gets.

visually the same (archive have f1red.exe and verite.dll) and both are not new comparing to what i have tested before, files exactly the same.

RaVeN-05 wrote on 2023-10-18, 15:54:

visually the same (archive have f1red.exe and verite.dll) and both are not new comparing to what i have tested before, files exactly the same.

Oops! That's a mistake, there was supposed to be an updated redline.dll.

Try this:
https://1drv.ms/u/s!As-dKk-N73dSljgb0TwAC0-up3cz?e=Fbd3r8
MD5: ac7e6d796c32bf4f77d4552a19d58432

Source:
https://1drv.ms/u/s!As-dKk-N73dSljkEJSLJVKKkKKZk?e=6bZZBW
MD5: 435fbb670a5ccc69773d9a4281b429b9

i can't provide logs, they are zero size.
can you make logging by every line to be saved? for once (i know horrible for harddrive)

there is good progress now i can see main menu, and loading demo screen, after black screen and it hangs.

I tested version 002 and 003.corrected. I'm joining the logs for the version 003.corrected.

Both versions stay in 1024*768, instead of switching to 640*480 I guess. It alternates 1 frame is the loading picture, 1 frame is something in memory, then the loading picture, then the frame in memory. When it finishes loading, instead of showing the game main menu, a message box appears but I can't read it because it's behind the game. When I press Enter the game quits. Logs don't seem to grow if I wait before pressing Enter.

I recorded a video in 60 fps. If you watch it in 60 fps and pause you can see frames alternate. I also launched the direct3d version for a comparison. I didn't record sound but there's no sound while loading, the only sound I had was in the menu when going up and down to quit.
https://www.youtube.com/watch?v=_oXAZEx2l2s

I want to say now after trying different drivers and installing a driver for the usb that wasn't made for the french windows, now I can't open the Windows display options to change resolution, and some minor issues like some Windows text is in english now. So I can't try what happens if the desktop is in 640*480 and the game doesn't have to switch resolution.

The log file should be flushed every single time, it was already like that for rendition.log, verite.log should be dead now, it's output redirected to rendition.log. There should be something in the file.

https://1drv.ms/u/s!As-dKk-N73dSljp7fXs3mzswhdQ-?e=At3ppW
MD5: 70473538a6012cf9b935fd4f509ae379

Source:
https://1drv.ms/u/s!As-dKk-N73dSljvMK0vip4FNrFao?e=m4VvhO
MD5: 5d71dda266debb976f3da77e465e789b

Raven are you also stuck in 1024x768? Chuky, these two lines should switch to 640x480. Not entirely sure why it's not working.

18:27:19.960 V_SetDisplayType_
18:27:20.010 V_SetDisplayMode_
The first sets the display type to (fullscreen)
The second (x-res, y-Res, refresh rate)

The reason the frames alternate is because the resolution switch fails. Vl_setsrcbase uses the wrong screen buffer address, depends on on x-resXy-resxbytes per pixel, when drawing the texture.

If logging doesn't show up with last version, this should definitely log something:

https://1drv.ms/u/s!As-dKk-N73dSljyF9KvFvKD8C12W?e=fAFP5g
MD5: 18e358bd36712f375ee3193c6f97a504

Source:
https://1drv.ms/u/s!As-dKk-N73dSlj0Ytw6aBAu0JwP_?e=hJvNjs
MD5: 004cf1f276efaeb92234e60b68494eb4