[Coco] [COCO} VCC 1.43beta release

[Brett Gordon]

>
>   Date: Fri, 19 Apr 2013 03:00:18 -0400
>   From: Aaron Wolfe <aawolfe at gmail.com>
>   Subject: Re: [Coco] [COCO} VCC 1.43beta release
>   To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>   Message-ID:
>           <
CAA6uQZSuBRCQrAm42tK1SsUJiJxfzeejvvbkaS6ay70FOLjhHw at mail.gmail.com>
>   Content-Type: text/plain; charset=ISO-8859-1
>
>   You know, its probably worth mentioning that the Becker interface
support
>   now found in Vcc, XRoar and CoCo3FPGA is not at all limited to use with
>   DriveWire.
>
>   If you've ever wanted a simple way to write code that gets data in or
out
>   of an emulated CoCo, it doesn't get much easier than the Becker port.
It
>   just maps a simple FIFO to a TCP socket, and the other end of that
>   connection can be nearly anything, including another program running on
a
>   PC or even another CoCo that is running DW.
>
>   We've worked hard to make this a standard across as many CoCo
>   implementations as possible, so it would be great to see it put to a
>   variety of uses.  There are even rumors of the Becker port being
>   implemented on a real CoCo :)
>
>   Anyway, yes it makes using DW with emulators possible, but I think there
>   are possibilities far beyond just that.

Speaking of Odd possibilites:  CoCoBoot's Virtual Machine, Legs, supports
the Becker interface in both it's C and 6809 asm implimentations.   This
allows me to code for the VM in Linux (fast), but still expect the same
byte-code to run on my CoCO.  Once I know the  OS-DW-Becker software stack
works in Linux, it'll work in an emulater ( and Gary's FPGA, I suppose )
So my Linux box has the LegsVM and a DriveWire server running, with no
CoCo, real or emulated, involved.   Because the DW via the Becker interface
is so simple I'm freed up to do the hard word of supporting RBF and RSDOS
filesystems....

-- 
Brett M. Gordon,
beretta42 at gmail.com