Yesterday I was about to suggest that the 300Kbps/300rpm mixup might be
the problem, but I figured that it would surface eventually.
IMD does have an RPM-checking routine--I use it frequently when
modifying 2.0MB 3.5" drives to masquerade as 1.6MB ones. It ensures me
that the result will beha
* On Fri, Apr 01, 2016 at 11:41:01PM -0700, Curious Marc
wrote:
It looks like you did everything right. However I thought one
specifies interleave directly in the BIN2IMD command using the DM=3
option. I see you have DM=4 on your command line. But since you can
load the kernel that might no
On Sat, 2 Apr 2016, Seth Morabito wrote:
After doing more experimentation this morning, I've discovered that
the data mode I should have been using was 250kbps MFM, NOT 300kbps!
After changing ImageDisk to write 250kbps (and ensuring that the
300RPM "I" jumper was strapped on the FD55-GV), the im
* On Fri, Apr 01, 2016 at 11:41:01PM -0700, Curious Marc
wrote:
> It looks like you did everything right. However I thought one
> specifies interleave directly in the BIN2IMD command using the DM=3
> option. I see you have DM=4 on your command line. But since you can
> load the kernel that might
It looks like you did everything right. However I thought one specifies
interleave directly in the BIN2IMD command using the DM=3 option. I see you
have DM=4 on your command line. But since you can load the kernel that might
not be the source of your problem. Having a disk being formatted in one
