Ready-made Amiga911 disks
* = Requires a 68020 or higher processor.
Activating the Amiga911 disk
As mentioned above, you will need to activate the Amiga911 disk before it can be used (due to copyright reasons), here you will need a Workbench 3.0/3.1 disk for the 3.x versions, and a Workbench 2.0/2.1 floppy for the 2.x ones. There are two ways to activate the Amiga911 boot disk:
Upon booting it for the very first time, you will be instructed to insert your Workbench disk so that the some system files can be copied from it. When this is done, you will be told to insert the Amiga911 disk again, and now the previously copied system files will be added to the Amiga911 disk, where the majority of them will be compressed. Have in mind that you will be asked some questions where the options given are Y/N (as in Yes/No), if you enter something else or simply press the Return key, the answer will be considered to be a "No".
After this is finished, you will be asked if everything went OK, and if the answer is yes, the final step of the activation can be done by pressing the Return key. But if you on the other hand experienced some problems, you can simply reboot the Amiga and try again.
This one is a bit easier since it allows you to activate the boot disk from the Workbench by using the supplied "Activate A911 disk" tool. The procedure is more or less the same, with the main exception being that you have more options of cancelling the activation during install. This method also makes it possible for a couple of workarounds, see the Workarounds section at the bottom of this page for more information. After the activation is finished, you can just delete "Activate A911 disk" from the floppy since it's no longer needed.
Please note! Both Low-Mem disks (for Amigas with only 1MB RAM) does currently require a minimum of 1.5MB RAM for activation. The PAL and NTSC monitor drivers are no longer included since they are really not needed for proper operation. The exception can be if you want to force a PAL display on a NTSC Amiga (or vice versa), in which case you will now have to add the driver(s) to the Amiga911 disk yourself.
PS! The above screenshots are now hopelessly outdated, and they will be replaced later.
Configuring the Amiga911 disk
When the activation is done, you can copy whatever extra files you want included to the Amiga911 disk, this can be stuff like device drivers or file systems. You can also create an Expansion drawer on the Amiga911 disk and copy whatever is present in the Expansion drawer on your system partition (this will usually be non-autoconfig hardware drivers). Another thing you can do, is to first create a Devs/Monitors drawer on the disk, and then copy your monitor driver(s) into it. There should be at least 70KB free disk space for this purpose.
If the boot floppy includes the Poseidon USB stack, you are good to go if your Amiga has a Subway or Thylacine board installed, otherwise you have to copy the correct device driver for your USB card to the Devs/USBHardware drawer on the disk. Have in mind that it's possible to have several drivers in this drawer.
After booting the finalized disk, you can do some minor configuration like changing the screenmode, font(s), and keymap used by the system. This can easily be done by selecting the relevant options from the System menu of the Workbench.
It is of utmost importance that you don't modify the Amiga911 disk in any way before it is activated. You should for example not copy anything to it, because although you will have some free space left for stuff after activation, the disk will at one point during the installation be almost full (maybe 10 - 15 KB space left). The reason for this is the extra installation files that is present on the Amiga911 floppy. These files will be deleted during the final stage of activation since they are then no longer needed (thus freeing up some space).
But if you still MUST add something to the boot disk before it gets activated, you could try the following: Let's say that your Amiga has a 060 processor, then you probably will need the correct 68040 & 68060 libraries to be present on the disk. So in order to temporarily free up some disk space, you can simply move the Programs.lzx archive from the Amiga911 floppy to somewhere you can find it later. Then copy the two libraries to the disk and activate it. When this is done, you can try to copy the Programs.lzx file back again. Please note that the above may only be required for activating by using the "Boot method".
Adding Large HD support
All of the ready-made Amiga911 variants includes some of the stuff required for large harddisk support (>4GB), this includes NSDPatch, LoadModule and PFS3 AIO (All-In-One). Some of the disks also includes SmartFileSystem (SFS), which requires a 020 or higher CPU. As for the remaining files, you will have to add them yourself. Here are some brief examples:
1. If you want to use IDEfix for patching scsi.device upon booting, you must copy it to the C directory on the Amiga911 disk. If you have previously saved the settings, it may also be a good idea to copy the small IDEfix.prefs file to the Prefs dir as well.
2. For patching scsi.device with a newer version, you must find and copy the correct scsi.device file that best suits your Amiga model to the Devs dir on the Amiga911 disk. You must also edit the Startup-Sequence on the disk, where you change the "Set PatchSCSI 0" line to "Set PatchSCSI 1".
3. If you don't want to use PFS3 AIO on the harddisk, you must add another file system with large HD support instead. This can either be SmartFileSystem (if it's missing), or a newer patched version of FastFileSystem (FFS). Just copy the wanted file to the L dir on the Amiga911 disk.
Adding CD-ROM support
All of the ready-made Amiga911 disks includes support for using a CD-ROM drive with your Amiga, but in order to use this functionality, you have to configure it manually. First and foremost you will need a device driver that supports optical drives, and unless the controller already have this built-in, you will have to find the correct driver and copy it to the Devs drawer on the Amiga911 disk. Here is an example: If you want to use a CD-ROM drive with the internal IDE controller of an A600, A1200 or A4000, you might need a suitable variant of the atapi.device.
With the device driver sorted out, the next thing to do is configuring the mount file. Here you will have to open the Storage/DOSDrivers/CD0 file in a text editor, and then replace "dummy.device" with the name of the real device driver to be used. Next, you must change the correct unit number used by the device. Just to continue with the example above, the correct entries would have been "Device = atapi.device" and "Unit = 1".
Have in mind that for mounting the CD-ROM drive, you should either select "Mount CD0:" from the Workbench menu, or enter "Mounter CD0:" in a Shell.
How to free up some disk space
After activating the ready-made Amiga911 disk, you will have some space left for stuff you would like to add to the boot floppy. But if you still need more free space, you could try the things mentioned below. You may remember reading about not modifying the Amiga911 disk before it's activated, but these things should be relatively safe to do before activation.
1. If the boot disk is to be used on a Amiga with 030 CPU or lower, you can just delete the Libs/68040.library if it's present on the disk. This will free up 44 KB disk space.
2. If you don't have any intentions of patching the scsi.device with a newer version upon booting, and the disk doesn't contain the Poseidon USB stack, you can just delete the System0.lzx file. The result will be at least 5.5 KB more disk space
3. You can also delete the Devs.info, Disk.info & Storage.info icons from the Amiga911 disk since they are not really needed. Then you will get 4.5 KB extra disk space.
As mentioned earlier, the "Workbench method" of activating the Amiga911 disk provides the possibility for a couple of workarounds, they are the following:
1. If your Amiga does not have the amount of free RAM that is required for activation, you can temporarily assign T: to another directory on your harddisk. The installer script uses T: for temporary storage of installation files, and by assigning T: to a place on your harddisk, the harddisk will then be used for storage instead of the Ram disk. In order to do this, you can for example enter the following in Shell: Assign T: SYS:T
2. Upon activating the boot disk, you will be prompted to insert your Workbench floppy so that files can be copied from it. If you don't have a Workbench disk, you can try to make an assign where files will be copied from your System drive instead. This of course requires that the Workbench version present on the partition is the same version that the Amiga911 disk was made for. Here is an example of how to do it in Shell: Assign Workbench3.1: SYS:
The install scripts
When you activate the included Amiga911 disk (by using any of the two methods), you may notice that the install script is very similar to the one used in the ClassicWB packs by Bloodwych. This is because the Amiga911 scripts is partially based upon the ClassicWB installer, but there are some differences though. One thing is that the Amiga911 disk uses a ZShell script (Boot method only) for the majority of the stuff it does, another is that it's more verbose in the sense that it gives the user more info about the stuff it is currently doing.
Since activating the Amiga911 disk involves both reading from a floppy disk and writing to another, I didn't dare to simply use DF0: for copying files, instead the scripts uses the volume names directly. This means for example Amiga911: and Workbench3.1:
|Followed a link? Please go to the Main Site © Roger E. Håseth 2012 - 2015|