Thursday, June 28, 2012

How to get Delitracker working on X1000 under AmigaOS4

Today I wanted to share with you how to get Delitracker working on the X1000 under AmigaOS4.

For those who may not be aware, Delitracker is a AmigaOS 3.x program which is used to play Amiga (and other PC format) module song files. Most commercial Amiga games prior to 2000 used modules for the in game music. If you don't know what a module song or how to make them using a Tracker is, then this Wikipedia entry will bring you up to speed!

On the Amiga, there were many different types of module files like MOD (Protracker, Soundtracker, etc), MED, CUSTOM, FollinPlayer(TF), TFMX, JCB, DW, OLDW and dozens more. 

The issue is further complicated by Amiga modules being compressed to save more space (Powerpacker, XPK, etc) which required a decompression routine built into the module player to play them back!

On the PC there were also S3M, MTM, XM, ImpulseTracker (IT) formatted modules and many others too.

Delitracker supported nearly all these Amiga module formats, the PC module formats and even others like the Spectrum and Commodore 64 SID files!

These module formats all had their positives and negatives which is a topic too big to cover here! Ultimately modules were replaced by MP3, OGG, WAV and other modern day music formats as computers become faster and with substantially more memory, eliminating the need for space and cpu usage efficient module formats to be used.

So how do we play these module formats on the X1000?

Unfortunately most of the modern GUI music players on the X1000 I know of (eg. TuneNet, Schismtracker, Milkytracker) generally only plays the standard PC module formats plus some Amiga MOD and MED formatted files.

A command line module player on AmigaOS4 called UADE (Unix Amiga Delitracker Emulator) is able to play most (but not all) Amiga module formats, even CUSTOM format. However, it is CPU intensive and doesn't multitask well, breaking up audio when not in focus. It is also a command line based player which is crying out for a GUI. Seriously, can someone please write one for it!!

Screenshot below shows these programs in action on the X1000:

So we circle back to Delitracker, which I have been using on Amigas for over twenty years, right back to my Workbench 1.3 based Amiga 2000HD (which I still have!).

The last official version of Delitracker, 2.32, was released as freeware on in 2000. It was never updated to work with AmigaOS4, and has many incompatibilities which mean it will lock up the X1000 when you attempt to play any module through it.

So, even though it is AmigaOS 3.x Workbench friendly (to a point), Delitracker has a lot of issues to overcome to get it to work on the X1000 under AmigaOS4.

My focus today is to cover the steps to install and config it so it works, with some limitations highlighted on what it can and can't do.

First, you need to download some files. You will need:

  • Delitracker232.lha and AHI-noteplayer.lha from Aminet.
  • Delitracker v2.34 update dt234.lha from here!
  • timerhack.lha from
Extract all these archives to the RAM: and let's start with the installation of Delitracker v2.32 first. Open the Delitracker_II folder in RAM as below, and then double click on the English installer (or whichever language you prefer) to get started:

The Delitracker install present a load of options so I include the detailed install progress screenshots so you can see what I did during the installation:

I installed in SYS:Utilities - it will created a Delitracker_II folder automatically:

Make sure all players in below screenshots remain selected and click Proceed With Copy:

For the next question, answer Yes, as we want to install the rarer module format players as well:

For the screens below keep all these players ticked as well, and click Proceed with Copy:

For the next step I recommend not to install the PlaySID player to play Commodore 64 SID tunes - I should note here that it doesn't work under AmigaOS4 and will crash the system if you try to play SID tunes with Delitracker:

I installed the Spectrum player, but I didn't test this as I don't have any spectrum songs - in fact I never owned a Spectrum either!

For the next screen I recommend unselecting any genie with xxx-NotePlayer in the title, as these will not work on the X1000 and will cause it to crash when playing songs:

Next up I disabled the Xmas-genie. I didn't understand the point of this genie in 1996 and still don't - it does nothing useful or interesting!

