openMSX 0.10.1 released

Can you add support for MegaFlashROM of ASCII type (8/16K) in a next version ?

gdx - I've got information and some documents about it, but I can't promise anything. I do think it's worth implementing it.

I'm having little problem with LEFT ARROW key.
It doesn't work.
I know I must use BIND, but I don't know all the names of keyboard button.
I mean: BIND LEFT_ARROW lEFT should work?
I've looked to the command line guide, but i did't find any kind of keyboard map.

Wonderful job anyway !!!
I hope one day catapult (orsomethinglikethis) will have alabel for machine customization, a label for diskmanipulator tool.

Regards

I know it is mapped by default.
But since many days it does not work anymore.
I thought that installing ver.10.1 it would working back.
I was wrong.
It happens always, i do not know why.

@giuseve: Does it help if you delete your settings.xml file? OpenMSX will recreate it with all settings reverted to the default.
But please make a backup first so that, if this turned out to be the culprit, we can compare both versions and prevent this bug(?) from happing to other users.

The frequency is: (6 * 3579545) / (1368.0 * (([vdpreg 9] & 2) ? 313 : 262)))

PAL: 50.15897371223586 Hz
NTSC: 59.92274340431231 Hz

So, the framerate openMSX generates is always one of these 2 (if frameskipping is disabled of course).

I don't know exactly about the FB renderers. IIRC mth added them at some point and I forgot the story about them, so I asked him to reply here.

Oh, they were added by Wouter in 2005

Do you mean how much faster than real-time can openMSX emulate? This of course heavily depends on the type of software you emulate and on the speed of your host computer. But to give you some rough ideas: most PC hardware should have no problem running openMSX at 10x real-time speed.

Most often video rendering is the bottleneck, and occasionally sound emulation takes a significant part. So if you allow to skip rendering some frames (maxframeskip setting) and if the MSX software doesn't produce sound, it's possible to achieve 50x-100x real-time speed.

For certain MSX software even higher speeds are possible. E.g. the ZEXALL test almost exclusively needs Z80 emulation (there's no sound and only occasionally it prints something to screen). On a real MSX machine this test takes ~4.6 hours to complete. I just retested on openMSX .. with some setting-tuning it finishes in less than 1 minute on my system (that's ~275x real-time speed, or equivalent to a Z80 running at ~1GHz)!

I would guess that C-compilation on MSX is also mostly Z80 emulation (and a bit of disk access), so you may be able to achieve similar speeds.

Hello.

I installed "OpenMSX 0.10.1-26" but this version don't have Catapult. This is normal?

Paulo - Just install the official release. (But all Windows builds have Catapult.)

Works great with my compiling in MSX-C, very solid performance, also testing my game engine at 3x screensize is very helpfull, going to use this great emulator!

Only had 1 thing, it seems you need to let the emulator create a IDE HD image first before you can select your own, got errors before i let the emulator run its course, is there a reason for that order?

ren, about SDLGL-FB32 - what is the added value for you compared to the plain SDL renderer?

Brand new day! (more MSXing & other nerd-stuff to do! ;-))

So, it has nothing to do with the scaling, but with plain SDL stuff like scrolls are really choppy. SDLGL-FB32 works like -PP in that regard; even without vsync enabled, it's quite smooth (depending on the relation MSX freq <> monitor freq of course) (with a little hiccup at a regular interval).

Btw; with regular SDL & -FB32 I can't set scaling to 4x (it will fall back to 3x then)? I *can* set it to 4x with -PP.

No, but this has been fixed now. Thanks for trying development builds!

Well, the more people try development builds and report the problems they have with them, the less bugs we have in the release! So, I appreciate it a lot when people try development builds and report issues. Keep them coming, all!

Hi Manuel,
Sorry for the late reply, was quite busy actually using openMSX
I installed the previous build again on another laptop a few days ago and I tried to repeat the handlings I did, to replicate the issue, but it didn't occur, so it was or either a config thing I did wrong in the xml of my MSX hardwareconfig, or something else not quite sure. The first time I deleted my config and found one online and used that one and that did it.
I also wanted to know why a hard-disk image of 100mb was automatically being made in the first place when no image is selected, read that somewhere and actually saw the image appear while fooling around with Catapult, maybe better to put an extra Tab in the Catapult shell to create one manually or do a pop-up asking this to the user, just an idea

I will try the new build later today before my c coding session as well.

cheers!

Yes, i needed to elaborate it more it seems -=lol=-
the config was for the machine a was emulating, my own machine HB-F700 was new to OpenMSX, now I know what does what.

I do have minor thing I encountered yesterday when compiling (my own project) and testing and using resets and stop/start allot. It seems inconsistent, the time it takes for the screen to popup and start the emulator, it is sometimes seconds in difference, So i use reset more.

Thats all for now, compiling on msx has never been faster

The link to nekolauncher on the openmsx site is no longer working. IT moved to:
https://nekocanmac.wordpress.com/software/

