AddBootNode

Add a BOOTNODE to the system (V36)

This function will do one of two things:

This routine makes sure that your disk device (or a device that wants to be treated as if it was a disk...) will be entered into the system. If AmigaDOS is already up and running, then it will be entered immediately. If AmigaDOS has not yet been started, then the data will be recorded, and AmigaDOS will get it later when it is started.

We try and boot off of each device in turn, based on priority. Floppies have a hard-coded priority.

There is only one additional piece of magic done by AddBootNode(). If there is no executable code specified in the DeviceNode structure (e.g. dn_SegList, dn_Handler, and dn_Task are all NULL) then the standard AmigaDOS file handler is used for your device. This will be the Amiga ROM default file system.

Documentation note: a "Task" as used here is an AmigaDOS-Task, not an exec-task. An AmigaDOS-Task, in the strictest sense, is the address of an exec-style message port. In general, it is a pointer to a Process's pr_MsgPort field (e.g. a constant number of bytes after an exec Task).

Autoboot from an expansion card before AmigaDOS is running requires the card's ConfigDev structure.

Pass a NULL ConfigDev pointer to create a non-bootable node.

bootPri

a BYTE quantity with the boot priority for this disk. This priority is only for which disks should be looked at: the actual disk booted from will be the first disk with a valid boot block. If no disk is found then the "bootme" hand will come up and the bootstrap code will wait for a floppy to be inserted. Recommend priority assignments are:

+5 - unit zero for the floppy disk. The floppy should

always be highest priority to allow the user to abort out of a hard disk boot.

0

the run of the mill hard disk

-5 - a "network" disk (local disks should take priority).

-128 - don't even bother to boot from this device.

flags

additional flag bits for the call: ADNF_STARTPROC (bit 0) - start a handler Process immediately.

Normally the Process is started only when the device node is first referenced. This bit is meaningless if you have already specified a handler Process, dn_Task is not NULL.

deviceNode

a legal AmigaDOS DeviceNode, properly initialized. Typically this will be the result of a MakeDosNode(). Special cases may require a custom-built device node.

configDev

a valid board's ConfigDev structure. This is required for autoboot before AmigaDOS is running and if left NULL will result in an non-bootable node.

ok

non-zero everything went ok, zero if we ran out of memory or some other weirdness happened.

This function eliminates the need to manually Enqueue() a BOOTNODE onto an expansion.library list. Be sure V36 expansion.library is available before calling this function!

AddDosNode(), MakeDosNode(), dos.library/AddDosEntry(), dos.library/MakeDosEntry(), exec.library/Enqueue(), <dos/dosextens.h>, <dos/filehandler.h>