ARC firmware is the menu-driven firmware that Alpha systems use to boot Windows NT. It implements the Advanced RISC Computing (ARC) specification, which standardizes features of RISC computers including their firmware. ^{1) 2)}

There are three families of ARC firmware on Alpha:

• ARC (Windows NT ARC firmware, also "ARC Multiboot" or "ARC console"): Digital's original firmware, used on the Jensen, Multia, AlphaStation 200 and 250, AlphaServer 1000 and 2100, and the Digital Semiconductor evaluation boards and motherboards up to the AlphaPC 164.
• AlphaBIOS: the successor to ARC, with a different user interface. Digital introduced it with the Alpha XLT series. ³⁾
• ARCSBIOS: firmware written by Deskstation for its Ruffian boards (see ARCSBIOS).

"ARC BIOS" and "ARCBIOS" are used informally for both ARC and AlphaBIOS. ⁴⁾ "ARCS" in Alpha/Linux usage refers to Deskstation's firmware, not to SGI's ARCS.

Systems intended for OpenVMS and Tru64 UNIX use the SRM console instead. Some systems carry both, and can switch between them (see Switching to SRM).

Where SRM is available, it is preferred for Linux over MILO, whose PALcode is less complete than SRM's (see MILO: PALcode and Choosing firmware for Linux). ^{5) 6)} Linux 6.10 removed support for processors older than the EV56 (21164A) and for the Alpha XL, so a system without SRM can run a current kernel only if it has an EV56 or later processor. ^{7) 8)}

• ARC: Supplementary menu, "Set up the system…", then "Switch to OpenVMS or OSF console" (on later versions "Switch to OpenVMS or Digital UNIX console"), then "Switch to OSF", and power-cycle. ^{9) 10)} On the evaluation boards, this is under "Machine specific setup…". ¹¹⁾
• AlphaBIOS: in Advanced CMOS Setup, set "Console Selection" to "Digital UNIX Console (SRM)" or "OpenVMS Console (SRM)", then save with F10. ^{12) 13)}
• Single-image boards: the AlphaPC 164, 164LX, and 164SX hold only one firmware in flash, so switching requires flashing the other firmware. ¹⁴⁾ On the AlphaPC 164LX and 164SX, this is done with "Upgrade AlphaBIOS" and a floppy containing the SRM image (LX164SRM.ROM or SX164SRM.ROM). ¹⁵⁾

Switching from SRM back to ARC or AlphaBIOS is described in SRM Console: Switching to ARC or AlphaBIOS.

The SRM image for the AlphaPC 164LX, lx164srm.rom, is kept in the alphalinux/firmware repository with the other firmware listed in Firmware: Obtaining and updating firmware. After the first SRM start, the settings for a serial console and for booting Linux unattended are described in Using the SRM Console: Serial console and Installation: Booting the installed system.

The Alpha XL series has only ARC or AlphaBIOS, and no SRM. ²⁹⁾ Sources disagree about the Digital Server 3300: one describes it as having no SRM, ³⁰⁾ while another says that the Digital Server 3300, 5300, and 7300 can be switched to SRM but will not boot Digital UNIX or OpenVMS from it. ³¹⁾ See Conflicting information.

The firmware reads the operating system loader from the disk and runs it, and provides I/O services to the loader through ARC callback routines. The loader then loads the Windows NT HAL and PALcode, and the kernel switches to that PALcode. ³²⁾ ARC also stays in memory after Windows NT boots so that NT can make callbacks. ³³⁾

ARC and AlphaBIOS provide PALcode for Windows NT, which Linux cannot use, so they cannot load a Linux kernel directly. ^{34) 35)} Linux on these systems is booted through MILO, which supplies its own PALcode and reclaims all of the memory used by the firmware. ³⁶⁾ The UP1000 uses APB instead of MILO. ³⁷⁾ The BSDs, which need the OSF/1 PALcode, boot only from SRM. ^{38) 39)}

The instruction set is the same under either PALcode, but little else is: under the Windows NT PALcode, interrupts, virtual memory (with a 32-bit address space and two-level page tables), traps, and process structures all differ from the OSF/1 PALcode. ⁴⁰⁾ MILO therefore has to carry its own PALcode and switch to it. ARC also cannot read a BSD disklabel. ⁴¹⁾

ARC is operated from a set of text menus. ⁴²⁾

• Boot menu: "Boot Windows NT", "Boot an alternate operating system…", "Run a program…", and "Supplementary menu…". "Run a program" runs any ARC application, given its path.
• Supplementary menu: "Install new firmware…", "Install Windows NT from CD-ROM", "Set up the system…", and "Display hardware configuration".
• Setup menu: set the time, default environment variables, default configuration, boot selections, autoboot, machine-specific settings (including switching to SRM), and editing environment variables directly.