I've put the system roms in the userfolder, but it didn't recognize the roms in the first place, couldnt select the HBf700p from the list in Catapult, only C-bios setups. So i put an xml file in share/machines/ then it made it possible to select my machine.
I did saw the xml files of the pre installed machine, but it didn't show them after installation in the pulldownlist in Catapult.

I will try this probably tomorrow.

Clear as water, but will pay even more attention to this now

Ok, thanks for the link

OpenMSX is too dangerous!...

I just was working on my stuff, ans when get back to the openMSX window it show the "time bar" shit, and accidentally it get back in time and ruined all that I was doing.... this shitty timebar grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr, I never be capable on forwarding it again LOST everything.

For me, the reverse feature is essencial, as it allows the step_back feature when debugging. I can't live without it anymore.

But I agree that the reverse bar is dangerous for programmers. Long ago I disabled it to avoid accidents.

Manuel, I tried the "set auto_enable_reverse on" feature, but it doesn't keep that setting after I close and reopen openMSX... I'm typing the following commands on the console:

set auto_enable_reverse on
save_settings

->The reverse feature is still disabled.

I'm running openMSX 0.10.1 on Mac OS-X 10.9.3.

Don't ask me, all I know is that I upgraded openMSX to 0.10.1 and the reverse feature stopped working by default...

Me and my unwanted gift for finding bugs...

Here, the line 32 of lazy.tcl is:

register_lazy "_psg_log.tcl" psg_log

Since it didn't look to me as the correct line, I searched for "reverse", and found the following at line-39:

register_lazy "_reverse.tcl" {
        reverse_prev reverse_next goto_time_delta go_back_one_step
        go_forward_one_step reverse_bookmarks auto_save_replay_enable
        auto_save_replay_disable auto_save_replay_set_filename
        toggle_reversebar enable_reversebar disable_reversebar}

I added the auto_enable parameter just before the last brace and now the reverse function is working fine. Thanks!

BTW, I also found another bug. Have you seen the report?

Sorry if I wasn't able to test the prerelease of 0.10.1 when you asked in the forums, but I had no free time back then...

I thinks, instead of clicking in the window titlebar for seting back the keyboard focus on the MSX, I clicked like 2 pixel down off it. And it did the reverse. Then, maybe I panic and pressed some key with the arm or the left hand, and I never was capable of fowarding it again. Why not a confirmation box for reversing?.

why is this enabled in default, isn't it affecting performance?

Ok, thanks for clearing that up. reverse stop in the console should suffice, I tried to save that setting in the console with save_settings , but didn't do anything, is this also due to that little bug?

ok, clear as water, thanks! OpenMSX blows BlueMSX out of the water btw great piece of software!

BTW, it did work out with the auto_enable_reverse off,
OpenMSX now starts wayy faster than before, it's instant, before with the option on, it did take on my HP dv7 at least 5 to 7 seconds for the graphical screen startupscreen to appear via Catapult. Now when I press start, it starts immediately.

Will saving to .CAS files be possible in future versions ?
CAS files are easy to edit with use of a HEXeditor, and saves time
not have to convert WAV in to CAS every time.

Keep up the great work

No, there were no messages in status tab. :S

But i found a bug, its not a constant, an occasional bug.

the situation is as following:
I have a floppy dsk file that I use to transfer files to my harddisk dsk file with openmsx, then in openmsx it compiles the files. I cannot leave my image filemanager open with m HD image and leave openmsx on, then it becomes read-only from one end, so the floppy image is my file buffer, that dsk I open firstly with my image filemanager, so it is read-only end is for openmsx. And then the whole session (few hours) i can leave these open and copy and compile all i want, but....

... with this i found out that speeding this up in openmsx also 'sometimes' goes wrong, cause the copying and compiling i do not use on 100% normal speed ofcourse. I put it on max with F9.

The bug is that with Max speed on, openmsx makes copy errors in my sourcefiles, extra characters which screw up so the compiler gives allot of errors or it puts the EOF marker somewhere else.

Then when i execute my batchfile (for copying and compiling) again, then all goes well.
I have this maybe 2 times out of 10.

yes i am using disk image.

Copy is simple MSX-DOS2 copy from one small floppy DSK image to the other which is a 32mb HD DSK image, a few c source files are copied. I copy around 10 sourcefiles at once.(not all are compiled at once)
I am using Openmsx Version 0.10.1.
The errors occur during compiling in ASCII MSX-C 1.20. Cause the compiler then sees the errors in the files.

I first thought is was the compiler, but I opened the copied files with type and with TED and saw characters that not supposed to be there and arent in the originals.

I hope you have enough info. You can get some example files and compile them in this same kinda situation. But My guess is that this is during the copy stage, which is basically simple ascii text files.

here are some files, and also some complex sourcefiles to compile.
http://msx.hansotten.com/index.php?page=msx-c

Will do tomorrow. The machine is a hb700p

OK, there's nothing I can do about it without more input from your side.

OK, thanks! And thanks for reporting in the first place!