The executable files of the two last nightly builds will not run

[BridgeHeadland]

Describe the bug

I do say the two last, because I tried both "Merge pull request #5417 from xrip/patch-1", "cleanup" and "Make an alternate API to access memory by physical address, not linea...", where the last one I mentioned came before the other two, and the last mentioned is so far the last nightly build where the executable actually works, So something must have happened during the development of "cleanup".

Steps to reproduce the behaviour

Download the last two nightly builds, feel free to try all workflows of each of the two nightly builds if possible, install one build, launch the executable file and see if it will run, which it doesn't, do the same with the other nightly build and see the result.

Expected behavior

I expect the executable file to work. :)

What operating system(s) this bug have occurred on?

Windows 11 Pro 24H2

What version(s) of DOSBox-X have this bug?

The last two nightly buildings. All of the MinGW and Visual Studio workflows for the latest Windows are the ones I've tried, probably it applies all of them.

Used configuration

Output log

Additional information

No response

Have you checked that no similar bug report(s) exist?

• I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

• I agree to follow the code of conduct and the contributing guidelines.

[joncampbell123]

Please clarify how it "doesn't work".

Does it abort immediately? Does it E_Exit() with a message? Does Windows claim it lacks a dependency? Does it steal your credit card and go on a shopping spree? What does it do to "not work"?

[BridgeHeadland]

More like the former. The DOSBox-X window opens and closes itself before it is about to start properly.

[joncampbell123]

More like the former. The DOSBox-X window opens and closes itself before it is about to start properly.

Got it. Whatever it is doesn't affect my Linux dev system but does affect Windows.

[BridgeHeadland]

I have now set the configuration to default settings, DOSBox-X starts, and these things happens.

[joncampbell123]

I recently committed code that should fix that weirdness for Windows builds. At least on my machine I was able to restore normal functionality, by compiling from Visual Studio. Not sure about MinGW.