[Coco] NitrOS9 build errors

[Bob Devries]

Hi Tormod,

I think a combination of bits from DD.FMT (offset $10) in LSN0, that is:
bit 0 = number of sides (0=single, 1=double)
bit 1 = density (0 = single density, 1 = double density)
bit 2 = track density (0 = single (48TPI), 1 = double (96TPI)

So it should be enough to read LSN0 byte $10 to identify the disk. However, 
if the byte at $10 is not correct when the disk image was created, we have 
problems.

Regards, Bob Devries
Dalby, QLD, Australia

----- Original Message ----- 
From: "Tormod Volden" <lists.tormod at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Monday, January 20, 2014 9:33 AM
Subject: Re: [Coco] NitrOS9 build errors


> On Sun, Jan 19, 2014 at 6:56 AM, Bob Devries wrote:
>> Hi Tormod.
>>
>> One remaining small (trivial?) issue I have is with the index.html file
>> which is created in the DSKS directory, in which 80 track double-sided 
>> disks
>> are listed as 48TPI. They should be either 96TPI or 135TPI IMHO.
>
> Hi Bob, the format string is generated with "os9 id" from Toolshed.
> The documentation says it "is intended for RBF disk images only" and
> "displays information about an image from the identification sector
> (LSN 0)". From the code it seems that the disk image format byte only
> has one bit for 48/96 PI, one bit for DD/SD, and one bit for DS/SS.
>
> The index.html is created by 3rdparty/utils/aaw/mkdskindex based on
> the "os9 id" output, so maybe it has to look at the "Total sector
> size" as well and adjust the format string? What would be the most
> helpful format string? TPI or capacity in KB?
>
> Tormod
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco