[Coco] Eureka! I'm Running My Coco 3 with Drivewire 4 Server Finally! or I Found a Bug in HDBDOS v1.4 DW4 Coco 3!

[Bill Pierce]

Thanks Aaron, I'll check it out. Wasn't the cable mod just tying a couple of the wires together on the PC DB9 end? I seem to remember that being mentioned in the DW wiki. If so, my cable is already modded for it as I used that configuration.

Bill Pierce
My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com




-----Original Message-----
From: Aaron Wolfe <aawolfe at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Tue, Sep 17, 2013 2:22 pm
Subject: Re: [Coco] Eureka! I'm Running My Coco 3 with Drivewire 4 Server Finally! or I Found a Bug in HDBDOS v1.4 DW4 Coco 3!


I'm looking at

http://sourceforge.net/p/nitros9/code/ci/default/tree/level1/modules/

and it seems there are 3 pairs of read/write sub modules for dw.  One
is simply called dwread/dwwrite... this is the standard 115.2 on coco
3 module.
then there is the dwrd/dwwrmess pair for use with MESS and John L.'s
mess patch (this is kind of outdated, should really be changed to use
Becker port like VCC and XRoar do).  Then there is a pair called
dw4read/dw4write... these are the 230k mode drivers. Their label being
"dw4" is consistent with the 230k HDBDOS ROM being labeled "dw4"...
maybe there is some logic here and I'm just not aware or have
forgotten :)



On Tue, Sep 17, 2013 at 2:03 PM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>
> Aaron,
> Where are the OS9 drivers for the 230k mode?
> Are they in the repo? If so, under what name?
>
> Bill Pierce
> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Co-Webmaster of The TRS-80 Color Computer Archive
> http://www.colorcomputerarchive.com/
> Co-Contributor, Co-Editor for CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> E-Mail: ooogalapasooo at aol.com
>
>
>
>
> -----Original Message-----
> From: Aaron Wolfe <aawolfe at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Tue, Sep 17, 2013 12:34 pm
> Subject: Re: [Coco] Eureka! I'm Running My Coco 3 with Drivewire 4 Server 
Finally! or I Found a Bug in HDBDOS v1.4 DW4 Coco 3!
>
>
> On Mon, Sep 16, 2013 at 11:29 PM, Kip Koon <computerdoc at sc.rr.com> wrote:
>> Aaron,
>> In the HDBDOS portion of the toolshed repository,  there are two DW4
>> versions, HDBDW4CC2 and HDBDW4CC3.  They are built along with the other
>> versions of HDBDOS so I was under the impression that they were the latest
>> versions.  If they ARE 230K Baud versions, then that would be the reason why
>> there was no communications with the DW4 server.  The server is set to
>> 115200 Baud.  That raises another question.  If that is the case, then how
>> do you set 230K baud for the com port on the Windows PC?
>
> Hmmm I do not know exactly what those ROMs are, but IIRC there was a
> 230k ROM for CoCo 3 and a 115.2k ROM for CoCo 2 using Darren's
> technique, so that might be them.  If so, we should try to make it
> more clear that they are not "standard" nor required for DW4 use...
> that or I should make the wizard ask the user about which they have
> and then set the 230k mode accordingly.
>
> One problem the DriveWire project has is that while I'm happy to hack
> on the server, I really don't know much about ROMs or "hard core" CoCo
> stuff.  I can just barely write some ASM when I absolutely have to,
> but things like Darren's awesome serial routines are way over my head.
>  This leads to a disconnect between the ROMs and the server sometimes,
> and has limited some features I'd love to have due to lack of support
> on the ROM side.
>
> If these "DW4" ROMs are indeed the 230k version, you can set the
> following items in config.xml or via Config Editor to use them.
>
> Possibility #1: If the ROMs send the special sequence of bytes that
> the OS-9 driver does to identify 230k mode, you would only need to
> set:
>
> <DetectDATurbo>true</DetectDATurbo>
>
> This detection was originally intended to allow automatic switching
> from a standard, 115k ROM to 230k mode when the OS-9 driver loads, and
> if you want to play with 230k mode without changing ROMs, this is a
> good way to do it.  When the 230k OS-9 module inits, the server will
> automatically kick up to 230k mode.
>
> Possibility #2: If the ROMs require the server already be in "DATurbo
> Mode", you will need:
>
> <SerialRate>230400</SerialRate>
> <SerialParity>none</SerialParity>
> <SerialStopbits>2</SerialStopbits>
> <ProtocolFlipOutputBits>true</ProtocolFlipOutputBits>
> <ProtocolResponsePrefix>true</ProtocolResponsePrefix>
>
> I believe that would do it.  Note that you also need a cable with CD
> and RD connected on the coco side.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco