The Programs

Home    The Programs

On this page you can read more about the programs you can include on the boot disks you create. Right now you can choose between 22 different programs, but more might be added in the future. It may seem odd that I have chosen to use the term "Programs" on the software mentioned on this page, because most of the other stuff that can be included on the boot disk are actually programs as well, but it was the only thing I could come up with upon planning the concept of the Amiga911 floppy. Some of the programs will include requester based sort of Guis which really is shell scripts that uses the RequestChoice and RequestFile commands. They are very simplistic in style, but are still quite functional and they will not use much disk space either. 

Some people may wonder why I have decided to include support for three file managers (DiskMaster2, FileMaster3 & Ordering), but the reason is to give people the freedom of choice. Each of the managers have both their strengths and weaknesses, and different people may have different ideas of what makes a file manager great. But my opinion is that any file manager is better than no file manager since it makes dealing with files so much easier.

Below you can see a list over the supported programs, and you can click the links to read more about them. Have in mind that the disk usage sizes mentioned are just (old) estimated values which are meant to help the user find the right combination of programs that will fit on the Amiga911 disk to be created, the real disk usage may be off by up to a few kilobytes.

Please note!  With Amiga911 Maker 1.62 it is no longer necessary to download any Programs in order to add them to your projects, this is because all relevant program files are included now.


Disk usage (estimated)
Check4GB    Check if your HD setup is 4GB-ready.    14 KB
DiskImage    Mount any disk image file as a DOS device.    13 KB (25.5 KB with AmiCDFS)
DiskMaster2    Small, fast and compatible dir utility.    48 KB
DiskSalv2    Disk salvage program by Dave Haynie.    54.5 KB
DiskSalv4    Disk salvage program by Dave Haynie.    N/A
FileMaster3    Very powerful file manager.    155.5 KB (v3.1) or 161 KB (v3.2)
HDInstTools    Harddisk installation tool.    62.5 KB
HJSplit    Split large files into smaller ones.    9.5 KB
ImageMount    Mount ADF, ISO and HDF disk images.    N/A
JanoEditor    Simple and efficient text editor.    34.5 KB
MaxTransTest    Tests the MaxTransfer value of a partition.    N/A
Ordering    Powerful directory utility.    81.5 KB
PFSDoctor    Repair and recovery tool for PFS volumes.    N/A
PFSSalv2    Save files from damaged PFS partitions.    N/A
Redit    Small, fast and compatible text editor.    N/A
SFSSalv    Recover files from damaged SFS partitions.    N/A
SnoopDos    Well known system and application monitor.    48 KB
SysInfo    Gives comprehensive system information.    29 KB
TransADF    Reads & writes ADF/ADZ disk images.    24.5 KB
TurboText    Fast and highly customisable text editor.    95 KB (100 KB on XPK disk)
Virus Checker II    Anti virus program. v2.5 (Brain v3.0).    N/A
WhichAmiga    ShowConfig kind of tool. V1.3.3.    17 KB



Setting up a large harddisk on Amiga computers is relatively easy for users of AmigaOS 3.5 & 3.9 since these OS versions includes everything that is needed for using large drives. Users of AmigaOS 3.1 and lower on the other hand, will need to use some third-party patches in order to overcome the default limitations where only the first 4 GB of the harddisk can be used, and where partitions can be max 2 GB in size. In addition to this, a different file system must also be used (SFS, PFS or a newer FFS).

So in order to overcome the 4 GB harddisk + 2 GB partition limitations, the user needs to find the right combination of patches and a proper file system to be used on the Amiga. This can be a bit confusing for some, and there may also be a bit of uncertainty if everything is configured like it should. After all, it would really suck to set up a system and belive that everything is safe - only to experience corrupt files/partitions later on.

This is why a tool like Check4GB comes in handy since it can examine all partitions on your drives, and it will let you know if there are any conflicts with the 4 GB border. As you can see from the screen grab, Check4GB examined all partitions on my 80 GB harddisk and found no problems with any of them.

For more information about Check4GB, read the documentation that follows the program.

Author: Thomas Rapp,    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



DiskImage allows the user to mount any disk image file as a DOS device, although on the boot disks and packs it will be limited to ADF floppy images, ISO CD-ROM images and HDF harddisk images only. When a virtual device is mounted and a image file is "inserted", the user will be able to copy files from/to the image, and it may also be possible to delete files from the image as well. Basically, almost everything that can be done with real devices can also be done with the virtual devices too.  One important thing to have in mind regarding HDF image files, is that they must have been made by using the defaults in WinUAE, this means a block size of 512 and a BlocksPerTrack value of 32.

