Return to the Amiga

I am a huge Commodore fan and have been since the very early 1980s. I bought an Amiga 1000 the fall of 1985, and an Amiga 500 a few years later. The Amiga was my sole personal computer until around 1983, and I played hundreds of amazing games on it in the 8 years I owned it.

When I bought a MiSTer FPGA a month or two ago, it was mostly so I could play many of those old Amiga games again. Little did I know the amount of work it would take to get the games onto the MiSTer.  This post mortem details at least some of the steps I took to fruitlessly try to get Amiga games working as .hdf files on the MiSTer FPGA. 

AI as the Sole Source of Truth

I have relied on AI, Gemini in this case, every step away. Interestingly, it has proven to be a double-edged sword. It’s been invaluable in some respects, and downright stupid in others. It’s often provided incorrect information, or led me down pathways that didn’t work. It was also sometimes unwilling to provide any information, which forced me to coax it out of it. 

I admit I rely heavily on Gemini for most things nowadays, and I relied on it here, to my detriment. Had I been more knowledgeable about these matters, I might have had a better outcome.

 The Journey

• Amiga Vision – I read that Amiga Vision provided an all-in-one solution with hundreds of games. I just had to download and copy some folders to my SD-CARD. I either downloaded the wrong version (I don’t think that was the case) or it somehow didn’t copy over correctly because it didn’t work. I got errors on the MiSTer FPGA when I tried to use it.

• Conversion – I downloaded .lha files from WHDLoad and was directed by Gemini to use a Bash script to convert them to .hdf files.This didn’t work even though I was using Git Bash, AmiTools, and some GnuWin32 utilities. In the end I had Cursor fix the script to get it working..
• Bash –  A critical failure occurred where the script logic, likely due to improper variable handling or file path iteration, effectively mapped the same game file into every generated .hdf file, resulting in a batch of corrupted or redundant images. This was resolved, or at least partially so, by adding a line to the Bash script to delete the tmp folder before copying new game files.
• Amiga Forever – Attempting to create a boot hard drive (DH0) in Amiga Forever failed because that environment is unable to create SCSI hard drives that are compatible. In the end, I could create the initial .hdf file in Amiga Forever, then had to copy it to the SD-CARD, and boot it in MiSTer FPGA, and from there, set the drive information, partition it, format it, and install Workbench 3.1.
• WHDLoad – Once I got my Workbench 3.1 hard drive working, I attempted to mount a game .hdf file, but found it was missing WHDLoad. Gemini directed me to use a PowerShell script it created to inject WHDLoad into the .hdf files.

• WHDLoad Continued – I abandoned the automated batch approach in favor of manually injecting files into a master .hdf. This required using the Amiga shell to manually handle the installation of the WHDLoad package. This was difficult because I had to copy the WHDLoad files to the boot drive, and install it. In the end, I created a floppy disk in Amiga Forever, copied the necessary files to it, then copied that to the SD-CARD, and was able to copy it to the hard drive and install it.
• Mismatched Files – A recurring issue involved the game .slave file on the .hdf. When the .lha was initially unpacked, the internal naming conventions in the .hdf file didn’t match the expected launch parameters, forcing me to manually rename the slave files within the Amiga environment. Potentially, this would have to be done for every .hdf game file, or maybe the Bash script could be altered to do it for me, which would require converting all of the .lha files again.

• Amiga Vision Again – Finally, after many false starts, Gemini directed me to again install the AmigaVision structure to source the necessary Kickstart ROMs and .RTB files manually, validating them against the requirements of the specific Workbench 3.1 setup.
• It Works! –  Bewilderingly, when I mounted Amiga Vision in the MiSTer FPGA, it worked, providing a list of hundreds of games I could play. I tried running a couple, and they just worked!

Final Thoughts

This whole experience has been illuminating and frustrating, and I’ve felt helpless while Gemini continued to pump out information that I wasn’t knowledgeable enough to refute. I often got upset with Gemini, raised my voice at it, letting it know how displeased I was with it. This of course made no difference to it.

I have working games via Amiga Vision and my old floppy images, and I’m happy about that. I’ve also spent more time using AmigaDOS and WorkBench in the last several days than I have in 35 years, which has been fun and interesting. It’s also a bit bewildering to see how antiquated yet perfectly functional this old operating system is.

The worst part is how much time this has taken. I was fortunate to have a few days off work and spent most of several days doing nothing but this. Of course, I could have spent the time playing games, but this is all new to me, since I have never had a MiSTer FPGA before. Also, I’ve been buying new versions of Amiga Forever for probably 20+ years, but I’ve never spent that much time using it.

My recommendation if you decide to buy a MiSTer FPGA or similar just to play Amiga games is go with Amiga Vision and hopefully it works for you. Playing games from floppy images works fine, but it’s nice to have a unified launcher and a list of hundreds of games to play.