Bug with save&load in BlueMSX

By YuN

Rookie (22)

YuN's picture

26-10-2014, 03:50

For unknown reason, many saves ("CPU state saves", which I use to save and load games, as you may guess) stopped working. I start BlueMSX, press F6 or LAlt-F6, the game loads - and freezes (the emulator is not frozen, however). Previously (including just several hours ago) I loaded from these saves, and everything was OK. Not all saves freeze, but only from certain games - mostly "old" games (1981-85), while "new" games (like Vampire Killer, Usas, Aleste...) still load and run OK. Moreover, an old game still runs (if started from the very beginning) and can be saved and then loaded - and this new save works, but previously made ones do not!
I am sure that STA files were not damaged on my harddrive. I also didn't change any configuration of the emulator, at list deliberatory. Restarting the emulator does not help. Any ideas? I can send you my STA files to check them on your computer.
The BlueMSX version is, I guess, the last one existing - 2.8.2, and I use MSX2 configuration.
I tried to ask in Emulation section, but nobody responded. Maybe this place is better.

Login or register to post comments

By mars2000you

Enlighted (6019)

mars2000you's picture

26-10-2014, 06:24

Your 'old' save states have probably been made with an older version of the emulator. There have been so many changes since version 1.3, especially 2.0 step (no more any code from fMSX) and 2.6 step (video capture with .cap files that are extended .sta files + AVI rendering).

Unfortunaly, there's no any conversion tool, so the only solution is to play again the games from the beginning and make new save states.

By ren

Paragon (1888)

ren's picture

26-10-2014, 12:15

Why do you double/cross post (http://www.msx.org/forum/msx-talk/emulation/help-very-strang...)? You could have bumped your original post instead?

Anyway, I recall also experiencing some issues regarding save-states a little while ago. But I was also fooling around with the 2.8.3 beta's back then, so that might just have been the issue...
But the experience did effect my trust in he emulator/save-states a bit, and the fact @dvik doesn't seem to be much active/involved for roughly the last 2 years now (though he *did* make a commit to the repo April this year), and the last stable release is from 2009, made me really move more into the direction of OpenMSX.

It would be great if @dvik could give some love to (t)his emulator again, and e.g. incorporate the emu fixes that have been done in the OpenMSX project, and perhaps aim for a fresh release? (Are you still in contact with him @m2k?)

Other peeps around perhaps that've experienced save-state issues?

It is still a cool emu for windows, with it's own cool features, but the more reliable MSX emu really is OpenMSX.

ps: are you experiencing any other vague issues with other apps perhaps? If that's the case you should check your RAM / run a memtest perhaps.

By YuN

Rookie (22)

YuN's picture

27-10-2014, 00:10

No, I wrote already that I used one and only version 2.8.2, and the save files which worked stopped working several hours later. Nothing was altered on my HD (I even copied those saves and the BlueMSX files from backup drive, nothing changed).
I have no problems with other software. On the other hand, there always were issues with BlueMSX quickloads (it hangs if at the moment of loading top menu bar is visible, and after several loads the sound disappears), but never that bad and exiting and restarting BlueMSX always helped. But not now.
Maybe rebooting Windows will help, but I hate to do it unless really necessary (opening all these windows again!)
I don't know how to delete my old topic.
Again, those who have BlueMSX 2.8.2, can you test any of my .sta on your system?

By ren

Paragon (1888)

ren's picture

27-10-2014, 16:45

Have you tried using a fresh/clean blueMSX installation? (Just use the zipped archive, unpack it somewhere & run it.)
You're using the standard/default machines, or something exotic?
What windows are you on, and for how long haven't you rebooted it? (It just might help ;-)

Sure, upload a .sta somewhere. (As long as it's not a trojan in disguise of course.. ;-)

By YuN

Rookie (22)

YuN's picture

28-10-2014, 00:37

I've said, I use standard MSX2, and I copied clean blueMSX from backup, nothing changed.
I use Windows XP which runs 24/7. The last reboot was weeks ago, but see above.
I explored the situation more, and that's what I found:
Any game works normally from the beginning, but previously made saves for old games do not work. However, if I start the same game from the beginning and then save it and then load, it works (while old saves still do not). BUT! It works only until I quit blueMSX. If I quit and restart blueMSX, these new made save files stop working like the previous ones. So, STAs work correctly only if they were made during the current session of the emulation. Of course this is not normal, and it never happened before.
Here are 2 sta files from different sessions:
http://www.fileconvoy.com/dfl.php?id=g7a30979eca0526a5999574...

By mars2000you

Enlighted (6019)

mars2000you's picture

28-10-2014, 11:17

Why do you use temporary directories to store the rom files ? Besides, it's not always the same temporary directory :

BOSCONIA21 - C:\temp\Rar$DI00.719\BOSCONIA.ROM

BOSCONIA55 - C:\temp\Rar$DI00.297\BOSCONIA.ROM

Probably, you use roms that are stored in a 'giant' RAR file. Windows seems to use every time a different temporary directory. It should be better to extract the game that interests you in a non-temporary directory.

Additionnal infos :

1 - as explained in the manual, you can see the contents of a STA file by renaming it with the ZIP extension.

After unzipping, you can read the binary file board_00 with for example an hexa editor, and you find there the original path to your ROM/DSK/CAS file. In your case, temporary paths are used because your games are compressed in a RAR file.

2 - blueMSX does not support directly the RAR compression format, only the ZIP format. I think you have many windows, because you need one to see the contents of the RAR file, one for blueMSX and eventually one for the blueMSX trainer.

I guess you select the ROM of the game in the first window and drag and drop it in the second window. Acting this way has as effect that Windows uses every time a different temporary directory for the path to the ROM included in the STA files.

By YuN

Rookie (22)

YuN's picture

28-10-2014, 13:39

mars2000you, thanks! That was the reason. I didn't know that it needs rom file to run a saved game - I thought it had all the necessary in STA. And of course temporary directories where I unpacked roms from game archive were deleted after every session.