08-08-2013, 06:45 PM
As far as I see, isSecureFile is called for every file individually. If we have the situation you described, we have a SAVEDATA_FILE_LIST(because PARAMS.SFO has been updated upon saving a file).
Now if an old savedata-file is loaded, the check for the existance of the SAVEDATA_FILE_LIST works and we only get a fail because the file we are looking at is not included in the SAVEDATA_FILE_LIST.
What I'm proposing is this: If isSecureFile returns false, check if we have a valid value for saveFileSecureEntriesAddr before we declare it to be saved as normal.
That would be a fix that works if there is a SAVEDATA_FILE_LIST as well as when there is none.
Now if an old savedata-file is loaded, the check for the existance of the SAVEDATA_FILE_LIST works and we only get a fail because the file we are looking at is not included in the SAVEDATA_FILE_LIST.
What I'm proposing is this: If isSecureFile returns false, check if we have a valid value for saveFileSecureEntriesAddr before we declare it to be saved as normal.
That would be a fix that works if there is a SAVEDATA_FILE_LIST as well as when there is none.