Search

[Razul]

Here's the thing.I'm sure other's had experience with this in Pokemon games..

In VBA, I set the Save type and size toFLASH 128K and it produces a 128KB SAV file.. no corrupted save errors...

In the SF, after patch it thru the prg with the "Enabled More Save" checked, the SAV becomes 256K and i get the Save is corrupted message. Without the option check it become 128K which is Correct by still the same Save error message in the game

Any way around this?

[Diablo]

So in VBA the "Save Type" is set to "Automatic" and "Flash 128K"?  Have you tried setting it to "Flash 64K" and saving?  Backup your save before you try changing the size of it.

Doesn't Pokemon require RTC support?

BTW, if you are importing a save file in the Supercard software, you shouldn't need to enable the "Enabled More Save":  that is only necessary when creating a save file that is larger than usual, not importing one.

[Razul]

If you set it to auto you'll get the save corrupt error in VBA too.
And Pokemon does use the RTC but it wont cause a save error if it's not enabled.

So if i'm importing sav I dont need to enable more saver... thats good to know.

[Diablo]

And Pokemon does use the RTC but it wont cause a save error if it's not enabled.

The Supercard does not support RTC.  Whether this means certain parts of the game will not function, you cannot use saves, or whatever, I do not know.

If you set it to auto you'll get the save corrupt error in VBA too.

That can't be right.  If you set it to "Automatic", VBA automatically choses the appropriate save method.  If you are getting errors, then there are other configurations in the emulator that you have altered to an incorrect setting that are required in order to save properly.

Set the "Save Type" to "Automatic" and "Flash 64K", and RTC disabled, and see if you can save.  If you can't, try with "Automatic", "Flash 128K", and RTC disabled.  Then with "Automatic", "Flash 64K", and RTC enabled.  Then with "Automatic", "Flash 128K", and RTC enabled.  If none of those combinations works, we'll go from there.

[Razul]

Heee Hee Reporting in

RTC - Disabled, Save Type - Auto 64K
VBA - Save File was Corrupted message
SC - Save File was Corrupted message

RTC - Disabled, Save Type - Auto 128K
VBA - No Error message
SC - Save File has been Deleted message

RTC - Enabled, Save Type - Auto 64K
VBA - Save File was Corrupted message
SC - Save File was Corrupted message

RTC - Enabled, Save Type - Auto 128K
VBA - No Error message
SC - Save File has been Deleted message

THe saves still loaded with the Corrupted message.
With the deleted message it'll only let me start a new game..

Anything else I should try ? =\

[Diablo]

THe saves still loaded with the Corrupted message.

Okay, but are you talking about the Supercard or VBA?  You need to know what settings to save as for use with VBA, and what settings to save as for use with the Supercard (what settings allow saving and loading in each, that is).

[Razul]

i mean they still load on both even with the corrupted message.

You need to know what settings to save as for use with VBA, and what settings to save as for use with the Supercard (what settings allow saving and loading in each, that is)

I'm not quite sure what you mean.. I know that Pokemon games uses Flash 128K because, atleast that what I use for VBA. It wouldnt make sense to change the save type for the SC. Or am I suppose to change it for import to the SC?

[Diablo]

I didn't know if you could save and load on both using the same settings (which you have just posted you can).

I know that Pokemon games uses Flash 128K

If it used 128K, then it wouldn't save when you set it to 64K. :wink:

[Razul]

If it used 128K, then it wouldn't save when you set it to 64K

Yeah it does make sense.. with 64K I get the corrupted message on both VBA and SC. I guess I can live with that error as long as my game loads.