[Coco] newb: Can I use DriveWire with my CoCo 2?

[Ken H.]

You need to set DetectDATurbo=true   at the drivewire config menu (turn
advanced config on) so that he sever will respond to the HDBDOS request to
switch to turbo mode.
Also make sure that your cable is turbo mode compatible.  Pins 1&2 on the
CoCo side should be connected.

On Monday, September 23, 2013, Chad H wrote:

> Ok, I switched to XP box and got DriveWire 4 running after having to
> install
> Java (Version 7, latest).  I created a test.dsk file and loaded my
> DriveWire
> 3 ROM and all was working well.  I then loaded the DriveWire 4 ROM in the
> Snapshop archive posted by Tormod (Thanks again) and it does boot and say
> "HDB-DOS 1.4 DW4 COCO 2" and go to OK prompt.  But all Disk ops are failing
> with ?IO ERROR, even simple DIR of the test.dsk.  Here's the DriveWire 4
> server side log of this.  Any ideas?
>
> Sun Sep 22 2013 18:45:41.359  INFO   DWProtocolHandler   dwUIcliIn-44
> requesting protocol device reset
> Sun Sep 22 2013 18:45:47.406  INFO   DWSerialDevice      dwproto-0-10
> opened serial device COM1
> Sun Sep 22 2013 18:45:49.156  WARN   DWProtocolHandler   dwproto-0-10
> UNKNOWN OPCODE: 25
> Sun Sep 22 2013 18:45:49.156  WARN   DWProtocolHandler   dwproto-0-10
> UNKNOWN OPCODE: 33 !
> Sun Sep 22 2013 18:45:49.359  WARN   DWProtocolHandler   dwproto-0-10
> Timed out reading from CoCo in OP_FASTWRITE_10
> Sun Sep 22 2013 18:45:49.359  WARN   DWProtocolHandler   dwproto-0-10
> OP_FASTWRITE_10 took 203ms.
> Sun Sep 22 2013 18:45:51.890  WARN   DWProtocolHandler   dwproto-0-10
> UNKNOWN OPCODE: 25
> Sun Sep 22 2013 18:45:51.890  WARN   DWProtocolHandler   dwproto-0-10
> UNKNOWN OPCODE: 33 !
> Sun Sep 22 2013 18:45:52.093  WARN   DWProtocolHandler   dwproto-0-10
> Timed out reading from CoCo in OP_FASTWRITE_10
> Sun Sep 22 2013 18:45:52.093  WARN   DWProtocolHandler   dwproto-0-10
> OP_FASTWRITE_10 took 203ms.
> Sun Sep 22 2013 18:45:56.890  WARN   DWProtocolHandler   dwproto-0-10
> UNKNOWN OPCODE: 29
> Sun Sep 22 2013 18:45:56.890  WARN   DWProtocolHandler   dwproto-0-10
> UNKNOWN OPCODE: 33 !
> Sun Sep 22 2013 18:45:57.093  WARN   DWProtocolHandler   dwproto-0-10
> Timed out reading from CoCo in OP_FASTWRITE_10
> Sun Sep 22 2013 18:45:57.093  WARN   DWProtocolHandler   dwproto-0-10
> OP_FASTWRITE_10 took 203ms.
>
> -----Original Message-----
> From: coco-bounces at maltedmedia.com <javascript:;> [mailto:
> coco-bounces at maltedmedia.com <javascript:;>] On
> Behalf Of Aaron Wolfe
> Sent: Sunday, September 22, 2013 11:44 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] newb: Can I use DriveWire with my CoCo 2?
>
> On Sun, Sep 22, 2013 at 11:59 AM, Chad H <chadbh74 at hotmail.com<javascript:;>>
> wrote:
> > I concur with this entirely.  I also feel what Aaron said about
> > "documentation not being fun".  While I'm not currently employed as a
> > "programmer" per say, I do make use of my skills in this area at my work
> > place not only for personal benefit but also for the benefit of
> co-workers.
> > Many of my projects there are SOLEY for their benefit in fact.  I to  do
> not
> > care for "waisting time" on documentation.  Some of those knuckleheads
> > wouldn't even read it anyways, they just come straight to me to figure
> out
> > how to do something with the applications I come up with.  It's just how
> > people are wired...they go to whatever resource is the most convenient
> and
> > helpful.   Here in the CoCo online community, people can't just call up
> or
> > talk directly to the authors, they need a good place to go to get
> > 'standardized/official' support.  Now if they take it upon themselves to
> > experiment and go outside the box to 3rd party ROM's or other mods, they
> > should seek support elsewhere on that.  It's not the responsibility of
> the
> > author to support mahem they didn't create.
> >
> > On a side note... I think I found that DriveWire 4 package is NOT
> supported
> > by Windows '98.  If it is, will someone please tell me what I'm missing.
> I
> > will describe what I've done so far.  Keep in mind DriveWire 3 already
> runs
> > fine on this machine.
> > *  Unzipped and executed DriveWire 4, got message: "Java 1.5 is required"
> > and it closed, so I researched
> >         For the lastest win'98 compatibal Java package which does seem to
> be
> > 1.5.
> > * Installed Java 1.5 (586) revision 18 and attempted to execute DW4, got
> > message: "Could not find the Main class.  Program will exit".
> >         I Googled this and found someone had some luck running it from
> the
> > command line after Java was added to the PATH so
> >         I tried that and got: Exception in thread "Main"
> > Java.Lang.UnsupportedClassVersionError
> >
> > I suspect DriveWire 4 was compiled to use a higher version of Java, which
> > Windows '98 doesn't seem to be able to run a higher version of Java.  I
> > tried installing Java 1.6 and it failed.
>
> DW4 is supposed to require only Java 1.5, but I may have broken that
> somewhere along the way.  At one point I did have it running on a
> Win9x virtual machine but that was a good while ago.  I'll see if I
> can find out more.
>
> --
> Coco mailing list
> Coco at maltedmedia.com <javascript:;>
> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com <javascript:;>
> http://five.pairlist.net/mailman/listinfo/coco
>