=?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?=

Hi Nick,
> 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.
So is there no kernal.asm or equivalent now: is it all done by blocks 62 
and 66 etc.?  (Oh, hang on, they’re just the boot.asm equivalent aren’t 
they?) Has this been sourceless too, inasmuch as it’s built on CF05?

The CF2EXE tip is handy as two versions can be compared side by side.

Thanks,
Jason