I didn't install the Arexx scripts - you can if you really want - but I have never used them:

I said Yes to install the decompression libraries, as you need these:

The next two screen are just notes to finish the installation:

Ok, so now we have installed Delitracker v2.32, we next need to manually copy the Delitracker2 executable from dt234.lha over the top of the Delitracker2 executable in the installation folder, in my case SYS:Utilities/Delitracker_II. I did this from the Unarc program to save time copying the file manually but either way is ok. Once this is done, Delitracker will be upgraded to the last version available, v2.34. For whatever reason the Delitracker v2.34 update is not available on Aminet and only available on an obscure website! (I included the link in this article)

Next, we need to check the noteplayers. Navigate to the SYS:Utilities/Delitracker_II folder. Inside there you will see a folder called DeliGenies. As per the screen shot below, you will see a number of files in that folder, plus a GenieStore folder. I also have the AHI-Noteplayer folder (extracted from ahi-noteplayer.lha) on the RAM disk open, ready to copy the AHI-Noteplayer to the DeliGenies folder:

So first, move any xxx-NotePlayer files in the DeliGenies folder into the GenieStore folder. Next, as mentioned before, move the AHI-Noteplayer file from the RAM disk to the DeliGenies folder.

The result should look like this:

Next we need to install the timerhack.kmod file and update the kicklayout file to load this module on bootup. This file is needed so that Delitracker can play back modules to the correct older Amiga CPU timing, rather than the current CPU which is much faster and causes big problems with module playback.

As this file is a kmod file (Kickstart Module), it now needs to be copied from the RAM disk where you extracted timerhack.lha, to the SYS:Kickstart folder, as per the shell command in the screenshot below:

Next, we need to edit the kicklayout file using Notepad or similar program. The kicklayout file is located in the SYS:kickstart folder as below:

Now we need to edit the kicklayout file - be careful here! This file is used when booting AmigaOS4, and defines which kmod files are to be loaded as part of the startup of the OS. There are two sections of the file, one is the live "in use" loading configuration (labelled AmigaOS4.1_Update_5 as below), and one is the debug section. Make sure you add the new line to the correct live section of the file or it won't work! (I found this out the hard way):

In the live section, find the series of kmod files that has timer.device.kmod and then xena.resource.kmod. Then add a new line underneath them that says MODULE Kickstart/timerhack.kmod - as per the screenshot below:

You then need to reboot your Amiga to do the next steps of the configuration within Delitracker - we are not finished yet. Do not load any modules into Delitracker yet.

After the reboot, run Delitracker. You will get a prompt from two popups, one for PlaySID (if you installed it), and one for the Converter. Click on each window in turn, then right click the top menu and under Settings menu deselect Pop Up. Then right click the top menu again, under Project menu select Save Prefs. Do this for both windows and then select Hide for each window.

Ok, now we need to configure Delitracker itself. Click the ? button in the main program window, which will bring up the program options, as per the screenshot below. Make sure that Low Chipmem is selected. For your sanity I also suggest ticking the Songend option, so that looping modules stop when they finished playing once. It should now look like below:

Click on Ok to continue.

Next we need to stop Delitracker using the built-in Paula-noteplayer. This is not a file, so it cannot be moved to the GenieStore and must be deactivated within Delitracker. This will then force Delitracker to use only the AHI-noteplayer for playing back modules, which is what we need.

To do this, click on the Genie bottle icon in the main program window. On the Genie window that appears, click to highlight the Paula-Noteplayer in the right side, and the select the Show option, which will show the Paula Noteplayer v1.9 window, as per the screenshot below:

Click the Paula-Noteplayer window so it is in focus. Like the other popups discussed earlier, we need to now right click on the top menu, and under the Settings menu deselect Activate. Then right click the top menu again, and under the Project menu, click on Save Prefs. Then click Hide on the Paula Noteplayer window but keep the Genie window open still.

