openMSX bugs

Hero (657)

22-08-2020, 05:36

So, some bugs already...

Downloaded the last one build from here:
https://openmsx.fixato.net/builds/windows/x64/openmsx-0.15.0...

It did NOT installed catapult at all.

So I had to download this one in order to recovery catapult:
https://openmsx.fixato.net/builds/windows/x64/openmsx-0.15.0...

After the install, I'm getting build version error now:

By Gradius2

Hero (657)

22-08-2020, 05:45

Btw, I have VS2019 v16.7.2 installed on my PC.

https://docs.microsoft.com/en-us/visualstudio/releases/2019/...

Update...

After researching I found out build 1926 is from Visual Studio 2019 version 16.6.

PLEASE, update it!

By Gradius2

Hero (657)

22-08-2020, 06:09

Catapult.exe from 24/07/2020 build 892 works.

SHA1: 6DB472272ED1B17FA286435F58D56E54DB411F94

By Manuel

Ascended (19678)

22-08-2020, 22:32

The build has a problem indeed, the version of the wx library we use is very pedantic about the library having been compiled with exactly the same compiler as the application. And at some point, apparently the compiler was upgraded indeed for the build of Catapult, but the library build was not redone.

It's not a bug in openMSX, it's not a bug in Catapult, it's a 'configuration" problem of the Catapult build on the Windows build server we use.

By Manuel

Ascended (19678)

27-08-2020, 21:20

This issue should be fixed with the latest builds and the openMSX 16.0 release.

By Metalion

Paragon (1628)

28-09-2020, 13:37

Hello,

I downloaded the 16.0 release and got that error when launching a rom :

By Manuel

Ascended (19678)

28-09-2020, 21:06

Which ROM file name is it? Does it have special characters?

The error is: No mapping for the Unicode character exists in the target multi-byte code page.

By Metalion

Paragon (1628)

29-09-2020, 10:01

Manuel wrote:

Which ROM file name is it? Does it have special characters?
The error is: No mapping for the Unicode character exists in the target multi-byte code page.

The name of the rom is 'test_sfx.rom'.
The path does contain a 'é' character, but I never had problem with earlier version of OpenMSX.
Same remark about '_'.

By Manuel

Ascended (19678)

30-09-2020, 00:05

Very strange, i have never heard about this problem. Can you confirm it is that character in the path causing the issue?

Any other people who have this problem?

Can you confirm the problem is not there with 0.15.0, our previous release?

By Metalion

Paragon (1628)

30-09-2020, 13:27

Manuel wrote:

Very strange, i have never heard about this problem. Can you confirm it is that character in the path causing the issue?

It's not the path: I put a copy of it in the OpenMSX directory and got the same error.
It's not the name: I renamed it to "testsfx.rom" and got the same error.

I thought it was related to the rom size, because it was a bit unorthodox.
So I made it right, and it's a 16K rom. But still the same error.

I will check with 0.15 version, but I need to download it again first.

EDIT : It must be something else, because I have the same error with ALL my roms, even with standard Konami ones. Not a single rom file is working at all.

By Manuel

Ascended (19678)

30-09-2020, 17:55

It could be originating from another file than the particular ROM you're loading.

Can you start up without any ROM?