openMSX bugs

Page 3/5
1 | 2 | | 4 | 5

By ren

Paragon (1521)

ren's picture

01-10-2020, 13:56

@bodhi1969: yes, latest dev. build (Win7)

By Metalion

Paragon (1203)

Metalion's picture

01-10-2020, 14:09

Manuel wrote:

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?

Yes, that's OK.

Changing my path from {Privé} to {Prive} and then back had some unwanted consequences Sad
I lost all my settings on Notepad++, and other config files as well ....

By Manuel

Ascended (16962)

Manuel's picture

01-10-2020, 21:17

can you check whether the issue is still there with this openmsx.exe: http://openmsx.org/temp/16.0-debug/openmsx.exe ?
This is just 16.0 openMSX.exe, but compiled by myself, so I can quickly build debug versions to get more info.

Don't forget to backup your original openMSX 16.0 binary.

By mcolom

Expert (112)

mcolom's picture

02-10-2020, 00:50

I found an issue recently.
In openMSX 0.15.0-620-g7c070781d (installed from the Debian testing package), the indicators (as fast-forward with F9, and so on) didn't disappear from the screen as usual, and the following message was printed at the beginning:

Error while executing /opt/openMSX/share/scripts/osd_menu.tcl
Invalid keycode: filedrop
while executing
"bind_default filedrop osd_menu::drop_handler -event"
(in namespace eval ":Shocked!sd_menu" script line 10)
invoked from within
"namespace eval osd_menu {

# default colors defined here, for easy global tweaking
variable default_bg_color "0x7090aae8 0xa0c0dde8 0x90b0cce8 0xc0e0f..."
(file "/opt/openMSX/share/scripts/osd_menu.tcl" line 1)
invoked from within
"source /opt/openMSX/share/scripts/osd_menu.tcl"
(in namespace eval "::" script line 1)
invoked from within
"namespace eval :: [ source $script]"

I've compiled from the sources in git (master branch) myself, and then installed with sudo make install, and the problem disappeared. I don't know if this is happening to other Debian users around, or if it was just me with a messy installation.[/]

By Manuel

Ascended (16962)

Manuel's picture

02-10-2020, 07:41

That looks like newer scripts and older openMSX binary were used.

Debian testing doesn't ship development version and doesn't install in opt.

By mcolom

Expert (112)

mcolom's picture

02-10-2020, 09:33

OK, thanks. Then it was my messy installation after all.

By jonesypeter

Expert (74)

jonesypeter's picture

03-10-2020, 19:56

Hi,

Just downloaded OpenMSX 16.0 (Thanks for another update). I have some .sta files which are magazine type in games, they load fine in BlueMSX, but in OpenMSX I get an error:

I'm using the Sony HB-75B ROM (As that is the machine I have)

This is the file.

https://drive.google.com/file/d/1NwHUSc0yom7NvL3vAbDjzc_eQLg...

I have about 50 of the files, and have tested 10 all with the same results.

Thanks

PS - As a supplementary question, can I output BASIC listings to a text file? Cheers.

By Manuel

Ascended (16962)

Manuel's picture

03-10-2020, 22:45

I'm sorry, openMSX does not support loading blueMSX save state files.

Yes, you can in many ways:
1. Save in basic with ,A behind it and export the file from the disk image, or use dir-as-disk
2. LLIST the file and use the printer logger
3. If it's short, copy from the screen and paste in notepad like application

By jonesypeter

Expert (74)

jonesypeter's picture

03-10-2020, 20:37

Thanks @Manuel. Will give that a go. Could I put in a feature request for save states to be added in the future?

Best wishes

By Manuel

Ascended (16962)

Manuel's picture

03-10-2020, 21:42

openMSX has full support for save states for over 10 years already. But you can't exchange save states between different emulators. Save states are not a good way to store typed in programs...

Page 3/5
1 | 2 | | 4 | 5