Porting AmiKit XE to FS-UAE

AmiKIT XE Installation on FS-UAE
Written and created by Espen Skog
(C) 2019


Thank you to Ján Zahurančik for making AmiKit and the donation of
the full AmiKit XE allowing me to make this guide


LIMITATIONS AND DISCLAIMER: This author of this guide does not take any responsibility for whatever data or setup you might lose. You should always back up things before trying any of the steps in this tutorial. This guide is unofficial and based on current versions of FS-UAE and AmiKitXE, thus changes in either solutions may render this guide outdated. The launching of native OSX apps thru Rabbithole is not supported but work is currently being done to achieve this for full Rabbithole functionality under FS-UAE. Again – if you are following this guide, make sure you back up your current AmiKit setup in case you want to roll back to the default AmiKit setup with Wine and WinUAE. Do not email the author of AmiKit if you have any problems or questions in regards to this guide.




Purchase AmiKit XE from the official page http://www.amikit.amiga.sk. Download and Install AmiKit XE on your Mac according to the installation procedure. This means opening the DMG package and dragging AmiKit over to your Applications folder, starting it and following the on screen prompts until the whole setup process is done. Refer to the manual if needed.

PS! You will of course need e.g. OS39 ISO file + kickstarts to properly install AmiKit.

When AmiKit installation is done and you are finished setting up the screenmodes and so on, boot up your AmiKit and make sure it all works fine. Upgrade to Workbench 3.1.4 and run all the Live Updates if you like. When you are done and happy with this, you must ask yourself the following question:

“Am I satisfied and happy – or do I want to proceed to migrate things over to FS-UAE ?”

If the answer is that you feel fine with using wine+winuae like it is, you can stop reading here and enjoy your newly installed AmiKit on your Mac.

But if the answer is that you really want to use FS-UAE as your emulator instead of WinUAE on your mac, then you should read on.


Background for this tutorial…

So – many are probably like me. They use a Mac because they don’t find themselves happy with Windows operating system. If you are like me – then you probably don’t like the thought of having Wine and WInUAE running on your Mac (and messing up your perfectly Microsoft Free operating system with DLL files and Wine stuff J )

But, since AmiKit comes with WinUAE (and Wine to run it) you need to find a way to host AmiKit under another emulator – like FS-UAE instead (which in my opinion is a super great Amiga emulator for Mac).

This tutorial will help you get your AmiKit over from the WinUAE emulator to the FS-UAE emulator. This might sound easy! Just take that hardfile and boot it up in FS-UAE instead, right ? Wrong! J The hardfile which AmiKit runs on is in a format which FS-UAE does not boot up straight out of the box. If you try – FS-UAE will just guru at boot. The reason is, if I recall correctly, because the hardfile image on AmiKit uses the Dynamic HDF format.

So the next part of this tutorial will show you how you get your newly set up AmiKit hardfile to run on FS-UAE.


Initial preparation…

I have prepared a 2GB Hardfile for you which is pre-formatted and setup with Professional File System 3.5 so that this shitjob is done in advance and you don’t have to do it. The hardfile is empty (I cannot provide neither the OS or AmiKit itself as they are not free) so what we are going to do now is to mount the new 2GB hardfile in parallel with your AmiKit hardfile and copy all fies from one drive to the other.


Let’s begin…

STEP 1: Download the empty fs-uae compatible hardfile

  • First – you must download the empty 2GB hardfile from: here
    NOTE: The ZIP file is very small, but once unzipped it is 2GB.


STEP 2: Configure WinUAE under AmiKit to mount the new hardfile

  • Open AmiKit from your Applications folder and click “Configure”.
  • Now click on the HARDWARE->CD&HARDDRIVES meny on the left most side.
  • Choose the newly downloaded hardfile (unzip it first) and click OK

Screenshot 2019-05-13 at 15.45.38


  • Then click “Start” on the lower button row to start the emulation.



When it boots up, it should look like this:

Screenshot 2019-05-13 at 15.45.49



  • Open up a shell by clicking the icon to the right of the magnifying glass on the icon row at the bottom of the screen. It should look like this:

