AnachronautandClaude Opus 5
3449405b18
CosmOS had 1,161 bytes of Program Memory left before the address applications load at, and Tab completion is not going to fit in that with anything to spare. So the wall moves up one page: the system keeps below 0x4FFF and 0x2FFF, and an application is based at 0x5000 and 0x3000. A PAGE IS A CHEAP THING TO GIVE IT AND AN EXPENSIVE THING TO RUN OUT OF. An application still has 44K of Program Memory before the vector table and the largest one here uses 7.5K, so what was taken from applications is space nothing has ever asked for - while what the system gained is the difference between building the next thing and counting bytes while building it. Not doubling, which was the version that would have cost application space worth minding. One page, and the same again when it is needed. Nothing in the machine knows where the wall is, so this is 34 #Base lines, one threshold in the fault handler, and the table in the CosmOS README that Tests/docs.sh reads its limits out of. The native assembler's scratch map had to move with it, and docs.sh said so before anything ran: its data reached 0x40D6 and its buffers began at 0x4000, so they were sitting on its variables. That file already carries a paragraph about the floor coming up and the map staying where it was. It has happened twice now, and been caught by a check the first time wrote. Twenty three recordings are the same runs a page higher. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW
53 lines
1.6 KiB
NASM
53 lines
1.6 KiB
NASM
; Reboot.asm
|
|
; Starts the machine again.
|
|
;
|
|
; Whatever put the first instruction in memory does it again, and everything after that
|
|
; follows: the boot slot is read, the loader runs, and whatever the configuration names -
|
|
; or whatever Once asked for - is what starts.
|
|
;
|
|
; ---- Why this writes a port ----
|
|
;
|
|
; A reset has to work when the system does not. Something that could only be asked for
|
|
; through SWI would be unavailable in exactly the case that wants it most, and a program
|
|
; that owns the whole machine has no system to ask. So the machine takes it directly, the
|
|
; way it takes everything else: a byte out of a port.
|
|
;
|
|
; It is still a program rather than a shell word, because it is not the shell's business
|
|
; and because a word built into the shell is not callable by anything else.
|
|
;
|
|
; ---- What survives ----
|
|
;
|
|
; The disk, and everything written to it. That is what warm means: the machine starts
|
|
; again, the world it starts into does not. Nothing here flushes anything, because nothing
|
|
; on this machine is held back - a file is on the disk when the write returns.
|
|
;
|
|
; Written by Anachronaut
|
|
|
|
#Include services.asm
|
|
|
|
#Program
|
|
|
|
#Base 0x5000
|
|
|
|
start:
|
|
SETD.0 Saying
|
|
SWI osPrintString
|
|
|
|
INIA 0x01
|
|
OUTA 0x13
|
|
|
|
; Not reached. The machine has started over by the time the next instruction would run,
|
|
; so anything here is a statement about a machine that no longer exists - but a program
|
|
; whose last instruction is an output is one byte from running into whatever follows it,
|
|
; and that is not a habit worth keeping.
|
|
RSTA
|
|
SWI osExit
|
|
|
|
#Data
|
|
|
|
#Base 0x3000
|
|
|
|
Saying:
|
|
"starting again
|
|
"
|