-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReadMe File Must Inform the New Naming Convention for Existing Backups #92
Comments
I updated the release text, but a list of possibl e names still needs to be put somewhere, maybe on the flashcart_core repo? |
Thanks on the fast reply, mate. |
I'd much prefer the names be in the flashcart_core readme, listing which carts are supported by each name (and the short name to go along with it) |
Any updates on this? |
While the Release Notes for version 0.4 acknowledges that "Backups now have the shortname of the cart prefixed for backup/restore. e.g. ak2i-backup.bin", it does not state that existing backups must be renamed according to this new convention to be read by the flasher.
As it is currently phrased, that note only implies that backups are "created" with a short name, but says nothing about renaming existing backup files.
What is worse, the name possibilities that must be used to rename the existing backups are not stated in the ReadMe file or in the error message of the application (it only says that the restore file was not found.)
Because of the inexistent documentation, checking that the backup file is in the right location in the console's SD card or trying different versions of the corresponding backup are all in vain.
I checked the recent commits and noticed that the naming convention of backup creation (02cdb99, from Dec) and backup restoration (93f60c5, from Jan) had changed, but it is not easy to tell what exactly the new names must be just by reading those commits.
Luckily, I came across this message on GBATemp, and finally knew how to name my backup and re-flash my flashcard.
The text was updated successfully, but these errors were encountered: