openMSX bugs | MSX Resource Center (Página 5/15)

Por Manuel

Ascended (19468)

06-10-2020, 21:35

Metalion: are you sure that isn't a typo somewhere? Catapult gives this if the file doesn't exist...

Please try with that debug version, from Catapult or directly, doesn't matter.

Por Metalion

Paragon (1625)

07-10-2020, 14:02

Manuel wrote:

Metalion: are you sure that isn't a typo somewhere? Catapult gives this if the file doesn't exist...

Yes it was a path error, sorry about that.

Manuel wrote:

Please try with that debug version, from Catapult or directly, doesn't matter.

I did ... I thought it would give more data about the bug

Por Manuel

Ascended (19468)

07-10-2020, 16:53

OK, that is unexpected... I'll make the error simpler.

Por Manuel

Ascended (19468)

07-10-2020, 22:33

Please try http://openmsx.org/temp/16.0-debug/openmsx-debug2.zip

Por asdrubalivan

Supporter (1)

17-10-2020, 21:29

Helllo! I'm new here and I'm having an issue with OpenMSX. I can't use the full screen mode, currently when I use F12 to toggle full screen mode all that I get is a black screen and nothing else. No logging information and nothing that indicates the cause of the error.

I'm using Fedora 32 which is a linux-based operating system. Is there a way I can start openmsx with a more verbose logging to see what's going on? Also, is there a way to reset the configuration? Since I used F12 to start full screen mode, now whenever I try to use OpenMSX the system always tries to enable full screen mode which results in this black screen I mentioned earlier

Thanks in advance!

Por Manuel

Ascended (19468)

17-10-2020, 23:08

Which version of openMSX are you running?

You can reset your settings by removing ~/.openMSX/share/settings.xml

Por Manuel

Ascended (19468)

17-10-2020, 23:09

Manuel wrote:

Please try http://openmsx.org/temp/16.0-debug/openmsx-debug2.zip

Any results Metalion?

Por sd_snatcher

Prophet (3659)

24-10-2020, 03:31

Does openMSX now require the sha1 checksum to locate a ROM on the systemroms folder?

On older versions whenever I wanted to develop patches for the mainROM/subROM, I just deleted the sha1 line of these ROMS, and openMSX would use the filename to locate the ROM instead.

But now it just doesn't find the ROMs this way, terminating with an error:

Fatal error: Error in "FRS_test" machine: Couldn't find ROM file for "MSX BIOS with BASIC ROM" FRStest_basic-bios2.rom.

Error: openmsx system down, Termination status 1

This makes any development related to the MSX built-in ROMs a nightmare. Every time I change anything and want to test, I have to manually edit the xml file and replace the sha1 checksums.

Por Manuel

Ascended (19468)

24-10-2020, 10:53

Where did you put the file? The path is relative to the XML file.

Por mcolom

Champion (316)

24-10-2020, 13:27

I confirm the same as sd_snatcher. If you comment out from the XML config the "sha1" entry, the error message is misleading. In my test machine: Fatal error: Error in "miguel" machine: Couldn't find ROM file for "MSX BIOS with BASIC ROM" hb-20p_basic-bios1.rom.
I think the sha1 should be optional. For example, that machine I'm using uses a modified ROM which makes my development easier. But I had to recompute the shasum each time I modified it. I guess it's a bug in src/memory/Rom.cc