A program called DiskImageCtrl is used for inserting and ejecting image files to/from the virtual drives, and even though it has the possibility to open a MUI front-end for making this easier, it will be of no use on the boot disks since MUI can't be included there (due to disk space limitations).  Instead you can use DiskImageGui, which is a script that controls DiskImageCtrl for easily inserting and ejecting image files. DiskImageGui also handles the mount files as well, so if the virtual device has not yet been mounted, the script will first generate a temporary mount file on the fly, and then it will use this file for actually mounting the device.  Please note that by default, none of the virtual devices are mounted at startup.

For more information, take a look at the Using DiskImage & ImageMount tutorial.

Please note!  Mounting ISO CD-ROM images requires either AmiCDFS or CacheCDFS to be present on the boot disk or A911Extras pack. To make sure that a CD-ROM filesystem is included, you can enable the "ISO support" option in the "Configure programs" window of Amiga911 Maker.

Author: Thore Böckelmann,  Roger Håseth (script),    Requires: AmigaOS 2.x or higher & 68020+ cpu,    Download: +

    To the Top



DiskMaster2 is a file manager/dir utility, and the biggest advantage it has over the other file managers is the amount of space it will use on the Amiga911 disk, where it will actually only use around 48 KB in compressed state. The biggest disadvantage of DiskMaster2 is the way it has to be configured, because where the other file managers allows the user to configure the settings by using graphical user interfaces, it must be done by editing a text file instead - something which makes things a bit more cumbersome. But on the other hand, this may also be one of the reasons why the program is so small in size.

Visually speaking, DiskMaster2 uses a somewhat more simplistic style regarding the interface than the other file managers, one example is that it doesn't use any real graphical buttons in the middle window, it uses clickable text strings instead. There are also certain features missing in DiskMaster2 which would have been nice to have, one is an option for selecting the screenmode from the main program, and another is an icon viewer.

Other than that, there's not much more to be said about DiskMaster2, it is fast and does what it's supposed to do, and it also scores high on the small disk space it will occupy.  

If you want to change the screenmode of DiskMaster2, you must first open a file called Startup.DM in a text editor like Ed. If you have booted from an Amiga911 disk, you will find the file in Ram:System/S. When this is done, you must find a line which looks like the one below:
  NewScreen ID=167936 D=4 W=640 H=256 F=topaz.font FS=8
Change this line to the following:
And make sure that nothing follows after the NewScreen word (not even an empty space), then save the file. Now when you start DiskMaster2, you should be asked to select a screenmode, so do this. To make the change permanent, select "Save Config" from the Settings menu. If you have booted from an Amiga911 disk, you must also copy Startup.DM from Ram:System/S to Amiga911:S or the change will be lost when you reboot or turn off the Amiga.

Authors: Greg Cunningham & Rudolph Riedel,    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



DiskSalv Version 2 is a disk recovery program for all Amiga file system devices that use any of the 2.04/2.1/3.0 file systems. DiskSalv will scan (analyze) a bad disk volume for anything that can be recovered, and will restore these items to any AmigaDOS volume. It can also attempt to fix a bad volume in place under most circumstances. DiskSalv is a complete redesign of the orignal DiskSalv program, with a new AmigaDOS-2.0-compliant command-line interface, new Intuition interface, and tons of new features.

This program along with the standard FFS file system (and AmigaOS version 2.04 - 3.1 in general), was made at a time when harddisks of several GB in size were still only a wet dream and something distant in the future for most people, and as a result both FFS and the program reflects this.  So if you want to use DiskSalv for salvaging files from a harddisk, do have in mind that certain limitations applies: It will only work on harddisks with FFS partitions that are max 2GB in size, and only on the first 4GB of the drive. It is not safe to use the program on partitions that exceeds these borders, and it can't be used on partitions that uses other file systems like SFS or PFS.

DiskSalv can also be used for salvaging files from faulty floppy disks, but only if the disks are in the standard DOS format (something which excludes most games & demos).

Author: Dave Haynie,    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



