[colorforth] NASM for colorforth

["t" <loveall@xxxxxxxxx>]

From: "Mark Slicker" <maslicke@xxxxxxxxxxx>
Sent: Sunday, July 07, 2002 9:24 AM

> Think I've mentioned this a few times. I've done a GNU assembler port of
> the MASM source, so you can compile on all platforms the GNU tools are
> available for (pretty much all C platforms).
>
> If there really is interest in NASM let me know. I could do a
> port. The program I wrote can translate with excelent acuracy. Give
> me an email if you are interested. If this is really holding so many back
> to contributing to colorForth, I would be glad to help.

There have been repeated requests for a NASM port on this email list and in my
private communications. Since I have a functional development system using MASM
have not felt the need to port it, but thought others might find the link
useful.

> I have no interest in a Linux port. Seems like giving up to me. Chuck is
> aparently working networking. I'm working on some devices, ethernet,
> sound, graphics. I've implemented one internet protocal, jpeg. Bernd
> Beuster has done sound for the sound blaster, and PIT. A colorForth
> system with base software does seem realizable.
>
> What is needed is to get more people into the process of
> contributing. The hardware required is probably holding many back. What is
> a good strategy for addressing this?

The major roadblock to having a more active colorForth development effort is
the lack of an efficient method of sharing code. Until colorForth has a network
interface or (travesty!) an ASCII implementation, the requisite hand
translation of colorForth source will inhibit code sharing. If you will notice,
most of the shared development efforts have centered around
the ASCII assembler source which is easily communicated. This is not a
coincidence.

> There is pretty much only two things
> that seem to go wrong, floppy and graphics. What is needed is proper
> diagnoses. What kind of system the person has, what graphics card. Which
> one fails. Chuck has a database for some of this. What could also be
> useful is if colorForth does work, what version are you using? What
> versions did you try that didn't work? Some of the versions I created with
> vbe code did help some people. There have also been mesages posted to
> this list which contain fixes for other graphics cards.
>
> Another thing that is needed is to centralize all this information. This
> information is of no use if it scattered about a hundred different pages,
> and someone can't find it. Should the colorForth community have a
> centralized web page?

There are two indexes to colorForth resources. Kris Johnson's Wiki page
http://kristopherjohnson.net/cgi-bin/twiki/view/Main/ColorForth
and my colorForth index
http://www.users.qwest.net/~loveall/c4index.htm

My index has indices into Chuck's colorForth site and Jeff Fox's UltraTech
page. It also has commented links to your stuff, Bernd's efforts, Kris's Wiki,
a current archive of this email list, MASM32 and zipped build kits.

The only thing it might be lacking is a data base of operational colorForth
versions and matching hardware. That information is available in the email
archive.

If the colorForth email sysop were to include links to either of the these
colorForth indices in the footer along with the URL to Chuck's home page, it
might help.

Regards,
Terry Loveall
------------------------

To Unsubscribe from this list, send mail to Mdaemon@xxxxxxxxxxxxxxxxxx with:
unsubscribe ColorForth
as the first and only line within the message body
Problems   -   List-Admin@xxxxxxxxxxxxxxxxxx
Main ColorForth site   -   http://www.colorforth.com