Hi Michael,
So I use fdrawcmd, feeding in the track/head/sector number. I wrote a script which issues fdrawcmd for each track, reading 18*256 bytes.
./fdrawcmd read $PHEAD $TRACK $LHEAD 0 1 18 0x1b 0xff length=4608 rate=1 track=$((TRACK*2)) >> out.dsk
One problem, though: For each track, the drive seems to seek in and out, which heavily slows down loading. That is, instead of stepping to the next track, it seems as it if steps back to track 0 and then forward to the next track. What can I do to prevent this?
It's been a long time since I did this, but you're right, it does step from track zero every time. http://inputplus.co.uk/ralph/#adfs covers where you've got to and then goes onto mention LibDsk; perhaps that'll be useful to you. Cheers, Ralph.