ARC names devices by a path of bus, controller, and device, e.g. scsi(0)disk(1)rdisk(0)partition(1). multi() devices are on the system board (keyboard and serial ports), eisa() devices are on the EISA bus (video and floppy on the AlphaServer 2100), and scsi() devices are SCSI disks and CD-ROMs. ^{43) 44)}

Sources: ⁴⁵⁾

Each boot selection is a set of variables:

Sources: ⁴⁶⁾

The firmware passes SYSTEMPARTITION, OSLOADFILENAME, OSLOADPARTITION, and OSLOADOPTIONS to the loader it runs. ⁴⁷⁾

The ARC specification requires a DOS-formatted primary partition, the system partition, to hold operating system loaders. The specification requires ARC systems to read both FAT12 and FAT16 but to create only FAT16. ⁴⁸⁾ ARC only understands PC (fdisk) partition tables, not BSD disklabels. ⁴⁹⁾

Older ARC versions cannot create a system partition; arcinst.exe from the Windows NT CD, started with "Run a program", does this. ^{50) 51)}

ARC runs linload.exe, a small ARC program that loads MILO and switches to MILO's PALcode. MILO then relocates itself and boots Linux. ⁵²⁾ A typical boot selection is: ⁵³⁾

LOADIDENTIFIER=Linux
SYSTEMPARTITION=multi(0)disk(0)fdisk(0)
OSLOADER=multi(0)disk(0)fdisk(0)\linload.exe
OSLOADPARTITION=multi(0)disk(0)fdisk(0)
OSLOADFILENAME=\noname.arc
OSLOADOPTIONS=

• OSLOADFILENAME names the MILO image. ⁵⁴⁾
• MILO runs the contents of OSLOADOPTIONS as a command, e.g. boot sda2:vmlinux.gz, which allows unattended booting. ⁵⁵⁾
• The required linload.exe version, and other ways to start MILO, are described in MILO: From ARC or AlphaBIOS.

The Jensen (DEC 2000 AXP, DECpc AXP 150), supported by Linux 6.9 and earlier, has both ARC and SRM, and Linux on it is booted from SRM; see Jensen. ^{56) 57)}

AlphaBIOS replaced ARC with the Alpha XLT series. ⁵⁸⁾ Digital Semiconductor used it on the AlphaPC 164LX and AlphaPC 164SX; its earlier boards kept ARC. ⁵⁹⁾ The AlphaBIOS release notes of July 1999 list these supported products: ⁶⁰⁾

• AlphaPC 164LX, 164RX, 164SX, and 264DP
• AlphaServer 800, 1000 5/xxx, 1000A 5/xxx, 1200, 4000, 4100, and DS20
• AlphaStation 255 and 600A
• Alpha XLT
• Compaq Professional Workstation XP1000
• Digital Personal Workstation and Digital Ultimate Workstation
• Digital Server 3000/3300, 5000/5300, and 7000/7300

The final V7.3 firmware CD also includes AlphaBIOS for the AlphaServer 4000, 4100, 8200, 8400, GS140, DS10, DS20, and ES40. ⁶¹⁾

AlphaBIOS Setup is entered by pressing F2 during startup. Its main menu offers "Display System Configuration…", "Upgrade AlphaBIOS", "Hard Disk Setup", "CMOS Setup…", "Install Windows NT", "Utilities", and "About AlphaBIOS…". ^{62) 63)}

• CMOS Setup sets the date, time, floppy and keyboard type, and "Auto Start". Advanced CMOS Setup (F6) includes "Console Selection" and SCSI BIOS emulation. ^{64) 65)}
• Hard Disk Setup creates and formats partitions, including the FAT system partition. ⁶⁶⁾
• Utilities has "OS Selection Setup…", "Run ECU from floppy…", and "Run Maintenance Program…". ⁶⁷⁾ An operating system selection has a boot name, boot file, OS path, and OS options. ⁶⁸⁾

On a serial console, ARC and AlphaBIOS require a VT220-compatible terminal. Control keys stand in for function keys, e.g. Ctrl+B for F2 and Ctrl+U for F10. ^{69) 70) 71)} AlphaBIOS 5.66 and later boot without a keyboard on the AlphaPC 164LX and 164SX. ⁷²⁾

To boot MILO, add an operating system selection in "OS Selection Setup" with \linload.exe as the boot file on the FAT partition and \ as the OS path, and put a MILO command such as boot sda2:vmlinux.gz in the OS options. AlphaBIOS warns that the selection is not valid, which only matters for Windows NT. ⁷³⁾

