Help

Requirements

There are two things required that are not packaged with Hataroid (due to copyright reasons).

  • TOS rom image (uncompressed - not in a zip file)

  • Disc images of titles you want to run

TOS rom image

Hataroid requires a TOS rom image to run. This is the equivalent of an operating system for the Atari ST/STE.

Unfortunately this is still under copyright by Atari so you will need to google for it if you don't have one.

Alternatively, you can use the excellent free alternative called EmuTOS (http://sourceforge.net/projects/emutos/). But note that compatibility may not be the same as using an original TOS rom.

Emu-TOS is now built in, so if you want to use it, you can toggle the option in the Settings preferences.

If you're using your own TOS image, please copy this to anywhere on your device.

Disc images

You will also need floppy disc roms/images of the programs you want to run. These can be in ST, MSA, DIM, or STX (pasti) formats.

Hataroid will also load the disc image if it's in a compressed zip archive (but the disk will be marked as read-only). If you want to write back to the disk, you need to extract it if it's in a zip file.

Copy the disc images to anywhere on your device just like you did with the TOS rom image.

Initial Setup

The first time you run Hataroid, you will get a prompt to setup the location of your TOS rom image.

This will bring you to the settings screen automatically.

From the settings screen:

- click on System

- click on TOS image (ST)

- select your TOS rom image from the file browser or tick the built-in Emu-TOS option (see Requirements above for more details).

- click your hardware 'back' button to exit the Systems settings and then 'back' again to exit the Main Settings screen

- click 'Yes' to reset the emulator when prompted

- the main screen will show and the system should load up to the familiar green of the GEM desktop

Basic Usage

An outline of the most common operations will be described here. More details can be found in the relevant sections.

Once you're familiar with the basic running of the emulator, you can tweak more advanced parameters to suit your own preferences.

Inserting a disc

- Click the soft menu ('three dots' button). The soft menu bar should pop up on the screen.

- Click the Atari folder (Disk) icon.

- Click Insert Floppy A

- Choose your disc image (ST/MSA/DIM/ZIP) file from the file browser

- Click 'YES' when prompted to reboot the ST

Resetting the ST

- Click the soft menu ('three dots' button). The soft menu bar should pop up on the screen.

- Click the reset icon.

- Click either Cold Reset to fully power off and on the ST or the Wam Reset to do a soft reset of the ST.

Toggling between the Mouse/Joystick

- Click the Mouse or Joystick icon on the top left of the screen to switch between using a mouse or the joystick. The on-screen buttons will automatically switch to the appropriate mode.

Bringing up the virtual keyboard.

- Click the keyboard icon on the top left of the screen to bring up the Virtual Keyboard.

- Once the keyboard is up, you can change the size either with the pre-defined presets (x123 button) or you can position and scale the keyboard yourself with the scale button.

Fast forward

Disc access is emulated accurately as well so load times may be a bit long. In these cases, you can click the 'Turbo' (running man) button on the top right of the screen to toggle fast forwarding through the slow bits.

Additional Features

Save State support

You can save and restore your current session at any time to your device.

There are 2 types of save states:

- normal save states which you save/restore through the soft menu

- auto saves (which automatically get saved/restored when you quit/start Hataroid)

If you're using an external input device, you can also map a key/button to save/restore to a normal save state slot (Quick Save shortcut).

To use save states, you must first setup where you want to store these save state files. On Android pre-Kit Kat, you can save anywhere on your internal or external storage devices. After Kit Kat, you can still save anywhere on your internal device, but you can only save to a pre-determined folder on your external storage device (eg a SD card).

To set where you want to save your files:

- Enter the settings menu (click the 'Soft Menu' (3 dots) buttons, then click 'Settings')

- Click the 'Storage' settings category

- Click 'Save State Folder' and select where you want to save your files from the file browser

- If you want to save to external SD card on Kit-Kat or newer, you can click the 'Save to Secondary External SD' option. Since this folder is chosen automatically by the Android system, the normal folder option will be greyed out).

To save/load a save state:

- Click the 'Soft Menu' (3 dots) button

- Click 'Save' or 'Load'

- Choose your save slot to save/load to/from.

MIDI support

