Multi Evolution 500 and Amiga A501 expansion cards on an Amiga 500

0.00 avg. rating (0% score) - 0 votes

I came across a Multi Evolution 500 SCSI controller expansion card on eBay, which was described by the seller as faulty since the card did not seem to detect his SCSI hard drive and simply reported either SCSI Read, SCSI Status or SCSI Timeout for all the available SCSI IDs:

Multi Evo Boot Not Installed

Knowing that the unit couldn’t just be faulty as electronic devices of this age (circa 1994) were built to very high quality standards and literally like tanks, that is to last for decades, I decided to purchase the item for my experiments. The item arrived a few weeks later from Germany in good physical conditions. The front with the LED indicator, the side expansion socket, and the SCSI port also look clean, with no metal rust or things like that:

Multi Evo 500 FrontMulti Evo 500 Back

I opened it up and noticed the 2 SIMM memory sockets, which showed that my unit is manufactured by Off Limits, which uses SIMM memory, and not SIPP memory which is very rare and probably cannot be found today:

SIMM Socket

The original unit, with the SIPP memory socket, could have looked like this:

Multi Evo 500 SIPP Memory

I proceeded to search my junk box for old SIMM memory, and sure enough, I found 2 pieces of 4MB 30-pin SIMM memory that fits into the socket. After a simple installation and reboot, my Amiga now reports 9MB of memory, that is 512KB chip RAM, 512KB from the trapdoor slot and 8MB which has just been installed:

9MB of memory

Take note that you have to use normal SIMM modules, and not composite SIMM modules, which have a lot of memory chips (usually 8) on it and is not compatible with the Multi Evolution 500 (or with many other older hardware such as Apple Compact Macintosh). Below are the photos of a typical normal SIMM memory and a composite SIMM module:

Normal SIMM4x-1MB-30-Pin-60ns-FPM-Memory-SIMMs-4MB

With the maximum supported amount of memory (8MB) installed, I now needed to install the SCSI hard drive so that I no longer had to boot my Amiga 500 from floppy. As I do not have any working 3.5″ SCSI drive, I resorted to using the SCSI2SD converter by AmigaKit, which emulates a 3.5″ SCSI hard drive using an SD card:


This device is originally designed by codesrc, and all the associated firmwares, circuit diagrams, etc. are in the public domain. The documentation can be found here and the firmware source code can be found here. Take note that the SCSI2SD has an internal built-in active SCSI terminator, which should work by default with the Multi Evolution 500, but can be disabled by sending commands through a Windows application via the onboard micro-USB port, in case you want to connect other devices on the same SCSI bus.

With the SCSI drive physically installed, the next step is to partition it and install Workbench 1.3. Download the Evolution-30.dms listed under the Multi Evolution 2000 files (not the MultiEvo500-22.dms file which is listed under the Multi Evolution 500 files – I will explain why later) install disk from here and write it to a 720KB floppy disk. For this, you will probably need another Amiga and a tool to burn DMS images, for example this one. In my case, I used my other Amiga 600 for this task:

Multi Evo DMS Write

Now boot from the created floppy and you will be presented with some German prompts. Just press J (German for Ja – Yes) to proceed:

Multi Evo Install 2

The tool should detect the SCSI drive and asks if you want to change the drive parameters. Press N twice (German for Nein – No) and it will reported that the installation has been succesful:

Multi Evo Install 3 Done with Partition Need KS 1.3

At this stage a single partion containing the entire available space is created on the drive, which should be good enough for most purposes. If you want to create multiple partitions, you may need to use something like HDToolBox. If not, just reboot from a Workbench 1.3 boot disk and the system should detect that the SCSI drive has been installed and set up properly:

Multi Evo SCSI Installed

If your Amiga hangs at the next reboot, checks to make sure that it is on Kickstart v1.3, and not Kickstart v1.2 (even though the specs say v1.2 is supported). Also make sure that you are using the Multi Evolution v3.0 setup disk, and not v2.2. If the v2.2 disk is used, you may encounter a “Software Error – Task Held” error message during partitioning, and will have to reboot your Amiga:

Multi Evo 2.2 Install 3

It is worth mentioning here that the Multi Evolution startup code only reports that a SCSI drive has been installed if it has been partitioned properly; otherwise it will simply say “SCSI Read” or “SCSI Status”. The code will also try to enumerate the SCSI bus several times before giving up, most likely to cater for old hard disk drive which takes time to spin up and initialize. With the SCSI2SD all it takes is a single enumeration for it to be detected, but the algorithm is still there for backwards compatibility.

Once you are inside the Workbench desktop, right click the new hard drive partition (which should show something like DH0:????), and choose Initialize to format the disk, giving it a name like WB1.3. The process should take a while as it attempts to format the hard drive cylinder by cylinder:

Formatting Hard Drive

