Have you tried using the Core input remapping menu to re-configure the input ?

@jimmyfromthebay

There is nothing wrong with the lr-atari800 build Did you put the right BIOS roms where they need to be? Are you running good ROMs. Make sure to check what's in the ROM files and not that they are double zipped...some downloads have that issue

Also..did you follow this?

once you have the correct BIOS files in place and the emulator(s) working. I highly suggest taking some time to go through this build setup for lr-atari800/5200.

Without it, your systems will work, but look nothing like they should, especially the a800 side.

https://retropie.org.uk/forum/topic/22392/lr-atari800-5200-artifacting-basic-and-other-guidance

@jamrom2 I did, but that doesn’t give me the option of choosing keyboard keys when I go to the config.

Got it working. This required a visit to Atari Age to understand what was going on.

There are some protections in A800 disks that lr-Atari800 can't get around but Altarri can. This was one of them, hence the odd error message. The emulator reads the disk, but it's not jumping over the sector of copy protection.

I was graciously given a "newer" version of CA that had the protections removed.

The underlying Linux operating system that RetroPie runs on top of is intrinsically multiuser.
You only need a free TeleTYpe program (I recomment putty for Windows) to gain access from your laptop in the same way as WinSCP does to move files.

Username pi - Password raspberry
The pi user does NOT have administrator rights, but the 'run as super user' keyword "sudo" can be used in front of any commands that needs them (no admin password required).

Make the terminal window as big as you need and use the nano editor to change configurations.

bye.

@grand_national to exit Atari 800 standalone emulator you have to use the keyboard (F9). F1 enters the configuration. Only retroarch emulators and a couple of standalone emulators like amiberry and mupen64 support exiting with the select+start combination. But the standalone Atari 800 emulator is a lot more functional than the libretro core.

I don't know any settings to make it start in Game Focus mode by default - not sure it is possible.

EDIT: you can install the standalone atari800 emulator and use the runcommand launch menu to use it for text adventure games.

@tpr said in Question about Multi-Disc Consoles:

Going back to the Sega CD question, what are my current options? Do I just have to have all the discs listed in the rom directory?

Yes, since no SegaCD emulator supports .m3u files at the moment, so you'll have to load the game directly from a disc.

@mitu Ok, I'll give Skyscraper a try.

It looks like they're listed under "Atari 8-bit" instead of calling it Atari 800, maybe because it included all versions of the 400/800 system?

Thanks for fishing this out, and hopefully will be an easy fix for you and the team.

Best,

JR

@macraem I have the same problem. Were you able to find any solution?

Ok, it was me not saving the config for the Rom in the Options menu...

Now it works perfectly.

Thanks again.

Found an issue with source code. Pull request are pending.
https://github.com/libretro/libretro-atari800/pull/38

marianob85 created this issue in libretro/libretro-atari800 closed Fix for not working virtual keyboard #38

@mitu I solved it by zipping the roms

Ok I just did one more test and I downloaded the Atari800 core from the retropie setup and it does have perfect sound quality (audio coming from my left speaker only, though), and it uses the same BIOs files than the lr-atari800 core. Is this normal? I want to use the lr-atari800 because of the keyboard being mapped to the joypad, or maybe if it is a way to get into the Retroarch menu in Atari800, and the set up my gamepad being Atari Joystick?

Thanks in advance!

I use these cool devices on icode.com. They allow you to have up to 4 paddles or joysticks connected to you PC via usb. There is even a bluetooth version.

Atari paddles and joysticks usb adapter

This is the solution of the problem:

Step 1

Launch any game

If the game starts automatically then everything is OK, otherwise one of these 2 conditions may occur:

1. Black screen

2.
2a. Atari logo and "Copyright 19 Atari" text
2b. Crash screen: "!!! The Atari computer has crashed !!!" and a series of options

If condition 1 occurs, you must do this:
a. Press F5 if you have the keyboard inserted, or X button on the joypad
The system will perform a "warm reset" and at this point you will arrive at condition 2.

Step 2

If you have the keyboard connected: press ALT + C, If you only have the joypad (not recommended, because many games require the keyboard), click A with the joypad on "Menu" and in the next menu click A with the joypad on "Cartridge Managment" Select "Cartridge: none" and press the enter key (or A with the joypad) (there may already be the name of the rom instead of "none", but it does not matter)
Now you should see the directory (atari800) with all the roms, and the rom you have chosen in the emulation station menu already selected Press the enter key (or A with the jpypad) on that same rom
*
A new menu will open: "Select Cartridge Type" Select "Standard XX KB Cartridge" (where XX may vary with 8, 16, 32 or 64 depending on the selected rom) and press the enter key (or A with the joypad) Then you will return to the menu: "Cartridge Management", press ESC and again ESC (or X and again X with the joypad)

The game will be launched!

* it may happen that the menu: "Select Cartridge Type" does not appear. No fear, just press ESC and again ESC (or X and again X with the jpypad) to launch the game.

The stand-alone Atari800 emulator, not the Retroarch lr-atari800, you can goto the menu (F1), then "Display Settings", then scroll down to "Color preset" and select "Vibrant". That fixed the washed-out look, for me. There is also a manual "Saturation" setting, under the color preset, so you can further increase the saturation, if required. Mine is set to 0.28.

@SpudsMcToole said in Is it possible to reinstall an older version of an emulator?:

Fortunately, in the last possible attempt before having to type lines like THAT, I got it all working...

Very nice! Glad to hear everything's working now. Something to keep in mind for future endeavors is that no one actually types command lines like the ones listed above, as there would be too much margin for error. For situations like that, a quick copy and paste into a remote ssh session will save finger cramping and your sanity.