@mitu

Story of my life.... As soon as I decided to ask a question, I find the answer.

According to the documentation (at the very end), there is a line that says I should replace my mount command with the following:

sudo mount -t cifs -o sec=ntlmv2,username=something,rw,file_mode=0777,dir_mode=0777,password=********,nounix,noserverino //SERVER/Software/Games/roms/ /home/pi/RetroPie/roms/

That solved the problem.

I wonder however what would be the difference between this whole new line, versus your suggestion of just adding uid=pi to my previous line. Would you know?

@mitu That was indeed the problem, using the same emulator fixed everything! Thank you so much, I was going crazy there for a while. Merry Christmas to all of you!

Thanks for the reply!

You can launch discs for supported cores by starting any rom for the system in question first (which avoids having you to load up a core first before launching a disc) and then selecting "load disc" from the retroarch menu.

You're right, defining a per-system folder for the savefiles is a good idea, but it doesn't help with the save states, which is indeed a retroarch problem.

@mitu Thanks that did solve it, was able to save emulator settings. Just uninstalled and then update retropie setup script =D

Do what, exactly ? If you're asking about removing ROMs, then it's easier to delete the files from \\retropie\roms\<folder>.

Ok thanks for the reply. I will do that. Thanks

Maybe @jandalf81 gots a script solution in his pocket: [SCRIPT] Setup script to sync saves to cloud services

@mitu I'm going to look at it thank you very much !

@jandalf81 Interesting..thanks!

again.... playstation games..... and the snes9x2010 emulator lol i figured i wouldnt find a answer on here im pretty sure the official power supply is enough

just posted a issue with re3 having load issues.... the guy wanted to know what kinda power supply i was using LMFAO outa 166 games why does the type of controller i use a issue at all.....

@rmigd it depends on the emulator, if not handled properly, size of savestates can be different between 32 and 64 bits. Most likely your android device is using arm64 retroarch while your rpi is using arm32 retroarch.

Hi Mitu,
Sorry about not posting that information, must've missed that post. I started collecting the data, but while I was running through it I decided to run the following commands:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install alsa-utils

After that my save states worked normally even with auto-login enabled. When I originally updated the device was when the save states stopped working, but I guess now that has been figured out :)

Sorry for the late reply... ;-(

@joelkolb I'm glad you like this. I did this more as a "proof of concept" since I don't really use save states. There will very likely be a whole batch of errors in this scripts... ;-)
Nevertheless, I corrected the script to work with games with dots in their names. If you install the script now, this should work out of the box.
As for the timer, that can be changed from inside RetroPie. The setup added a configuration script to the main RetroPie menu

@cyperghost Thanks for helping with the quick fix!

@robertybob I have no intention of adding any of my scripts to the "official" RetroPie setup. This is more of a side project or hobby to me. Having more users means having more problems as my scripts have not been thoroughly tested. This would create frustrations on all sides. Now, if someone were to fork my projects and take over support for that fork... I wouldn't have a problem with that.

@ExarKunIv You either need to manually activate the setting to create a thumbnail on saving states or the first savestate won't have one. If you use my script to start a ROM with a savestate that setting will be set to TRUE by the script. This will be done per system, as @joelkolb said

@montecore >Sounds like there's nothing that can be done

Well, you could manually recompile it from an earlier version to get back to where it was but as far as converting the savestates I'm not aware of any method

@radiusxe

The best you can hope for is to load the save state from the previous core version and work your way to an area that allows for a normal memory save. Afterwards, update the core load the save and make a new save state. I realize this wouldn't be possible for all games and it's a major hassle, but it's really the only option. It's best to only utilize save states for very casual use and at no time when it's crucial to keep them for long periods of time. Save state formats can change at any time depending on development. You might see an emulator/core keep its format throughout its lifespan, or you might see it change several times a year.

@rustymg Ooh, that's odd. I just use the joystick, if that doesn't work I have no idea what to suggest.

Thanks @dankcushions I didn't knew that I needed the parent rom. Problem solved. It's up and running. Now I can save my progress in Pacman.

Thank you all.
@mitu and @jonnykesh

You've been a great help.

Maybe your changes messed up your retroarch.cfg files. It might help if you give us your configuration for savestate_directory.

Can you run this and give us the output:
cd /opt/retropie/configs
grep -r 'savestate_directory' ./

I fixed my problem with the Y cable. The savestate are more faster, but it long.... So I have mounted my external hard drive manually by editing the fstab. All works but with Y cable only.

@matthimself no worries :) now get raising chocobos and cry when [REDACTED] ... or whatever happens on disc 2 (i forget!)