Jump to content

Archived

This topic is now archived and is closed to further replies.

thatman84

(Tutorial) Android Atari 5200 & RetroArch Setup

Recommended Posts

MAME Atari 5200 Setup with RetroArch Android

 

How to get Atari 5200 and other systems working on Nvidia Shield with Retroarch “Arcade (MAME)” core

 

Limits

  •           Everything RetroArch is subject to change without warning, cores break and improve and RetroArch is constantly evolving. The exact same goes for MAME     but this is more consistent.

  •        You must have the correct roms and BIOS files that MAME emulator is expecting.
  • ·        They must all be named as MAME requires

Note I have assumed you are familiar with setting systems up in Hyperspin and are familiar with Retroarch. Native RetroArch and RetroArch launched from Hyperspin use separate configuration files. Please search around for the topics relating to this issue.

 

Tested on:-

 

  • ·         Nvidia Shield TV PRO v3.2
  • ·         RetroArch 1.3.6 Stable Play Store app
  • ·         Arcade (MAME) Core 0.174 (Also known as MAME Git core)

 

 

What’s Covered...

 

 

  •                 Getting Atari 5200 setup to work with Hyperspin Start to Finish!!

 

 

Quick Steps...

 

  1. Grab the PC version of MAME and extract the files and folders
  2. Place your roms and BIOS in the correct place
  3. Set your RetroArch System/BIOS directory
  4. Build your RetroArch “System/BIOS” directory with above files/folder
  5. Create a5200.ini and adjust the rompath (not needed in mame 0.181)
  6. Adjust your Hyperspin Atari 5200.ini rompath to match
     

Full Details...

 

 

Step 1 – Let’s get the MAME files

 

 

Download and extract the PC version of MAME emulator. Try to match your romset version, RetroArch “Arcade (MAME)” core version and PC MAME emulator version. RetroArch is usually a couple of releases behind.

 

  • For the current release go HERE
  • For previous releases go HERE

 

Once extracted you will have something similar to this

MAME Directory.png

There is plenty more there than this guide will cover!!

 

 

  • Next copy the highlighted assets to a safe location

 

 

1) Hash folder – This has the MAME games databases (softlists) for all the different non Arcade systems MAME can emulate

2) Ini folder – All specific and global configuration (.ini) files go in here

3) Roms folder – All Arcade BIOS files go in here

4) mame.ini – This is the Global configuration file for MAME

5) CreateConfig.bat – This is an optional file to generate the mame.ini file

 

If you don’t have a mame.ini you will need to generate one

 

  • Open Notepad and type the “name of mame.exe” –cc

 

 

Example

 

  • mame64.exe –cc

 

 

 

 

Step 2 – Organise your roms & BIOS

 

 

I have my roms located on a NAS drive called “MYCLOUD”. Wherever you locate your roms they must end up in a subfolder called “a5200”

 

Your compressed BIOS folder (a5200.zip) can be located WITH you ROM file zip's

/ROMPATH/a5200 - place zipped BIOS and zipped roms here

/ROMPATH/a5200/a5200 - Place UNzipped BIOS files here

An additional a5200 folder with the Unzipped BIOS files can also be place in the a5200 folder

 

Your roms and BIOS will need to match what’s in the a5200.xml in the “hash” folder

  • This means whatever roms and BIOS you have MUST be named the same as the name given in the hash file.

 

Note To automate the renaming process you can grab the MAME Atari 5200 Hyperspin compatible xml from the dropbox linked in the 1st post of this thread (Official) MAME XML Database. Then use something like Don’s Renamer to rename your roms to match. These XML’s are religiously kept up to date with current MAME versions

 

This is an example of some roms in the correct “a5200” subfolder (HERE IS MINE Atari 5200.ini)

ALSO place your BIOS file (a5200.zip HERE)

rom names.png

 

Note – The other “a5200” subfolder is optional and is used if you prefer to have your BIOS file uncompressed.

 

 

Step 3 – Get RetroArch setup

 

 

You should have a “system” folder somewhere in you RetroArch directories.

Check these locations

 

  • sdcard/Android/data/com.retroarch/files

Or

  • sdcard/RetroArch

 

Wherever you keep it you must make sure the “System/BIOS” directory path is correct

  •                 Go to RetroArch Settings -> Directory and check what’s listed

 

 

 Step 4 - Build your RetroArch "system" folder

