Although 90% of installations will likely boot from the installation media using the default configuration and and run without the need for any special settings, the ArcaOS installation facility is quite flexible to accommodate non-standard conditions.
Overriding detected hardware and setting non-default values for the installation environment
There may be instances where the built-in hardware detection might properly identify devices needed for boot, but yet be unable to determine the proper device driver ordering to boot successfully. Likewise, identifying hardware and matching that against a database of known device drivers may not tell enough of the story (e.g., what special parameters are required for a given disk driver, controlling a particular device in your fancy workstation). This is where the boot option “Boot with menu for own values” is the correct path to take.
Selecting this option at the second installation boot menu access the Preboot menu. From here, hardware may be specially selected, a non-default keyboard layout for the installation environment may be set, and it is even possible to edit the CONFIG.SYS file before booting into the installer.
Adding a device driver not supplied with ArcaOS
There are several methods available to supply additional device drivers to ArcaOS for booting into the installation environment and including them in the installed system. In general, however, the process entails copying the driver(s) to some form of supplementary media (floppy, floppy disk image file, or the USB installation media) and having this present (mounted) while the system is performing its preboot setup.
For a physical ArcaOS installation disc, the only method currently available is floppy diskette. This
diskette must either be labeled BOOT_UPDATE or contain the file BOOT_UPD.TXT in the root directory in order to be recognized and read. (BOOT_UPD.TXT may be a completely empty file; its content is not read.)
ISO installation (virtual machine)
If installing to a virtual machine from the ISO, a floppy disk image file may be used, subject to the same requirements as for physical media, above (either labeled BOOT_UPDATE or contain the file BOOT_UPD.TXT in the root directory).
USB stick installation
This provides the most flexible option for supplying additional drivers. Simply copy the additional driver file(s) to the root of the USB stick after it has been created with the rest of the installation files. Any additional drivers here will be copied to the RAM disk at the start of installation, and from there, to the target system volume during install.
Saving and restoring custom Preboot menu settings
Similar to the methods for supplying additional device drivers, the settings used when accessing the Preboot menu may be saved and reloaded to prepare other similar systems. To do this:
- Once the installer starts, select the option (button) to access the System Management console.
- From the menu, select Command Prompts | Command Line (CMD) or Command Line (4OS/2).
- Determine the letter of the RAM disk by checking the following environment variable:
[r:\sys\install\gui] SET MEMDRIVE <Enter>
- Next, copy OS2CSM.SET from the RAM disk to the supplementary floppy (or floppy disk image) or to the root of the ArcaOS installation USB stick. To determine the drive letter of the ArcaOS installation USB stick, use the following command:
[r:\sys\install\gui] DFSANOS2 map <Enter>
The output will scroll. Generally, the last screenful will contain a disk labeled ArcaOS Stick, containing a FAT volume labeled AOSBOOT, identified as Removable.
To utilize these saved settings for the next boot, ensure that the supplementary floppy is mounted after the first boot menu is displayed or simply boot form the USB stick where OS2CSM.SET is located. OS2CSM.SET will be loaded as though each selection had been made in the Preboot menu.
Tip: OS2CSM.SET is also saved to the \sys\install\rsp directory on the system volume of the installed system, and may be copied from that location following phase 1 of the installation.