DiskSalv is a disk recovery program. Its main purpose is to recover AmigaDOS disk integrity when a disk fails, or when impossible, the data from a failed disk. The name DiskSalv is short for Disk Salvage. Originally, DiskSalv's only function was to extract as much data from a failed disk as possible and copy this information to another disk.

DiskSalv 4 has extended this function in various ways. It can recover deleted files from an undamaged disk, which is often a more common need than failure recovery. In many cases, DiskSalv can fix a damaged disk in-place, rather than copy out its contents to another volume. In these days of multi-gigabyte hard disk drives, that's an important concern.  Finally, DiskSalv 4 adds a number of related features. It can find partitions on a disk, even when AmigaDOS can't. It can report errors on a disk without repairing them for you. It can backup an AmigaDOS volume to any AmigaDOS disk or tape device.

In other words, this version of DiskSalv has a lot of improvements when compared to the older DiskSalv2, but it's file size is also 90 KB larger as well.  In Amiga911 context this actually is a big deal, and that's why both versions of the program are currently supported.  It's up to the user to choose which version to use: either the one with the most features (V4), or the one that uses the least disk space (V2). The documentation mentions "multi-gigabyte hard disk drives", which somehow indicates that DiskSalv4 might support large harddisks (>4GB) as long as the FastFileSystem (FFS) supports this as well, but have in mind that this has NOT been tested by me!
Another thing worth mentioning is that DiskSalv4 is able to recognize PFS partitions, but it will report them as AFS (AmiFileSafe). It may also be possible to recover files from PFS partitions by using this program, but it probably is best to use PFSDoctor or PFSSalv2 for this task instead.

Author: Dave Haynie,    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



FileMaster3 has been my favourite file manager for many years now. It was made by Toni Wilen, and thanks to the enhancements and bug fixes by Christian Kummerow, it will most likely remain my favourite in the future as well. Three versions of FileMaster is now supported: V3.2, V3.1(B11) and V3.1(B4). The main difference between them is that the most recent one contains more functions, and this also means that the file size is slightly larger than the older versions. It's up to the user to choose which version to be included on the boot disk or pack. You can read more about them right here.
This program requires bgui.library which also will be included on the boot disk, and in addition to the main library, there is also the bgui_palette.gadget file which now will be added as well. This means that it should be perfectly safe to configure all aspects of FileMaster3 now.

