Hacking Easy Flash Omega's Saver folder randomly corrupts.

[SegaSnatcher]

I'm using a AGS 101 and a Sandisk 32GB MicroSD card. The Omega works and saves just fine for awhile then randomly when I choose a game that has a save feature I get a error 4.

I will get this error 4 for any game that has a save feature while games that don't will boot just fine. For some reason while the Omega is trying to create a new save folder for a game it ends up totally corrupting the Saver Folder.


I first had to reformat my card to get it to work again, but I found a temp work around. I just rename the corrputed Saver file something else and then create a new Saver Folder and move all my saves that didn't get corrupted to that folder, but its not a real fix as it'll end up giving me that Error 4 eventually. When I look in the Saver folder I see a bunch of weird named files.

 

[EZ-Flash2]

It only happens with turn off the console without wait. please read the manual.
Your SD card needs to be repaired by using windows diskscan or chkdsk /F in command prompt.

 

[SegaSnatcher]

But I do wait like 5 seconds before shutting down after a save has been made. I'm gonna wait 10 seconds from now on and see if I get that error again.

 

[Searinox]

Team EZ-Flash maybe add a CRC32 with save so that when the console is turned on, incomplete/corrupt saves are detected and not written back to drive.

 

[kuwanger]

Team EZ-Flash maybe add a CRC32 with save so that when the console is turned on, incomplete/corrupt saves are detected and not written back to drive.

That's a non-sequitur. There's no storage area when the system is turned off to copy over incomplete/corrupt saves. The issue is turning off power midwrite is basically bad on every storage medium. While there are possibly steps that could be taken to deal with corruption after the face on the EZ Omega, there's no real way to overcome the problem of turning off power midwrite. It's why I'm still hoping Team EZ-Flash figures out a way to notify people when writes are occurring. Then we'd at least know if that's the main culprit or it's actually something else (bad microSD, something in the fat library, etc).

 

[Searinox]

Oh I thought it does something similar to the 3in1 and could write saves on next restart.