[Coco] DW, My Problem, sure

[Luis Fernández]

 that happiness, I am very pleased that this next to free


--------------------------------------------------------------------------------- 
Making 
CoCoDskUtilPack V 1.0.10.zip
http://cococoding.com/cocodskutil/ Thank Aaron Wolfe
My personal blog: http://www.luis45ccs.blogspot.com
---------------------------------------------------------------------------------

> Date: Sun, 6 May 2012 23:19:22 -0400
> From: aawolfe at gmail.com
> To: coco at maltedmedia.com
> Subject: Re: [Coco] DW, My Problem, sure
> 
> The ability to view disk contents is not in DW4 yet, I haven't
> finished the interface.  I hope it will be done in the next week or so
> though
> 
> 
> On Sun, May 6, 2012 at 10:42 PM, Luis Fernández <luis46coco at hotmail.com> wrote:
> >
> > Thank Aaron
> > ok
> > and Pictureview?
> >
> >
> > ---------------------------------------------------------------------------------
> > Making
> > CoCoDskUtilPack V 1.0.10.zip
> > http://cococoding.com/cocodskutil/ Thank Aaron Wolfe
> > My personal blog: http://www.luis45ccs.blogspot.com
> > ---------------------------------------------------------------------------------
> >
> >> Date: Sun, 6 May 2012 23:05:32 -0400
> >> From: aawolfe at gmail.com
> >> To: coco at maltedmedia.com
> >> Subject: Re: [Coco] DW, My Problem, sure
> >>
> >> I will take a guess.  Lets say you insert a regular disk image into
> >> the first drive (actually drive 0), and do DIR on the CoCo:
> >>
> >> You will see the contents of the disk image.  Normal enough.
> >>
> >> Now you insert another disk image into the second drive, and do DIR 1:
> >>
> >> You see a blank disk, not the contents of the image you inserted.  Why?
> >>
> >> If this is indeed the problem, I can explain it.
> >>
> >> This is because of the way HDBDOS historically considers each "disk"
> >> to be actually a hard drive containing up to 256 disk images.
> >> When you insert a disk image into drive 0, this by default maps *all*
> >> drives on the coco to 256 slots inside that single disk image.
> >>
> >> To actually see what is inserted in "drive 1" or "drive 2", you must
> >> use the command: DRIVE # X  where X is the drive you want to see.
> >> But, for instance if you do DRIVE # 1: now DIR 0 gives you the first
> >> disk in the second drive.  It's all a bit bizarre if you're dealing
> >> with the
> >> single disk images commonly found online.
> >>
> >> If you are using DW4, you can enable "HDBDOS translation".  This will
> >> make drive X on the coco == the disk inserted in drive X in DW.
> >> For using single disk images, this makes life much simpler.
> >>
> >> Here is some documentation:
> >>
> >> http://sourceforge.net/apps/mediawiki/drivewireserver/index.php?title=Using_DriveWire#HDBDOSMode
> >>
> >>
> >>
> >> On Sun, May 6, 2012 at 10:18 PM, Luis Fernández <luis46coco at hotmail.com> wrote:
> >> >
> >> > Finally I have drivewire connected, I think I'm the last one, hehe
> >> >
> >> >
> >> >
> >> > But I have a problem
> >> >
> >> > Ok Go DIR1 any disk I put in the server
> >> >
> >> > DIR2 sees nothing ..... 255
> >> >
> >> > Any ideas?
> >> >
> >> >
> >> > ---------------------------------------------------------------------------------
> >> > Making
> >> > CoCoDskUtilPack V 1.0.10.zip
> >> > http://cococoding.com/cocodskutil/ Thank Aaron Wolfe
> >> > My personal blog: http://www.luis45ccs.blogspot.com
> >> > ---------------------------------------------------------------------------------
> >> >
> >> >
> >> > --
> >> > 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