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
ADF file corruption on some SD cards long term solution #62
Comments
Hi, First of all, thanks for all your bug reports, I appreciate it. This is probably not a size issue, ss I am successfully using a 16GB SD card. It seems some cards are just different then others, but what exactly is the difference, I don't know, as I have a bunch of them and they all work, from 32MB to 16GB. It could be a ARM -> SD card timing issue, I'll look into that first. |
I had this problem with a SANDISK 8Gb SD card. |
I had this issue with some cards, a 32GB Sandisk, a 2GB Sandisk and a (I think) 16GB Kingston. A permanent solution for this would be really great, because none of my SD cards worked properly on the MiST. I would really appretiate a fix! |
Hi @RootFather , http://lotharek.pl/products.php?kid=29 Could this be the problem? Too many faked cards of bad quality out there? |
Nearly all read errors I had on ADFs went away with V1.2.3! I assume, this bug is fixed now. MinimigAGA is becoming perfect after all these years :-) |
It's a known issue that minimig/MiST has problems with corrupt ADF files when using larger SD cards. I had the same problem and solved it by moving to a smaller SD card with 2 GB capacity (thanks to a hint by chaos :-) ).
I don't know why this problem exists when using some SD cards, but I think there should be a 100% solution that works with all SD cards. The current situation is really frustrating especially to new users. On some forum entries, users report that they had to try (=buy) several SD cards, before they found one that was reliable. What about this:
This is just what comes to my mind, when I think about this problem. Maybe other/simpler solutions exist.
The text was updated successfully, but these errors were encountered: