|Re: [hatari-devel] Autostart with stored memory state|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Autostart with stored memory state
- From: Miro Kropáček <miro.kropacek@xxxxxxxxx>
- Date: Sun, 24 Oct 2021 20:11:29 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=XVODlqfxLXvXFEKzaTIncCczGzDsF4Wx6U07uHn5HRw=; b=N+weIpROD7XtG5cGarw/JPkBbH29tDPSLhHK/7yh7hc458vogWsqX3jkSHI9oeZ9hf CTnq3MQL1tf3OElGz8CrlCvOZYlPfiWonot2sGKYyF5m06RLK3l7GCbQdAw8zkwyPG41 YvVozfK7v7M06GA1hYknrfEtkhPa4a/QEQkxpre4n63ApFJbDZyW7Atgi6U1DLtMT5yB RitRWu7jV0A0tE2bXsGnjPpCUhsWuXZLWZONNLpQGbrpyeKrErzoaCDivNQBD/ic2RcK tF07Lf5y+1pxX6TeY9EfpH+6txKSCx1lU1RLQX28acEblMUnk8w/C/fdf2rxWp2jmGRZ DNvg==
I'll let you know when I start Hatari again (I also owe Eero some testing) but in the end, I'd learned to live with that.. I think I found out that I was saving the state too early or something like that, i.e. that UI pretended that everything was saved but I had push OK first and then reenter the UI again and save my setting or something like that -- it was still a bug (creating nonsensical .sav files) but not so fatal anymore.
Am Tue, 27 Jul 2021 08:25:07 +0200
schrieb Miro Kropáček <miro.kropacek@xxxxxxxxx>:
> don't know if I'm doing something wrong but with latest Hatari 2.3.1
> for win64 I'm unable to get this feature working. If I save the
> state, I see a new hatari.sav created in my AppData folder. If I
> check that "autostart feature", I see another auto.sav created there.
> So I close Hatari, start again and boom, crash.
> While looking at the files I noticed they have different file sizes
> (962 456 = ok, 960 183 = not ok). So I rename hatari.sav to auto.sav,
> start hatari, everything's great. Close Hatari, auto.sav has again
> different size (to be honest, not sure whether that size has changed
> exactly then).
> Can anyone verify this? Attaching my cfg, can provide the memory
> snapshots as well.
did you ever find a solution for this problem? I just tried to recreate
it (with the current development version on Linux), but it seems to
work fine for me...
If the problem still persists, could you maybe try to set
"nTextLogLevel = 5" and see whether there is anything interesting in
the log file afterwards?