openMSX bugs | MSX Resource Center (Страница 2/15)

Paragon (1625)

30-09-2020, 18:14

Manuel wrote:

Can you start up without any ROM?

No, as I wrote in my previous message : no other ROM is starting either.
They ALL give me the same error message.

Maybe my installation was wrong ?
I did a zip-file download (not the installer).
Deleted the old version directories and content, and replaced them with the v16.

I'll try to reinstall again OpenMSX.

By Parn

Paladin (837)

30-09-2020, 20:27

Manuel meant you try without selecting any ROMs, just to see if the MSX machine boots. Perhaps you could also try a different machine as well.

By Manuel

Ascended (19469)

30-09-2020, 23:26

Yes, exactly that. Until someone else speaks up who suffers from this, I need you to dive into this, Metalion! I hope you're willing to help to solve this issue.

By Metalion

Paragon (1625)

01-10-2020, 10:03

OK, no problem.
Sorry for misunderstanding.

Without rom: same error
Without rom, C-BIOS MSX2 machine: same error
Without rom, C-BIOS MSX1 EU machine: same error
Starting without rom, without Catapult: same error

By Sylvester

Hero (589)

01-10-2020, 10:24

Maybe the issue is the directory where openMSX is located, the Privé part , what if you start openmsx from c:\OpenMSX ?

By Bodhi1969

Expert (93)

01-10-2020, 12:10

Sylvester wrote:

Maybe the issue is the directory where openMSX is located, the Privé part , what if you start openmsx from c:\OpenMSX ?

Well, Metalion stated that it is neither the path nor the filename. The file name with the accent could be a possible source for this error, indeed.

By ren

Paragon (1934)

01-10-2020, 12:33

I tested, definitely related to the é in the executable path.

I didn't have issues running a ROM from a path containing an extended ASCII char (é).

By Metalion

Paragon (1625)

01-10-2020, 13:26

OK, so I changed the directory {Privé} in the OpenMSX path to {Prive}.
Everything works now.

But it was working with {Privé} with OpenMSX 0.15, so somehow it's a loss of functionality.

By Manuel

Ascended (19469)

01-10-2020, 13:34

OK, thanks for making that clear. I'll think what the next step should be. Probably finding out where this error originates from in the code and then finding out why it's now an issue and it wasn't with 0.15.0.

I will probably make a MinGW build of openMSX.exe, which I will need you to verify whether it's giving the same issue. If yes, then I can give you another MiNGW build with some extra logging to figure out where the error originates in the code.

Is that OK?

By Bodhi1969

Expert (93)

01-10-2020, 13:53

ren wrote:

I tested, definitely related to the é in the executable path.

I didn't have issues running a ROM from a path containing an extended ASCII char (é).

And you also use 0.16, as Metalion does?