[Coco] dw 3

[Joel Ewy]

This sounds good to me.  Having to use a floppy disk to copy between 
virtual hard drive images (DRIVE # files) was a royal pain, and I never 
could find a RAM disk that was compatible with HDBDOS.

JCE

On 11/23/2010 06:42 PM, Aaron Wolfe wrote:
> ...
> I would propose that going forward, we load individual disks rather
> than files containing 256 disks.  This allows easier management of
> files and makes it easy to get disks in and out of the CoCo system.
>
> If that is agreeable, then the remaining issues would be to continue
> support for those who prefer the 256 disk files (already done) and to
> provide a mechanism for those who wish to transition to individual
> .dsk files to do so.
>
> This is what the utility I mentioned before would do.  It would take
> as input a large file containing 256 disks and create as output (up
> to) 256 individual .dsk files, each containing one disk image.  At the
> same time, it would create a disk set definition for these new files
> so that they can all be loaded with a single operation, effectively
> the same as mounting the original file is a single operation.
>
> It seems that supporting the .vhd files is again an example of using
> DriveWire in a less than convenient way but if someone is operating
> from such a file, I'd like to be able to support that.
> I suspect that this is not common.  How about just letting the user
> specify the offset to be used rather than trying to determine it
> automatically?
>
> Does any or all of this sound workable?
> -Aaron
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>