[hatari-devel] Issues after restoring a memory snapshot
laurent.sallafranque at free.fr
Thu Jan 27 00:04:13 CET 2011
I don't understand Eero, I've tested 2 snapshots :
First one with the very first screen
Second one after the first screen
They both restore perfectly (sound + anim).
I've tried to restore them from the gui and from the command line
(I test with the new CPU, if that helps)
What's wrong with your test ?
Le 26/01/2011 20:02, Eero Tamminen a écrit :
> On keskiviikko 26 tammikuu 2011, Laurent Sallafranque wrote:
>> I've just fixed the issue with crossbar saving / restoring memory
>> snapshot. I've tested with Mahab demo, and it runs for me.
>> Could you just do 1 or 2 tests to confirm there's nothing else missing ?
> Unfortunately it still doesn't work for me properly.
> I started Hatari like this:
> src/hatari --fast-forward yes --tos tos404.img mahabhar/mahabhar.prg
> and saved a memory snapshot from the Memory dialog.
> Then I tried the snapshot with:
> src/hatari --tos tos404.img --memstate maha.sav
> Besides seeing the demo screen contents I only get a continuous "diesel
> engine" sound that comes when the same audio buffer contents get re-played
> and demo is frozen.
> This happens even if I'm already running the Mahab demo and restore
> an Mahab memory snapshot from the UI, so it doesn't seem like HW
> initialization issue. Some state just seems incorrectly restored.
> The snapshot is from the first screen.
> If I reset the emulation the "diesel sound" continues. It disappears only
> after second reset. If I try to run the Mahab demo then, it freezes
> the first time it resizes the screen to an extra wide size.
> There's no store/restore for Videl values, but I didn't notice videl.c
> having any state that wouldn't get set to right values when videl code is
> used or being capable of freezing the demo.
> (nvram.c lack of save& restore could give inconsistent state, but that's
> fairly harmless also.)
> Btw. Sometimes I'm able to get the diesel sound just by opening the Hatari
> Options dialog during Mahab demo. I've seen that to happen only with Falcon
> emulation. Nicolas, maybe you have some comment to that?
> - Eero
> PS. I updated the memory snapshot version as adding Crossbar data into
> it makes it incompatible with previous versions.
> (By manually extending the data snapshot files suitably, one could still use
> the old ST snapshots as the Falcon parts are at the end of the snapshot
> hatari-devel mailing list
> hatari-devel at lists.berlios.de
More information about the hatari-devel