It turns out that iForth is radically,
tuliply different (why don't they stick
to wooden shoes and windmills, those
"fliegende Hollaender"?) from Win32Forth.
In iForth (Intel-Forth), you do not
"fload" a file to run it, you "include" it.
The main iForth executable considers itself
a "server" which may or may not deign to
do things for you. A lot of Deep Thought
has gone into the creation of iForth,
and it will take years to grok iForth.
Meanwhile before I had a completely free
day to come to grips with iForth, I spent
about three partial days carefully composing
http://cyborg.blogspot.com/2009/11/linux.html
which lays out my wildest dreams for iForth.
Your fellow slave to the Forth mystique,
Arthur
--
http://cyborg.blogspot.com
http://code.google.com/p/mindforth