This is a change i'd like to request. From the past few days i am seeing people not backup up the original cards' firmware, and then;
1a. Attempting to restore back the dumps available on-line and failing.
1b. Succeeding in a restore from a dump on-line but loosing options or partially failing.
Sometimes a new HW revision comes along and it differs from the previous one.
Flashing 'old' dumps into those cards breaks them (or some part is gone, like wifi or rts/ability to read SD, as it was just a clever clone with a different SD interface in the globtop.
2. Not backing up the cards' firmware (resulting in a restore, and we're back to # 1 above.)
Implementing this would mitigate the risk of a broken card.
I would suggest a double backup with a crc file (sha256?) to ensure both are the same file proper dumped.
A database could optionally be created to detect (un)dumped firmware and implemented later in GUI. (as done with EvoX and the original Xbox in its .ini file)
This is a change i'd like to request. From the past few days i am seeing people not backup up the original cards' firmware, and then;
1a. Attempting to restore back the dumps available on-line and failing.
1b. Succeeding in a restore from a dump on-line but loosing options or partially failing.
Sometimes a new HW revision comes along and it differs from the previous one.
Flashing 'old' dumps into those cards breaks them (or some part is gone, like wifi or rts/ability to read SD, as it was just a clever clone with a different SD interface in the globtop.
2. Not backing up the cards' firmware (resulting in a restore, and we're back to # 1 above.)
Implementing this would mitigate the risk of a broken card.
I would suggest a double backup with a crc file (sha256?) to ensure both are the same file proper dumped.
A database could optionally be created to detect (un)dumped firmware and implemented later in GUI. (as done with EvoX and the original Xbox in its .ini file)