A: Yes. An RP9 package can contain both ADF or HDF disk images with games or other applications, and a configuration reference (in the XML manifest) specifying that the system should boot from a well-known reference configuration. This results in an RP9 file that does not contain Amiga operating system files, and which therefore is both more compact and unencumbered from third-party copyrights.
The simplest form of a bootable RP9 is one that contains no disk images at all, and which simply references a built-in boot system. In order to add content to the RP9, it is usually desirable to add one or more disk images to the RP9.
The Amiga system configurations in Amiga Forever are set up so that if a volume named "AF-Application" is detected, the "S/user-startup" file on that volume is executed during the Startup-Sequence of the initial system. This hands over control of the Amiga environment to the content of the RP9 (e.g. to start a game). In order to use this functionality, the RP9 must contain an ADF or HDF disk image with an Amiga volume name of "AF-Application", and having the desired code in "S/user-startup".
By default, the session is shut down after execution of "S/user-startup" has completed. This is to ensure that once the application has terminated the session is not left in a state which is unrelated to the application and which could be confusing to the user. To avoid the shutdown, run LoadWB (if desired) and include a final EndCLI > NIL: at the end of the custom "S/user-startup" file.
To configure a bootable RP9 within Amiga Forever, the easiest way is to right-click a title in the Systems tab, select Create Copy, and then Edit the copy. The Media tab of the editor makes it possible to set a built-in boot system (which is a standard part of Amiga Forever, and is not in the RP9) and to add disk images. The volume name of the disk images can be set by selecting an image and then Edit.
Alternatively, it is possible to set the Built-In Boot option to None, and to add one or more floppy or hard disk images where the first image is bootable.