(HERE IS A CLEAN EXAMPLE DOWNLOAD system.zip) MAME Version 0.173)

 

  • Next thing to do is create a folder called “mame” in your “system” folder.

mame folder.png

  • Now drop the extracted folders and files into the “mame” folder (You should have a “roms” folder but I missed mine off for testing)

mame structure.png

 

Step 5 – Configure MAME a5200.ini

(NOT NEEDED NOW PLEASE SKIP CREATING a5200.ini)

 

  • Make a copy of the “mame.ini”
  • Rename it a5200.ini
  • Place it in the “ini” folder

atari a5200 ini.png

 

  • Now open the “a5200.ini” and edit the rompath line to match the location of the rom folder

 

This is my rompath

ini file.png

 

 

Step 6 – Setup Hyperspin

 

  • Adjust your Hyperspin “Atari 5200.ini” to match the same rompath set in the “a5200.ini”
  • Set your extensions to zip, 7z
  • Set your exe
  • Set your parameters

MY SETTINGS FILE Atari 5200.ini

 

Hyperspin ini.png

 

If you don’t have a settings file for Atari 5200 I have attached mine above or a full set can be found HERE

 

 

Now you should be ready to start smashing buttons!!!

 

 

This is a little bit of a WIP so please excuse me if it’s not perfect. Please comment and I will help out and adjust stuff as needed

 

 

Hope this helps someone

 


Supporting Images

 

BIOS LOCATION

bios location.png

 

ROMS's Location

rom location.png

 

 

a5200 Software List Databasehash files.png

 

System Folder Location

System Folder.png

OPTIONAL Uncompressed BIOS location

unzipped bios.png

bios & rom folder.png

Share this post


Link to post
Share on other sites

My Atari 5200 and adventurevision are not loading anymore. They go to retroarch menu. All my other mame systems are working. Does anyone know why?

Share this post


Link to post
Share on other sites
30 minutes ago, badhemi said:

It all worked before. Didn't touch anything. Now this. Mame git

The only thing that is likely to have change is the core. Have you updated the Arcade (MAME) core since you last played those systems?

Share this post


Link to post
Share on other sites
1 hour ago, thatman84 said:

The only thing that is likely to have change is the core. Have you updated the Arcade (MAME) core since you last played those systems?

Intellivision, arcadia ECT all work just atari5200 and adventure vision. I did update but shouldn't effect certain systems. I can't download retroarch nightlys either. They say not installed

Share this post


Link to post
Share on other sites

I don't bother with nightlies, maybe something changed in MAME or retroarch update. 

Maybe try over at their forums see if anyone has similar problems

if the core is the only thing that's changed its just a case figuring out

Share this post


Link to post
Share on other sites
1 hour ago, thatman84 said:

I don't bother with nightlies, maybe something changed in MAME or retroarch update. 

Maybe try over at their forums see if anyone has similar problems

if the core is the only thing that's changed its just a case figuring out

I downloaded store app. It can't be a core issue because 98 percent of my mame systems work. Just 2 don't and I didn't change anything

Share this post


Link to post
Share on other sites

I guess it seems odd but something must have changed mate otherwise they would still work.

What version is your core currently? 

 

I think its rare now but maybe the hash files for those two systems have been changed. Not been around long enough to know how that stuff impacts on it.

Share this post


Link to post
Share on other sites
33 minutes ago, thatman84 said:

I guess it seems odd but something must have changed mate otherwise they would still work.

What version is your core currently? 

 

I think its rare now but maybe the hash files for those two systems have been changed. Not been around long enough to know how that stuff impacts on it.

Mame 174

Share this post


Link to post
Share on other sites

Same core as me and the above works.

 

i remember messing around before I started this because it stopped working without the ini files. Only thing is I messed so much I couldn't remember what I had done!

 

 

Share this post


Link to post
Share on other sites
On 11/4/2016 at 11:32 AM, thatman84 said:

Same core as me and the above works.

 

i remember messing around before I started this because it stopped working without the ini files. Only thing is I messed so much I couldn't remember what I had done!

 

 

Got it working the mame ini was missing for some reason.

Share this post


Link to post
Share on other sites

I just updated to retroarch 1.4.0 stable and Arcade(MAME) 0.181 core

i don't seem to need any MAME specific ini files anymore.

i have the correct rom/bios folder structure and it works straight off the bat.

