![]() So, for "Activision Decathlon, The (USA).a52" the cmd file contents is: a5200 -cart "/storage/ALEXANDRIA/Data/ROM/HyperSpin/Atari/5200/Activision Decathlon, The (USA).a52" The file types had been all over the place after the first renaming, since Don's Hyperspin Tools do ignore those so I renamed them all to ROMNAME.a52. ![]() Naming convention is per Hyperlist XML v2.0, the roms have been verified by me to match the CRC and renamed accordingly using Don's Hyperspin tools. But I'll give using an unzipped BIOS and a regular zipped BIOS a try, just for completeness. So far, 7zip support in RA has not given me any grief A2600 and A7800 sets are all 7zipped and work like a charm. I will check again tonight but I may be on different versions of RA & mame core Please post the contents of your cmd file. What type and naming convention are your roms? The regular PC version of MAME works perfect with a5200 and roms named like HyperSpin database though RL and HS. When you don't have any idea what it could be, I think we can blame RetroArch, which btw shows a similar behaviour on my PC with the MAME core and RocketLauncher. Google couldn't find anything recent enough other than what was said here on the forum or around March, 1st on the RA forum. All I get is "Your application just died, do you want me to restart, quit or report the error" and the same behaviour when started from HSA. Parameters=cores/mame_libretro_android.so Rompath=/storage/ALEXANDRIA/Data/ROM/HyperSpin/Atari/5200Įxe=com.retroarch/.RetroActivityFuture So my ROM directory looks basically like yours like you posted here Ītari 5200.ini in HSA Settings_Android looks like this I created the CMD files with your script (.and checked the path in there, twice, thrice.) and put them with the ROMs onto the NAS. So there is now /storage/emulated/0/RetroArch/configs/a5200.7z, /storage/emulated/0/RetroArch/configs/mame/a5200.7z, and /storage/emulated/0/RetroArch/configs/mame/roms/a5200.7z in addition to 5200.7z with the ROMs on the NAS. Since it still kept crashing I successively placed the a5200.7z BIOS over the various config locations. ini folder, as the tutorial mentions it's not needed anymore. roms folder and I did not create an a5200.ini file in the. roms and mame.ini from the PC installation, the first rompath in mame.ini points to the local. (/storage/ALEXANDRIA/Data/ROM/HyperSpin/Atari/5200) My ROMs are on a NAS, like yours, the path is a tad deeper, but that has not stopped A2600 or A7800 ROMs from working with their respective cores.Īll my ROMs are compressed in 7z including the a5200 BIOS and are lying together on the NAS in one directory. It just keeps crashing on trying to load any Atari 5200 content (also Virtual Jaguar is not working, but that is not subject of this thread ) I did the config file magic to make HSA launched RA use the same locations as the standalone version, so config/BIOS points to /storage/emulated/0/RetroArch/configs. ![]() I still must miss some vital part there or RA 1.5.0 with MAME 0.185 core is broken. *sigh* A5200 setup is kind of driving me crazy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |