[Coco] DriveWire 4 - Turbo Mode + ROM SOLVED!

Mon Sep 23 05:51:40 EDT 2013

The Coco with a "DW4" ROM sends the code to switch to 230k (or 115k on
a coco2) when HDBDOS is started.  If you are using the DetectDATurbo
switch, then you'll have to restart HDBDOS to send this code any time
the server is restarted.

This code is also sent by the DW4 mode OS9 drivers when they start, so
you can use a regular DW3 ROM and only use the turbo mode when OS9
boots up (this was originally the only was to use turbo mode. there
was no turbo ROM, and this is the reason the detectDATurbo option
exists).

Another option would be to just set your server to always use turbo
settings.  Then detection would not matter.  These are:

<SerialRate>230400</SerialRate>  (or 115200 for coco 2)
<SerialParity>none</SerialParity>
<SerialStopbits>2</SerialStopbits>
<ProtocolFlipOutputBits>true</ProtocolFlipOutputBits>
<ProtocolResponsePrefix>true</ProtocolResponsePrefix>

Setting things this way probably makes more sense if you are using a
turbo ROM.  When the server code was written, this was not available.
Also, when the server code was written it was only available for CoCo
3.  This is why there are some static references to 230k mode.  Don't
let that bother you if you are using a CoCo 2, the actual serial port
rate is now set to 2X whether 57600 or 115k originally.

On Mon, Sep 23, 2013 at 1:36 AM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>
> Chad,
> I was going to suggest you "reset" the server after the changes as well as power down the Coco. Glad you figured this out. It seems the Coco sends a code to the serial port on power up. I think it was originally to "wake" up the printer or modem.... don't really know. In the old versions of DW, you had to do this on every startup to sync things (I think). It was also part of the Simple Config Wizard when setting it up and the "Test for Coco" function that used to be there. It more of less makes sure theres a Coco online. From this, it has always been my habit to not power the Coco until I started the server.
>
> Yes, the "Write to server" has been broken for a long time. It writes, but the server doesn't reset properly. A reboot is always best after any changes to the config.
>
> And yes, I think the speed you're seeing is just a static text message as the Coco 2 would have to be in double speed mode for that to be true and the Coco 2 loses video at that speed.
>
> Now that you have this running, it makes me want to see what the Coco 3 does with 230k baud in NitrOS-9. I can't hardly wait. I just have bridge the 2 pins on the cable and get the Nos9 dw4 drivers built. I may play with that tomorrow after I wind up the starter kit. Still working on the tutorial tonight.
>
> 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: Chad H <chadbh74 at hotmail.com>
> To: 'CoCoList for Color Computer Enthusiasts' <coco at maltedmedia.com>
> Sent: Mon, Sep 23, 2013 1:02 am
> Subject: Re: [Coco] DriveWire 4 - Turbo Mode + ROM *SOLVED!*
>
>
> P.S.  #$%@! This thing is fast now!  Did DSKINI in 20 seconds by
> stopwatch....simply awesome.
>
> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
> Behalf Of Chad H
> Sent: Sunday, September 22, 2013 11:49 PM
> To: 'CoCoList for Color Computer Enthusiasts'
> Subject: Re: [Coco] DriveWire 4 - Turbo Mode + ROM *SOLVED!*
>
> Ok, with have verified both the .BIN and the .ROM variants of the DW4 ROMS
> in the Toolshed Snapshot are indeed operational (atleast CoCo 2 versions
> anyways).
>
> Some critical (i.e. made the difference!)  points I learned...
>
> *  Changes to the DriveWire 4 configuration do NOT necessarily take effect
> after "writing to server" completes.  Should exit the server application and
> re-launch it in order to make sure settings are in effect.
>
> *  If you are making changes to DriveWire 4, particularly with the
> "DetectDATurbo=True" option, you need to power-down the CoCO unit as well!!!
> I was not doing this before and kept getting errors.  Apparently the CoCo
> does some sort of 'initialization' at bootup (just before the OK prompt
> shows).  Its at this time DriveWire 4 kicks in and says the following...
> Sun Sep 22 2013 23:35:14.218  INFO   DWProtocolHandler   dwproto-0-9
> Detected switch to 230k mode
>
> Yes, you read that right, "230k mode".  I thought I had read that the CoCo 2
> was only doing 115k and that the CoCo3 was doing 230k.  Maybe its just a
> standard status message that really just means "double-speed"?  I don't
> know.  Also, as Ken pointed out, the base serial bit rate is set at "57600".
> It's the CoCo Boot sequence in the Turbo ROM, coupled with the
> "DetectDATurbo=True" setting in the DW4 configuration that makes the magic
> happen
>
> Hopefully these keypoints and others will be incorporated into the "Starter
> Kit" Bill is working on.  Thanks all!  Time to crash now, mission
> accomplished.....
>
> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
> Behalf Of Chad H
> Sent: Sunday, September 22, 2013 10:06 PM
> To: 'CoCoList for Color Computer Enthusiasts'
> Subject: Re: [Coco] DriveWire 4 - Turbo Mode + ROM
>
> Err.. D'oh (Home Simpson)
>
> That explains that.  Must have gotten crosseyed from trying to solve this.
> Will advise when my UV eraser cycles and I'm able to reflash.. Thanks Gene
>
> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
> Behalf Of Gene Heskett
> Sent: Sunday, September 22, 2013 9:58 PM
> To: coco at maltedmedia.com
> Subject: Re: [Coco] DriveWire 4 - Turbo Mode + ROM
>
> On Sunday 22 September 2013 22:43:55 Chad H did opine:
>
>> OK I felt like Chris' thread had been hijacked a bit so I started a new
>> one specifically for this issue.
>>
>>
>>
>> I got DriveWire 4 up and running on a XP box, the Drivewire 3 ROM runs
>> fine.
>>
>>
>>
>> Using the DriveWire 4 ROM from here..
>> http://toolshed.sourceforge.net/snapshots/  it doesn't work no matter
>> what I set in the server configuration, always errors.  I did short
>> pins 1 and 2 and verified with multimeter.
>>
>>
>>
>> I had been used a PORT'd .BIN of the rom that was being LOADM > EXEC.  I
>> then went back and flashed a EPROM with the .ROM file and it wouldn't
>> even boot..blank screen.   Wondering what was up with that, I started
>> eyeing the Hex codes in my Flash editor and found something out of
>> whack, or atleast it seems to me.  All "good" ROMs I've encountered,
>> even the DW3 ROMS hosted on the Cloud-9 site, begin with the same
>> sequence.
>>
>>
>>
>> 44 4B 20 08 D7 5F 00 . and so on.  None of the roms in the above
>> Toolshed snapshot archive follow this pattern!  Even the DW3 ROMs in it
>> are different.  They begin with
>>
>> 00 20 30 4F D0 . and so on.  What gives?
>
> You are not looking at a *.rom file then.  I think thats a .bin file.
> There are many others in that directory.  They are correct in my build
> here, built from an hg clone in mid july.  No clue whats happened to the
> main toolshed repo since though.
>
> According to the files on the above site, toolshed-2.0 hasn't been touched
> since 2010/04/04...
>
> Frankly I find that very hard to believe, bordering on incredible.  What
> the (expletive deleted) is going on here?
>
> So fess up folks, just where IS the CURRENT, uptodate  toolshed-2.0
> repository?
>
> Cheers, Gene
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
>
> Real programs don't eat cache.
> A pen in the hand of this president is far more
> dangerous than 200 million guns in the hands of
>          law-abiding citizens.
>
> --
> 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
>
>
> --
> 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