Hello there First of all sorry for my bad english I would like to help all AMIGA lovers to make their favorite games runs as fast as possible and to be able to select them nice via emulation station gui. Please keep in mind that this is my first tutorial, i’ll do my best to make it as easy as possible even for a new amiga emulation fans. Let’s start: To achieve the goal we are going to use optional RetroPie emulator UAE4ARM (which is the best option as for now). All amiga games will be stored as.hdf files (runing games via harddrive using the build-in installers or WHDLoad images is way faster then runing from.adf files.
Also you will forget about disk swaping). Each amiga hdf file (each game) going to have its own UAE4ARM.uae config file which is very important. Thank to it every game will have an unique configuration which is as much compatibile with a specify title as possible. Following tutorial was made on the latest version of RetroPie 4.2 running on RaspberryPi 3b. Most operations we are going to do using windows and Total Commander. As an example we are going to use whdload image of a great freeware amiga game called SQRXZ (WHDload image attached) developed by RetroGuru. Please give a hug and see more amazing games here.
Download Commodore Amiga WHDLoad Games WHDLoad ROMs and Games for PC,iOS or Android Phone.
What we need: RetroPie:. UAE4ARM emulator – it can be downloaded from optional packages in RetroPie RetroPie setup Manage packages Manage optional packages. Amiga bios files – Highly recommended to buy Amiga Forever. For only 30$ you can get Plus Edition which constain every legal kickstart rom you need.
Its also nice to support this amazing project, as it keeps amiga alive and thats what we want;) otherwise use google to find it. We have to place 2 bios rom files inside a RetroPie BIOS folder (/home/pi/RetroPie/BIOS ): Kickstart v2.05 r37.299 (1991)(Commodore)(A600)!.rom (rename it to kick20.rom) Kickstart v3.1 r40.63 (1993)(Commodore)(A500-A600-A2000)!.rom (rename it to kick31.rom). HDF image files – follow tutorial. Mouse and keyboard – i know that most of you would like to use only controler but you still have to press F12 and Q to exit an emulator. To be honest: be serious guys, you are about to emulate a computer, and computer needs its keyboard and mouse. Lots of games use keyboard for highscores, passwords, cheats ets, a lot was made for mouse also. Windows.
WinUAE emulator whit working workbench (can be loaded from ADF) –. I will not explain how to use it since it would take a lot of time. In this tutorial i’ll try to use it as less as possible, but if you are real amiga lover you should learn how to use it, its like amazing. Quick begginers tutrial can be found on youtube here.
WHDload – the one and only (now finally for free) HD games loader. Lha archive can be found here. Total Commander with AmigaDX plugin. Test version can be found here and the AmigaDX plugin here. We could use only WinUAE but its demands advanced knowledge about it and about a real amiga itself, thats why i recommend to use TC with AmigaDX plugin since its way faster and easier for noobies. Why TC with plugin? It allowes us to easly copy and remove files from within a hdf files (as well as all most common amiga files like.adf.dms.lha etc) which are a base for our games.
WHDLoad images – here will be difficult. Making a WHDload images from scratch its for advanced users only (you can find many tutorials on internet). You have to use Amiga OS for it, you need game disks images stored as IPF files, you need to know how amiga works which can take a time (i highly recommend to go deep in it since its very beautiful machine). Of course if you own your amiga game but you simply unable to do it, you can search google for WHDLoad collections. Preparing HDF image. (If you are lazy or really noobie you can skip point 1 and 2 and download my preconfigured HDF files with all (freeware) stuff you need inside).
First we have to create HDF file using WinUAE. Lets call it SQRXZ.hdf. Nice tutorial can be found here. Before u set a size of your hdf image let me tell you something about hdf files. HDF image will be used for load a content as well as save a content. It means that all games which supports saving will store data within the hdf file itself thats why i highly recommend to use like 1mb – 2mb bigger hdf file then a specify whdload image.
In our case we have like 1mb whdload image so for this game we are going to use 2mb hdf file. Thanks to it game has a space for additional save data. Before we can use it, it must be formated under amiga OS (Use amiga workbench under WinUAE). Insert workbench adf file into DF0 and mount hdf file as DH0 (while mounting hdf file is important to uncheck the „bootable” option, otherwise emulator will try to boot from our hdf file which is empty instead of load workbench from floppy image). In workbench desktop simply right click your hdf icon and select format, put a nice name for your image (SQRXZ in our example) and continue. After this our hdf file is ready to be edited in Total Commander.
Prepearing hdf folder structure. Open total commander and find your SQRXZ.hdf file which you created.
Thanks to AmigaDX plugin you should be able to easly browse image (just like zip files). Open your hdf file and create folder structure like this: C Data Devs / Kickstarts Libs S C – in this folder we’re going to store some importent tools including whdload launcher itself. Data – here will be a place for our whdload image files Devs / Kickstart – some games require additional rom files to work which if needed will be stored here. Every whdload image contains „read me” file with additional info about requirements. Highly recomended to read it.
All kick roms can be found on your workbench disk in same folder (devs/kickstarts) or Amiga Forever cd. Libs – some titles require additional libraries (kind of DLL file on windows) which if needed will be stored here. Very rare, but if really necessary you can search huge legal amiga repositorium. S – this is the place for startup-sequence.
In startup-sequence we specify what and how will be loaded. Coping files into hdf image. Folder C: in total commander navigate and open adf file with workbench image and copy following files from C folder to your C folder on hdf: Assign, Execute, Setpatch.
Next, open whdload package and copy WHDLoad to you C folder on hdf file. Folder Data: here we unpack our sqrxz game data from wdload package.
Open SQRXZ.lha (total commander) and copy content of sqrxz folder into data folder of your hdf file. Since sqrxz dont need addtional kickstarts file and libraries we can go direct to folder S Go into S folder (on your hdf file) and create text file (without extension) named „startup-sequence”. Copy/paste this into startup sequence and save C:SETPATCH quiet C:Assign NIL: ENV: RAM: C:Assign NIL: T: RAM: cd Data; Whdload Sqrxz.slave PRELOAD QUITKEY=89; in our case we use Sqrxz.slave (slave its a main boot file used by whdload launcher) but you can use this sequence for other titles, just place a correct slave name. Next open again whdload package and copy WHDLoad.prefs to S folder also. If you did everything good you should have file structure like this: Sound pretty complicated but if you get used to it you can prepare a game in less then 10 mins.
Copy your hdf file to your retropie amiga roms folder. Prepare retropie: Our first hdf image is ready to go, now we have to prepare our retropie and emulator. The main file for our game list will be a config file.uae created directly in UAE4ARM. Default emualtion station settings do not support this extension thats why we have to add it by hand to our essystems.cfg file.
In retropie open console (F4) and type following: sudo nano /etc/emulationstation/essystems.cfg find amiga and add.uae extension in. Field ctrl+x to save your file and then type „reboot” to restart machine. Thanks to it emulation station will show our uae „roms” on the list (i wrote „roms” because technicly those are only configuration files for UAE4ARM) Second thing we have to do is to let UAE4ARM run our uae file direct without poping up gui. Latest instance of UAE4ARM support this feature as default but if for some reason something is not working follow this: Open termianl (F4) and type: sudo nano /opt/retropie/configs/amiga/emulators.cfg wipe out entire text and put this one instead: uae4arm = 'pushd /opt/retropie/emulators/uae4arm/;./uae4arm -f%ROM%' default = 'uae4arm' thanks to this all games will start automaticly direct from ES gui. Now we’re going to configure the UAE4ARM.
We have to set the paths for our bios files and config files. To do it we start UAE4ARM. In the menu we choose „Paths” and set paths like this System ROMs: /home/pi/RetroPie/BIOS/ Configuration files: /home/pi/RetriPie/roms/amiga/ Now emulator will use kick files stored in BIOS folder (its easy to operate in this folder via samba share etc) and store config files direct in roms folder. Prepare configuration file: now when we have our hdf file and configured retropie its time to prepare configuration file for our game. This we do in UAE4ARM itself. Few words about configuration file.
Depending on what game we choose we have to set specific configuration to make it work as good as possible. Some games require different kickstarts (2.0 or 3.1), some of them needs more ram memory or chip memory etc, some of them runs with ECS chipset some with AGA, some need powerfull CPU to run smooth and some need slower because otherwise they run to fast. Thers quite a lot possibilities which im unable to write here, you must try by yourself, learn a little bit about it etc. The best way to do this is to practice it using WINUAE coz UAE4ARM is based on it and has almost same options. Fortunetly (from my experience) most of the games runs very good using the same specs, only some of them need special treatment;).
Im going to explain a little bit how to do it and of course attach config file so you can check it, compare it and use it. First of all start emulator using a shortcut +START UAE4ARM. I noticed that latest build of UAE4ARM start direct to amiga boot screen so press F12 to popup gui.
Lets add our first config file in Configurations tab: In the „Name” field write the name of your game (in our case SQRXZ) and press save. The config file should now appear in the top menu. Now set up my „almost” universal config: CPU and FPU: CPU = 68040, JIT FPU = CPU internal CPU Speed = Fastest Chipset: Chipset = AGA Blitter = Normal Copper = Fast copper Collision Level = Sprites and Sprites vs.
Playfield ROM: Main ROM File = KS ROM v3.1 (A500,A600,A2000) rev 40.63 (512k) RAM: Chip = 2mb Fast = 8mb Floppy drives: DF0 = on Input: Port1 = here set up your joypad (i use ps3 controller) Save your config. The rest of options you can leave as default (note: when your game wont start or runs not so good you can play with config by changing kickstart, CPU speed, amount of ram etc). Now add hdf file as your main harddrive.
To do this select „Hard drives / CD” and click „Add Hardfile”. In popup menu select path to your game (in our case it will be /home/pi/RetroPie/roms/Amiga/SQRXZ.hdf). Check (if not checked) „Bootable” and click OK.
Now save your config for a last time. Thats it, restart emulation station (so roms appear on the list) and you are ready to go. If you set everything good your amiga game list should look and work like this (not my video).
Good luck;) Less then 10 mins method: if you get familiar with this tutorial and succesfully made your first hdf file you can use those tips to make it even faster. Pick whdload file (check size). pick one of my preconfigured hdfs (select proper size). open it in TC and copy whdload game files into data folder and edit startup-sequence by adding only a name of slave. copy hdf file to amiga roms. copy and rename the same as new hdf file your config file you just did (SQRXZ.uae in roms folder). start UAE4ARM and load your new config.
change hdf file path and save config. Thats it, another game ready hope i help;) Here are attached files:. Preconfigured hdf images -.
SQRXZ whdload image -. SQRXZ hdf and cfg example. First of all many thanks for this! It's really amazing! I have one Question: I am using a selfmade bartop and retrogame for the Key inputs. Is it possible too load the right keysettings (retrogame GPIO) for every game when starting the Game? I tried to add a line into emulators.cfg but i think it's not recognized!
The only thing i wanna do, is copy the right keyfile (named the same as the ROM only with other extension) to the standard file, for Sqrxz it would be: sudo cp /home/pi/Sqrxz.cfg /home/pi/retrogame.cfg. Is there a way to do this? Many thanks in advance! Thanks for the guide! Is this libretro/retroarch based? I have an iPac setup, that maps buttons as a USB keyboard does.
So if I could edit a retroarch.cfg file and change button mappings that way, I'd be happy.? Or is button mappings done via some kind of menu in the emulator? Edit: a quick google search shows older topics that state that UAE4ARM doesn't include button mapping at all, meaning that games are unplayable unless you're using a keyboard.
Is this still the case? I see your guide recommends this for quitting games etc, but what about game controls?
Legal Notice: In order to use the following guide, it's really important for you to own legally an Original Amiga OS 3.9 Installation, along with a legal Kickstart 3.1. Ok lets start.
To be able to run Remus and make the Custom ROMS the requirements are the following: Hardware: - Amiga OS3.0 and above. At least 1MB of free RAM Software: - (everyone has it anyway) -The MUI libraries bellow. (although optional) - (used by Arexx scripts) - (used by Arexx scripts) - (for Anti-Virus usage) Or you can get ALL the above in the following archive that I putted on my Dropbox Once we install everything.
We need to run the program ROMsplit in order for us to extract the modules from our Kickstart 3.1 ROM and from our BB2 ROM update (DEVS: AmigaOS ROM Update). So we either click 'Grab ROM' for ROMsplit getting the contents from our Kickstart 3.1 ROM. We search from our Partitions to find a legal 3.1 ROM in file for contents to appear. (1st pic has 3.9 Update while 2nd pic has the 3.1 Kickstart). Lets get a bit familiar with the interface a bit. Left side below toolbar are the contents that we're gonna put on our future ROM 2. Right side below toolbar are the folders/files from which we're gonna choose what to put into the left list.
In this screenshot for example I have in the right side a folder in which I have the following folders: - 40.68(A1200) - This is an extract of my A1200's 3.1 Kickstart ROM - 44.57ROMUpdate(3.9bb2) - This is an extract from 'AmigaOS ROM Update) - BlizKick - This is a copy of DEVS: Modules that were installed with BlizKick In next step, we're creating a new Normal Kickstart by pressing the button 'New' in toolbar, and we insert the info from the following screenshot. As an example, I'm attaching the order of my files based on folder name. IMPORTANT: YOU NEED to insert 'Exec' first and then '1MBROM' module or else the Kickstart won't work at all! As you will realize, we putted all the Modules of Kickstart 3.1 (with the same order as it existed on the Kickstart itself) but we changed some modules with the new ones from the extracted BB2 3.9 Update.
That way we have a nice new Custom 3.9 Kickstart missing though Workbench.library and Intuition.library. No worries, we left them to save space, and we're gonna put them in the extended Kickstart (Hell yeah!
1MB ROM ftw) in a while. Now, we're gonna click the button 'Compile' in toolbar that will make the Kickstart under RAM:3.9normal.rom (if you kept the same name as the screenshot under 'Settings' tab like mine) (It's a good idea to save the template of your Normal Kickstart for future use like 'MyCustomKickstart39Normal.rpf') Time for the extended Kickstart ROM now. We're clicking on 'New' in toolbar and we insert the info from the following screenshot. As an example, I'm attaching the order of my files based on folder name. IMPORTANT: YOU NEED to insert ROMHeader and DummyCDstrap (only if you use an BPPC or CSPPC accelerator) first, or else the Kickstart won't work at all!. Others/RomHeader/romheader. Others/DummyCDstrap/DummyCDstrap (This is optional module for BPPC and CSPPC accelerators).
System:Libs/workbench.library. DH0: Devs/morelibspacemodule (This is AfA OS Morelibspace Module to avoid declaring it in Startup-Sequence!). DH0: Devs/Modules/BPPCFix (This is BPPCFix Module to avoid declaring it in Startup-Sequence!). The last step asks us if Remus should perform a ByteSwap operation for the ROM. Our choice will be based on the following: - If you wanna burn the image to a Real Kickstart Image: then choose YES, since we won't need to byteswap it in the EPROM Programmer application - since Amiga requires ByteSwapping procedure for its ROMS). If you wanna use the image to kick it via MapROM (like for example on ACA6x0/ACA12xx accelerators via ACATune utility): then choose NO, since ACATune and general MapROM applications use normal (non-ByteSwapped) images.
In that case. Your ROM image is ready to be used so you can kick it right away by using the following line in you Startup-Sequence (according you have an ACA6x0/ACA12xx with ACATune utility installed). You can comment them also if you included them in the Custom 3.9 ROM. That's all folks. I hope this guide will be useful to someone else but me. P.S. I'm attaching an example of my Custom Kickstart Remus files (renamed to.txt).
You just need to alter the location of the folders if you wanna try them out. EDIT: Since I was tinkering with creating a Custom Kickstart 3.9 for an Amiga A4000D I found and solved the following problems: Problem: A4000 doesn't support 512KB ROMS which can be a problem for custom 1MB ROMS Solution: Create your custom rom as a 512KB as my guide says but you exclude the 1MBROM module (if you use the 3.1 exec, or 3.9 exec). We'll leave outside though Workbench.library which is rather big and can't be left out (can be put in hard drive's LIBS: folder with no problem). You'd should include the module in your ROM as well as it's a module that tells the system that the Workbench.library exists in SYS:Libs Problem: Since we're not making an 1MB ROM (we'll only make Normal ROM without Extended), we can't actually use Doobrey's awesome Make1MBROM Arexx script (since it combines normal/extended, and splits and byteswaps according to your need). Using utilities like most guys suggest in forums (WinHex) is cool, but it was certainly uncool for me to register WinHex (45 euro) just to dissect the 512KB ROM file to even/odd files.
Solution: After checking Doobrey's script, I managed to realise that you only need to use his tool SplitRROMImage that exists in 'Tools' folder under Remus installation folder. The declaration of the command is fairly simple: SplitROMImage SWAP (SWAP is optional and it only ByteSwaps your files for using it under your Eprom Burner) In my example: SplitROMIMage kick39a4000.rom SWAP.created 2 files:. kick39a4000.rom.hi (256kb). kick39a4000.rom.lo (256kb) Now you can get these files and burn them to your programer (in 256KB EPROMS). Note: If you want to write your custom Kickstart to 512KB EPROMS (like 27C400) you'd need to double the HI and LO images (since they are 256KB in size) before burning them or else the Kickstart won't work. To double these images, the easiest way is to use the DOS Command Prompt like this: C: copy kick39a4000.rom.hi /B+kick39a4000.rom.hi /B kick39a4000512.rom.hi /B C: copy kick39a4000.rom.lo /B+kick39a4000.rom.lo /B kick39a4000512.rom.lo /B That way you created 2 new files ( kick39a4000512.rom.hi and kick39a4000512.rom.lo ) which now you can burn to the 27C400 EPROMS just fine:).