=?windows-1255?Q?Re=3A_=5Bcolorforth=5D_if_then_else_-?= =?windows-1255?Q?_but_why_is_there_no_=91else=92_in_colo?= =?windows-1255?Q?rForth=3F?=

Jason Kemp <[email protected]> Wed, 05 Nov 2008 23:42:56 +0000
Newsgroups gmane.comp.lang.forth.colorforth
Message-ID <[email protected]>
Hi Nick,

Thanks, that is great news.  I think I tried booting CF2a and got 
frustrated at that load-the-whole-floppy thing and  I'd started on CF05 
and so didn't want to change at that point.  So if I continue working my 
way through CF05 blocks 20 and 22 (be nice if I finish by xmas!) I won't 
have invested in something that has been superseded.

Jason

Nick Maroudas said the following on 05/11/2008 06:40:
> Nick  here:  USB and USBoot stuff in CF2a
>
> block 62 boot assembler 
>       64 USB assembler
>       66 boot sector 
>       68 USBoot 
>       72 flash files 
>       82 USB macro (like block 20 in CF05) 
>       84 USB flash (like CF05 22) 
>       86 USB command
>
> This seems to continue Chuck's progress from CF01 to
> CF05, moving boot code from assembler 
>
> to Forth blocks; and from CF05 TO CF2A, moving from
> floppy boot to flash boot. The fact that 
>
> the new bootloader CF2.EXE can boot all 3 versions into
> Windows (CF01, CF05 and CF2a) 
>
> indicates a structural similarity: it would be nice to
> have a dissassembly of the native 
>
> CF2a kernel from OkadWork.cf, to compare with the
> dissassemblies that Karig, Tim and Terry 
>
> made for CF01, and Josh's dissassembly of CF05.  The
> dissassembly of CF2a will be short: a 
>
> dump of blocks 0 to 17 reveals great swathes of zeros,
> presumably where cpu code has been 
>
> shifted to Forth source code.
>
> Caritas,
>
> Nick  
>
>