Ok, next we need to configure the AHI-Noteplayer. You should still have the Genie preferences window open, so now click to highlight the AHI-Noteplayer on the right (scroll up to see it), and then click Show. You should see the AHI-Noteplayer window as below:

Update 25/6/2014: this AHI-noteplayer prefs changes depending on whether you are running AmigaOS4.1.5 or 4.1.6.

Now, for AmigaOS4.1.5 users untick Use the best audio mode option, which will make the Audio Mode button available. Click on the Audio Mode button, and then select Unit 0:Hifi 16 bit Stereo++ and drag the frequency bar across to 48000Hz. This higher frequency is needed to play back IT and S3M modules files in good audio quality. It should look like the screen below:

Now click OK. then Click Hide on the AHI-Noteplayer window, and click Ok on the Genie Preferences window.

For AmigaOS4.1.6 users using the built in X1000 sound card with HD Audio driver, leave "Use best audio mode" checked in the AHI-noteplayer above, click Hide on the AHI-noteplayer window, and then click Ok in the Genie Preferences window.

Finally,  we need to save all the settings we just did in Delitracker - we sure don't want to do all that again!

From the Delitracker main program window, click to make sure it is in focus and then right click on the top menu and under the Settings menu, select Save Settings. It didn't for me, but if it prompts you for a filename just accept the defaults and click OK.

Now close Delitracker by right clicking on the Top Menu, under the Project Menu click on Quit (Note: closing Delitracker from the close gadget on the main program iconfies it on the desktop and does not close it). You can edit the tooltypes of the Delitracker icon if you want to have the close gadget close the program instead of iconify it.

We need to close Delitracker so that it initialises using the AHI-Noteplayer only.

Now you can rerun Delitracker and load a test module - I chose a very customised David Whittaker DW format song from a game called Quadralien, an even older OLDW format module from a game called Obliterator, and a VectorDean formatted module from a game called Cannon Fodder - and now Delitracker works fantastic now on AmigaOS4 on the X1000 as below:

Some important notes about what can't play in Delitracker under AmigaOS4 on the X1000:

  • PlaySID (C64) SID files do not play and will crash the system if you try to play them
  • CUSTOM Amiga modules (ie. CUST.filename) will crash the system if you try to play them. This is because CUSTOM modules have a built in replayer that expects to have the Paula soundchip from the Amiga present and it will not retarget through AHI.

Custom Amiga module formats can be safely played in UADE without a problem, but keep in mind it is a command line program that doesn't multitask well.

Overall, I am very glad to have Delitracker running on my X1000, although I have to say it took ages to get working! I hope this guide is useful for anyone out there trying to get this program working so they can enjoy the classic Amiga modules and save a lot of time getting it up and running!

Tuesday, June 26, 2012

Inside my X1000 and how to add/configure a new 500Gb Sata Disk under AmigaOS4

I decided to install an additional spare 500GB Sata Hard Disk in my AmigaOne X1000 to gain more space and a backup OS partition on a separate disk. (Actually the drive came originally from my Sam440EP which died a long time ago)

This meant for the first time today I opened the case on my X1000!

I wanted to share with you all what is involved in this process, and some very interesting things I found while doing it!

First I opened up the X1000 and took a few photos inside, starting with the side cover off:

Next you can see the PA6T Processor with CPU cooler and two memory slots filled on each side. I noted that a lot of hot glue has been used on most of the cable connectors and expansion cards to (presumably) stop them moving in transit to Australia.

I am pleased to note the power supply supports 100-240V, so it can work in Australia (240V) or Japan (100V) which is good for me.

Next you can see the CF card slot and Motherboard "Nemo" v2.1 designation. You can use the CF slot to put Boot image files on CF Card to run Linux on the X1000, but for me this is an Amiga - so my X1000 runs AmigaOS4 only:

