[hatari-devel] Issues after restoring a memory snapshot

[Eero Tamminen]

Hi,

On torstai 27 tammikuu 2011, Laurent Sallafranque wrote:
> 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).

Was this with WinAUE or AUE core?

I guess you've commited & pushed all your related local fixes?

> I've tried to restore them from the gui and from the command line
> --memstate xxx
> 
> (I test with the new CPU, if that helps)
> 
> What's wrong with your test ?

No idea.  :-/   I'll test tomorrow more.


> Le 26/01/2011 20:02, Eero Tamminen a écrit :
> > Hi,
> > 
> > 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.


	- Eero