Concerning the boot process for the Geneve, this would be my approach:
- Try to load _LOADSYS_ from DSK1 (search the device by standard DSR lookup). Allow for skipping this step by pressing the space bar.
- If this fails, or if it has been skipped, try to load _LOADSYS_ from "HD", "WDS1", "SCS1" in this order.
- If all this fails, output an error message and offer to start again.
- If LOAD_SYS could be loaded successfully from somewhere, pass control to _LOADSYS_. This is supposed to load _SYSTEM_ which contains the GeneveOS.
The advantage would be:
- No more low-level code in the boot ROM.
- _LOADSYS_ can be tailored to your needs. It can, for instance, be configured to load _SYSTEM_ from a different device than it is stored on.
- _LOADSYS_ can contain the low-level code that is specific for the various floppy and hard disk cards. We would need to create a version for TIFDC, HFDC, DDCC-1, ASCSI etc.
- In case you messed up your system, you can always override your configuration by DSK1._LOADSYS_
On other platforms, we would call _LOADSYS_ a driver for the boot device.
Note that I renamed the files, since the slash in the file name was arguably the worst idea of all.
This concept is alive since more than a year, but I did not find enough time. Someone to volunteer in the meantime?