[Coco] CoCoSDC question: default .DSK size?

[Allen Huffman]

> On Dec 17, 2014, at 1:31 PM, Darren A <mechacoco at gmail.com> wrote:
>> I see -- CoCoSDC uses this header to know how big the disk is.  What is in
>> that header when I use ",NEW" to make a new disk image from CoCoSDC DOS?
> 
> Using ",NEW" creates an image without a header. The initial size of the
> image is that of a 35 track single-sided floppy.
> 
> The only information obtained from the header is the number of sides. When
> no header is present, the CoCo SDC makes assumptions about the disk
> geometry based on the file size. The "Disk Image Formats" page on the blog
> has a table showing how the size is interpreted.

Excellent - I was using that table earlier for a series of articles I am putting together for my Sub-Etha blog as I dig in to this new toy.

What about using ",NEW+"?

Also, I have a ton of RGB-DOS disk images on an SCSI hard drive. I forget if I ever cloned it to a CompactFlash card for my SuperIDE interface, but possibly. I expect the only way I am going to be able to transfer those over on CoCo hardware would be to back each RGB-DOS drive to a floppy, then swap the controller over to CoCoSDC and back the floppy to a CoCoSDC disk.

I plan to be putting together a series of programs and articles on how someone could use the CoCoSDC to try to archive all their old physical CoCo software (disks, hard drives, etc.) to something modern. It should be a fun learning experience.

		-- A