[Coco] Bit-Banger Serial as external console?

[Stephen Fischer]

You go Forth in paths I don't know about.

As the baud rate must be set and code to write to the bitbanger port 
must be present, perhaps using the DEBC routine.

I would look for any keyword that implies output.

Trying just to print with other Forth's output routines might give a 
clue. I have a couple of other Forth that are on RTSI in a huge zip 
should you not find any with "PRINT".

It might be that no code is present because VCC was written after the 
Forth you are trying to use was written.

If you are on Windows, load the binary into WordPad (NOT notepad) to 
look for keywords.

If you are on OS-9 / NitrOS-9 my Colorful SLED ED6 can also be used to 
look for keywords.

(Don't save the files, ALL control codes are stripped with both of those 
methods.)

On other OS look for a text viewer that ignores control bytes, just look 
at the binary again.

SHF

On 3/27/2019 10:52 PM, M. David Johnson wrote:
> Thanks, Stephen -
> 
> Okay, I clearly didn't word my question properly. I apologize.
> 
> I'm generally not having any problem with printing to a text file via the Vcc BitBanger's capture tab. I do it all the time. It works just fine under DOS too.
> 
> The specific problem I'm having is that I can't figure out how to print at all from Talbot's ColorForth 1.1.
> 
> I've read Section 12.2 "Printing" in the ColorForth Manual, and I've LSCR'd CCF-MISC, but ColorForth still doesn't seem to recognize the "PRINT" word.
> 
> Since Stephen Pereira did the rewrite on ColorForth, I was hoping he might point me to something I've missed.
> 
> --
> M. David Johnson
> mdj at bds-soft.com