Screenshot 2019-05-13 at 15.46.04



  • Type the following command and hit enter:

Screenshot 2019-05-13 at 15.46.31


This process will copy ALL files from the native AmiKit hardfile over to our new FS-UAE compatible hardfile (called AK00: for now). Don’t worry – we will change AK00: to AK0: at a later point 🙂

(NOTE: This copy process might take from 15-30 minutes depending on your system)


  • Now, open HDToolBox from the menu as shown below:

Screenshot 2019-05-13 at 15.46.40


The output from HDToolBox should show you the same output as in the image below:

Screenshot 2019-05-13 at 15.46.52

  • Click on the 2GB drive and the click the “Partition Drive” button.
  • Change the Partition Name from AK00 to AK0 (beware: these are zero’s and not O’s)

Screenshot 2019-05-13 at 15.46.58


Change it from:
Screenshot 2019-05-13 at 15.47.07

Change to:
Screenshot 2019-05-13 at 15.47.13


  • Hit enter and the Click the “Save” button. This will bring you back to the main screen.
  • Exit HDToolBox.


Now we need to rename the new harddrive to its proper name before we reboot.

  • Right click “AmiKit00” and select “Rename” (Beware: Make sure you right click on AmiKit00 and not AmiKit)

Screenshot 2019-05-13 at 15.47.23


  • Enter the new name “AmiKit” and hit OK.

Screenshot 2019-05-13 at 15.47.30

  • EXIT your AmiKIT/WinUAE Emulation window. You are almost finished!



STEP 3: Setting up in FS-UAE

Now that we have successfully set up the new hardfile and copied ALL the files from the native AmiKit hardfiles over to our new FS-UAE hardfile, we can start up FS-UAE and begin configuring it.

Before that – you should have downloaded and installed the latest FS-UAE for your Mac (actually, it should work for Linux as well). Please follow the instructions on the screenshots below to set up FS-UAE Launcher with the proper settings for AmiKit to boot smoothly.

  • Create a new Configuration (in this case it is called TEST KIT).
  • Choose A4000 and 3.1 ROM
  • Set Amiga Joystick = NO HOST DEVICE

Screenshot 2019-05-13 at 15.47.41


Choose the PFS-AmiKitXE_2GB.hdf file as your first disk by clicking the grey document-icon (right to the yellow icon) to pop a requester so you can choose your hardfile.

Then (VERY important not to for get this) create a directory called “Rabbithole” and “Dropbox” on a place on your system disk. For instance on your desktop. Then Create the 3rd and the 4th entry according to the picture below. Keep in mind to click the “Yellow Folder” icon to create these two directory links. You could probably also point to your real Dropbox folder if you have one.

Screenshot 2019-05-13 at 15.47.48


  • Set ChipMem to 8MB
  • Set Zorro III Fastmem to 128MB (or more if you like)
  • Set Graphic Card RAM to 128MB

Screenshot 2019-05-13 at 15.47.58


  • Set Amiga Joystick to No Host Device

(in my experience, if if do not do this, they keyboard arrows do not work as they are interpreted as joystick movements which is very annoying under CLI if you wanna use keys to move the cursor)

Screenshot 2019-05-13 at 15.48.09



  • Set Graphics Card = UAEGFX Zorro III
  • Set UAE bdssocket.library = Enabled

Screenshot 2019-05-13 at 15.48.23


  • Set CPU = 68040-NOMMU
  • Set JIT = Enabled
  • Turn off floppy sounds if you hate them 🙂

Screenshot 2019-05-13 at 15.48.31

