How does ImageDisk develop its list of sector
numbers?
I ask because it seems to think this stiffy has 70 tracks, with 17
sectors per track, with the sectors numbered 0, 11, 6, 1, 12, 7,
2, 13, 8, 3, 14, 9, 4, 15, 10, 5, 17 on the even tracks and 8, 3, 14,
9, 4, 15, 10, 5, 0, 11, 6, 1, 12, 7, 2, 13, 17 on the odd tracks.
(These derived from IMDU output after a run.)
With interleave set to "As original", ImageDisk will wait for a sector index
pulse, then begin reading sector ID fields and storing them until another
sector index pulse occurs.
It would appear that you disks are interleaved 3:!, and that the interleave
is offset by 1/2 revolution on the odd tracks (not all that uncommon - it
means that the disk has 1/2 revolution to step before it has to wait for
the next revolution. This can make disks noticably faster to read when
reading sequential tracks. If you like, you can set interleave to "Best
Guess" which will regenerate the calculated interleave from the first sector
on each track. You can also pick an interleave if you want to change it.,
however either of these choices would likely result in disks which are
slower to access than your original.
Read into C:\FRANK\WORK\V2B.IMD
Interex CSL/150 volume 2 from master
0/0: Unable to determine interleave
: 250k DD - 17 sectors of 256 bytes - G1:24 G2:37
: Read error <17> NoSector - Reanalyzing
: Unable to determine interleave
: Read error <17> NoSector - Unavailable
0/1: Single-sided
4/0: Unable to determine interleave
0/0: Single-step
1/0: Unable to determine interleave
: Read error <17> NoSector - Reanalyzing
: Unable to determine interleave
: Read error <17> NoSector - Unavailable
It continues much like this through subsequent tracks (gronk, gronk),
which takes a while, but this may be what I get for asking it to do a
full analysis.
When it says "unable to determine interleave", it means that it could
not read the sector id's reliably in the same order on multiple attempts.
Imagedisk will read the disk for several revolutions, storing any new
sector IDs that it finds. If it figures out that it is not seeing all of the
sector IDs on each revolution, it generates this message. Most likelt
the disk is marginal to read with the PC controller.
Full analysis will cause it to perform quite slowly as it reanalyzes the
disk "from scratch" on every track. Full analysis is very rarely
required.
It would appear that your PC controller is unable to read the last sector
on the disk (17) - also not uncommon, many systems use gaps etc. in
their formats which are outside the tolerances of the PC controller. The
good news is that PC's vary widely, and you will likely find that another
machine may read the whole disk, or it may be able read different sectors
(in which case you can use IMDU to merge the two images to get a
complete one). Out of a dozen or so machines that I tested ImageDisk
with, only a couple of them were able to read all of the disks I've been
able to make work. I've also found that slowing the drive a bit can help
with some of these. See the notes in the document and in the online help.
Yes, I should probably sit down and read the manual a
bit before
charging in like this.
Yes, please do - I have also provided fairly extensive online help at
the touch of the F1 button. Spend some time with it, as there is a lot
of information there, and you will not get the most out of ImageDisk
if you do not understand it. I designed ImageDisk to allow me to
archive disks that I had trouble with by other means, and it has a
lot of fairly technical options - it is not a "click OK" type program.
-- A general note to everyone about ImageDisk "support" --
In one of my "day jobs", I produce and sell development tools for
various small/embedded processors - 80+% of my technical support
consists of cutting and pasting pages from the documentation and
sending it back to people. In most cases, it's obvious that they have
not even "cracked the cover" of the manual, since several of the most
common questions are answered on the first page.
Since ImageDisk is being made available as free software, I am not
going to be overly inclined to do this on an ongong basis for it. I know
nothing can overcome he urge to fire up a new toy "right away' (I do it!),
however when doing so brings questions, please refer to the
documentaion and help files (in detail) before coming to me.
Also note that there are *MANY* disk formats which cannot be read by
the PC floppy controller. If ImageDisk just can't seen to digest your favorite
systems disks (or even your less favorite ones) - there's not much point
coming to me about it, as chances are that it simply is not possible.
For other issues, reasonable suggestions, legimate bugs etc. I am here and
am happy to help.
Regards,
Dave
Regards,
Dave
--
dave04a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools:
www.dunfield.com
com Collector of vintage computing equipment:
http://www.parse.com/~ddunfield/museum/index.html