(76 replies, posted in Amiga)

Awesome Mike. I'm so much looking forward to buy my daughter board from Laurent @ Amedia Computer. Wondering if I'm going to be able to use the same Antec Mini ITX case that I have now.


(76 replies, posted in Amiga)

I have and old M68060 chip, model Motorola 68060 MC68060RC50 71E41J. Would this chip work with the daughter board?


(1,708 replies, posted in Amiga)

MikeJ wrote:

I consider RTG stable assuming you are using the latest ARM firmware.
Let me know if there are still issues.
(I know of one, which is if the HRTMON is activated the system hangs)

How can I check if I have the latest ARM firmware? And If I don't have it, where do I find it and install? Thank you.


(1,708 replies, posted in Amiga)

MikeJ wrote:

Here's the binary if you wish to give it a run.

Just change the rom load in the ini and load at the usual place

ROM = kick_12.rom,0x80000,0x00F80000

Mike, would you be posting also a "replay_amiga_pal.ini" file?

Or are these new files only for people using RTG configuration, which I haven't configured yet waiting for a stable version?


(1,708 replies, posted in Amiga)

Why is it been so quite in the FPGA Replay front for so long? It's been over a month now since last hear anything.

Maybe Mike is giving the final touches to the daughter board? It'd be nice to have Internet access, USB ports and the capacity of using external storage media to transfer files directly to and from the FPGA Replay.

I'm not even sure if this is a valid question, but since I understand that the A600 Vampire uses FPGA, what are the main differences between one and the other?


(102 replies, posted in Amiga)

cunnpole wrote:

Assuming AmigaOS is using 2.3 there isnt much in the changelog:
version 2.3 (01.21.2013) done by Keith Krellwitz/Abaddon:
- Custom4=1 - Enable CD32 joypad support
    Red             - Fire
    Yellow             - Bring Up Map Screen/Exit Map screen
    Play             - Pause
    Play+Forward+Reverse     - Quit
    Green+Forward+Reverse     - Abort Game

I am using version 2.2 of Desert Strike


(102 replies, posted in Amiga)

cplnobby wrote:

The 2.2 WHDLoad version of Desert Strike seems to work without issue.

I'm using version 2.2 of Desert Strike


(102 replies, posted in Amiga)

I think I already reported this once, but just in case the previous post wasn't noticed. I have never been able to play WHDLoad version of Desert Strike, since it gives the following message:


Note that I'm using A1200 configuration (68020, ~14MHz, 2 MB Chip RAM, 8 MB fast RAM).

The ADF image (3 disks) play well.

Any ideas?

NB - I forgot to mention that the same error is seeing playing the game in a MIST FPGA


(1,708 replies, posted in Amiga)

gouky wrote:

@AmigOS let's wait for Mike core update in case there's an ini update as well

OK. I'll stay put. Thanks.


(1,708 replies, posted in Amiga)

gouky wrote:

post your ini not the core smile

Oops..sorry. Here you go.


(1,708 replies, posted in Amiga)

gouky wrote:

Not sure if i follow you.

Same core for both ini but you need to take the latest .ini (pal or not depending on your taste) and make the changes you like. Just make sure to set the cpu to a1200 if you want the maximum compatibility with whdload and maybe use the fastest cpu with cache for your os3.9?.

Feel free to post your ini if you have doubt and backup your current ini just in case you want to rollback if you have some problem.

Thank your offer to help. Please find here my current configurations. I will appreciate your suggestions and guidance.


(1,708 replies, posted in Amiga)

So, this one for my WB 3.9 replay_amiga_pal.ini 9.31 kb and replay_amiga.bin 728.72 kb for my WB 3.1? And replay.ini 9.34 kb for both configurations?

I just want to make sure I will be installing the right cores.


(1,708 replies, posted in Amiga)

I'm using two different SD cards, one configured with WB 3.1 and the other one with WB 3.9 (PAL). In both, I am using the cores released on Sep 18, 2015, which are very stable. Working as charms.

My settings are 68020, Amiga 1200 ~14MHz, AGA, Chip RAM 2 MB, Fast RAM 8 MB, XRAM none.

Question: Is there any benefit in updating the cores? For instance replay_amiga.bin of Jan. 22 and replay_amiga_pal.bin of Jan. 21 (for my WB 3.9 configuration)?


(150 replies, posted in Amiga)

I found the sticky, but I also see that there were many core updates and notes that went up after the creation of the sticky. The same applies to the XRAM instructions, hence the answer if there was a new guide consolidating everything in one RTG guide and another one for the XRAM.

If not, I'm for a long reading project.


(150 replies, posted in Amiga)

I need the help of the fellow members of this forum. Due to work overload I've been away from the forum and my FPGA Replay for some weeks. Trying to read all the posts about the RTG and XRAM, I feel completely at loss.

Could someone point me to the files that I need to use and a configuration guide that summarizes the process to configure RTG and add XRAM?

Thanks in advance.

