@AlexMurphy

However, exophase will do whatever he wants regardless.

True, and we shouldn't go around walking on eggshells, but a consideration to his wishes regarding the beta certainly doesn't seem inappropriate.

No additional work has been done on the Pi version of DraStic since the Beta as far as I know.

That's tough to gauge. He maintains that his work there will resume when he gets time. Plus, we really don't know what's been done so far. DraStic is normally paid software on most platforms and I'm sure they get a higher priority.

Anyone been in contact with him?

He's remained quiet. There are a few others that have commented on the issue here as well.

@rridenour can you show a way to reproduce your issue?

@rsimmy it should be permanent. Have you moved the configs into another device anything? Or any custom scripts? Did you install RetroPie under a normal user instead of root?

@edmaul69 It keeps turning itself off. Like I turn it on, exit, but when I come back it's turned off. I've even gone into retroarch.cfg to turn it on, but it still turns itself off.

How did you sort it? I'm having the exact same problem

wait, sorry i needed to restart retropie, it seems to be up now. thank you

@BuZz Thanks for the insight here. So installing then uninstalling the PS3 drivers had fixed the permission issues. I was able to attach the controller and configure the inputs. Thanks!! We can mark this one solved.

@jrhessey I updated the wiki :)

You can mark this SOLVED! I remembered I was following another site's suggestion on creating ".SH" files to automatically launch games in DOSBox without having to manually type the commands. Along the way, I had modified the es_systems.cfg file to give it an entry so it would show as an emulator because it wasn't coming up after installing DOSBox.

It turns out, there's more than one es_systems.cfg file. The one I posted above was in the ETC path. I found another one under /opt/retropie/configs/all/emulationstation/

When I opened it up, I guess I had somehow split the line:

<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ pc %ROM%</command>

into this:

<command>/opt/retropie/supplementary/ runcommand/runcommand.sh 0 _SYS_ pc %ROM% </command>

Once I backspaced each separation so it was on one line, it worked! Well, the "+Start DOSBox" entry works, but the ".SH" scripts I made do not launch the games properly, so that will be my next mission. Thanks for your help BuZz.

Not yet - I will update https://github.com/RetroPie/RetroPie-Setup/issues/1696 when it is done.

@edmaul69 said in DOSBox - saving? Write permissions...?:

@BuZz the problem i have with dosbox is you get a "disk is write protected" error if you dont have better permissions on the right files, but how can you tell which files are the save files that need more permissions or not? I agree with you that you dont want to do it with everything but in the case of dosbox i dont know any way around it. And games wont even run for me if i dont give more permissions to the .exe files.

I would need to see some example of a path to advise (showing the current permissions).

@Joebo happy to help - glad you got it working