openMSX bugs

Page 2/13
1 | | 3 | 4 | 5 | 6 | 7

Par Metalion

Paragon (1444)

Portrait de Metalion

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.

Par Parn

Hero (652)

Portrait de Parn

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.

Par Manuel

Ascended (18161)

Portrait de Manuel

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.

Par Metalion

Paragon (1444)

Portrait de Metalion

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

Par Sylvester

Hero (537)

Portrait de Sylvester

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 ?

Par Bodhi1969

Expert (89)

Portrait de Bodhi1969

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.

Par ren

Paragon (1876)

Portrait de ren

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 (é).

Par Metalion

Paragon (1444)

Portrait de Metalion

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.

Par Manuel

Ascended (18161)

Portrait de Manuel

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?

Par Bodhi1969

Expert (89)

Portrait de Bodhi1969

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?

Page 2/13
1 | | 3 | 4 | 5 | 6 | 7