collapseos/blk/405

: BOOT
    0x02 RAM+ CURRENT* !
    LIT< (parse) (find) DROP (parse*) !
    ( 2e == SYSTEM SCRATCHPAD )
    CURRENT @ 0x2e RAM+ !
    ( 0c == C<* )
    LIT< (boot<) (find) DROP 0x0c RAM+ !
    ( boot< always has a char waiting. 06 == C<?* )
    1 0x06 RAM+ !
    LIT< INIT (find)
    IF EXECUTE
    ELSE DROP INTERPRET THEN
;
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-23 15:14:14 -04:00			`: BOOT`
			`0x02 RAM+ CURRENT* !`
			`LIT< (parse) (find) DROP (parse*) !`
			`( 2e == SYSTEM SCRATCHPAD )`
			`CURRENT @ 0x2e RAM+ !`
Replace the "> " prompt with the more traditional "ok" one 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. 2020-04-24 12:10:07 -04:00			`( 0c == C<* )`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-23 15:14:14 -04:00			`LIT< (boot<) (find) DROP 0x0c RAM+ !`
Replace the "> " prompt with the more traditional "ok" one 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. 2020-04-24 12:10:07 -04:00			`( boot< always has a char waiting. 06 == C<?* )`
			`1 0x06 RAM+ !`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-23 15:14:14 -04:00			`LIT< INIT (find)`
			`IF EXECUTE`
			`ELSE DROP INTERPRET THEN`
			`;`