tested with Atari 5200 & Bally Astrocade

Share this post


Link to post
Share on other sites

hust to confirm I'm talking about the MAME.ini and a5200.ini that the retroarch MAME core uses not Hyperspin. Reference the guide above.

 

i got my retroarch.apk from the downloads tab of the website. It takes you to the 1.3.6 stable. Then I scrolled down to the 1.4.0 folder

Share this post


Link to post
Share on other sites

Hi guys. Previously, I had Atari 5200 setup and running in RA and Hyperspin on a Shield TV. Since that time, I have updated the STV FW to ver. 5.1 and RA to ver. 1.4.1. I had black squares for the icons in RA and didnt know what the issue was. I reloaded RA but forgot to save the SYSTEM folder I had the files in for Mame/Atari 5200. I recreate the necessary files and got Atari 5200 games to work in RA again. However, when I try to launch from HS, RA crashes.  The mame core version is 0.182. I dont know what Im missing. I havent touched my HS files. Any help would be appreciated.

Share this post


Link to post
Share on other sites

Check your "system/BIOS" directory is set correctly once you have launched any RA game any core from Hyperspin 

Share this post


Link to post
Share on other sites

I have other console bios files in REtroarch.com/System and had my "system/BIos" directory pointed there. I also have the Atari 5200 bios in there too. Sega CD still works from HS but I am no longer able to navigate to that directory after I quit a game in HS! I can however go to that directory if I run RA straight away. Why this is, I dont know.

Share this post


Link to post
Share on other sites

Try this

 

also your zipped 5200 bios needs to be in with your zipped roms in a folder called a5200

Share this post


Link to post
Share on other sites

I got it working as another user with the same RA 1.4.1 issue suggested. Since I couldnt point to the RA system directory on my internal drive, I copied the system directory and files to the external drive. Ran a game in HS, then adjusted the system BIOS directory to point there. Now Atari 5200 works again from HS. Thanks for your help.

 

Share this post


Link to post
Share on other sites

No worries, it's probably a good idea to do the config trick for some of the directories just incase you want access to take stuff in the future

Share this post


Link to post
Share on other sites

I followed all of these steps but still can't get any roms to launch through HS or RLHQ. They're working fine when I launch them from RA and my mame roms also work. Mame roms will launch from HS or RLHQ. I'm using the .182 core. Anyone know how to get them to launch with HS? 

Share this post


Link to post
Share on other sites

Having the same issue with the Mess2014 core as well. Roms run fine in RA but won't launch at all from HS or RL. I checked the RLUI logs and keep getting this:

"- You have your path set to  defined, but it could not be found here:" but all my paths (roms, emulator, core) are set correctly. If anyone can help, I'd be pretty grateful. I've now spent hours trying to get this working and I'm about out of ideas

Share this post