Hataroid has built-in midi playback support that is synced in time with the emulation. As this is quite cpu intensive, you'll need a fast Android device to utilize this feature. There are some tweaks you can do to improve performance if you're having issues. These will be detailed below.

Currently Hataroid has General Midi (GM) support, but MT-32 emulation is planned for the future as well.

MIDI has been tested in various games (eg Police Quest II, Leisure Suit Larry 2 and 3, Bomb Jack, Karate Kid II, etc) as well as many music applications (such as EditTrack, Cubase, RealTime, Music Maker, OnStage, Band-in-a-Box, Jazz Guitarist, M, AEX, Notator, etc).

There is also experimental support for outputting directly to USB midi devices like keyboards and synths.

Enabling MIDI output

- Enter the settings menu (click the 'Soft Menu' (3 dots) buttons, then click 'Settings')

- Click the 'MIDI' settings category

- Click the 'Enable MIDI out' option.

Custom Sound Fonts

Hataroid includes a small and fast, good quality GM sound font. But you can use any sound font you want (eg if you want higher quality sounds, or different instrument sets).

To enable your own custom sound font:

- Enter the settings menu (click the 'Soft Menu' (3 dots) buttons, then click 'Settings')

- Click the 'MIDI' settings category

- Click 'Use your own SoundFont' option.

- Click 'Custom SoundFont (.sf2) and select your soundfont from the file browser.

Synth Quality/Performance Settings

The default options have been setup for a good trade-off between performance and quality. There are a few settings you can tweak if you have a fast Android device.

  • Reverb and Chorus

    • If your soundfont supports reverb or chorus, you can enable these options to improve the sound quality of the MIDI instruments.

    • Note: The built-in soundfont doesn't support these, so it will have no effect

  • Interpolation Quality

    • Sets how the synth will blend together samples from an instrument.

    • 4th Order interpolation is the recommended option for fast devices, but Linear interpolation is a ok for general use.

  • Max Polyphony

    • The number of simultaneous voices that can be played. For games, this can be reduced a lot if you're having performance issues.

Additional Performance Tweaks

Apart from the above settings, if you're still having performance issues (eg stuttering sound), there are some other options you can tweak to try to improve performance.

  • Settings -> MIDI -> Mute ST Sound

    • This will output only MIDI sound. This will help a little with performance

  • Settings -> Sound -> Playback Quality

    • This will have the biggest impact on performance. 22kHz is the default setting. Reducing to 11kHz will make a big difference in performance. Conversely, if you have a good device, I would recommended pumping this up to 44kHz.

  • Settings -> Sound -> Device sound buffer size

    • Try increasing the sound buffer (at the cost of extra latency)

  • Settings -> Display -> Show borders

    • Try disabling the screen borders. This will help a little with performance.

  • Settings -> Storage -> Legacy Floppy Emulation

    • This will use the older floppy emulation which is less accurate, but faster. Pasti disk images are not supported in this mode.

Instrument Patches

General MIDI was still in it's infancy when the ST was released. As such many MIDI devices at that time did not conform fully to the standard or have the full feature set. A lot of songs authored in MIDI packages were setup for a specific device and/or used sysex messages to setup the instrument before playing the song.

In Hataroid, you can map specific instruments to each of the MIDI channels and send those up as a patch to more conveniently switch instruments. This will also help with software such as games which had no way to setup the patches themselves.

To setup and send an instrument patch:

  • Settings -> MIDI -> Load Instrument Patches

  • Setup your instrument/channel mapping

  • Click 'Send to Synth' to send the patch to the Synthesizer

Karate Kid II Tweaks

Karate Kid II supports MIDI output, but it was designed for a Casio CZ-101 synthesizer. It also seems like it was setup using a synth that was not tuned correctly so the MIDI output is off-key compared to the ST sound chip by a tone.

You can tweak the MIDI options yourself to get Karate Kid II sounding nice, but there is also an 'Auto' option which will automatically setup all the required options for you.

  • Settings -> MIDI -> Auto-Setup options for Karate Kid II