Probably others have reported this....there is a much higher chance of success playing WHDLoad games in the FPGA Arcade if you unarc the zip files that you download from whdownload directly in your Workbench configuration in the board.

I did that for a long list of games including: Banshee AGA, Deuterios, Disposable Hero, Frontier Elite II, Rise of the Robots AGA, Robocop 3, etc. The only 2 ones I haven't been able to play from WHDLoad games are Desert Strike, which I can play from the adf images and GODS, which doesn't work period. In total I have tried 30 different games, including Wolfestein3D.

For configuration of my board I am using 68020, A1200-~14MHz, Accurate, Chip Ram 2.0 MB, Fast RAM 4.0, PAL.


(94 replies, posted in Amiga)

Kremlar wrote:

Mike/Wolfgang... a simple text editor would be a real handy option for the OSD!

Yeah, it's only been a few days and I'm already worried about wearing out the SD card socket!

I am using one of these http://i358.photobucket.com/albums/oo30/AmigOS923/SD%20card%20extender_zpseibgmq2k.jpg

that runs for about US$5. It gives me easy access from the front of my case, and the biggest advantage is that if it gets damaged, it only costs 5 bucks to replace. I keep a spare one just in case.

On a related issue, would it be possible for someone to post an updated, ste by step guide on how to setup a SD card with Workbench, of any flavor.

I have two microSD cards; one with Classic Workbench 3.1 and another with WB 3.9, and swapping them with the use of the card extension cable is not an issue.


(94 replies, posted in Amiga)

Faranheit wrote:

Hi Everblue,

You can have a look at our HDF creation guide HERE

Thanks, Lionel and Laurent
Amedia Computer

Laurent, I'm having problems following your guide for hdf creation, and in particular with the steps outlined in "Second step : Minimig’s board parameters." After creating and copying the RDB hardfile, and inserting the card in the FPGA Arcade, I can't access the menu as described.

Do I need to add the core files too? And of course, the guide was written for the old Minimig so I see little resemblance in the steps to follow.

I am trying to create a new microSD in which I could use a Classic Workbench 3.1 configuration that I'm using in WinUAE. Thanks in advance for any help.


(93 replies, posted in Amiga)

JimDrew wrote:

I looked at your hardfile.  I get an "OUT OF MEMORY" pop-up box when I try to select a file when running it under WinUAE.  I am selecting any type of file, as I don't have any actual games.

Strange. I just tried the same games that I included in the image that I sent to you, in WinUAE, running them from the hdf in SD card, and they all run fine.


(93 replies, posted in Amiga)

JimDrew wrote:

Is it possible that your non-bootable hardfile is corrupted?  Do you have a backup copy?

Did you try downloading the older version of the core (and .ini file) and see if the older version works?

Since this appears to be more of a loading issue, rather than a core issue, I would tend to believe the issue is drive related.

Jim - Thank you for taking the time to look into this.

I followed your suggestion and copied the original non-bootable hdf I received with my system, and stored in a safe place, but I continue having the same issues (DOS Error messages).

I only copied 2 WHDLoad games to test: Desert Strike and SoccerKid AGA, but I'm still getting the same error messages.

If you want I can send you copy of that non-bootable file for you to examin. Please let me know.


(93 replies, posted in Amiga)

Sheldon wrote:


AmigOS: Try with 14Mhz speed.
Some Issues with 28Mhz speed disappear with 14Mhz with Core version 20/09/2015.

Best Regards

Tried 14MHz and 68020 for CPU and no change. I'm still getting DOS errors :-(


(93 replies, posted in Amiga)

As additional information to this apparent incompatibility case, here is another case:

Dessert Strike WHDLoad not working and giving error:


ADF version working:


I'm keeping my fingers crossed that is not a faulty FPGA board, since I waited for almost 1 year and half to get it :-(

What eases my anxiety is some other WHDLoad games are working fine :-)


(93 replies, posted in Amiga)

JimDrew wrote:

Is it possible that you are really out of memory?  I know that people often times tell you that "nothing changed", but I found that people did change small things that they didn't expect to be a source of a problem.  For example, a cache program might be stealing a block of memory that use to be available.  The default in your .ini file might be just 2MB of memory when you use to have 8MB as the default, etc.  Take a look at Workbench's info for memory and see what it says.

In response to the "end-user error" approach, here is a picture of my Workbench screen showing available memory: http://i358.photobucket.com/albums/oo30/AmigOS923/AmigOS2/20151012_134340_zpsrzw8r0an.jpg

BTW, All I have used in my system is WHDLoad games which I have stored in my microSD card in non-bootable hdf.

Some pictures from SysInfo:




(93 replies, posted in Amiga)

MikeJ wrote:

Could you email me the core/ini files which work, and let me know which ones don't?
Its odd, the only change is in way chipset timing works.

I just sent you an email with links to dropbox. I include 2 folders:
- Non working cores (Sep 20)
- Working cores (July. Came with my system)

I hope this information helps a bit.