Link to post
Share on other sites

  • Similar Content

    • By therourke
      I have a fully working build for Commodore Amiga now on my NVIDEA Shield (2017 model). It took me a good while to get it up and running.

      I thought it might be useful to post an 'all in one place' tutorial. Thanks go to Honosuseri over in this post for convincing me it was possible.
      Commodore Amiga is infamously painful to configure on any and all emulation setups. Retroarch takes the pain out of some of this, since we don't need individual .uae files for every single game now. But there are still some hoops to jump through.
      Onto the tutorial
       
      1. Find/setup your own Hyperspin
      Hyperspin is free and available on this very website. Install the app on your NVIDEA Shield, and compile your roms and Hyperspin setup on an appropriately sized external harddrive/USB.
      As for the ROMs, videos, wheel images and all the aesthetic stuff you need to get your setup running, you will have to source that yourselves. The Hyperspin website is good for some material, emumovies for videos, and Google and Archive dot org for everything in between. 
      For this setup I used a properly named romset for Commodore Amiga in .zip format, but you can also use .lha or .hdf format. .lha is smaller in size, but all of these run pretty much the same on Retroarch now. 
      There is no need for those pesky .uae files anymore!!!!!!!!!!
      Once you have all your roms, you will need to allocate them to the right videos and images and build your .xml database. The info for how to do this is available elsewhere on this very website. I used HyperspinChecker to do this.
      Now, onto the part where we make Hyperspin and Retroarch play nicely so you can finally play your Commodore Amiga games 
      2. WHDLoad and kickrom setup (bios file preparation)
      I obviously can't link to kickroms or WHDload.hdf and some other stuff, but Google is your friend.
      You can get kickroms legally as part of the Amiga Forever app on Google Play Store for only £1.79.
      You ABSOLUTELY NEED to get hold of these EXACT kickroms:
      kick34005.A500 kick37175.A500 kick40063.A600 kick40068.A1200 Some info on kickrom file names and how to match them up correctly can be found here.
      MAKE SURE THE FILENAMES ARE PRECISE! I left one of those As in lowercase and Retroarch didn't like it.
      You also need a properly prepared WHDLoad.hdf file: ADD THESE EXACT KICKROMS TO YOUR WHDload.hdf file (guide to do this here using ADF Opus)
      Copy all these file to the external drive you are keeping your Hyperspin setup on (I made a 'bios' folder in mine for safe keeping).
      3. Retroarch Setup
      Install the latest Retroarch on your NVIDEA Shield (probably works on other Android setups too). You can do this through the Google Play store, but as of writing this, version 1.8.9_GIT definitely works.
      You will need to make sure you have setup a way to load the Retroarch main menu from within games. Go to 'Settings', 'Input', 'Hotkeys' and set the 'Menu Toggle Gamepad Combo' to something like 'Select + Start'.
      Download the latest Commodore - Amiga (P-UAE) core from within Retroarch (use 'Online Updater' menu)
      Now 'Load Core' and choose the P-UAE Core. Start the core, then immediately go back to the Retroarch menu (Start + Select). From the 'Quickmenu' select 'Options'. Change the 'Model' here to something with plenty of power like the 'A1200 (2MB + 8MB)'. Scroll down to 'Global Boot HD' and 'WHDLoad Support' and make sure both of these are marked as 'Files'.
      One other thing from within Retroarch: having a way to 'Quit' from within games is useful for Hyperspin. So go to 'Settings', 'Hotkeys' choose a button for 'Quit Retroarch' (I use the click of my Left Analogue, but anything will do). You may also need to mess around with button mappings, but most of this should work fine if you have a NVIDEA Shield compatible gamepad. Mouse and keyboard are also, obviously, nice additions for Amiga stuff.
      Go back to 'Quick Menu', 'Overrides' and select 'Save Core Overrides' to make sure your Retroarch Amiga setup is saved.
      Lastly, and very importantly...
      Leave Retroarch. You will need an Android directory viewing program like 'FX File Explorer' for this step. Copy the EXACT kickroms listed above and the WHDload.hdf file you created into the /Retroarch/System/ folder on the INTERNAL drive of the NVIDEA Shield.
      4. Commodore Amiga.ini Commands
      In your Hyperspin setup you should now have all your roms, videos, images, menu setup, and a Commodore Amiga.xml database file all neat and tidy.
      You now need to get Hyperspin to talk to Retroarch properly.
      Back on your PC, load your Hyperspin folder and go to the /Settings_Android/ folder.
      Create or open the Commodore Amiga.ini in a text editor. Most of the stuff in here will be the same as other systems, but you can find my ini file attached here.
      Make sure the top lines in your ini read like this:
      [exe info] path=H:\hyperspin\emulators\Commodore Amiga\ rompath=Roms/Commodore Amiga/roms userompath=true exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture romextension=zip,hdf,lha,HDF,ZIP,LHA parameters=cores/puae_libretro_android.so searchsubfolders=false pcgame=false winstate=HIDDEN hyperlaunch=true Each of these lines corresponds to your setup. So if you have your roms folder somewhere else, you need to tell the file. If you are ONLY using .zip versions of your roms, then you don't need the entire 'romextension=zip,hdf,lha,HDF,ZIP,LHA'  line - you can change this to just 'romextension=zip' and it will work fine. (But my line here covers all the possible rom extensions, so you can leave it). The 'exe' and 'parameters' entries are really important, as this tells Hyperspin to load Retroarch, and then Retroarch which core to load for Commodore Amiga.
      Save your file, and hook your Hyperspin external drive back to your NVIDEA Shield.
      5. Play some games
      Everything *should* be working now. If you are having problems with videos and roms matching up, or entries showing in the Amiga menu on your Hyperspin, then that is an issue with your original setup. There are many tutorials out there.
      I can vouch that THIS EXACT setup works great, and loads and plays most Amiga games I have thrown at it without too many glitches.
      6. Now, please answer me a Q 
      When using an external mouse in Retroarch and playing a game like Lemmings, I get TWO cursors - the in game Lemmings cursor, and the NVIDEA Shield arrow.
      Does anyone know how to get rid of this for good? Thanks
      Commodore Amiga.ini
    • By thatman84
      Please note my knowledge of this system does not run deep but everything here works and plays fine.
      What is it?
      Capcom Play System III or CPS-3 is an arcade system board that was first used by Capcom in 1996 with the arcade game Red Earth. It was the second successor to the CP System arcade hardware, following the CP System II. It would be the last proprietary system board Capcom would produce before moving on to the Dreamcast-based Naomi platform.
      How to emulate in Android (Shield TV)
      Quick and simple way is with the FBA core of RetroArch and matching FBA romset.
      At time of writing current versions are:-
      Core:- FB Alpha v0.2.97.42 (commit 6b7a701)
      FBA:- 0.2.97.42 (9 July 2017)
      Other options are MAME core in RetroArch or MAME4Droid reloaded (0.139mame romset). I believe the CHD files are needed for some games and with MAME4Droid, at least,  I had to "install" the game when it 1st launched in the emulator. That process took about 20-30mins and not all worked. Redearth was one I tested and "installed".
      Games
      JoJo no Kimyouna Bouken: Miraie no Isan (Japan 990913) = (jojoba.zip)
      JoJo's Venture (USA 990108) = (jojo.zip)
      Red Earth (Euro 961121) = (redearth.zip)
      Street Fighter III 2nd Impact: Giant Attack (USA 970930) = (sfiii2.zip)
      Street Fighter III 3rd Strike: Fight for the Future (EUR 990608) = (sfiii3.zip)
      Street Fighter III: New Generation (USA 970204) = (sfiii.zip)
       
      Note:-
      I replaced this entry in the official database with the european version as I could not get it to launch in FBA.
      Street Fighter III 3rd Strike: Fight for the Future (USA 990608) = (sfiii3u.zip)
      EDIT:- USA version is working with RetroArch core version 0.2.97.44. Make sure you have the correct RomSet version
      Setup Steps...
      1.  Open RetroArch and download the Arcade (FA Alpha) core.
                                     Main Menu -> Online Updater -> Core Updater

      1a. Transfer your games to your prefered location (You only need the six zip files listed in the database and above)

      2. Add the "Capcom Play System III" system to your Hyperspin setup with HyperHQ on a PC and transfer the files/folder to your device or by manually creating all the relevent folders to your device. (Download at bottom of guide)
      3. Add Capcom Play SYstem III to your Main Menu.xml or Main Menu_Android.xml
      4. Add these lines to your Capcom Play System III.ini file found in Hyperspin/Settings/ or Hyperspin/Settings_Android/
      exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
      romextension=zip
      parameters=cores/fbalpha_libretro_android.so
       
      PLAY SOME STREET FIGHTER .......................
       
      Extra Notes:-
      Under the FB Alpha "Quick Menu -> Options" you can select between different regions. Choosing a different region will give you the different loading screens along with other things I'm not sure about.
      Street Fighter III 3rd Strike (Default)Euro

      Street Fighter III 3rd Strike (USA)

       
      ANDROID MEDIA PACK AND DATABASE (Get your videos from emumovies.com)
      Hyperspin-CPS3Android.zip
       
       
    • By thatman84
      (FYI having trouble with upping some screenshots and the new formatting so please excuse the wierd format)
      Converting 16x9 Themes for Hyperspin Android
      List of theme animation compatibility
      https://drive.google.com/folderview?id=1-8Ofa_GrAdnQ22nf7W7QYVeQoKBQxA_-
      (I am in NO way competent with artwork resolutions but my method works and looks good to me)
      Why...
      Because sometimes that theme you really liked just doesn’t display correctly 
      The main reason for theme problems is the use of animation and scripting of the .swf assets in the “theme”.zip
      (It’s best to replace themes that cause Hyperspin to crash out, but you can try to convert them)
       What’s covered...
             1.      Extract PNG assets from swf files
             2.      Reduce HQ artwork to be compatible with Hyperspin
             3.      Further reduce artwork width to allow for Hyperspin 4x3 -> 16x9 stretching
             4.      Recompile your theme
       
      What is Needed:
      Update on resizing tool.
            Fotosizer is now advised against because of the compression/quality loss it causes.
      pPlease use Photoshop or this program recommended by @IceLancer https://sourceforge.net/projects/easyimagesizer/?source=typ_redirect
      A    A  Fotosizer (http://www.fotosizer.com/) batch resize image files
              B.     Flash Decompiler (https://www.free-dec...flash/download/) extract png’s from swf
              C.     Time and Themes
       I have done a little testing for Main Menu themes. This spreadsheet shows what I have tested and its Android compatibility status. The sheet has download section links for all themes I have tried.
       
       
      Let’s get to it... 
       
      So grab a theme zip you want to play with and Unzip it. Any 16x9 Main Menu, Game or System Default theme will do.
       
       
      BakerMan provided me a guide to extracting the PNG’s from SWF but it has since been lost. 
      These are the steps
              1.      Open JPEXS once downloaded and installed from link above
              2.      Click on the “Open” tab and browse to the offending .swf file from your unzipped theme
       
           SCREENSHOT
      3.     
       

       

             3.      Right click on “Images” on the left and click “Export Selection”
      (At this step you may find multiple images. If these images are only parts of one image, say the arms and legs of a character, you will have to lose that image completely from the theme or replace it with another one)
       
      SCREENSHOT2
             4.      Click “ok” to PNG file type then choose a location for the exported images (Default is Desktop. Only export one at a time and  then move the PNG out of the output folder as it overwrites each one if not)
       
       
      SCREENSHOT3
             5.      Now browse to that Output location and you will find your PNG’s in an “images” folder.
       

       
      You are now ready for phase 2 – Resizing the images
      Note, fotosizer does cause a reduction in artwork quality. If your sensitive to this you may want to use another method. (If you know of a better program please comment) I only run a 37' screen and don't mind myself.
      (Resizing Artwork is covered comprehensively by Avar in his tutorials found HERE)
      Open Fotosizer Add the Artwork that was converted to PNG Reduce the images to 68% KEEP MAINTAIN ASPECT RATIO TICKED (this is the best size for the ones I have done)  
              4.       Move the right side settings bar down and select an Output Folder
       

      5   Remove that Artwork from Fotosizer
      6.   Add the newly resized artwork back into Fotosizer
      7.   Reduce the Width to 75% (to allow HS to stretch it back when its loaded)
      8.   UNTICK MAINTAIN ASPECT RATIO
       
             9.   Now add this finished art back into the theme folder and zip it up again
            
             10.       Name the zip file the same as you have it in the “Main Menu.xml” database
       
      Final Thoughts...
       
       
      Now when you try this theme out you may find the artwork has slightly changed location. If so adjust the Artwork positions in the theme.xml file within the theme.zip OR load it into Hypertheme and adjust it as required
       
       
      Hope this helps someone.
       
       
      HS Android Theme Animations.txt
    • By ninja2bceen
      Ha not going anywhere but wanted to put in the plug that I’m going to create some tutorials on random things hyperspin and maybe pinball. The channel I’ve created is below, please let me know if you have a specific topic to get covered. Just made one around randomized intro videos
       
       Planet Geekdom
       
       https://youtube.com/channel/UCdcby-s2GwriaOHGmVC2vGA?sub_confirmation=1
       
      *If you do the facebook thing, find me on the group Hyperspin Arcade Users Worldwide
      https://www.facebook.com/groups/581676831988120/?ref=group_header
       
      Sent from my iPhone using Tapatalk
       
       
       
       
    • By thatman84
      This is the start of the WIP guide and Amiga Project thread
      DONT REPLY TO THIS THREAD
      REPLY TO THIS ONE(clicky)
       
      For now this will become a tempory guide to UAE4arm setup with the Ultimate Amiga Raspberry Pi Project a helpful source of information in google
      Step 1 - Install Uae4arm (beta)
      You need to follow this link to sign up to be a beta tester to gain access to the apk that can launch games directly from Hyperspin.
      https://play.google.com/apps/testing/atua.anddev.uae4arm
      Link above taken from the English Amiga Board and the post below
      http://eab.abime.net/showpost.php?p=1158186&postcount=349
       
      Step 2 - Install Kickstarts
      WIP
       
      Database taken from this thread post
       
      More to follow
       
      Amiberry Android progress threads
      https://github.com/midwan/amiberry/issues/206
      https://github.com/midwan/amiberry/issues/241
×
×
  • Create New...