State-save issues

andreas · 27 January 2002, 03:31

Hi,

triggered by a new attempt to play my old favourite The Surgeon again, I started to experiment with the state-save feature of WinUAE. WOW! That's what I call handy!

Anyway, I found three small issues. One is that if you have just loaded a state-save file, re-loading the same one again makes WinUAE crash.
The second is that you MUST use the same configuration you used when saving the game state, otherwise: bad luck!
WinUAE would just crash with a random configuration.
The last maybe isn't *that* important: without a kickstart you cannot load a savestate-file, seems this is because of copyright reasons because in theory, someone could just load a state, reset the machine and WALLA ... there's the kickstart! ;-)

A sample file is in the zone.

Toni Wilen · 27 January 2002, 10:14

You need Kickstart because Kickstart ROM isn't stored in state file. Copyright is one reason, another is state file size. (Storing KS image to state file would make it 512Kb bigger, state file size is RAM size + couple of kilobytes for CPU/CIAs/custom chip registers)

Configuration is needed because only part of configuration is loaded from state file. This will be fixed in future versions..

Thanks for state file. Reloading should not cause crashes..

27 January 2002, 11:28

How about compressing the save state file when saving and decompressing it into RAM again when loading. I sent a mail to codepoet about this but I don't think anyone read it.

Toni Wilen · 01 February 2002, 09:16

The Surgeon state loading fixed. (Partially fixed by me, another bug was fixed by Bernd)

State file compression will be implemented in future.

andreas · 01 February 2002, 13:20

Thank you. (By the way, what was the cause?)
I hope that it was only an example for a couple of games, and that this fixed many similar crashing problems with save-state files for everybody.

You had fixed lots of floppy-loading problems in the past, and thus made another shelf of games relive on the emulator, sometimes by applying just ONE fix

andreas · 14 February 2002, 15:21

Toni,

I've found out something that can be very FATAL regarding save state saving: if the partition is full! This is not handled yet. I only had this once, but it can easily happen.
This will produce a file that's incomplete and that could possibly crash the whole system. I only need to remember the issues that occured with CCS64 (C64 emulator) with a BROKEN save state file...

27 January 2002, 03:31	#1
andreas Zone Friend Join Date: Jun 2001 Location: Germany Age: 50 Posts: 5,857	State-save issues Hi, triggered by a new attempt to play my old favourite The Surgeon again, I started to experiment with the state-save feature of WinUAE. WOW! That's what I call handy! Anyway, I found three small issues. One is that if you have just loaded a state-save file, re-loading the same one again makes WinUAE crash. The second is that you MUST use the same configuration you used when saving the game state, otherwise: bad luck! WinUAE would just crash with a random configuration. The last maybe isn't that important: without a kickstart you cannot load a savestate-file, seems this is because of copyright reasons because in theory, someone could just load a state, reset the machine and WALLA ... there's the kickstart! ;-) A sample file is in the zone.

01 February 2002, 13:20	#5
andreas Zone Friend Join Date: Jun 2001 Location: Germany Age: 50 Posts: 5,857	Thank you. (By the way, what was the cause?) I hope that it was only an example for a couple of games, and that this fixed many similar crashing problems with save-state files for everybody. You had fixed lots of floppy-loading problems in the past, and thus made another shelf of games relive on the emulator, sometimes by applying just ONE fix Last edited by andreas; 01 February 2002 at 13:30.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WinUAE "save state" to include the current state of floppies.	seuden	request.UAE Wishlist	2	03 February 2012 09:36
Save state....	Fuddles	support.WinUAE	4	08 May 2009 13:14
Save state	hrafnkellg	New to Emulation or Amiga scene	5	06 May 2009 18:05
Save State how ?	DrunkGuy	New to Emulation or Amiga scene	6	02 December 2006 20:22
Save-State and Load State don't work	Klownk	support.WinUAE	15	27 December 2002 14:24

27 January 2002, 10:14	#2
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,518	You need Kickstart because Kickstart ROM isn't stored in state file. Copyright is one reason, another is state file size. (Storing KS image to state file would make it 512Kb bigger, state file size is RAM size + couple of kilobytes for CPU/CIAs/custom chip registers) Configuration is needed because only part of configuration is loaded from state file. This will be fixed in future versions.. Thanks for state file. Reloading should not cause crashes..

27 January 2002, 11:28	#3
oldpx Posts: n/a	How about compressing the save state file when saving and decompressing it into RAM again when loading. I sent a mail to codepoet about this but I don't think anyone read it.

01 February 2002, 09:16	#4
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,518	The Surgeon state loading fixed. (Partially fixed by me, another bug was fixed by Bernd) State file compression will be implemented in future.

14 February 2002, 15:21	#6
andreas Zone Friend Join Date: Jun 2001 Location: Germany Age: 50 Posts: 5,857	Toni, I've found out something that can be very FATAL regarding save state saving: if the partition is full! This is not handled yet. I only had this once, but it can easily happen. This will produce a file that's incomplete and that could possibly crash the whole system. I only need to remember the issues that occured with CCS64 (C64 emulator) with a BROKEN save state file...

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)