Re: How to recreate the 31 July color.com

Jason Kemp <[email protected]> Mon, 25 Feb 2008 12:13:34 +0000
Newsgroups gmane.comp.lang.forth.colorforth
Message-ID <[email protected]>
Good afternoon Nick,

I sent this on Friday but I have just found it was rejected and returned 
by the list server:

***
Dear Nick,

Thank you: that has solved it. Having no icon data explains why the
red, green and blue oblongs appeared but no text.

Jason
***

My other messages this morning might make more sense if it is understood 
that you corrected my error on Friday.

Jason


Nick Maroudas said the following on 22/02/2008 20:14:
> Quoting Jason Kemp <[email protected]>:
>
>   
>> Hello,
>>
>> I should be most grateful if anyone could show me my
>> error. 
>> [snip]
>>  up to byte 12,347, but after this point the
>> original file is 
>> mostly non-zero values whereas the assembled one is
>> just padded with 
>> zeros, so I think I am overlooking something
>> fundamental.
>>
>> Regards,
>> Jason
>>
>> Nick here:  I think you might be missing the ikon
>>     
> data.  According to Tim Neitz the first 12 blocks are
> filled by the "editor", and the last 6 by the ikon
> data.  You can read his note at the end of Tim's nasm
> version of CF01, which is in John Comeau's sourceforge
> site that you use.  If you go to Tim's site you will
> see his complete set of nasm source, including data
> in the slot "cfinal". He says that his nasm code ought
> to compile into a faithful version of the original
> native CF01.    
>   
>> http://www.dnd.utwente.nl/~tim/colorforth/
>>
>> Likewise Josh Gram's source code for CF05 includes an
>>     
> icons.asm file.  I guess this will compile to be
> compatible with the complete 72k of selfbooting native 
> CF05.com that he also supplies (I use the 16bit color
> version). Ray has links with Josh: 
>
> http://www.nabble.com/Re:-ColorForth:-if-and--if-p10716747.html
>
>
> Caritas,
>
> Nick
>
> PS: Apologies to ColorForthers for inadvertently
> posting
> a private reply to Ray's post today, including my blog
> on
> a completely different subject.  Sorry.
>
> ****************************
>
> No trees were killed in the sending of this message.
> However, a large number of electrons were terribly
> inconvenienced
>
> *************
>