When formatting is completed, launch a Shell session, and copy all files from the Workbench 1.3 floppy over to the hard drive with the following command:


After that, type ENDCLI to close the shell session (there is no option to close it from the user interface!) and press Ctrl-Amiga-Amiga (the Amiga’s way of saying Ctrl-Alt-Del) to reboot and your Amiga should boot into Workbench from the hard drive:

Amiga 500 Full Set

At this point the basic setup is completed. I also tried SysInfo and noted that the SCSI2SD is detected as evolution.device:

Sysinfo SCSI

The Memory section reports 512KB chip RAM, 512KB slow RAM (from the trapdoor expansion slot) and 8MB fast RAM installed:

Amiga SysInfo Chip RAM  Amiga Sysinfo Slow RAM Amiga Sysinfo Fast RAM


My final wish for this Amiga is to installed a Real Time Clock RTC module so that the computer can remember the time (something taken for granted nowadays) properly. The Amiga (and most vintage computers of the 80s) does not have the RTC installed by default. For this I found a junk Amiga A501 with 512KB RAM expansion and an onboard RTC module from eBay:

Amiga A501 No Battery


The 3.6V Ni-Cd battery to maintain the time leaked and had to be removed. I cleaned up the PCB and soldered in a new replacement battery, also purchased from eBay:

3.6V Battery

With this repair, I proceeded to remove the existing 512KB trapdoor memory module and install the A501. AmigaDOS now could detect the RTC upon startup, and showed the current time (after it has been set in Preferences, or from a shell session using the DATE command):

WB Boot with RTC


Take note that the RTC will not run without a working battery installed, unlike modern computers whose RTCs can run from the motherboard power supply rails when power is on. If no RTC is detected, AmigaDOS will report “Battery Backed-up Clock Not Found”, and default the system clock to the timestamp of the floppy disk:

WorkBench 1.3 Boot No RTC


With 8MB of RAM, a 256MB SD card running using SCSI2SD, and a real-time clock, my Amiga 500 setup is completed. Next on my wishlist is to get this Amiga 500 on the Internet, perhaps by using a PPP server or by using plipbox, an Arduino-based parallel port Ethernet adapter for the Amiga. When I have the time to work on it, I will write the next article. Stay tuned!

0.00 avg. rating (0% score) - 0 votes


A tough developer who likes to work on just about anything, from software development to electronics, and share his knowledge with the rest of the world.

6 thoughts on “Multi Evolution 500 and Amiga A501 expansion cards on an Amiga 500

  • October 28, 2017 at 8:51 am

    I know this is an old post from last year but I also have an Amiga 500. I recently purchase an Multi Evolution 500 SCSI-II. I want to also be able to connect it to my Amiga 500. At one point in you explanation you mention that a second Amiga might be needed, that’s where I’m out, because I don’t have a second Amiga. So I would like to know if you have the files needed on 3.5 floppy disk to make this successful. If you do I am willing to purchase them from you.

  • ToughDev
    October 28, 2017 at 8:55 pm

    Since the burning of DMS image to a floppy requires some disk space to store the image and another floppy drive to insert the floppy disk to be programmed (besides the system drive where Workbench is booted from), a second Amiga is preferred so that you can burn the image conveniently, unless your Amiga has more than one floppy drive. I can send you a floppy disk pre-programmed with the Multi-Evolution image. Will contact you via email. Thanks.

  • August 30, 2018 at 4:58 am

    Some “magic” keys for the Multi Evolution 500 controller:
    -Press fire button (joystick in second port) on reboot and the controller will skip initialization and will be disabled.
    -Press (and hold it) when SCSI scanning reaches unit 6. After scanning unit 6 this will break the infinite SCSI scanning loop.

  • ToughDev
    August 30, 2018 at 10:27 pm

    Foo, thanks a lot for sharing the tricks on the Multi Evolution 500 :)

  • August 31, 2018 at 3:05 am

    The second bullet point was cropped because it was partly interpreted as HTML…
    It should read:

    Press Del key (and hold it) when SCSI scanning reaches unit 6. After scanning unit 6 this will break the infinite SCSI scanning loop.

  • September 2, 2018 at 5:42 pm

    After installing VXL 030 accelerator I had to press the button to disable the controller, boot from floppy to kickstart 40.68 (if I remember correctly) and then reboot again to be able to boot from hard drive. There was some conflict between the VXL and Multi Evolution I think. Can’t remember, many years ago. Unfortunately I can’t remember all commands for Multi Evolution, maybe some are linked to mouse buttons as well, not just joystick button and keyboard.

    Just mention this for the record, if someone has trouble with an accelerator in combination with Multi Evolution.

    (I stumbled across this as I try to read an old SCSI drive formatted for Multi Evolution in a PC running Linux. Not too sure how well Multi Evolution followed partition standards and boot standards)

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>