This will automically set the following options:

  • Mute ST sound output (sounds better with just MIDI instruments)

  • Send an instrument patch set to the Synthesizer that maps the instruments used by Karate Kid II

  • Ignore program changes (Karate Kid 2 resets the instruments on the title screen after playing the tune. This will ignore those changes and keep the instruments that we've setup in the instrument patches)

  • Transpose key by 2 semi-tones.

Hardware USB MIDI support (Experimental)

This is an experimental feature that allows inputting and outputting MIDI info to a hardware MIDI device via a USB Host cable.

A fast device is required and there will be lag due to emulation <-> os <-> real device.

The internal software synthesizer will be automatically disabled if USB Midi output is enabled.

UI Button Configuration

You can change the sizes of the on-screen buttons if they are too large or too small for your screen. They can also be hidden or made more transparent if you want. The future plan is to have these completely dynamic so you can tweak the sizes of individual buttons and be able to move them around anywhere on the screen.

You can also edit which shortcut buttons are available on the main screen.

These can be all be accessed through

  • Settings -> Input

Sizeable button groups

  • Joystick D-Pad

  • Joystick Fire button

  • Vertical layout shortcut buttons (left and right of screen)

  • Horizontal layout shortcut buttons (bottom of screen)

Transparency groups

  • On-Screen Transparency (overall transparency of all the buttons)

  • On-Screen Joystick Transparency (transparency of just the Joystick itself)

Hideable button groups

  • All on-screen buttons

  • Joystick

  • Horizontal and vertical shortcut keys

Configuring shortcut keys

You can configure which shortcut keys you want in the horizontal and vertical shortcut groups via:

  • Settings -> Input -> Configure Shortcut Keys

Hardware Input Devices

Hataroid supports external input devices like Mice, Keyboards and Joysticks (either through Bluetooth or USB).

Currently Joystick and Keyboards must work through the IME (Input Method) Android drivers.

Joysticks and Keyboards

To use hardware Joysticks and Keyboards, you must first enable them in your Android System Input Methods and then you can re-map the keys if you want (or just use the default mapping).

  • Switch to the correct Android System Input Device

    • Settings -> Input -> Switch Current Input Device

  • Enable the external input device

    • Settings -> Input -> Use Input Method Device

  • Re-map keys (if desired)

    • Settings -> Input -> Configure Input Mapping

Mice

Hardware mice, once paired with your Android device will just work automatically.

One issue currently is that Android has no way of hiding the system cursor (unless you are on a rooted device). This has the side effect of having two cursors (the emulated Atari one and the Android system one) displayed at the same time. There is nothing I can do about this at the current time.

If you're using a TV Android device, you may have to enable the Old Android Hardware Mouse Behaviour in Settings -> Input if the mouse does not behave like you would normally expect.

Game Database Support

Hataroid has built-in Game Database support. What this means is that you can name your Disc Images anything you like and if the disc is in the database, you can see the proper titles on the Disc rather than a filename. Discs with multiple titles in it will automatically be shown as well.

Eg.

  • Disc Name: A200.ST

  • Titles on Disc: Some Game 1, Some Game 2, Some Game 3

  • File Browser will show:

    • Some Game 1 (A200.ST)

    • Some Game 2 (A200.ST)

    • Some Game 3 (A200.ST)

To use the database:

  • When selecting a Disc in the file browser

  • Click the Refresh DB button

  • Hataroid will scan the current folder and any subfolders (including Zipped files) for any matching discs.

  • The file browser will automatically display the titles instead of the file name if there are any matches

If you want to clear the database, just click the Clear DB button and you will see the normal file names again.

Hard Drive support

There is support for three different types of Hard Disks in Hataroid.

GEMDOS emulation is the easiest way as you can mount any Android folder on your device as a Hard Disk.

ACSI and IDE Hard Discs

ACSI and IDE hard discs use an image file similar to normal Disc images. To use these

  • You just need to attach the hard drive

    • Settings -> Storage -> Attach ACSI / IDE Master / IDE Slave

  • Select the Hard Drive image from the file browser

    • Settings -> Storage -> ACSI image / IDE Master Imager / IDE Slave Image

For more information on ACSI and IDE hard disk images see (http://hg.tuxfamily.org/mercurialroot/hatari/hatari/raw-file/tip/doc/manual.html#Hard_disk_support)

GEMDOS Hard Drive Emulation

You can use any folder on your Android device as a Hard Disk. So any files in that folder will automatically show up on the ST. This is a convenient way to move files between your ST and Android device or run ST programs directly off your Android Device.

To enable GEMDOS hard drive emulation:

  • Settings -> Storage -> Attach GEMDOS drive

  • Select the folder you want as the root of your hard drive on the ST

    • Settings ->Storage -> GEMDOS drive directory

  • If you want to be able to write to the Hard Disk, disable the write protection

    • Settings -> Storage -> GEMDOS drive write protection

Main Screen

This is the main screen once you've setup your TOS image and your main point of interaction with the emulator.

1. Keyboard Toggle

This will switch the UI to the on-screen keyboard. You can interact with the ST just like you were typing on a real ST keyboard.

The keyboard is fully sizeable and positionable. There are 3 preset sizes for convenience.

The buttons on the top left function as follows:

  • Toggle the Keyboard (will hide the keyboard and will show the normal on-screen buttons again)

  • Free scale/position

    • This button will allow you pinch/zoom to scale the keyboard up or down in size

    • Drag to position the keyboard

    • While in this mode, you can't type on the keyboard. Toggle this button off to be able to type again.

  • Preset sizes (x123)

    • There are 3 preset sizes. You can toggle between them by pressing this button

2. Screen Adjust

This button will allow you to size and position the ST screen anywhere you want. You can pinch/zoom to size the screen and drag to move the screen.

There are also a few presets (the x123 button), you can cycle between.

To exit this mode, click the top left toggle button again.

3. Mouse/Joystick Toggle

Clicking this button will switch the UI between the on-screen Joystick and Mouse controls.

4. Joystick/mouse controls

In Joystick mode there will be a D-PAD and a fire button.

In Mouse Mode there will be a Left mouse button and a Right mouse button. You can press both buttons simultaneously by clicking in-between the L and R buttons. The mouse can be moved by dragging your finger along the screen.

5. Turbo button

You can speed up the ST temporarily by toggling this button. This is great for skipping past loading screens or cut-scenes which aren't skippable.

6. Quick keys

These are shortcut keys that are frequently used (without having to bring up the keyboard). You can map these to any key you like or hide them if they are in the way.

7. Soft Menu button

This is an important button if your device does not have a hardware menu button. This button brings up the Soft Menu from which you can perform oprerations like changing discs or configuring the emulator through the Settings screen. You can hide this button if you have a hardware menu button on your device.

Soft Menu

The soft menu bar is brought up when you click the soft menu button (the 3 dots). If you have a device with a hardware soft menu button, you can use that as well to bring up this menu.

Once this menu is up, you can perform various operations like changing discs, using save states, resetting the ST and entering the Settings Screen to configure the emulator.

Disk

    • Insert Floppy A / B

    • This will bring up the file browser and let you select a disc into insert into the floppy drive. Once inserted, you can either reset the ST or keep running (eg for multiple disc titles).

    • If there is a disc already inserted, it will be automatically ejected so you don't have to manually eject it first.

    • Eject Floppy A / B

    • Ejects the inserted disc from the floppy drive

Reset

    • Cold Reset

    • This will perform a Cold Reset of the ST (like pressing the power button on the ST)

    • Warm Reset

    • This will perform a Warm Reset of the ST (like pressing the reset button on the ST)

Save/Load

This button will allow you to manage your save states

    • Save

    • This will bring up the save state chooser where you can select which slot you want to save the current state of the emulator

    • Load

    • This will bring up the save state chooser where you can select a save slot you want to load

    • Delete

    • This will bring up the save state chooser and allow you to delete save slots you no longer want to keep

    • Select Quick Save Slot

    • This selects the save slot you want to use for the Quick Save functionality (save/load through a mapped button on an external input device)

Settings

Brings up the settings screen where you can configure the emulator to your liking.

Pause/Unpause

Pause or unpause the emulation.

Quit

Quits the emulator and auto saves the current state (if enabled).

Settings

The settings screen is where you configure all aspects of the emulator. A brief rundown of each setting will be described here. More detailed info will be added as needed.

Input

    • Switch Current Input Device

    • Switch the current input device from the Android System menu

    • Use Input Method Device

    • Enables receiving input from the chosen Input Method Device

    • Configure Input Mapping

    • Configure which input keys map to which emulator keys

  • ST Keyboard Region

    • Switch between English / French / German virtual keyboard overlays

      • Note: You need to use the correct region TOS rom for this to work properly.

    • On-screen Joystick Port

    • Select which joystick port the on-screen joystick will control. The default ST joystick port is ST Joystick 1.

  • Arcade-style Virtual Joystick

    • Virtual joystick simulates an eight directional arcade stick

  • Floating (Arcade Virtual Joystick)

    • Virtual Joystick will 'float' on the screen.

    • Center of joystick will be set to the finger position on touch.

    • Joystick will disappear when finger is lifted off screen.

  • Dead-zone (Arcade Virtual Joystick)

    • Amount of movement from center of joystick before movement is detected.

  • Diagonal Sensitivity (Arcade Virtual Joystick)

    • Detect region for diagonal movement

    • 0% = no diagonal movement possible

    • 100% = only diagonal movements possible

    • Autofire

    • Toggles auto fire

    • Map Arrow Keys

    • On-screen joystick presses map to the Arrow Keys and Space on the Keyboard. This is useful for some menu disks which use the cursor keys to move the avatar (instead of having to use the on-screen keyboard).

    • Size of On Screen Joystick

    • Adjusts the size of the on-screen virtual joystick

    • Size of On Screen Joystick Fire Button

    • Adjusts the size of the on-screen virtual joystick fire button

    • Mouse Button Emulation Type

    • Direct (Touch)

      • Experimental feature where you can tap to Left click and tap with two fingers (in succession) like on a MacBook to Right click

      • Buttons (On-Screen)

        • Uses on-screen buttons you can press for Left or Right mouse button

    • Mouse Emulation Speed

      • Adjust the speed of the on-screen mouse.

      • 1x = finger movement mirrors cursor movement

      • 2x = cursor moves at twice the speed of the finger movement

    • Old Android hardware mouse behaviour

    • Hardware mice can click on-screen controls, but won't detect normal mouse clicks, requires holding LMB to move cursor

    • On Screen Transparency

    • Adjusts the overall transparency of the on-screen controls

    • On Screen Joystick Transparency

    • Adjusts the transparency of the on-screen joystick only

  • Auto hide on-screen UI

    • Automatically hides all on-screen UI if no touches detected.

    • UI will automatically show again by touching anywhere on the screen.

    • Hide all on screen UI

    • Hides all on screen controls

    • Hide Joystick

      • Hides the on-screen joystick

    • Hide extra joystick keys

    • Hides the extra shortcut keys on the bottom right of the screen

    • Hide shortcut keys

    • Hides the shortcut keys on the top right of the screen

    • Configure Shortcut Keys

    • Map or hide the on-screen shortcut buttons to different keys

    • Obession mode keys

    • Swaps the on-screen joystick out with keys suited for the pinball game Obsession

    • On-screen key size (vertical / horizontal / width / height)

    • Adjusts the size of the vertical and horizontal shortcut key groups

System

    • CPU Type

    • Sets the emulated cpu type.

    • ST and STE should use the default to 68000. The other modes are for TT and Falcon emulation.

    • Machine Type

    • Sets the emulated machine type.

    • Falcon and TT support are planned for the future

    • Switching between these will automatically use the corresponding TOS setting for each machine type.

    • CPU clock

    • Sets the speed of the emulated system.

    • ST and STE should run at 8Mhz.

    • You can increase the speed (eg. for some 3D games), but not all titles will work correctly at higher clock speeds.

    • NOTE: Notator currently requires the speed to be set at 16Mhz to work correctly. This is an issue with the emulation that will hopefully be resolved at some point in the future.

    • Memory

    • Adjusts the size of the memory on the emulated system.

    • 1Mb is the most compatible. A few titles may need to be set to 512kb to work.

    • Some titles will work with more memory

  • Use Built-in Emu-TOS

    • Use the free, open-source TOS image that is built into the emulator

    • TOS image (ST)

    • Brings up the file browser to select the TOS image that will be used when the system is set to ST mode.

    • The recommended TOS version for ST emulation is 1.02 UK

    • TOS image (STE)

    • Brings up the file browser to select the TOS image that will be used when the system is set to STE mode.

    • The recommended TOS version for STE emulation is 1.62 UK

    • TOS image (Falcon)

    • Planned feature (not currently supported)

    • Slower but more compatible CPU

    • Enables 68k address errors and CPU prefetch buffer but is slightly slower

    • Blitter emulation

    • Toggles emulation of the blitter chip (ST only).

    • This is always enabled on STE

    • Real time clock emulation

    • Emulates a RTC (using the host for the time)

    • Requires TOS >= 1.02

    • Patch Timer-D

    • Modifies the MFP timer D rate for improved performance

    • Can be left on for most titles

    • May cause incompatibilities on a few titles (eg super sprint music plays too fast)

    • Patch TOS for faster boot

    • By-passes the boot memory test

    • Printer Emulation

      • Planned feature (not currently supported)

    • RS232 emulation

    • Planned feature (not currently supported)

Display

    • Frame skip

    • Changes how many emulated ST screens get drawn per emulation frame.

    • AUTO will automatically drop frames to keep the ST running at 100%

    • Indicators

    • Statusbar

      • Shows a status bar with emulatoin information at the bottom of the screen

    • Drive LED

      • Shows drive activity as a green flashing icon at the top right of the screen

    • Bi-linear filter

    • Smooth the emulated screen output

    • Full screen

    • Stretch the emulated screen to the full width and height of the Android device (may not be aspect correct)

    • Keep screen awake

    • Keeps the Android's screen on without any user input. Useful for watching demos or long cutscenes.

    • Shader Effect

    • Adds rendering effects which simulate a CRT display

      • Scanline [Horz]:

        • Adds vertical scanlines

      • Scanline [Horz+Vert]:

        • Adds horizontal and vertical scanlines

      • CRT-Geom Curved:

        • Simulates the beam of a CRT display with curvature

        • Needs a fast gpu

      • CRT-Geom Flat:

        • Simulates the beam of a CRT display without any curvature

        • Needs a fast gpu

    • Atari monitor type

    • Changes what monitor type the ST is attached to

    • Mono

      • Monochrome high-res monitor

    • RGB/TV

      • Low-res color monitor/tv

    • VGA

      • High-res color monitor (not currently supported)

    • Show borders

    • Shows the extended screen borders on the emulated screen.

    • Slightly faster if disabled.

    • Some games and most demos will make use of the borders

    • Use extended VDI screen

    • Emulates an extended graphics card to allow higher resolutions

    • Planned feature (not currently supported)

    • Extended VDI resolution

    • Planned feature (not currently supported)

    • Extended VDI colors

    • Planned feature (not currently supported)

Sound

    • Device sound buffer size

    • Adjust the buffer size of the emulated sound output. Larger buffer will increase latency but reduce glitches if your device can't keep up

    • Sound

    • Toggles sound emulation. (Faster when off)

    • Sound synchronize

    • Improve sound latency by adjusting video emulation to match audio output.

    • Playback quality

    • Adjust the quality of the emulated audio output.

    • 22050 Hz is a good balance between quality and performance.

    • 44100 Hz is recommended if you have a relatively good device

  • Disk Drive Sounds

    • Enables the simulated sounds from the disk drive

  • Disk Drive Sounds Volume

    • Change the volume of the simulated disk sounds

    • YM voices mixing

    • The function used to mix the 3 YM channels.

    • Use ST table or Math model for more accurate ST emulation

    • Downmix stereo->mono

    • Downmix the audio output from stereo to mono

Storage

    • Save State Folder

    • This is required if you want to use save states

    • Select the folder from the file browser where you want to put your save states.

    • If you're using KIT KAT or newer, this can only be on internal storage. If you want to use external storage, enable the Save To Secondary External SD option.

    • Auto save on quit

    • Automatically saves the session on quit and restores on load. This is saved separately from normal save slots

    • Save to Secondary External SD (KIT KAT+)

    • Required option if you're using KIT KAT or newer versions of Android.

    • Saves to the application folder on the External SD Card (folder is pre-determined by the Android OS)

    • Enable Drive A/B

    • Enables the disk drive in the system. Some demos require Drive B to be disabled.

    • Auto insert B

    • Automatically detect and insert second floppy disk

    • Disc must be named with a/b at the end (eg game_a.ST and game_b.st)

    • Fast floppy access

    • Speed up floppy disc access (may cause incompatibilities)

  • Legacy Floppy Emulation

    • Enables the old floppy emulation code with is faster, but less accurate. Pasti disks are not supported in this mode.

    • Write protection

    • Enable/Disable write access to the floppy disc.

    • Write access will only work if the disc is not inside a Zip file.

    • Attach ACSI HD

    • Enable ACSI HD emulation.

    • ACSI HD image

    • The Hard Disk image used for ACSI emulation. Click this to select the image from the file browser.

    • Attach IDE master

    • Enable and connect the IDE Master HD to the emulated system

    • IDE HD master image

    • The Hard Disk image used for the IDE Master. Click this to select the image from the file browser.

    • Attach IDE Slave

    • Enable and connect the IDE Slave HD to the emulated system.

    • IDE HD slave image

    • The Hard Disk image used for the IDE Slave. Click this to select the image from the file browser.

    • Attach GEMDOS drive (Use local folder as hard drive)

    • Mount a local folder on your Android device as a hard drive

    • GEMDOS drive directory

    • Click this to select the folder you want to use as the Hard Disk root.

    • GEMDOS drive write protection

    • Enable/Disable write access to the folder that is used as the emulated Hard Disk.

    • Boot from HD

    • Automatically executes the AUTO folder on the hard disk

    • Cartridge image

    • Planned feature (not currently supported)

MIDI

    • Enable MIDI out

    • Enable's MIDI output

    • This is cpu intensive so you'll need a good device to use this.

    • See the MIDI section above for more information.

    • Reset MIDI synth on ST Reset

    • Reset the MIDI synth when the ST is reset by the user

    • Mute ST Sound

    • Mute the ST sound output (allows MIDI output exclusively)

    • Use your own SoundFont

    • Use your own sound font instead of the built-in one.

    • Custom SoundFont (.sf2) Soundback

    • Click here to select the sound font you want to use.

    • Support Reverb

    • Faster if disabled. (Reverb compatible SoundFont required)

    • Support Chorus

    • Faster if disabled. (Chorus compatible SoundFont required)

    • Interpolation Quality

    • Interpolation method when blending between the instrument samples

    • Max Polyphony

    • Max number of simultaneous voices

    • Volume Gain

    • If the MIDI synth is too soft you can change the amplification of the the MIDI output

    • Note that clipping may occur if you set this too high

    • Load Instrument Patches

    • Setup and send program channel changes to the MIDI device

    • Load Drum Patches

    • Setup and send drum configurations to the MIDI device

    • Planned feature (not currently supported)

    • Ignore Midi Program Changes

    • Ignore program changes sent to the synth (eg Karate Kid II sends program changes that aren't mapped nicely to GM instruments)

    • Transpose Keys (semi-tones)

    • Transpose the midi output (eg Karate Kid 2 is actually tuned incorrectly)

    • Auto-Setup options for Karate Kid 2

    • Automatically setup recommended options for Karate Kid 2 (transpose, ignore program changes and instrument patches)

    • Output to USB MIDI device

    • Send midi output from emulator to a hardware USB MIDI device

    • Input from USB MIDI device

    • Receive midi input from a hardware USB MIDI device

Device

  • Force Android TV Mode

    • If your Android TV device is not automatically detected or you want to use Hataroid only with a gamepad, you can force this mode on.

    • Immersive Mode

    • Enable Immersive Mode (Android 4.4 Kit Kat or newer required)

    • Toggle access to developer options

    • Enable experimental (potentially unstable) options

External Frontend Support

Preliminary basic support for launching Hataroid from another frontend is available.

The activity to launch is com.RetroSoft.Hataroid.HataroidActivity

The following extra parameters are available (more can be added if requested):

  • "_argFloppyA"

    • Floppy Disk A to insert on startup (can be a zip file or a raw st disk image)

  • "_argFloppyAZipPath" (Optional)

    • if _argFloppyA is a zip file with multiple disk images inside it, you can specify the path to the specific disk image within the zip archive