USSLoad kickstart 3.1 support

[kremiso]

hi Toni
this is my new year wish

just noticed that the states made with kickstart 3.1 cannot be reloaded with USSLoad, there is an unsupported chunk error on my side

if its not an error on my side, hope it will be added in future, if worth the trouble

[Toni Wilen]

Originally Posted by kremiso

if its not an error on my side, hope it will be added in future, if worth the trouble

It is almost surely your error because KS can't cause this

Also the full error message is required. This is currently "it does not work" report.

[kremiso]

tomorrow ill check better
iirc its an A3K1 chunk error

i have tried a couple of games with A500, A1200 and A4000 and different ks3.1 versions, i mean the correct ones for each machine

[Toni Wilen]

You have Processor slot or mainboard RAM enabled. (0x08000000 RAM)

[kremiso]

Originally Posted by Toni Wilen

You have Processor slot or mainboard RAM enabled. (0x08000000 RAM)

isnt the mainboard RAM in the A4000 default config?

i made 3 tests starting with a default 68030 A4000 (with 3.1), then default A1200 (with 3.1) and for last A500 also 3.1
now im wondering if the mainboard RAM is not correctly disabled when a config change occur then?

[Toni Wilen]

It is not supported. Only chip, slow and $200000 RAM (usually Z2 fast) is supported.

[kremiso]

Originally Posted by Toni Wilen

It is not supported. Only chip, slow and $200000 RAM (usually Z2 fast) is supported.

the strange thing is that i also made a state using an A1200 and an A500 configs, and still generate the error

maybe something didnt go correctly after the A4000 test and reset
ill better check thanks

[Toni Wilen]

Maybe you have always had it enabled? Only KS 3.1+ detects it (except A3000/A4000 where it is always detected)

[kremiso]

Originally Posted by Toni Wilen

Maybe you have always had it enabled? Only KS 3.1+ detects it (except A3000/A4000 where it is always detected)

worth also a check
better way to be sure is it disabled?

[kremiso]

Toni, i have made some more tries;
seems that something is not going right after an A4000 config use;
after a reset and change of config, also the further savestates seems to still contain something related

i have uploaded a default A1200 savestate (kick3.1) taken after a first A4000 use (then changed to A1200 after a reset)

[Toni Wilen]

I don't understand what you are trying to do. That RAM region is unsupported by ussload (and it stays that way), you must disable it manually.

[kremiso]

let me try to clarify then
launching WinUAE and setting a machine with kick3.1 (A500, A600 or A1200) all the savestates taken can be reloaded without issues with USSLoad

getting the savestates with the same machines, but after having used an A4000 in first (i presume any setting with mainboard RAM then) instead, all the savestates cannot be reloaded

i would like to know how to manually disable that yes;
i know i can just close and restart WinUAE afterall, i mean after having used any 'RAM on mainboard' hw config

[Toni Wilen]

RAM panel -> Advanced memory settings -> Processor slot Fast RAM -> set to zero. (Only visible if 32-bit CPU)

[kremiso]

tried a bit ago, yes doing that before the reset is perfect!

thanks again, and sorry for the misleading thread title
i would like the possibility to change the thread names, expecially the games/emulation issues related

its difficult to catch the correct cause/triggering factor

[thomas]

To be honest I would consider it a bug if I select a quickstart config and it leaves RAM from the previous config in place.

[Toni Wilen]

It was a bug, mainboard/cpu slot memory was not reset when changing QS configs. It was not noticed because 24-bit CPU ignores them and hides them from listing.