Click the SAVE BUTTON (the red arrow right to the “TEST KIT” name to save your new config.


STEP 4: Booting up FS-UAE and tuning the screenmode…

Everything is now ready and you are good to go. If you have done everything according to this guide, you should be able to hit “START” in FS-UAE.

Here is what to expect from the first boot:

  • It will show 5-20 seconds of black screen (don’t worry – just wait)
  • Then you should see (only the first time you boot) a progress bar which load up to 100% on the top of the screen and then nothing seems to happen for a while
  • Just wait 2-3 minutes and all the sudden the workbench shows up in a dull 8 colorgray/blue color like on the picture below (THIS IS NORMAL!)

Screenshot 2019-05-13 at 15.48.40


Hit Right Amiga+E (or right CME+E) to open a file request and enter Screenmode and hit OK. Or you can navigate to the the screenmode icon under Prefs I you like. Never the less, just open “Screenmode” somehow 🙂

Screenshot 2019-05-13 at 15.48.51


  • Now scroll down to 1600x1080x32bit.
  • Select it and click SAVE

Screenshot 2019-05-13 at 15.48.58


You will be prompted with 2-3 requesters like the one below and just click SAVE and RETRY afew times until they go away.

Screenshot 2019-05-13 at 15.49.07

After 2-3 requester clicks, you should see a beautiful blue desktop like this:
(we are very close now)

Screenshot 2019-05-13 at 15.49.14

It is time to reboot to getall things in order (as you might see – the task bare is missing).


  • Reboot by pressing Left CMD+R (or restart the emulation in your preferred way)

After reboot the emulation should boot up perfectly into this nice full AmiKit XE Workbench Screen as seen in the picture below (look – the taskbar is back!)

Screenshot 2019-05-13 at 15.49.27



STEP 5: Final words…

So – you successfully migrated AmiKit from the WinUAE hardfile over to a hardfile for FSUAE. You can now run Morpheus and do a Live Update and use your AmiKit XE. We are finished!

GOOD JOB – you did well.

You can now use AmiKit XE normally and run Live updates and so on. Enjoy! 🙂


UPDATE #01 – AUGUST 2019 – Speed Control:

There is a need to point out that there is no quick way, like on WinUAE, to set the cpu_throttle. This means that when you set up FS-UAE in 040-NOMMU mode, it will suck your host-cpu dry and your cpu fan will  most likely run like crazy (mine does!).

So — to fix that, I have set a manual config value for FS-UAE which speeds down things a little. Enough to keep my CPU fan silent when idling in FS-UAE. My goal was to find a cpu_throttle value which worked for my hardware in terms of spinning fast enough to keep emulation to a nice level, without the CPU fan going crazy 🙂

Beware that the “perfect” value for cpu_throttle varies from system to system. My host system is a I7 with 8MB Ram and running on 3GHz. So I found out which cpu_throttle which worked best or my setup. Your setup might require a different value to operate as you wish. It’s just a process of trying out different values in increments of 100’s until you feel ok with speed vs. noise ratio.

Screenshot 2019-08-23 at 12.20.05

In the illustration above, you can see that I have added a CPU Throttle of -400. This works perfect for me and the HW on my host laptop. The fan runs silent and the emulation is good for my workbench use.

The CPU_Throttle values range from -900 to 5000.

  • uae_cpu_throttle = -900  <– Lowest speed
  • uae_cpu_throttle = -400  <– Quite low speed — but works good on my setup
  • uae_cpu_throttle = 5000  <– Max speed.


So to sum things up. Work your way up from -900 up to a value which works for your hardware setup. If you want the max speed, just set it to 5000 or you can also skip the option as default is 5000 (max) and maybe you don’t care about fan noise 🙂 If you are on a laptop, you might care more about the speed and heat than if you run on a desktop machine.

If you want to really tone things down, and mostly work in Workbench, you can add even more parameters:

uae_cpu_throttle = -400
video_format = rgb565
video_sync = off

So, enjoy this little update and I hope it helps if you are a little annoyed about your laptop fan noise.



Telnet-oppsett mot ABBS

Screenshot 2019-04-15 at 13.38.29

Dersom du ønsker å få til et oppsett i din Telnet klient, enten det er på Windows, OSX eller Linux, så er det en enkel løsning på dette. Heldigvis så har vi noen enkle steg allerede laget for deg som bare ønsker å klikke seg gjennom en ferdig laget oppskrift.

Det er i praksis to viktige ting du må endre i innstillingene:

  • Justere innstilling slik at Backspace fungerer (“CTRL-H sends Backspace“).
  • Definere korrekt tegnsett i telnet-klienten slik at ÅØÆ fungerer.

www.silverhawk.me så har vi samlet litt info om BBS’en og vi har samtidig laget en oppdatert guide til deg som bruker Putty eller innebygget telnet klient (via BREW i OSX eller under Linux).

Så for deg som bare vil ha det enkelt og greit, kan du se på skjermbilder av oppsett her for å enkelt sikre at tegn som ÅØÆ og Backspace fungerer slik vi ønsker.


Når dette er gjort så er det en siste lille ting som kan være viktig å merke seg. På selve BBS’en må du sjekke at du har korrekt tegnsett. Dette gjør du ved å bare skrive (hvor som helst inne på BBS’en) kommandoen “u s iso” og så trykke enter. Da settes tegnsettet til ISO. Logg deretter av og på igjen og norske tegn og backspace skal fungerer korrekt.

Dersom du har problemer når du er inne på basen kan du skrive “COM” + enter for å sende beskjed til SysOp direkte.

Skulle du ha problem med at ditt passord ikke fungerer eller du rett og slett har glemt dette (!) etter 20 år, så finner du tips om hvordan du kan få nytt passord på SMS dersom du telnet’er til BBS’en (info står på forsiden).

Til slutt kan vi informere om at support kan man søke i Amiga Norge Facebook-gruppa. Her finnes både SysOp og CoSys. www.facebook.com/groups/CommodoreNorge





Passion For The Product – The importance of Customer Service


Forget the money-aspect for a while. Money is just a side-effect and an outcome of something much more important. Put yourself in the position of being one of your own customers instead.

Now, imagine you are having a problem with a system or a piece of software. It’s not the first time it bails on you, and this frustrates you. Now, what do you do? You reach out to Customer Service, of course. The team of selected employees you put your trust in to handle all your paying customers daily issues.

Let’s stop here for a second! Any system, or piece of well written software, can and will crash every now and then. It means that your company will need a set of highly skilled support and service minded individuals. They are the ones who are brought in to put out the fire, stabilize and re-set these situations. To keep everything under control on a daily basis.

Most teams do this already, but that is beside the point. The important factor is how the team operate, how they care for the situation and how they resolve it. You could, or rather: you should, think of them as the company’s ER-Team that handle critical situations and acts as Rescue-Gods for any given IT-crisis. Why? Because it is actually true.

So, let’s get back to you and your current system issue. You are contacting Customer Service and you hope they greet you with a magic wand which miraculously takes care of things so that you can go back to your tasks again. It is true – when we call Customer Service, we hope for the best, but we prepare for something less. So, why is that? Why do we often tend to expect not to be blown away by user friendliness and ultra-fast resolve times and swift solutions by the “IT-Ninjas”? We deserve it – don’t we? I mean – we paid full price?


Many businesses treat the Customer Service center as a place to put employees in order for them to learn the products and get to know the company, and then they move on after a while. This team is often the face of the company when it comes to daily contact with the customers. The passion and dedication from these individuals makes the company stand out as a caring and helpful partner. The passion for helping and resolving any kind of situation and to treat the customer call as if it was the most important thing of the day. That is what will put a smile on the customer’s face. It lowers the bar for contacting Customer Service. It actually has nothing to do with technology at all.

An important part of helping a customer is to recognize and understand the given situation and to quickly drill to the core of the problem. All this while making sure nothing turns into a full day of frustration. Then, guide the customer to a solution in the same manner as we would expect to be treated if we got hurt and had to be hospitalized. You know, most of us don’t really care so much for the surgeon’s way of performing that particular operation. You probably value the steady flow of information, the quality of the caregiver and the level of service higher than any details of the actual surgery being done:

 “Wake me up when you are done and tell me everything is ok”– Right?

Back to your system-issue again: If you take the current IT-problem and split it in half; First half is the technical part, obviously. The second half is the communication part. Then you will often find that the situation is much easier to resolve if you set aside time to keep the customer updated regularly as opposed to them having to call for updates (The latter will definitely fuel the fire).

Let us kick it up a notch: If you are truly passionate about both what you do and especially the products which you are working with, you will stand out as very trustworthy and this builds confidence. You will be trusted and selected every time something happens. People always follow the pattern of the least resistance.

Let me bluntly put it like this:

“If you love what you do – the customer will recognize this and look forward to calling you back”. Not only that – they will speak dearly of their experience to their colleagues, friends and family.


Why is this so important? Well, because the next time it might be that the roles have shifted and you are on the receiving end. I am pretty sure you would like to be reassured that your surgeon is highly dedicated, passionate and will walk that extra mile to make sure the operation is a success, right? Don’t we all feel extra special when the surgeon (or IT-guru if you like) takes time to both keep you well updated on the process while actually solving the situation?


So – make sure your Customer Service team is extremely passionate and then treat the team as if they were brain surgeons — because they actually perform digital surgery every day.





SilverHawk BBS – Omtalt i IT Avisen

Screenshot 2019-04-12 at 21.55.10Det er spennende teknologitider vi befinner oss i. Jeg sikter selvsagt (!) ikke til dagens teknologi, men til det som vi vokste opp med på 80 og 90 tallet. Teknologi som formet oss fra å være kinaputt-sprengende småunger i gata som slædda rundt på løkka, til å bli ærverdige Amiga brukere som vokste opp med den feteste hardwaren på markedet. Vi rewla det meste — også på BBS fronten. Særlig i Norge. Her i landet var det BBS-Frenzy på 90 tallet og vi var alle bergtatt av å arbeide oss opp grusomme telefonregninger. Heldigvis var BlueBox’ing en praktisk løsning på utfordringen, men ingen brukte jo det ettersom det ikke var lov.

Modemet var kommet for bli (på gutterommet). Døgnet hadde ikke lenger noen særlige begrensninger på hva som ble ansett som dag og natt — ei heller hva man anså som skikk og bruk i forhold til å få nok søvn 🙂 Heldigvis på den tiden hadde man plenty av energi og holdt ut både 24 og 48 timers sesjoner foran skjermen…erm…korreksjon: CRT skjermen.

Heldigvis så er Amiga miljøet i full sving fortsatt. Det lages ny hardware, akselleratorkort, minnekort og til og med helt nye Amiga hovedkort og FPGA kloner. Alt skjer av dedikerte selskaper og privatpersoner. Sky is the limit! Det er Amiga Klondyke om dagen. Prisene på C= hardware er syke og man må glatt ut med 5000 for en bra specca Amiga.

Her er to screenshots som omhandler hva du bør sette som settings i Terminal under OSX for å få optimal connection med norske tegn på basen:

I tillegg må du sette ISO karakterset inne på basen ved å skrive “U S ISO” og så enter + logge av/på. Deretter kan du nyte norske tegn og backspace som fungerer 🙂

For å komme litt tilbake til BBS-temaet så er SilverHawk BBS omtalt i dagens IT-Avisen under:

IT-AVISEN: https://itavisen.no/2019/04/12/slik-var-var-det-a-koble-seg-til-nettet-for-www-flyttet-norsk-bbs-til-skyen/


Nyt sommeren (innendørs foran skjermen)!




Interplay – The Story Behind The Success


© 1994-2019 SilverHawk Software


The Story Behind The Success


Every now and then, you come up with a brilliant idea. An idea which originates from frustration because no one else has solved the problem. In our case, it all started when we received a CDRom. You’ve got to remember, this was back in 1994 and the first 1x and 2x CDRom drives were emerging for the Amiga. We had one of the French made 2x CDRom drives from a company called Archos. This was a PCMCIA-connected CDRom solution which had an external case and a proprietary pcmcia-adapter going from the IDE connector of the Mitsumi-drive and connected into the PCMCIA connector of the A1200.

Picture1(Picture: The Archos PCMCIA Overdrive CDRom for Amiga 1200)


The CDRom worked quite well. It mounted discs as CD0: under Workbench and everything worked well. It even let you play CD32 games by doing some scripting and mounting tricks. I remember we bought one CD32 game with this CDRom, and that was the game Banshee – a shoot ‘em up game. It was more or less just the A1200 game with some added Audio tracks on the CD.


The CDRom was a nice addition to the A1200 setup, but it lacked one very important piece of software: A good audio cd player. The audio cd-player provided with the CDRom opened up in full screen and looked like it was made to mimic the one which CD32 had: Colorful and fullscreen.


Picture2(Picture: Specifications of the Overdrive CD Rom Drive)


We were always a bit annoyed that we had to use a full-screen player in order to listen to audio cd’s back then, and started looking for a better piece of software which would play audio CD’s on the workbench screen instead.  What we actually found out in ’95 was that there wasn’t a player which worked for the Overdrive CDRom. Remember that back then, most CDRoms for the Amiga was using the scsi-interface and thus most CDPlayer software was targeting the scsi.device to control it. In our case with the Overdrive CDRom drive, it was using the Commodore cd.device.


So – we had to make our own software. Stian Olsen was already then a great C programmer on the Amiga and was using Lattice C as his main development suite so he was doing the programming part. Espen Skog did the GUI design and development part. Together we combined our knowledge and enthusiasm and started on what was going to be the first version of “CD Player”. This first version was more like a proof of concept. We used the cd.device and tested its functions to see if they corresponded with the set of features which we added to the GUI for our program. It worked very well. We had a fully working version and released this to the public via Aminet on the 27thof February 1995.


Internal versions of the player took shape and we had a V2 and V3 done during 1995 and added more and more useful functions.

(Picture: Interplay 2.1 – with programming mode added)


We decided to do a name change after the first release of CDPlayer1.0 and came up with a more suitable name for our bellowed CDPlayer and named it: Interplay. Interplay versions 2 and 3 are not currently available on Aminet but we will see if we can dig them out and upload them from our BBS which should hold all versions ever released (www.silverhawk.me) . SilverHawk BBS (still running at telnet nodes on bbs.silverhawk.me on port 6400) is the Support BBS for Interplay.


Now, some of you might say “Hey – you ripped off the name from the makers of Doom”. Please keep in mind, we were pure Amiga enthusiasts. We did not own PC’s or play games on them. So the name Interplay was actually something we came up with without knowing about that PC Software House. The name suited the product and we were happy to now have named our baby. It was now time to really take Interplay to the next level. So we added something which did not exist on any Amiga CD players back then: An algorithm which gave each inserted CD a unique checksum and stored this in the Interplay Database. The user could then open the TrackName Editor and label each audio track and the name of the CD and the band. The next time the user inserted the CD, it would recognize it and would be presented with a playlist with the name of the tracks instead of the somewhat boring “Track 01, Track 02….etc” type of presentation.


So, we now had a proper CD Player for the market and we were targeting those with IDE CDRom drives (like the Archos Overdrive) in general. Of course, we did not exclude the owners of SCSI CDRom drives, but we were glad to have a very juicy CD Player for the growing IDE Interfaced CDRom drives which had started to emerge.


The market started to pick up on Interplay and it did not take long before we saw people supporting us, emailing us with tips and bugs to solve. One guy (Steven Ross) actually made a complete editor which loaded the Interplay Database and enabled you to edit your complete library of registered CD’s.


Picture5(Picture: CD List Editor by Steven Ross)


His software was called InterplayCDEditor and was launched on Aminet November 1995 and you can find the link for it in the resource section below. A big thank-you to Steve for making the great editor.

Picture6(Picture: CD List Editor – Editing entries made easy)


Amiga Shopper included our version of Interplay (4.0beta) on their cover disk in the February 1996 edition. And handed us a quite nice review.


Picture7(Picture: Amiga Shopper Feb ’96: Reviewing Interplay)


Another contributor was Gregor Rosenauer who gave Interplay a pretty NewIcon as we had not included a NewIcon with our product. Thanks, Gregor. His Icon can be downloaded from Aminet and the link is in the resource section below as well.


While Interplay was getting more and more users worldwide, the product also got excellent reviews in different Amiga magazines and was spread on cover disks as part of their PD section.


Picture8 Picture9
(Picture: Nice feedback from a user of Interplay in Amiga Shopper March 1996 edition) (Picture: Excellent review from Amiga Shopper February 1996)



Since we did not charge any money for Interplay, the software was bundled with a lot of Amiga magazines back in the mid 90’s. We had no idea that Interplay was being bundled until free magazines started to appear in our mail boxes.


During 1996 we had Interplay in sort of a Final version 4, but released a 4.1 version which included some minor fixes. Since Interplay now worked very well with IDE based CDRoms on the Amiga (plus the SCSI drives we tested via our supporters) we figured we should freeze the software and let it rest for a while. We had no more ideas how to improve it and we were actually very happy with its performance. But, “Feature Creep” came lurking and we revisited the idea of making a new type of GUI for it. Many Module players started to have these nice graphic GUI’s and we began planning a Version 5 of Interplay and even a Gold-edition. The Gold edition would have a GUI with a gold-coloured theme. So Deluxe Paint was used to draw buttons and to add a colorful theme to Interplay.


(Picture: Interplay v5 About Screen)


Sadly, we did not finish this and we published a note on Aminet http://aminet.net/disk/cdrom/Interplay5inf.lha where we informed the users that V5 would not be released. We were so busy running our BBS and this was also a busy time with school and work so neither the Gold of the regular Version 5 of Interplay was released.


(Picture: Interplay 5 Gold template buttons)


During 1995 and 1996 we were informed from our various users that Interplay worked very well with many different setups and models of CDRoms. So we started to add a list of CDRoms and cd-controlers which reportedly worked well with Interplay, and we put this information in with the documentation so that the user would be able to see if his setup was supported.


Here is the list of what we gathered back then. As you can see, it support so much more than just the Archos Overdrive:


Interplay should work fine with the following setups:

* Archos’ Overdrive
* Zappo CD-Rom
* SCSI CD-Rom drives under Kickstart 3.1
* HiSoft’s Power CD-Rom (Using squirrel pcmcia scsi-2 interface)
* Commodore CD32 (with SX-1 Module present)
* Commodore CD32 (with ProModule present)
* Other SCSI CD-Roms connected to the Squirrel scsi interface.
* SCSI CD-Roms connected to Dataflyer SCSI+

Interplay is reported to be working on these setups:

* Archos’ Overdrive
* Zappo CD-Rom
* SCSI CD-Rom using the Squirrel ™ SCSI controller.
* SCSI CD-Rom and Kickstart 3.1
* Commodore CD32 (using the SX-1 module)
* Commodore CD32 (using the ProModule)
* HiSoft’s Power CD-Rom (Using squirrel pcmcia-scsi-2 interface)


During the months of the Interplay era, we received lots of great reviews from various Amiga magazines. We received great feedback from the users around the world and we were sent magazines which had reviewed and incorporated Interplay on their Cover Disks. Two Norwegian guys in their early 20’s, just doing what started as a fun idea, and we started to receive incredible reviews like these:


Amiga Computing – Sept 1995:

“This is one of the best CD players for the Amiga”

Amiga Shopper – Dec 1995:

“Interplay 3.1 is an excellent audio CD player…”

Amiga Shopper – Feb 1996:

“Rolls Royce’s of CD Players”


That was the long story behind Interplay. Thanks for reading.



Name Launch Date Link
CD Player V1.0 1995-02-27 http://aminet.net/disk/cdrom/CDPlayer10.lha
InterplayEditor V1.08 1995-11-01 http://aminet.net/disk/cdrom/IPlayEd108.lha
Interplay V4.1 1996-02-18 http://aminet.net/disk/cdrom/Interplay41.lha
Interplay NewIcon 1996-02-13 http://aminet.net/pix/nicon/2newicons.lha
Interplay5-info 1997-07-29 http://aminet.net/disk/cdrom/Interplay5inf.lha



Digital Care in Healthcare


No, not if you play your cards right. But if you focus solely on security, you might miss out on some very important factors. What do you do when there is an urgent need to take advantage of portable technology such as tablets or other mobile devices to bring portability and mobility to doctors and specialists within healthcare? How will you be able to bring certain kind of software, which was never meant to spin in that direction, to operate in this new world of mobility ?


For many companies, digital security and attending to that ever growing heap of important data is of course very important. No argument there. However, within certain areas some type of information can seem harder to protect because there is a growing need to strengthen the walls of digital security while still allowing access to the same information from the outside. I am not going to talk about different approaches to solve this as there are simply too many ways to do that (and to be honest, I am not an expert on that subject). But, what I would like to mention is that it is important to take a bold step out of the box and make sure that the focus is on the end user, the patient, the customer or whoever you are serving. Allow yourself to be brave and dare to step out onto that thin ice we call experimentation – to add and design the functionality from the users standpoint before digging in to details too early which might end up as a limitation to yourself and your creativity. Do not think that “If I just add enought security, I have at least covered my back and can work from there“.


So how can we conclude ? Shall we limit functionality and maintain the level of seurity to such a degree that we are almost guaranteed that the data is secure, or can we simply say that “this is good enough” and have a well balanced layer of both security and functionality ? I would recommend the latter. If you are sure that you are covering your basics and have a nicely designed solution which can expand and serve its purpose for as long as you need by simply modifying and perfecting it while you go along, you should try to maintain that track. It gives your solution a good Digital Health.


How does this translate to healthcare ? My experience is that you are forced to add lots of layered security. It is often one of the first things we discuss when talking about patient data. You need to cover the laws and regulations to correctly handle the patients data which they are either acessing or entering into an online system or an App.

I would like to introduce the term Digital Care because it is important in this situation to enable the subject to feel comfortable. To have them trust you — just like we trust the bank with our money. I mean, you can walk into a building with a pile of cash and hand it over to a person or shove it into a machine and get a receipt. Just like the bank cares for your cash — a hospital must care for its information in the exact same manner. It´s a trust issue. And the information is actually yours. It belongs to you. It describes you. You can (or at least, you should be able to) retrieve it any time you like. It is there for you when you might need it in a medical situation — it is like any other type of information: Useful when accessible!

..So, create accessibility!
…..Let security be a default instead of a limitation.
………Focus correctly.

Avoid getting left behind and beaten by your competitor!

Unfortunately, much too often we stumble upon online services where we ask “Why is this service too old and outdated and why are nobody doing anything to improve it ?”.

Online Services
(should we take this for granted ?)

Well, the reason can be as simple as the provider not having the right focus. We all know that there is no problem so large it can not be solved. I mean, the world is filled with incredibly talented people and it is just a matter of realising the untapped resources, putting the right people together and form the correct team to dig in and do the handy work needed to bring a solution online to the users.

Sounds easy, huh? So why do we still see low hanging fruits not being picked, you may ask ? Is it because there is just too much to pick from or is it merely a situation where the focus is lost (or was never there in the first place) and not quite regained!

Customers, patients, users or whatever kind of people who are out there searching for a solution to their problem or seeking information and services all have the same need: A need for help or a need for information. And one of the important things we need to remember is that the system of today is not the right system for tomorrow. It is already outdated and constantly needs to be reinvented — otherwise you will hear the aggressive footsteps from your competitor who have just the perfect solution, and you find yourself outdated, squashed and stepped on.

Remember that the quality of and how updated your system or solution might be is not measured against the needs of the user, it is measured directly against what your competitor offers. No matter how cool, great, new or elite you may think your systems might be, you should always look over your shoulder and to your competitors as that is where you can find great inspiration for your next move.

Don’t get left behind, look to your lefts and rights and re-invent and evolve.