Below shows the Radeon PCI-E R700 Video Card, and the SB128 and Ethernet PCI Cards. After seeing that both PCI slots are full, I realised that I can't put in my Radeon 9250 PCI Card to get Warp3D driver support (!!) as there are no PCI slots available in the X1000 until there are drivers for the X1000 Motherboard soundcard and ethernet port, which currently cannot be used:

This is a shot of the opposite side of the case with the side taken off. I needed to take this off to route the SATA cable and SATA power from the bundle hidden here:

So next I took out one of the removable metal hard disk trays and attached my 500GB Sata disk as below:

I then installed the 500GB in the X1000, two slots below the 1TB hard disk that came with the X1000 originally - for cooling:

I then put everything back together and powered on. All was good, and the system booted as normal, ready for me to do the Hard Disk preparation. This meant learning a bit about the new Media Toolbox program, which replaces the old HD Toolbox.

Media Toolbox is located in the System folder:

After loading Media Toolbox, much like the old HD Toolbox, it prompts you for which device you want to manage, which is sb600sata.device:

You then see the display below, which shows WDC WD10 (My 1TB HD), the DVD drive, and WDC WD50 (the new 500GB Drive):

Out of curiosity I wanted to check the setup of the 1TB hard disk first (setup by AmigaKit), which looks like this:

Interesting things I see here! First, a secret hidden partition BDH0 is listed of 116MB, running FastFileSystem (DOS\07)...basically it is not mounted automatically, which is why it is not visible. From reading in the forums and mounting this partition using the mounter utility this partition contains amiga_boot.of file only, which is used by the CFE BIOS to boot AmigaOS4.

The second thing I noticed - I found that the 1TB Hard disk was not being fully utilised! There was 229GB of space unpartitioned! Not sure if anyone had this on their First Contact X1000 too, but it sure surprised me! I can't see any reason for this unless you want to run Linux on it - I want to use the space for AmigaOS4 and I fixed it below, adding a new DH2 partition with SmartFileSystem2 (SFS\02) over the remaining space without touching the other partitions on the 1TB disk:

So I accepted the changes and then clicked on the 500GB disk, as I have not finished all the changes yet. After selecting the 500GB disk, I then prepared the partitions in a similar fashion to the original 1TB disk - a 116MB hidden disk BDH3, a 2GB bootable partition DH3 with lower priority than the 1TB bootable partition, and a 463GB Data partition DH4, as below:

I then accepted the changes and clicked Save to Disk on both disks to commit the changes to disk. Because none of these partitions or disks was currently mounted, I didn't need to reboot.

Next I mounted the hidden BDH3, DH3 and DH4 through the Mounter utility, which is also in the System folder. Just double click on the drive, and then select the partitions you want to mount and click Mount to see them on the Workbench, ready to be formatted:

Now I formatted the BDH3 drive, and the other drives in turn until all were formatted (Click to Expand):

 After this I then copied the amiga_boot.of file to the BDH3 drive, and backed up my System: drive (DH0) to DH3 and started copying files to the other drives now available:

It was fun to do this - I am glad to have much more space and a full backup now, and I learnt some interesting things about my X1000 along the way too!

Monday, June 25, 2012

How to change default picture viewer from Multiview to LoView on X1000

By default on the AmigaOne X1000, the default picture viewer for JPG, BMP, PNG files (amongst others) is Multiview.

Multiview is based on datatypes to view pictures, and to be honest is hardly feature rich. It displays pictures ok (like the picture of my Amiga 4000T as below), but it is limited for what I want.

LoView is a great program for viewing/saving/renaming images, works full screen or window, rotates photos, supports slideshows, thumbnails and also quickly flicking through all photos in a folder from the first photo opened in that photo - no need to open individually. This is standard fare in Windows and Mac land, but on Amiga Multiview doesn't do this. Like Multiview, LoView can also be used in the dock. LoView is free for personal use and is available on

However, Multiview is set as default for viewing pictures in AmigaOS4. How do we change this to something like LoView?