What I like best about FileMaster is the directory buffers which can be very useful in situations where file managment involves multiple dirs, then the user can easily switch between the 10 dir buffers by using the "<" and ">" buttons below the directory lists. Another thing I like is the function of the right mouse button which will do different things depending on the position of the mouse pointer when it's pressed. If the pointer is over the disk usage status bar, it will update (re-read) the current directory, and if it's over any of the buttons between the directory lists, it will toggle between the button columns (if there's more than one). What happens when right-clicking the mouse while the pointer is over the dir lists is really optional, but with the included configuration it will be the same as double-clicking the mouse, this means that you can open files and enter dirs by pressing the right mouse button instead of double-clicking the left one. Since FileMaster have this functionality with the right mouse button, it also means that menus isn't used by the program.  Another nice feature of FileMaster is that it will ask you to select another screenmode if it fails to open the one specified in the preferences file.

If I should find something to pick on, it has to be the layout of some of the configuration windows since they can be a bit confusing, this is because the gadget titles isn't always properly aligned with the corresponding gadgets. I also find it a tad annoying that the vertical slider bars of the directory lists gets half their width with interlaced type of screenmodes (like 640x512). But the biggest disadvantage of FileMaster (in Amiga911 context) has to be the relatively large space it will use on the boot disk, where it will actually use over three times more disk space than DiskMaster2!

Please note the following about FileMaster 3.2:
1. FileMaster looks best in a non-laced screenmode (imho), but this can lead to a problem if you are using version 3.2 with a 640x200 NTSC screenmode, the reason for this is that FileMasters screenmode config window will now be too big to fit on such a screen. I have temporarely fixed this by using a bit of overscan in the default NTSC non-laced settings, but you have to figure out a better workaround in order to fix this for yourself.
2. If you save the settings of FileMaster, the prefs file will be saved in Envarc: if you're using V3.1 (like it should). But with V3.2, the prefs file will be saved in the ProgDir instead (Ram:Programs/), which means that all changes will be lost when you reboot or turn off your Amiga. What's even worse is that FileMaster will also delete the prefs file in Envarc: as well (not really a big problem since the file is still present in System1.lzx), so remember to copy or move the prefs file to Envarc: (Amiga911:Prefs/Env-Archive/) after saving the settings.

Authors: Toni Wilen & Christian Kummerow,    Requires: AmigaOS 2.1 or higher + bgui.library,    Download:

    To the Top



HDInstTools can be used for setting up a harddisk on your Amiga. It's a good alternative to the standard AmigaOS HDToolBox program, and it was nice to have back in the day when Commodore didn't include the Install disk with Amiga computers sold without a harddisk (HDToolBox was on this disk). Then HDInstTools was the only option for the ones missing the Install floppy.

When compared to HDToolBox included with AmigaOS 3.1 and lower, HDInstTools have the following advantages: It has better support for large harddisks (>4GB), it works better with a wider range of storage devices, and it requires no patches in order to work with Compact Flash cards (via IDE - CF adapter). In my honest opinion, there is no reason to use HDInstTools instead of the HDToolBox version included with AmigaOS 3.5 & 3.9, but with AmigaOS 3.1 and lower, I will consider it to be a very good alternative indeed. And with AmigaOS 1.3 it might actually be the only alternative.

Some people claim that HDInstTools and HDToolBox is 100% compatible with each other in the way that you can set up a harddisk with one of them, and then later perform changes on the harddisk with the other, while others again claim that this isn't entirely true. So just to be on the safe side, it would probably be a good idea to continue using the program first used for setting up the harddisk when you want to change anything on it.

Author: Oliver Kastl,    Requires: AmigaOS 1.3 (2.x or higher recommended),    Download:

    To the Top



HJSplit is a program that can take a large file and split it into several smaller ones, this can be useful in situations where transferring files from one computer to another via floppy disks (or other small media) is the only option, and where one or more of the files is too big to fit on a single floppy. After a large file have been split you can transfer each chunk to the other computer, and then you can use HJSplit for joining all chunks into the original large file again.

Another example can be when transferring large files via a serial null-modem cable, because not only is this a rather slow method, there is always a chance that a transfer may be aborted due to an error as well. This can really suck if you have waited a very long time for a file transfer to complete - only to experience it being stopped at for example 95%, meaning you have to start all over again. Here it might be a good idea to first split the large file into several smaller chunks, and then transfer each chunk one by one instead. When this is done, you can on the other computer join every chunk into the original file again.

If you decide to include HJSplit on the Amiga911 disk, Emergency Disk II or A911Extras pack, you will also get a requester based script called HJSplitGui which can be used for controlling HJSplit, but you can of course use the program directly in Shell if you prefer that.  For more information, take a look at the Using HJSplit tutorial.

Versions of HJSplit exists for several platforms including Windows and Linux. All HJSplit editions are compatible with each other and allow you to exchange files between different operating systems. E.g. a file split on Linux can be joined on Windows 7 and vice versa. More information can be found at:

Authors: Henk Hagedoorn & Rhesa Rozendaal,  Roger Håseth (script),    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



ImageMount is a requester driven script which allows you to mount ADF, ISO and HDF image files in a really easy way with only a few mouse clicks, and you can then treat the virtual devices like any other storage device (copy, delete, rename files etc.). It works on any Amiga with KS 2.04 or higher, but requires minimum version 38.21 of the Mount command (included in WB2.1). ImageMount uses filedisk.device for mounting virtual devices.

Unlike with DiskImage, there are no sort of "change disk" or "eject disk" type of functionality involved, the mounted virtual drives will remain mounted until the Amiga is rebooted. When it comes to the amount of image files that can be mounted at any given time, there really are no limitations other than the currently free RAM available. As for the ImageMount script, it more or less works at the same principles as DiskImageGui, where the required mount files are automatically generated by the script. Also, the same limitations regarding HDF files applies to ImageMount as well. When compared to DiskImage, the ImageMount solution is a much more simpler and less advanced alternative, but the advantages is that it works on 68000 CPU Amigas, and that the required files are much more smaller in size.

For more information, take a look at the Using DiskImage & ImageMount tutorial.

Please note!  Mounting ISO CD-ROM images requires either AmiCDFS or CacheCDFS to be present on the boot disk or A911Extras pack. To make sure that a CD-ROM filesystem is included, you can enable the "ISO support" option in the "Configure programs" window of Amiga911 Maker.

Author: Unknown,  Roger Håseth (script),    Requires: AmigaOS 2.x  & Mount 38.21 or higher,    Download:

    To the Top



When I started planning the whole concept of the Amiga911 boot disk, one thing was clear: It should be possible to include a decent text editor on the floppy disk. By default AmigaOS includes a simplistic and very limited editor called Ed, and although it is somewhat usable, I really consider it to be a "better than nothing" type of solution. So the search for a better text editor started, it didn't have to be so advanced, but as a bare minimum it should include a vertical slider gadget on the side of the window, and it should also have proper cut, copy & paste functionality too. Another thing that would be nice was if it had text search & replace support as well.

A lot of text editors for the Amiga have all this stuff (and more), but there was also one last criterion - the editor should have a really small file size! And it was here that JanoEditor reallly stood out from the crowd, because this program does actually have a size of only 62.2 KB, and in compressed form (LZX) it is only ca. 34.5 KB big! One nice feature of JanoEditor is that it's possible to open several text files in the main window, the user can then switch between the text files by clicking the tabs under the window title bar. Another nice thing is that it supports multiple undo and redo.

I can't think of anything more to say about JanoEditor, it is quite simply a small, fast, and efficient text editor, and I use it on all my Amigas with OS 3.x and 020 processor (or higher).

Authors: Cyrille Guillaume & Thierry Pierron,    Requires: AmigaOS 3.x & 68020+ cpu,    Download:

    To the Top



When setting up a harddisk on the Amiga, it's important to configure the partitions to use a MaxTransfer value that is correct for the controller the disk is connected to. If this value is set too high, it might lead to corruption of files that is copied to the partitions. This mainly goes for IDE controllers only, since most SCSI controllers does not have this limitation.

Here a tool like MaxTransTest really comes in handy, since it's able to test if a partition has a proper MaxTransfer value. In most cases it's best to use this program before any files are copied to the partition. When MaxTransTest is started, you must first select the language to be used - either English or Deutsch. If the former is chosen, the window to the right will appear. Now click the Continue button, and you will be asked about what size the large file to be written should have, this can be either 5, 10, 20 or 40 MB. Here I will recommend that you select the largest size that will fit in your Amigas memory since this may give a more accurate result. After you have made your choice, MaxTransTest will create a buffer in memory with the selected size

Next, you will be asked to select the partition to test, and then the buffer will be written to a file on the partition. The whole point of all this is to write the big file as fast as possible to the harddisk. Now the newly created file will be checked for errors, and if none can be found, the partition does most likely have a suitable MaxTransfer value. Otherwise it has to be lowered!  The big file will now automatically be deleted from the harddisk. Have in mind that MaxTransTest will also create a log file on the Ram disk.

Author: Thomas Rapp,    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



Ordering is the third file manager/dir utility supported by Amiga911 Maker, and just like other two it have both it's strengths and weaknesses as well. To take the advantages first: Ordering is highly configurable, and it is also easy to do this with the included OrderingPrefs program. A really nice thing regarding this is how the layout of the main buttons can be changed, and as you can see from the screenshot, the buttons is located between the two directory lists, but they can also be above the lists or under them (DOpus style). The program uses two button banks, and you can easily switch between them by clicking the little gray bar below the buttons, or if the buttons are located above/below the dir lists - the little vertical bar to the right of the buttons.   

Now over to the negative stuff. Even though Ordering is easy to configure, there are two things that are sorely missing: One is the lack of a "Use" functionality in the OrderingPrefs program, something that makes just testing stuff a bit cumbersome since all changes will be permanent. The other thing is that it would have been nice to have the possibility of changing the screenmode from the main program instead of OrderingPrefs.
I also find it a bit limiting that Ordering doesn't display all volumes, devices and assigns in the directory lists (like the two other file managers), instead all  devices will be present in some buttons (DOpus style). So in order to start navigating the drives on your system, you will either have to click the device buttons, or you can enter the device or volume name in the text gadget below the dir lists.

Other than that, I can't think of anything else to pick on. Ordering does what it's supposed to do, and if you are a big fan of Directory Opus, I will really recommend it since Ordering is the closest you can get to DOpus out of all three file managers mentioned on this page. This of course requires that you do some minor configuring of the program.

Author: Julien Torrès,    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



PFSDoctor is a repair and recovery tool for PFS volumes (Professional File System).  It can repair almost all corrupted disks and can even locate delocated partitions. The tool has a wizard like GUI.

From the start window (right image), you can choose to Repair or to Check a disk.  In Check mode the disk will be write protected during the scan, so errors are shown but nothing will be fixed.  In Repair mode the disk will be repaired. Next the device or volume to scan has to be selected. The Back button takes you back to the start screen.

For more information about the usage of PFSDoctor, check out the found in the main PFS3_53.lha archive (link below).

PS!  If you just want to rescue data from a damaged partition, without risking corrupt files being deleted, you can use PFSSalv2 instead.

Author: Michiel Pelt,    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



This is version 2 of Thomas Rapp's program PFSSalv for Professional File System. It scans the directory area of a PFS2 or PFS3 disk for files and directories and saves selected files to another data medium.

This can be used to rescue important data from a damaged partition before attempting to repair it with PFSDoctor or DiskValid, because those programs irreversibly delete corrupted files and directories.

This part of the Programs page is not quite finished yet! More info regarding PFSSalv2 + a much better screenshot will be added later.

Author: Thomas Rapp,    Requires: AmigaOS 3.x,    Download:

    To the Top



Redit is a small, fast and very compatible text editor that works on all Amigas with AmigaOS 1.2 or higher. As you can see from the image to the right, it uses by default a white color for the background - which is a bit unusual for text editors on the Amiga. But if you prefer a grey background instead, it can easily be changed by editing the tooltypes of the Redit icon. Furthermore, it seems like author Kai Scherrer has taken a somewhat modern approach when developing Redit since it has some features that nowadays is just taken for granted on modern (but basic) text editors, but which are lacking on many of the Amiga editors. As a matter of fact, I don't think there even exists any other AmigaOS 1.x compatible text editor with all the features of Redit.  It must be said however, that if you require an advanced text editor with LOTS of features, then Redit may not be the thing for you. But if you on the other hand just want an editor that's better than the standard Ed (included with AmigaOS), which also has a rather small file size, I will highly recommend this program.

For more information about Redit, you can visit this site: Unfortunately the site along with the documentation that follows Redit is in german only, but don't let this scare you off though, because the program itself is in english.  If you have used any modern text editors before, you shouldn't have any problems with figuring out how stuff works.

Please note! The old conflict regarding asl.library on Amiga911 disks for Amiga OS2.0 has been fixed by using RTPatch. This patch will force programs to use reqtools.library instead of asl.library on the OS2.0 disks, which in turn means that there should no longer be any problems with Redit & TurboText.

Author: Kai Scherrer,    Requires: AmigaOS 1.2 or higher,    Download:

    To the Top



SnoopDos is a utility that allows you to monitor a variety of system operations carried out by programs on your Amiga. This includes what files a program is trying to open, what fonts, libraries, devices and environment variables it is looking for, and so on. SnoopDos was originally made by Eddy Carroll, but various updates has been done by the following persons: Luca Longone, Massimo Tantignone, Grzegorz Chmie, Thomas Richter and Oliver Roberts.

In my opinion, SnoopDos can be a very valuable tool to have for those situations where a piece of software simply won't work, and you don't have a clue as to why.  I have actually used SnoopDos quite a lot when developing the Amiga911 disk as well, and for the most part this have consisted in figuring out exactly which files are the only ones required for adding a cut down bare bones version of a program to the disk (one example is TurboText). I have also used SnoopDos for checking out where certain programs looks for their config files (Progdir, Env: or S:).

I don't know how useful you will think it is to add SnoopDos to the boot disk, but at least you have the option to do so now.

Author: Eddy Carroll,    Requires: AmigaOS 2.0 or higher,    Download:

    To the Top



SFSSalv is a program for recovering files from damaged SFS (SmartFileSystem) partitions. It can however not be used to repair any partitions, since it's a salvage tool only. When it comes to large harddisks (>4GB), it will only work with the NSD (NewStyleDevice) Patch, TD64 is NOT supported!

Since the Gui layout of SFSSalv is somewhat special, and any kind of documentation of the program is really non-existant, here's some very basic explenation of the usage:  First you must select a partition and then click the Start button. Now SFSSalv will scan the partition, and when this is done, a list over all directories and files will be shown. When you navigate through the directories, have in mind that the tall button to the left which contains a "/", does work as the Parent button. Files to be salvaged are selected by double clicking them, and when you're done, just click the Undelete button. This will bring up a directory requester, where you can choose where to store the salvaged files.  

Please note that some directories may be marked as "BAD-DIR", this doesn't necessarily mean there's something wrong with the partition. The thing is that SFSSalv seems to be very picky about certain "illegal" characters being used in dir names, this includes the following ones: ? # % | ~ * [ ] ' ( ).

Author: Joerg Strohmayer,    Requires: AmigaOS 3.x  & gtlayout.library,    Download:

    To the Top



SysInfo is an Amiga System Information program. It interrogates the Amiga and determines types of hardware, software, modes, speed etc. The main reason why I decided to include support for it, was because it can be useful for those who have just bought an Amiga without knowing exactly what is included inside it. Then the user can simply create an Amiga911 disk with SysInfo included, and use this floppy for booting up the Amiga. Next, the user can run SysInfo in order to get a quick overview of the Amiga's hardware without having to open it up first.

The most basic hardware information can be found on the right side of SysInfo's window, but you can get more info by clicking some of the middle-bottom buttons in the window. By clicking "Memory" for example, you will get a new screen with detailed info about the type of RAM your Amiga has. The "Drives" button will open a screen with detailed info about all drives that are present on the system, and here you can also test the speed of each drive. To find out how fast the CPU is on your Amiga, you can click "Speed" in the main window. This will cause the mouse pointer to disappear for a while until the final results are shown in the window (like in the screenshot).

There is also a button called "Boards" which will open a new screen containing a list over all AutoConfig boards found in the system. Most likely the details you find here will not appear to be so useful since SysInfo is an old program, and a lot of Amiga hardware have been produced since the last version was released. But it may still be possible to find out what type of boards that are listed since the Product and Manufacturer ID's should be mentioned there, and as an example I can use my main Amiga 1200: 

SysInfo lists the following AutoConfig boards on my Amiga:
Board 1:   Product = 35,  Manufacturer = 8738
Board 2:   Product = 40,  Manufacturer = 2206
Board 3:   Product = 168,  Manufacturer = 2206

Now by using the online Amiga Hardware Database at I can find more info about the boards by clicking "Search" on the main page, then on the next page I enter the Manufacturer ID and the Product ID in the text boxes located right above the Reset and Find buttons, and in addition I also select "Amiga 1200" from the Amiga model menu. Finally I click the Find button. 

It turns out that Board 1 is either a Apollo 1230/1240/1260 or a Viper 1240/1260 accelerator card, but since the main window of SysInfo shows that my Amiga has a 040 CPU, it can be narrowed down to either a Apollo 1240 or a Viper 1240.
Both board 2 & 3 turned out to be my Mediator PCI 1200SX bus board, they are really the same hardware which are configured to appear as two boards to the system. The reason why none of my PCI cards were listed in the SysInfo window, is because they are not AutoConfig cards.
Please note! The above stuff is just used as an example, I do of course already know what's inside my Amiga 1200 :-)

Author: Nic Wilson & Tobias Geijersson,    Requires: AmigaOS 1.x or higher,    Download:

    To the Top



TransADF can be used for transferring Amiga Disk Files (ADFs) to and from Amiga disk drives, and in addition it can support compressed Amiga Disk Files as well (ADZs). The TransADF distribution includes three different executables, but the one that can be included on the boot disks and A911Extras packs, is the version that has built-in support for (de)compression of floppy image files. This feature is also one of the reasons why TransADF was chosen over other similar type of programs.
Since TransADF is a CLI only program, a simple front-end called TransADFGui will also be included on the boot floppy or pack, this is a requester based script that can make it a bit easier to read and write ADF files.

A little tutorial which explains the usage can be found on the Using TransADF page.

Author: Karl J. Ots,  Roger Håseth (script),    Requires: AmigaOS 2.x or higher,    Download:

    To the Top



Since I wanted to add support for creating AmigaOS 2.x based boot disks with Amiga911 Maker, it also meant that I had to find another text editor that can be included on the Amiga911 disk (JanoEditor requires AOS 3.x). After testing a lot of the various 2.x compatible text editors out there, I ended up with TurboText since it is one of the very few that works with expanded Amigas, includes a vertical slider gadget on the side of the window, and have proper cut, copy & paste functionality. Another editor with these features that also was considered is Annotate, but this one was dropped since it requires ARexx (which is not included on the Amiga911 disk).

Have in mind that if you include TurboText on the Amiga911 disk, it will really be a cut down bare bones version of the editor. Another thing is that a workaround regarding the placement of the TurboText libraries is used as well. If you like this program, and you want to install it on your harddisk, it is highly recommended that you use the installer included with the TurboText distribution instead of just copying the files from the Amiga911 disk.  I would also like to mention that the TurboText distro contains a faulty amigaguide document, and if you have problems with opening it, you can do the following: Open the TurboText_Manual file in a text editor and go to the last line, then add an extra @endnode line at the end. After saving the file, you should be able to open it.

Author: Martin Taillefer,    Requires: AmigaOS 2.04 or higher,    Download:

    To the Top


Virus Checker II

Virus Checker II can be used for scanning your Amiga for viruses, where it can scan both files and the memory. If it finds a virus infected file, it may be able to heal the file in question.  If you insert a bootable floppy disk while you have Virus Checker II running, it will also check the boot block of the disk, and if it's a non-standard one, it will let you know about this. When you run the program, it will by default start in a minimized form (like you can see on the top-right image), and you must click the title bar with your right mouse button in order to change this. To start scanning files for viruses, you can just click the "Scan Files" button, and then select the files/dirs to scan.

Do have in mind that Virus Checker II may report "false positives", where it thinks something might be a virus, when it's really not so. An example can be that it reports something suspicious in memory, when it's really just some patches that were run upon starting the Amiga. Likewise as mentioned above, it will check the boot-block of inserted floppy disks, and report any non-standard ones. If this happens, it doesn't necessarily mean that there's a virus involved. The thing is that most floppy based Amiga games uses a custom boot-block, and if it gets overwritten with a standard one (like VC II may allow you to do), the result can be a no longer working game disk. So be careful with NDOS floppy disks.

If you add Virus Checker II to a project in Amiga911 Maker, it will be a really minimal version which only contains the most essential files. In order to add more functionality, you can enable the "Extra files" option in the "Configure programs" window. This will make sure that VCPrefs (for configuring Virus Checker II) and xvs.library (for extra virus protection) is included as well. The price to pay will of course be an increase in the disk space used. Virus Checker II was originally a shareware product, but was later made freeware, and a free keyfile was released. This keyfile will also be included in the project.

Antivirus software for the Amiga might be considered obsolete nowadays, because it's several years since the last time I encountered a virus on my Amiga, and I actually don't think there has been made any new Amiga viruses in quite a while now. But still, I have a collection of floppy disks that was included with the A600 I bought a few years ago, and I willl certainly feel a lot more comfortable going through all of them while Virus Checker II is running in the background.  I will advice you to do the same thing with old unknown disks that you get from others, because you never know what they may contain.

Authors: John Veldthuis & Alex van Niel,    Requires: AmigaOS 2.04, bgui.library & xvs.library    Download:

    To the Top



WhichAmiga is yet another ShowConfig like tool, except it's highly sophisticated and is capable of determining which Amiga model you're running. It should be able to recognize all classic Amiga models + the Draco Amiga clone, and it can also recognize if the Amiga is UAE emulated. Furthermore it recognizes several CPU models used by the Amiga (both 68k & PPC), and various FPU and MMU models as well. WhichAmiga can also recognize a range of graphics and sound cards too. For more information, read the documentation included in the WhichAmiga distribution.

If you add WhichAmiga to the Amiga911 disk, Thomas Barth's boards.library will also be included. This library will then be used by WhichAmiga for providing a list over the expansion boards found on the system. As you can see from the image above, my Apollo accelerator card was recognized, and I was also informed that I have something produced by Elbox in my Amiga. Since both the Manufacturer and Product ID's are mentioned there as well, it really is a simple task getting more info about the boards by following the example found in the last part of the SysInfo section. Have in mind that WhichAmiga doesn't really require boards.library, but it will be used if it's present.

I was originally thinking about using WhichAmiga as a replacement for the standard AmigaOS ShowConfig tool on the Amiga911 disk, but since it crashes on some soft-kicked Amigas, I decided to drop this idea. The reason why is because a main criterion for replacing system files with third party alternatives, is that they should work on ALL Amigas regardless of the configuration. So instead I made the decision to add it as a selectable program in Amiga911 Maker, this way the user have the choice whether or not to include it on the boot floppy.

Author: Harry "Piru" Sintonen,    Requires: AmigaOS 1.1+ & board223,    Download:

    To the Top

    Followed a link? Please go to the Main Site                   © Roger E. Håseth 2011 - 2016