@pmdci you have to open the Retroarch menu when you are running a game. Go to Quick Menu, Options, then Controls. Set the player 1 to Atari joystick (or something similar to that). That will allow you to use the start key on your controller.

Same for the Atari 800 if you are running that portion of the emulator.

@JuanZt set it, then choose Save Core Override. Or, find the line in the .cfg and manually edit it.

Wanted to say THANKS for the "menu_enable_widgets" fix and to share some more info.

First, it was interesting that ROMs were fine and that ATR disks were all failing.

I tracked down the segmentation violation in the /dev/shm/run command.log:

/opt/retropie/supplementary/runcommand/runcommand.sh: line 1283: 31257 Segmentation fault /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-atari800/atari800_libretro.so --config /opt/retropie/configs/atari800/retroarch.cfg "/home/pi/RetroPie/roms/atari800/Mule.atr" --verbose --appendconfig /dev/shm/retroarch.cfg

I took a look at line 1283:

eval $COMMAND </dev/tty &>>"$LOG"

All this is doing is running the right command, explicitly getting input from the tty, and tying file descriptors to the log.

I ran the command from the console and it worked fine without redirecting STDIN/STDERR. It also worked fine just redirecting STDOUT (fd 1). But every time I redirected STDERR (fd 2), I got a segmentation violation.

Not sure what exactly the widgets have to do with this, but apparently they do. If anybody wants a strace of this I would be happy to provide.

I hope this is helpful, and again, thanks for the fix!

lr-atari800 issues are almost always challenges with quirks of the original hardware, especially the fact that there are many versions. This is where all the things like cart autodetect for 5200, dealing with alternate versions of the OS, dealing with BASIC or not, etc, all come from. You actually run into many of these on the actual original hardware too (the infamous "Translator disk" for example).

Basic stuff like controls is now pretty sorted, as of last year, except for the 5200's analog stick in a small handful of games.

This isn't to say that there aren't some emu issues -- there definitely are, especially with the slightly older version of the mu that Retroarch uses.

Things like Atari 5200 cart autodetect don't work reliably because the person who coded it originally tied the autodetect table to filename, for example. But given that there are many alternate dumps of ROMs with and without headers, even a checksoum solution would need to be pretty extensive.

I strongly suggest people who are interested in Atari 8 bit emulation take a look at the guides in my signature, and in particular use the script I wrote. It makes most everything pretty seamless on the computers, and walks you through building a 5200 library that just loads without fiddling with anything.

@ciano said in Atari 5200 Not Working - "Atari800/OS Emulation Halted":

@Thorr69 Thank you so much!

Happy to help. =)

Hi, I asked the developer of lr-caprice32 if he would add save states to the core and he has now kindly implemented them.

https://github.com/libretro/libretro-cap32/commit/8dc1fe206abc480cfd55c419a4f24f227495488b

You can enable this functionality by running the "update from source" option for lr-caprice32 under RetroPie setup.

SOLVED: In Retroach, internal resolution must be 336 x 240 !

Just good to know

0_1523649048171_FullSizeRender.jpg

@davidgrohl

Learn how to use SFTP or Samba-Shares.
https://retropie.org.uk/docs/Transferring-Roms/#sftp
https://retropie.org.uk/docs/Transferring-Roms/#samba-shares If using SFTP, go to /opt/retropie/configs/all/atari5200/retroarch.cfg, or if using Samba-Shares, go to configs/all/atari5200/retroarch.cfg. Add core_options_path = "/opt/retropie/configs/atari5200/retroarch-core-options.cfg" to the retroarch.cfg above the #include "/opt/retropie/configs/all/retroarch.cfg" line.

RetroPie has some systems flagged as main or core systems, and as you've now discovered, the Atari 800 and 5200 are not part of that group. Going through the menu you will find it, and many others, in the optional systems menu. That process will add the emulator and create the necessary ROM folders.

The Binary option is always the safest and easiest way to install an emulator. Installing from Source is more advanced and only needed if you're after a recent code change to that emulator, but you run a higher risk of encountering bugs.