• linload.exe 1.3 or later is required; see MILO: From ARC or AlphaBIOS.
• AlphaBIOS only lists primary partitions (1 to 4). ⁷⁴⁾
• On the UP1000, AlphaBIOS loads APB, which reads the AlphaBIOS boot configuration to find the kernel. An SRM console is also available for the UP1000, and is preferred (see SRM Console: System support). ⁷⁵⁾ APB and old MILO versions hardcode the old kernel start address, so kernels booted by them must be built with CONFIG_ALPHA_LEGACY_START_ADDRESS (see Kernel). ^{76) 77) 78)}

On AlphaServers and workstations that support both Windows NT and Digital UNIX, AlphaBIOS is a separate, compressed image in flash. SRM always starts first, and then loads AlphaBIOS if os_type is nt or the alphabios command is entered. ^{79) 80)} AlphaBIOS moved to a new location in flash in version 5.67, which requires SRM 5.3 or later. ⁸¹⁾

• ARC: "Install new firmware" in the Supplementary menu searches the CD-ROM and floppy for FWUPDATE.EXE and runs it. ⁸²⁾ Versions before 4.42 can only run it from a floppy. ⁸³⁾
• AlphaBIOS: "Upgrade AlphaBIOS" searches the CD-ROM and then the floppy for an update. On the AlphaPC 164LX, the floppy holds lx164nt.rom. ^{84) 85)} Version 5.69 changed the search order to CD-ROM, floppy, then network. ⁸⁶⁾ On AlphaServers with SRM, "Upgrade AlphaBIOS" starts the Loadable Firmware Update utility. ⁸⁷⁾

Deskstation wrote its own ARC-compatible firmware, ARCSBIOS, for the Ruffian (the AlphaPC 164UX and 164BX), along with an ARCS program, ldmilo, to load MILO. The Ruffian has no SRM, ARC, or AlphaBIOS. ^{93) 94)}

• ldmilo ignores OSLOADFILENAME. It differs from linload.exe because ARCSBIOS lacks Digital's vendor callback vector. ⁹⁵⁾
• ARCSBIOS requires the VGA card to be in a 64-bit slot and beeps three times otherwise. ⁹⁶⁾
• The ARCSBIOS documentation describes no serial console support. ⁹⁷⁾
• Deskstation's ARC firmware and HAL were developed independently of Digital's. ⁹⁸⁾

• Time-of-year clock: ARC and AlphaBIOS store the year relative to 1980. ⁹⁹⁾ Linux detects the epoch at boot and prints e.g. rtc: ARC console epoch (1980) detected. ¹⁰⁰⁾ The epochs used by SRM, and the problem they cause when the same machine also boots from SRM, are described in SRM Console: Known issues.
• Video cards: ARC and AlphaBIOS initialize VGA cards with an x86 BIOS emulator. ¹⁰¹⁾ nVidia TNT2 cards fail in it. ¹⁰²⁾ AlphaBIOS allows no BIOS emulation if a Digital TGA card is installed. ¹⁰³⁾ If ARC cannot use the graphics card, it uses the serial port. ¹⁰⁴⁾
• SCSI boot devices: BusLogic controllers cannot be used to boot MILO from ARC or AlphaBIOS. ¹⁰⁵⁾
• ECU availability: EISA systems need the ECU floppy, which contains proprietary code and cannot be freely distributed. ^{106) 107)}

The following sources conflict with each other or with the account given above. They are listed here for further investigation.

• Whether Windows NT systems can switch to SRM
  • "RE: switching from ARC back to SRM", William H. Magill, axp-list, 14 Aug 2000: "I believe that there was only ever one box which had NO SRM console accessable by setting the CMOS "console selection".
  • "Re: DEC ALPHA 3305", William H. Magill, axp-list, 21 May 2000: "the 3300 series has no SRM console; it has the ARC console only."
  • "RE: Compaq to offer Tru64 for $99", John Jemiolo, axp-list, 5 Nov 1999: "You can switch the 33,53,73 to srm console, but they will still not boot unix or vms."
• Whether OSLOADOPTIONS reaches MILO
  • "Re: MILO on Multia: environment corruption?", Stephen C. Tweedie, axp-list, 14 May 1996: "that variable's contents will be executed as a command line by MILO when it starts up."
  • "Maximum Memory size", Brian Cruikshank, axp-list, 13 Dec 1996: "The OSLOADOPTIONS does not seem to be sent to Milo."
• Last AlphaBIOS on the ES40
  • FWREADME.TXT for the ES40 on the V7.3 firmware CD lists AlphaBIOS V5.71.
  • Alpha Systems Firmware Update V7.3 Release Notes Overview, p. 10, lists no Windows NT firmware for the ES40.