RM n80Z mixed format disks

[z80micro-mc]

David,

RM use mixed format disks on their 8 bit CP/M systems and on their CP/M86 systems

trk 0 16 x 128 byte FM trk 1-n 9 x 512 byte MFM

n is either 39 for 40T 48TPI disks, or 79 for 80T 96 tpi.

96 tpi drives also support pseudo 40T formats by double stepping.

A further complication is RM treats 2S drives as 2 x separate logical drives.

eg DS0.0 is drive A: DS0.1 is drive C:

and consequently labels sectors on both sides as head 0.

Formats: SD 1SSD 80k 16 x 128 byte FM sectors 40T, 1 K alloc, 64 directory entries, 3 reserved tracks DD 1SDD 166k 16 x 128 FM trk0, 9 x 512 MFM trk 1-39, 1 k alloc, 64 dir, 3 reserved tracks QD 1SQD 346k 16 x 128 FM trk0, 9 x 512 MFM trk 1-79, 2 k alloc, 128 dir, 3 reserved tracks

PSD as SD but double step on 96 TPI drive PDD as DD but double step on 96 TPI drive

Peter

[davidgiven]

This should be trivial to support, at least for reading; as always, writing is harder. For reading, try:

fluxengine read ibm --heads 0 (or --heads 1 for the other side).

Do you have a reference for the disk format I can look at?

[z80micro-mc]

David,

Information on RM formats plus Gotek FlashFloppy files attached in ff.zip. At present I can only either run 80T hfes either double step so PSD-74k, PDD-166k, 1SQD-346 k.

.img files only work on 40T controllers until Kier fixes double stepping in img.cfg.

Peter

------ Original Message ------ From: "David Given" @.> To: "davidgiven/fluxengine" @.> Cc: "z80micro-mc" @.>; "Author" @.> Sent: Sunday, 2 Jan, 22 At 14:03 Subject: Re: [davidgiven/fluxengine] RM n80Z mixed format disks (Issue #402)

This should be trivial to support, at least for reading; as always, writing is harder. For reading, try: fluxengine read ibm --heads 0 (or --heads 1 for the other side). Do you have a reference for the disk format I can look at? — Reply to this email directly, view it on GitHub https://github.com/davidgiven/fluxengine/issues/402#issuecomment-1003721068 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCK64BMXHQ6MATDGK4JISTUUBLJ5ANCNFSM5LCBILBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread.Message ID: @.***>