A911Maker Prefs & Edit project details
It has the following options:
Use Workbench ADF image files as copy sources
When the "Copy system files" function is run on Amiga911 disk projects, you will be asked to insert a Workbench disk, so that certain system files can be copied from it. This can be somewhat of a tiresome affair since maybe you don't have a Workbench floppy at hand right then, or the disk may have read errors, and besides - copying from floppy disks is also rather on the slow side.
But if you have one or more Workbench disks in the form of ADF image files, you can enable this option instead. This will allow you to select all the Workbench ADF's you do actually have (just click the ? buttons). Now every time "Copy system files" is run, it will first check if a proper Workbench disk is present, and if it's not, the ADF image will automagically be mounted as a DOS device. The requested files will then be copied from this virtual disk.
A couple of things to have in mind:
1. This functionality uses filedisk.device for mounting the ADF images. If this file is not present on your boot partition, you will be asked if it should be installed, and if the answer is yes, the file will be copied to the Devs drawer.
2. Keep the text boxes empty for all Workbench ADF's that you don't have! As you can see from the screenshot above, the "WB3.0 image" and "WB2.0 image" gadgets are empty. This will cause Amiga911 Maker to ignore trying to mount Workbench3.0 & Workbench2.0 images.
3. Make sure that the ADF files you select are the correct ones! Here's an example: For "WB3.1 image", you should choose an ADF file which is a DOS disk that really contains WB3.1 files, and that has "Workbench3.1" as volume name. Selecting the wrong ADF image will cause Amiga911 Maker to attempt mounting it every time "Copy system files" is run.
If a 68000 processor is chosen on page 1 of the "Configure system" window, Amiga911 Maker will by default make sure that all options which really requires a 68020 or higher CPU gets disabled. One example of this is the Poseidon USB stack, which then cannot be selected. But if you enable the "Expert Mode" option, it will be possible to include Poseidon and other 020+ only stuff to your 68K project. This can be useful when you just want to create a generic Amiga911 disk to be used on various Amiga models, where the lowest specced ones has a 68000 CPU. Do have in mind however, that this doesn't mean the 68020+ only stuff will actually work on a 68000 Amiga!
The "Expert Mode" option is mainly meant for those who know what they're doing (hence the option name), if you really want to be on the safe side, it's probably best to just disable it.
Always include BindDrivers
BindDrivers is a command that initializes any drivers found in the Expansion drawer upon booting. This type of drivers is usually for old non-autoconfig hardware meant for the oldest Amiga models. On Amiga911 boot disk projects, Amiga911 Maker will check if there's any files present in the System1/Expansion drawer, and if there is, BindDrivers will automatically be included in the project. If on the other hand the drawer is empty, the command will not be included.
By enabling this option, BindDrivers will as the title suggests, always be included on the Amiga911 disks.
Always use max LZX compression
If this option is enabled, and your Amiga has a 68020 or higher CPU, Amiga911 Maker will instruct LZX to use the maximum possible compression it can offer (-9) upon creating the lzx archives, otherwise -3 compression is used instead. This is because the 68000 version of LZX lacks -9 support. Disable this option if you want to force LZX to only use -3 compression, either because the 68000 version of LZX is used, or you want to ensure full compability with it. You can read more about LZX on the Some info about LZX compressing page.
When the Save button is clicked, the settings will be saved to a file called A911Maker.config in the main Amiga911 Maker drawer.
Edit project details
After creating a new project in Amiga911 Maker, you may regret some of the choices that was initially made. The most easiest way to change this earlier, was to simply delete the entire project, and then make a new one with the correct details. This was changed in version 1.59 of Amiga911 Maker, since you can now just select Project > Edit project details from the Amiga911 Maker menu. This brings up the window to the right, which has the following options:
Name - here you can enter a new name for the project, this will also rename the project dir.
Low-Mem disk - enable this if the boot disk is to be used on a Amiga with less than 2MB RAM, disable it if the disk is to be used on a Amiga with 2MB or more RAM.
XPK compress - if you want to create a Low-Mem disk, there will not be much space left for anything extra on the floppy since the majority of files won't be included in the LZX archives But by enabling this option, most of the files in question will be XPK crunched instead - thus leading to more free space on the disk. You can read more about the XPK system on this page.
AmigaOS - use the cycler gadget for selecting what AmigaOS version to include on the boot disk.
The last three of the above options is for Amiga911 disk projects only. A911Extras projects has in addition to the Name, a Disk/Drawer option and AmigaOS 2.x/3.x cycler. With Emergency Disk II projects, only the Name can be changed.
Have in mind that after changing the details of your project, it may then contain wrong and/or duplicate files. An example of this is if the project is an Amiga911 disk, and you change it from a Normal to a Low-Mem disk project (or vice versa). This may lead to there being double-up with the system files in the end. That's why it's recommended that you clear the project by selecting Project > Clear project from the Amiga911 Maker menu after such changes are made.
For now it's not possible to change the actual type of project, this means for example that an Amiga911 project will always remain an Amiga911 project.
|Followed a link? Please go to the Main Site © Roger E. Håseth 2015|