[Coco] DW4 with CoCo 2

[Mike Rowen]

This is my first time using it under DECB like this. Booting NitrOS9 through DW4 seems to behave differently, but it's using specific device descriptors without conflict between physical and virtual drives.

DW4 is an amazing product. The latest documentation is quite good. Thanks for your continuous effort.

Cheers,
-Mike


On Mar 13, 2012, at 1:23 AM, Aaron Wolfe <aawolfe at gmail.com> wrote:

> Believe it or not, the default, "non hdbdos mode" behavior is actually
> normal, and how DW3 and previous versions work.
> It through me for a loop too when writing DW4, but I kept it that way
> for compatibility.
> 
> On Mon, Mar 12, 2012 at 10:45 PM, Mike Rowen <mike at bcmr3.net> wrote:
>> Just to confirm, I have it working as desired now. I set the HDBDOSmode to
>> true under Advanced Settings and now the drives behave like typical floppy
>> disks. Thanks.
>> 
>> Cheers,
>> -Mike
>> 
>> On Mon, Mar 12, 2012 at 10:04 PM, Bruce W. Calkins <
>> brucewcalkins at charter.net> wrote:
>> 
>>> To shift primary drive access you need the command DRIVE # on the CoCo
>>> otherwise the default is drive 0.  Also many disk programs were coded for
>>> drive 0 and will not run while mounted in another drive.
>>> 
>>> Bruce W.
>>> 
>>> 
>>>  ----- Original Message -----
>>>  From: Mike Rowen
>>> 
>>> 
>>>  I'm having an odd issue with DW4 and a CoCo 2. Just wondering what I'm
>>>  doing wrong.
>>> 
>>>  The CoCo 2 comes up with DECB 1.1 (FD-501 in the cart slot).
>>>  I'm loading hdbdos for the CC2 via cassette and audio file from the PC.
>>>  HDB-DOS 1.2 DW3 COCO 2 appears on the CoCo screen after EXEC.
>>>  I mount fahrfall.dsk in drive 0 via the GUI and directory works great from
>>>  the CoCo2.
>>>  I unmount that disk and move it to DW4 drive 1 and issue DIR 1 from the
>>>  CoCo2.
>>>  I then get I/O error from the CoCo 2. The server tab on the DW4 GUI has
>>> the
>>>  following error:
>>> 
>>> 
>>>  Mon Mar 12 2012 21:50:08.425  WARN   DWProtocolHandler
>>>  dwproto-0-11        DoOP_READEX: No disk in drive 0
>>> 
>>>  So DW4 is acting like its still looking in drive 0 instead of 1.
>>>  Stranger still, I mount a another disk in drive 0. I can then get a DIR of
>>>  drive 0 ok. If I do a DIR 1, instead of an I/O error,
>>>  I now get a blank line followed by DRIVE=1    FREE=0, but no directory
>>>  information.
>>> 
>>>  The configuration within DW4 looks correct for a CoCo2, what am I missing
>>>  here? Any help appreciated.
>>> 
>>>  Cheers,
>>>  -Mike Rowen
>>> 
>>>   --
>>>  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