The answer lies in the deficons. This requires some explanation to understand, but I'll try to keep it brief.

In AmigaOS, it uses deficons in order to associate file types to a program to enable double clicking that file to view the file.

These deficons are prefixed def_filetype. So for example, def_png for PNG files. They are stored in one location called ENVARC: on your system disk and are copied to ENV: in the RAM disk when the AmigaOS boots up. Then, whenever you view a folder in Workbench, if a file in that folder has a file type that is PNG for example, it looks in ENV: for the def_PNG icon to display this as it's icon in the folder.

This file type behaviour differs from Microsoft Windows for example, because Windows only looks at the file name extension to determine that the file type is (eg. .png, .jpg, etc) - if you rename the filename extension in Windows from .png to .pxz for example it can no longer open the file using the normal program when double clicking on it - AmigaOS looks at the file header, so the file can be called anything - it will still work it out..this is a nice feature in AmigaOS.

I digress, sorry. Deficons are just standard icons stored in ENVARC:, which you can modify it's tooltypes to change what program you want. It is important to review the programs documentation carefully to determine how the author has written their program to support running as a default tool, and follow their instructions carefully. Note that not all applications support launching this way cleanly.

Today I will look at changing my default image viewer to LoView. I downloaded and extracted LoView to SYS:Utilities/LoView. If you open the LoView folder and view all files (not just icons) you will see below:

The important file here is LoViewDT. We need this later. Following the instructions in LoView.txt I need to create a environment variable for LoView/LoViewPath pointing to the folder where I installed LoView, since this is not in the system path. Accordingly, I added the following lines for LoView at the bottom of my SYS:s/user-startup:

This requires a reboot before it will work but do not reboot yet. Next we need to change the deficon tooltypes to use LoView. Go to SYS:Prefs folder and then view all files (not just icons). Locate and go into the Env-Archive folder. This is the root for the ENVARC: assign I mentioned earlier. Open the Sys folder within. You will get a large number of def_filetype icons in this folder. We will start with the JPEG filetype, so find the def_jpeg icon, right click on it and select Information. In the icon information window, select the Icon tab. You should then have a screen similar to the one below (Click to expand):

So now we will modify the Default Tool field. Click the File icon next to Default Tool and navigate to SYS:Utilities/LoView and select LoViewDT and click OK. Next, click on the Start From cycle option until it says Shell, and deselect Prompt For Input. It should look like below:

Click Save. Repeat this step for def_png, def_gif, def_bmp, def_ilbm icons and any other common image file formats you want LoView to be the default for viewing.

It is also possible to access deficons directly through the Deficons program in the SYS:Prefs folder, but this requires knowing which file formats have an icon associated - these entries in Deficons program will then allow you to right click on jpeg for example, select Icon and then Information to edit as I showed above. As a classic AmigaOS user I am more used to the approach I used browsing the ENVARC: folders directly, but feel free to use whichever method suits you best.

Next, you need to copy the LoView files to c:. I discovered (contrary to the documentation) that if you don't do this step it doesn't seem to work. You get errors when launching pictures saying it can't find LoView. Actually, you could just have the LoView files in SYS:Utilities in the root folder as it is in the standard AmigaOS path, but since I put in a sub folder originally I decided to copy the files to C: as well to get it working quickly.

This is a bit messy I admit, and you should just extract to C: or SYS:Utilities folder directly to avoid this step. You can also add the LoView sub-folder to the PATH. But I didn't, the documentation said put it anywhere which was not entirely correct, and I am a bit lazy today - if you followed what I did then copy the files using the shell as below:

Now, reboot the computer and test opening a JPG file through the Workbench - it should now launch in LoView (and I can now right arrow to view all photos in the same photo) as per the below screenshot:

LoView is a great program and well recommended replacement for Multview.

As a logical extension, this deficon information change process I did can be used to change default programs for avi's, etc.

I hope this information is of help to people wanting to use a different image viewer on their X1000!