@CaptRobovski said in Can I backup current emulator state - corrupted memory stick:

A quick question - should the filename under etc/udev/rules.d end in the suffix '.rules' ? I have other files in there, such as 99-input.rules, 99-bluetooth.rules.

No, the extension is not needed. Only the lexically order may be relevant of all rule files (cf. man udev -> RULES FILES).

The memory stick has left the factory mostly fine I would assume. It is the firmware that make things worse in use cases like this (as likely the USB spec has not been implemented by the letter by the vendor).

If you change make and model of the memory stick you may leave the power control rule enabled (adapt to the VID/PID). Does not have an impact unless you run on battery.

Or you can make a backup of you new memory stick and run it without the power control rule. If things repeat restore the memory stick and enable the rule.
However, if it repeats on a different make/model the issue could also be caused by the RaspBerry Pi Kernel USB implementation.

@mitu yeah i think, because i configured it normally, but dosen't work after some reset,

@jamiem1976
It appears you are using a recalbox image instead of a retropie image. You might want to ask your question on their forums instead.

@mitu said in Corrupt after every reboot:

What resolution is your display and how is it connected ? Have you tried forcing a specific resolution through raspi-config ?

Ok, thank you for pointing me in the right direction, I forced the resolution, which fixed that on start up, then it got me thinking., that was only for the system level, so I started poking around the retropie configs, and set the audio to HDMI, and changed the audio driver to SD12 and everything seems to be working now

@quicksilver nevermind i fixed it

I already try this and the result is the problem returning when I add a new game to favorites.

Yesterday I do some tests and the problem occur with Snes, Megadrive and Nes gamelist.xml. I don’t know the the reason and not see any difference between the files.

Just my findings:

commit 0343e3dbd8a22f64698e824e30b08e0887d77b6b
Author: retro-wertz retro-wertz@users.noreply.github.com
Date: Sun Mar 4 21:47:52 2018 +0800

Add missing variable to save state

This is the commit that breaks the loading of existing state files from old pi's.

And for anyone's future reference: here is the github issue regarding it: https://github.com/libretro/libretro-fceumm/issues/215

Are you using the correct program? Like win32diskimager? You cant use any iso/img program. They will always come up as corrupt

I got the same error message, I fixed it by changing the power supply :/

If it was in fact a Sony card, it should be compatible. I have to admit, bought it off eBay, probably fake, like BuZz suggested.

@BennieB I suggest you read above and see what @DJfist did.

the screenshot is already in the command line. if you type

sudo nano /etc/asound.conf <enter>

...you can edit it, and maybe fix it.