[Coco] CocoDisk was: nitros-9

[Darren A.]

Bob,

Thanks for the feedback. Replacing bad/missing sectors with a fill byte 
sounds like a reasonable request, and shouldn't require very much work.

An error message stating that a sector could not be found would be 
indicative of a bad disk, or a disk that has been formatted in a 
non-standard way. For example, some copy-protection schemes will 
intentionally omit sectors, or use non-standard sector numbers (>18).

Darren

---

>From: "Bob Devries"
>Subject: Re: [Coco] CocoDisk was: nitros-9
>Date: Mon, 14 May 2007 10:02:19 +1000
>
>Darren,
>
>I have tried your CocoDisk.
>The following observations are from my brief experience:
>
>The programme quits without saving anything when it detects any sort of 
>read error. With many of my disks being aged, I would love to see the 
>programme skipping over problem sectors, and storing a known pattern in the 
>bad sector. For preference, the fill byte for a bad sector should be user 
>selectable; that way, it can be made, say, $E5 for RSDOS, and $FF for OS9 
>(yeah, I know, that is the reverse of what is used for blank sectors... 
>That's the idea!)
>
>I also was not able to get it to write a (MESS) image onto the disk without 
>error. It may have been a bad disk; I'll need to experiment some more. BTW, 
>at this time, I'm using 3.5" disks, as that is all I have in this Windoze 
>box. The error given was that your programme could not find the required 
>sector.
>
>Hope that helps.
>--
>Regards, Bob Devries, Dalby, Queensland, Australia

_________________________________________________________________
Like the way Microsoft Office Outlook works? You’ll love Windows Live 
Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_outlook_0507