This would allow things like temporary giving control to the *CL
line on the TRS-80. For example... A very far fetched example. Not
at all the only *raison d'etre* of the layer...

Also, add word "C!+" and fix PSP leak in FILL.

I'm reserving the 100-200 range for non-bootstrapping needs.

XPACKed source needing to be kept in bootstrap bin didn't make
much sense. With the removal of stripfc, it makes more sense to keep
the compiled form of stage 1 in repository as a bootstrap binary.

Also, rename it to forth.bin.

no floppy yet.

This allows us to write LATEST at proper offset in emul/stage1.fs in
cases where we set a nonzero BIN(.

I have a working offset-by-0x100 stage0 now.

With cross compiling and IMMEDIATE words, things get icky with stable
ABI references. For the same reason that EXIT, (br) and (br?) need to
stay at stable offsets, these word references will not have BIN(
properly applied at Inner core xcomp.

The solution for now is to adjust during EXECUTE, which is ugly and
inefficient, but I don't see a better solution right now.

Will be useful as kinds of "#ifdef"s during xcomp.

ref #97

fixes #97

Will be useful for assembling binaries for the TRS-80 which can't start
at addr 0.

I have yet to test the whole process on real hardware. Soon.

This completes the migration of all Collapse OS code into blkfs!

And adjust rc2014/eeprom recipe

XPACK is more efficient than stripfc was, we can pack more stuff in 8K.
We now have enough space to fit readln.

Big bootstrapping change which greatly reduces the role of the modern
operating system in the bootstrapping process.

More reliable.

It's now a simple flag updated by the C< implementation. No more
routine pointer.

The goal is to avoid tons of "ok" during a LOAD operation.

The SD card driver is a bit too slow to be bearable. I'll write
_crc16 in z80 and see how it goes.

This will allow us to read from blkfs in tests.

Less noisy this way

This is done by adding a "C<* override" layer that is reset to 0 on
ABORT.

The problem was that when ABORT happened during a LOAD, we had a
resetted RSP and started from a clean INTERPRET, but LOAD didn't
have the opportunity to restore C<*, which caused it to continue
interpreting from the faulty BLK.

With a C<* override, we don't need to *restore* C<*, we just need to
clear the override.

This is more than cosmetic, it's also highly usable. The presence
or absence of the "ok" message allows us to know whether the command
aborted. Previously, the "> " prompt appeared when the system expected
a prompt in the INTERPRET context, whether the previous command aborted
or not.

Also, this allows us to get rid of that ugly FLAGS global variable.

That becomes irrelevant in Forth

The way is clear for complete stage1 bootstrapping on the RC2014
target!