How-to Guide: Atari ST and STe Computing on the Raspberry Pi with RetroPie’s Hatari Emulator

PingSpike

Props for this guide man!

GrethTom

Amazing work their buddy, done quite a bit on Hatari myself. One thing I didn't see mentioned was launching straight into Save states which I have managed to do for all my games. Guide is on the Atari forum if interested/needed:

http://www.atari-forum.com/viewtopic.php?f=51&t=29605

RetroResolution

@GrethTom Thanks, that definitely sounds worth doing. I'll update my installation to get this running.
If you don't object I'd like to include your advice in the main guide (I'll probably mainly quote your information verbatim from the forum post you linked, citing you as the author)

RetroResolution

@PingSpike Thanks, that's great of you to say

RetroResolution

@senkun You're very welcome, great to hear that it's appreciated, makes it all worth while

RetroResolution

@herb_fargus Cheers! I'm still tweaking and updating the guide as I find out additional useful information!

GrethTom

@RetroResolution No problem at all buddy, feel free to use my info directly.

RetroResolution

@GrethTom Thanks; I've just adjusted my system to load save states - works like a charm. I just tweaked things slightly to run in hatari compatible mode with borders - I run a lot of demoscene productions!
I'm updating the guide now.
Thanks again for the brilliant tip

RetroResolution

Three updates to the guide on 28/29th April:

Added sections for:

Atari ST / STe Specific Keys
Hatari Keyboard Shortcuts
Direct Loading Save States From Emulation Station

RetroResolution

Another update to the guide on May 2nd:

Hatari's in-built video capture

I've now worked out how to resolve the AVI Recording : failed to open file error when trying to use Hatari's in-built video capture. The solution requires editing Retropie's emulator configuration entries.

The updated guide covers the available codecs, editing the config, has some observations regarding codecs and impact on the emulator, amongst other items.

Direct link to the updated section: Screen Capture Options

Pyjamarama

Ι opened up the hatari.cfg because I am trying to find a way to map F12 to my XBOX 360 pad (xboxdrv).

Is that possible or I am fighting a loosing battle? :)

If yes, how can I find the pad button codes?

That is part of the Joystick0 part of hatari.cfg which works like a dream

nKeyCodeUp = 1073741906
nKeyCodeDown = 1073741905
nKeyCodeLeft = 1073741904
nKeyCodeRight = 1073741903
nKeyCodeFire = 1073742052

This is the part with the keyboard shortcuts

[ShortcutsWithModifiers2]
keyOptions = 111
keyFullScreen = 102
keyMouseMode = 109
keyColdReset = 99
keyWarmReset = 114
keyScreenShot = 103
keyBossKey = 105
keyCursorEmu = 106
keyFastForward = 120
keyRecAnim = 97
keyRecSound = 121
keySound = 115
keyPause = 0
keyDebugger = 1073741896
keyQuit = 113
...

I want to find the 10 digit number to put in the keyQuit

Thank you

mediamogul

@Pyjamarama said in How-to Guide: Atari ST and STe Computing on the Raspberry Pi with RetroPie’s Hatari Emulator:

I am trying to find a way to map F12 to my XBOX 360 pad (xboxdrv)... I want to find the 10 digit number to put in the keyQuit.

'keyQuit' is listed as being the SDL key code 113. Checking against the reference list here, you'll find it being the letter 'Q'. However, Hatari requires it's hotkeys to use the 'ALTGR' (or 'Right Alt') modifier. So, if you're looking to add that to an xboxdrv command, it would like:

--ui-buttonmap back+start=KEY_RIGHTALT+KEY_Q

Seeing as how 'back' normally stands in for 'select' in xboxdrv, this mapping keeps with the convention of using the 'start' and 'select' buttons together to exit a program like is seen in RetroArch, but you could also map to a single button as well.

Edit: The SDL code for 'F12' can also be found on that reference link above and is 1073741893.

sroweuk

I've just tried to install Hatari but I cannot get it to run. I have the correct TOS but i cannot even get the Hatari config window to come up. I have set the emulator up to be "hatari-compatible", but when I check the runcommand.log file, it reports
"Parameters:
Executing: /opt/retropie/emulators/hatari/bin/hatari --confirm-quit 0 --statusbar 0 --zoom 1 -w --compatible 1 --timer-d 0 --borders 0 "/home/pi/RetroPie/roms/atarist/tos-2.06-uk.rom"
/opt/retropie/emulators/hatari/bin/hatari: error while loading shared libraries: libcapsimage.so.5: cannot open shared object file: No such file or directory"

I have tried both the binary install, as well as the source install. However, it does not appear to be copying the libcapsimage.so.5.1 file to my pi, as I cannot find it anywhere.

I have also tried doing this manually; built the shared file and copied it to the Hatari install directory, but still receive the same error.

Pi Model: 2 B
RetroPie Version Used: 4.1
Built From: Pre made SD Image on RetroPie website
USB Devices connected: WiFi Network, Wireless mouse, wired keyboard
Controller used: none
Error messages received: None on screen. Error in runcommand.log as above
Log found in /dev/shm/runcommand.log (if relevant): as above
Guide used: Power Without the Price: Atari ST and STe Computing on the Raspberry Pi with RetroPie’s Hatari Emulator
File:
Emulator: Hatari
Attachment of config files:
How to replicate the problem: As above

Andreas77

@RetroResolution
This is great, thank you. I was having some issues before I read this.
Cheers.

fumanxu

Hi
I 'm strugling with the same problem. In my case is a retropie with a gpi case, which at the end, is like a raspberry connected to a xbox 360 controller (retropie identifies the controler within the case as x360). My problem is that I'm not able to create the initial configuration (to map buttons, select the tos image, etc) since I cannot connect a keyboard to launch F12.

Please, could you give me details how you achieved to configure f12?

michel30

So for my understating.

You want the F12 key somewhere under a key under the controller for xbox 360?