Unable to have a boot file with Start on Archive set and no connection to archive

[SumGuyTwitches]

It is currently impossible to have a working boot file on a craft that does not have a connection to the archive when the "Start on Archive" option is set. Create a ship with a kos core. set it's location to out of range of coms and run the following code.
log "print " + char(34) + "Boot Successful" + char(34) + "." to "1:/boot/testboot.ks". set core:bootfilename to "/boot/testboot.ks". reboot.
No message is shown. The docs say that you cannot specify the volume, and an open bug exists discussing whether booting from the archive should even be allowed ( #2165 (comment) ). My issue is that I cannot use a local boot file not where the core's current directory path is. I have no connection to the archive, and with the idea that a bootfile should be relative to the core's native directory it doesn't make sense to me that it would need to be at the archive. It would honestly make more sense to require the boot files to be on the local drive if you consider connecting to comms to be part of the boot up process, however, my suggestions are one of the following:

1. allow volume references in the bootfile name,
2. have craft with no connection to the archive fallback to local drives, or alternatively have a fallbackbootfile for when there is no connection to the start on drive
3. allow each core to set a flag for which drive it boots too. This could also be handy for the situation where you have a large local drive for storing scripts, and many local cores with identical boot up routines. each core could boot from the localarchive.