[Coco] Who worked on the coco3dw1 implementation for MESS?

[Richard Goedeken]

Hi Robert,

The MESS software contains all the code for emulating the hardware "becker"
port.  In order to use this with DriveWire, you need to load a special version
of HDB-DOS which is patched to communicate with the Becker port, which is a
"virtual" hardware device in the sense that it was never used with a real
original Coco - only the FPGA coco or emulated cocos use this special hardware
port.

You can either load HDBDOS directly from a ROM image (using the MESS target
coco3dw1 instead of coco3 or coco3h or whatever).  Or you can load the patched
HDB-DOS program off of a disk image and exec it.  The ROM image and the disk
image should be in the ToolShed archive somewhere.  Let me know if you can't
find it.

Richard

On 02/17/2015 08:57 AM, Robert Hermanek wrote:
> I loaded mess for the first time using 158.  I noticed on the console screen
> that it indicated it was trying to reach out to a drivewire server via TCP, so
> I made my home-brew DW server available on the matching TCP port.  It
> connected when coco3 emulation started, but did not issue any commands.  And
> HDB-DOS commands like DRIVE# were not supported, my coco3.zip must load stock
> DECB 2.1. So in the end I had no idea how much "support" was there, or if it
> had ever been fully implemented.  I'd be curious how mess dw support should
> (or if it can) be used...
> 
> Thanks
> -RobertH
> 
> On 2/16/2015 4:23 PM, Robert Gault wrote:
>> Would the person who worked on the Drivewire implementation for MESS please
>> get in touch with me. There is a bug in MESS .158b which the MESS team may
>> not be able to handle.
>>
>> Robert
>>
> 
>