1 May
2013
1 May
'13
8:58 p.m.
On 5/1/2013 8:16 PM, Dave Dunfield wrote:
If you take the time to read/understand the IMD docs
and/or help screens,
you will note that I explicitly state that IMD does not make ANY assumptions
about your drive. It simply uses the capabilities of the controller to see what it
can find "out there". The point of note here is that it supports up to the
theoretical
maximum of 255 cylinders that the 765 controller architecturally supports. So
why would it assume that your drive cannot have more than 80 physical cylinders.
It has no idea what type of drive you have.
I read the instructions and I felt I
understood them, and I understand
that IMD does not make any assumptions about the drive.
From my vantage point, I saw the first few items in the settings screen
as "tell me about your disk drive". So, I set it to 'B', 80 tracks,
because that's what I felt it was. I figured the SW would do the math
and say "Hmm, he's wants to do double stepping on a 80 track drive, I
need to pull in 40 tracks of data"
It's OK, but I'd appreciate it if you could see it from my vantage
point. I'm not ignoring your instructions, And, I agree the setting
being what it is saves a setting (my approach would require a setting to
describe the physical drive parms and another setting to describe how
many tracks I want to read/write, if less than the maximum).
Which leads to the question ... if you have TeleDisk images for the disks
you want to create, and are finding IMD unsuitable - why not use Teledisk
to recreate the disks. TeleDisk is designed to "make it easy" - it looks at
the BIOS settings to see what kind of drive it is, and makes decisions
based on that - for basic operations, it will be simpler than IMD to use.
I was
told by folks on the list to grab IMD and make the disks. I was
simply taking the advice.
Jim