Ich kann mir nicht vorstellen, dass es die komplette Installation auf Disketten gegeben hat, zumindest nicht für die DomainOS Systeme.
Afair konnte man ja eine Apollo von einer anderen über Apollo-Tokenring booten, das dürfte dann die Lösung für die Systeme ohne Tapedrive gewesen sein.
Das weiss ich nicht. Aber die Dokumentation von 1989 (http://bitsavers.trailing-edge…tallation_Tools_Oct89.pdf) hat das zumindest für ein Minimalsystem angedeutet:
Booting from Floppy Disks
Use the following procedure to boot your node from floppy disks.
NOTE: To boot from floppy disk. the node must have an internal Winchester disk.
1. Make sure the target node is in SERVICE mode. This mode is usually controlled by a toggle switch on the back panel of the CPU. See your node' s operating guide for more information.
2. If the node has a display: shut down the node by entering the shut command at the Display Manager (DM) command line:
Command: shut
Wait for the message SHUTDOWN SUCCESSFUL and for the Mnemonic Debugger (MD) prompt to appear. The prompt depends on the node firmware, but it will end in a >.
3. Enter a reset command, followed by a carriage return at the next prompt:
>RE <RETURN>
4. Put the floppy disk labeled FLPx_PREPn into the disk drive. Where x is 8, if you are using 8-inch floppies, and 5 if you are using 5-1/4-inch floppies.
n is the number corresponding to the /saun directory required to run the node you are using. Table 2-1 shows the correspondence between the machine types for which a floppy boot is possible and the /saun directories. Note that the /sau2 and /sau4 machines use 8-inch floppies to boot with and magnetic tape for the actual software installation.
Table 2-1. The /sau Directories by Machine Type for Floppy Boot
/sau2 -> Series 300, 320, 330
/sau4 -> Series 160, 460. 660
/sau7 -> Series 3500, 4000, 4500
/sau8 -> Series 3000
For example, if you are using a DN3000 with a 5-1/4-inch floppy, choose the floppy labeled FLP5_PREP8.
The x and n variables in all subsequent references of the form FLPx, PREPn, and BOOTn have the same meaning as those described here.
5. Select the floppy disk drive as the device from which to load software with the command
>DI F
6. Start the calendar program:
>EX CALENDAR
Respond to the series of prompts. See Appendix B for a detailed description of the prompts. Running calendar at this point ensures that invol will create valid Unique Identifiers (UIDs) for the objects it creates on the disk.
7. When you finish running calendar, reset the node and select the floppy drive again:
>RE <RETURN>
>DI F
8. Start the invol program:
>EX INVOL
If you are unfamiliar with the invol program, refer to Appendix A, which provides a detailed description of the invol procedure. When you finish with Appendix A, go to the next step.
On the invol menu, select option 1, Initialize a Virgin Physical Volume. Respond to the subsequent prompts.
When asked Anything more to do? enter y. Then select option 8, Create or Modify an OS Paging File. Respond to the subsequent prompts. Unless you have special paging size requirements, accept the default paging size. When asked Anything more to do? enter no.
9. Reset the node, select the floppy drive, and run calendar again, this time to set the time for objects subsequently installed on the disk:
>RE <RETURN>
>DI F
>EX CALENDAR
See Appendix B for a detailed description of the calendar program.
10. Remove the floppy from the disk drive. Then insert the floppy disk labeled FLPx_BOOTn into the drive, after you make sure it is write-enabled.
11. Reset the node, select the floppy drive, and boot from the floppy:
>RE <RETURN>
>DI F
> EX DOMAIN OS
After a series of messages, the phase II boot shell comes up, indicated by the ) prompt.
12. Transfer the contents of the floppy to the hard disk with the command
) CF /FLP/INSTALL/LOAD_BOOTn
13. Shut down the node, reset it, and boot from hard disk:
) SHUT
BEGINNING SHUTDOWN SEQUENCE
SHUTDOWN SUCCESSFUL
>RE <RETURN>
>EX DOMAIN_OS
14. Remove the floppy disk from the drive.
15. Insert the remaining Domain/OS floppy disks into the floppy drive and load their contents to disk. Insert the disks in the order shown below, or according to the prompts of the program, if they are different. If additional floppies are required, you are prompted for them by name.
After you insert each floppy, enter the command
) CF /INSTALL/LOAD_floppy_name
where floppy_name is the part of the floppy disk name appended to FLPx_. For example, to load FLPx_BASIC_l,
enter
) CF /INSTALL/LOAD_BASIC_1
Floppy Insertion Order:
FLPx_BASIC_l
FLPx_BASIC_2
FLPx_BASIC_n (Additional basic floppies as needed)
FLPx_TOOLS_l
FLPx_TOOLS_2
FLPx_TOOLS_n (Additional tool floppies as needed)
FLPx_LIBRARY_l
FLPx_LIBRARY_2
FLPx LIBRARY n (Additional library floppies as needed)
16. If your node is a DN460 or DN660, insert the floppy labeled FLPx_UCODE4. Then load its contents (/sau4 microcode) with the command
)CF /INSTALL/LOAD_UCODE4
17. Remove the floppy disk from the drive.
18. Switch the node from SERVICE to NORMAL mode.
19. At this point, enough of the operating system has been loaded to run the DM or the SPM. To complete the booting process, enter
)GO
If you are at a node with a display, the DM is started, and the login prompt appears. If you are at a DSP, the SPM is started.
Continue with the next section.