One final attempt before I call it quits for tonight:

https://1drv.ms/u/s!As-dKk-N73dSln0Mo-Zu9Ad0nTvO
MD5: af9b66500c0ca64445c356b63a69e5b3

And one more:

https://1drv.ms/u/s!As-dKk-N73dSln4Mo-Zu9Ad0nTvO
MD5: 1519851605218ba2b9967dd0e0e64924

Version 002 and 003 hang at the same place. Version 002 is behaves the same, but version 003 has wrong text textures in the pre-race screen but not in the credits. In the pre-race screen, the top half of the text is fine, but the bottom half is the alphabet texture, or the texture of digit numbers. In the credits, text and the Bizzare Creation textures are fine with version 003 (I didn't wait for the Psygnosis texture to appear). Maybe it's pre-made images and not actual text in the credits.

In the logs, I didn't run the credits with version 003.

Try this:

https://1drv.ms/u/s!As-dKk-N73dSlwAMo-Zu9Ad0nTvO
MD5: 971fa7785a3869eede325f6e2c46e2b8

The textures should look ok again in the menu and pre-race screens.

There's a dll function (imported by ID instead of name), which was previously fudged. Now it's handled correctly. I'm not entirely convinced this will work.

This time the pre-race screen looks fine (it wasn't in 11-16-003), but the menu and the credits don't display right. I took screenshots. The game still hangs after the pre-race screen. Screenshots have the same resolution, I don't know why vogons shows one bigger.
I put 3 logs, 1 with the game hanging after the pre-race, 1 going to the credits and back to the menu and quitting, and 1 just starting the game and quitting from the menu.

I think there's a version number mismatch copying the files across:
Check the timestamps and possibly the MD5s.

This should still lockup, but menus and everything else should render correctly:

https://1drv.ms/u/s!As-dKk-N73dSlwEMo-Zu9Ad0nTvO
MD5: eaad2f4734ca15c8955f406a38588c03

Verite.dll MD5: 129ff20a822db6da63458ffd870283be
Redline.dll MD5: 8e14542687f16402eee02d8294961e62

Timestamps at my end: 18 Nov-23 13:51 (GMT + 0530). Your timestamps may differ.

With this version the menus, the credits and the pre-race screen look fine. The game still hangs after the pre-race screen.

I checked the md5 of versions 11-18.001 and 11-18.002 on the test computer in Windows ME and they are what you posted. I tried again version 001 and it still has the same issue as previously. When going from 001 to 002, dates are these (I'm in GMT+1):
verite.dll 2023-11-18 4:55:07 -> 9:21:14
redline.dll 2023-11-18 5:00:04 -> 9:21:06

chuky wrote on 2023-11-18, 17:32:

With this version the menus, the credits and the pre-race screen look fine. The game still hangs after the pre-race screen. […]
Show full quote

With this version the menus, the credits and the pre-race screen look fine. The game still hangs after the pre-race screen.

I checked the md5 of versions 11-18.001 and 11-18.002 on the test computer in Windows ME and they are what you posted. I tried again version 001 and it still has the same issue as previously. When going from 001 to 002, dates are these (I'm in GMT+1):
verite.dll 2023-11-18 4:55:07 -> 9:21:14
redline.dll 2023-11-18 5:00:04 -> 9:21:06

BTW, the black streak in the end credits, some polygons darkening, is there in the actual game. There's a dark shimmer across the image.

One final attempt before I call it quits:

https://1drv.ms/u/s!As-dKk-N73dSlwoMo-Zu9Ad0nTvO
MD5: f8b73745f7bca6035bffc25e466eb588

This no longer preserves stack stack on entry to calls. I *don't* think this will make much of a difference , other than maybe introducing new bugs. It will once and for all eliminate the possibility that wrapper code is messing things up. Or it could fail completely.

The program crashes when I try to start it. The Verite log file is created and empty, but the Redline log file is not created.

I get a message like this one:
Application error C:\PROGRAM FILES\FORMULA1\F1RED.EXE
The instruction at 00409e9f referenced memory at 02c33fb8
The memory could not be written
Click on OK to terminate the application

chuky wrote on 2023-11-28, 13:13:

The program crashes when I try to start it. The Verite log file is created and empty, but the Redline log file is not created. […]
Show full quote

The program crashes when I try to start it. The Verite log file is created and empty, but the Redline log file is not created.

I get a message like this one:
Application error C:\PROGRAM FILES\FORMULA1\F1RED.EXE
The instruction at 00409e9f referenced memory at 02c33fb8
The memory could not be written
Click on OK to terminate the application

Yikes! Sorry. I guess that was a bad idea.

Someone try this with F1 and a V2k board.

https://1drv.ms/u/s!As-dKk-N73dSlzwMo-Zu9Ad0nTvO
MD5: 0dfbfcfec701ac00a143a6a136916987

Waited 16 seconds , demo gameplay starts, it shows loading screen, music starts, loading screen fade out to black, black screen and music plays, nothing happening.

Wasn't there a hard lock up before or us this the same as before?

See whether this makes things better or worse:

https://1drv.ms/u/s!As-dKk-N73dSlz8Mo-Zu9Ad0nTvO
MD5: abd1606353899e5ba36d409c9871cff3

It looks to be an issue with the callback function, which is never called by the menu or the credits screens.

[EDIT] I use a placeholder because the calling convention is different. At least that's what RReady does. I think this needs something slightly different.

Can you also run just the credits, then quit? Attach the logs.

logs with new build, (last, current)
tried to start Quick Race , heard announcer, no music, black screen just after loading, before even race starts black screen where should be 3d scene
will try credits

Could you try the credits with the previous build?

where is credits? i found checkered flag weaving (this seems from polygons)
tried to navigate menu seems works, ofc very slow, can you make builds with logging disabled also along with logging too? maybe its so slow even single 3d scene frame can't be rendered . The 16 seconds in main menu tics very slow like one in game sec is actually 45 real world seconds.

Will try previous build with checkered flag