Track reading (Sedoric / FDC)

Anything related to the tools Tap2Wav, Tap2CD, Tap2Dsk, Sedoric Disc Manager, Tape Header Creator, WriteDsk, and generaly speaking tools related to the management of Oric data files and devices.
christian
Pilot Officer
Posts: 84
Joined: Sun Nov 24, 2013 9:58 pm

Re: Track reading (Sedoric / FDC)

Post by christian »

Unlike Sedoric, there is no information stored on the disk because FTDOS does not permit to adjust the disk geometry.
So the format is always: 2 sides x 41 tracks x 17 sectors x 256 bytes. (with Jasmin 2)

User avatar
Symoon
Archivist
Posts: 1899
Joined: Sat Jan 14, 2006 12:44 am
Location: Paris, France
Contact:

Re: Track reading (Sedoric / FDC)

Post by Symoon »

Hey thanks a lot, very valuable information ;)

User avatar
Symoon
Archivist
Posts: 1899
Joined: Sat Jan 14, 2006 12:44 am
Location: Paris, France
Contact:

Re: Track reading (Sedoric / FDC)

Post by Symoon »

Interestingly, Omniflop lists 4 different formats for Jasmin:
40x17 340kB
41x17 348.5kB
42x17 357kB
They have been provided by Chloé so I suspect I should ask for details on the other forum!

User avatar
iss
Wing Commander
Posts: 1128
Joined: Sat Apr 03, 2010 5:43 pm
Location: Bulgaria
Contact:

Re: Track reading (Sedoric / FDC)

Post by iss »

This is from Jasmin manual, not very informative...
jas-man.png

User avatar
Symoon
Archivist
Posts: 1899
Joined: Sat Jan 14, 2006 12:44 am
Location: Paris, France
Contact:

Re: Track reading (Sedoric / FDC)

Post by Symoon »

Thanks. I suspect the differences are with the user available tracks (would the system be present on the disk or not).
Or maybe small differences betwenn the (apparently) many different FTDOS versions.

User avatar
Symoon
Archivist
Posts: 1899
Joined: Sat Jan 14, 2006 12:44 am
Location: Paris, France
Contact:

Re: Track reading (Sedoric / FDC)

Post by Symoon »

One mystery solved: the Nibble manual explains how it deals with track mode.
It actually reads the whole track first, keeping in memory each of the sectors ID positions. Then it reads each sector, and puts them in place of the ones that were read in track mode... "Because of the bad quality of track reading".

That's how there are much less $C2 in Nibble "track+sector" reading ;)

User avatar
iss
Wing Commander
Posts: 1128
Joined: Sat Apr 03, 2010 5:43 pm
Location: Bulgaria
Contact:

Re: Track reading (Sedoric / FDC)

Post by iss »

This makes sense - first to use whole track reading just to get the "description" of the track (i.e. number of sectors and their size) and then to read every sector individually. Very interesting! :)

ThomH
Flying Officer
Posts: 222
Joined: Thu Oct 13, 2016 9:55 pm

Re: Track reading (Sedoric / FDC)

Post by ThomH »

I've just discovered possibly the most egregious of false sync situations:

On track 41, the ID mark for any normally-written floppy will be [sync] A1 * 3, FB 29. The final nine bits of that sequence are 000101001, which MFM encodes to: 01 01 00 10 00 10 01 00 1x, i.e. the C2 sync followed by 00 1x.

So a read track is essentially guaranteed always to lose synchronisation when reading addresses on track 41.

Post Reply