Catweasel (MK3) floppy controller question..

[Patrick Finnegan]

I figure this might be a decent place to ask..

Does anyone know of a program I can use (preferably under Linux, but DOS 
would probably work as well) to read a flux-transition level image off a 
disk using a catweasel card?  I'm trying to read some 2.4MB (5.25") 
floppies from an IBM 3174 controller (using an 2.4MB floppy drive), and 
am able to read in 1.2MB floppies using cw2dmk just fine, but it doesn't 
do so well at processing the (aparently) mixed-density floppy I've been 
screwing with since yesterday.  Using the "testhist" program included 
with cw2dmk, I can get information about the "unreadable" tracks, but 
cw2dmk won't process them. I'm trying to make a backup image of a disk 
so that I'm not screwed when the disk stops being readable...

For those interested, it appears that "2.4MB" floppy drives are 96 TPI 
just like 5.25" DS/HD drives, but they support a higher bit rate.  
Here's what testhist tells me for a "normal" HD track:

mii-300:/usr/src/cw2dmk-3.4# ./testhist 0 0 0 1 2
Reading track 0, side 1...
  0: 000000 000000 000000 000000 000000 000000 000000 000000
  8: 000000 000000 000000 000000 000000 000000 000003 000001
 16: 000008 000005 000002 000005 000012 000006 000010 000479
 24: 003590 012073 083091 150788 000112 000013 000004 000004
<snip>
peak 0: mean 26.52101, sd 0.67534
peak 1: mean 41.56100, sd 1.04145
peak 2: mean 55.25931, sd 0.90741
drive speed approx    360.943152 RPM
MFM data clock approx 510.486128 kHz

And for a higher density "2.4MB" track:

mii-300:/usr/src/cw2dmk-3.4# ./testhist 0 0 1 1 2
Reading track 1, side 1...
  0: 000000 000000 000000 000000 000000 000000 000000 000000
  8: 000000 000000 000000 000000 000000 000000 000324 000605
 16: 000579 000472 006881 107754 120911 001047 000736 000639
 24: 000743 000819 000079 000019 000003 000005 000000 000006
<snip>
peak 0: mean 19.51057, sd 0.82054
peak 1: mean 33.65562, sd 1.27275
peak 2: mean 48.29739, sd 0.48487
drive speed approx    374.227723 RPM
MFM data clock approx 653.668108 kHz

I don't care so much about being able to interpret the data that's there 
as much as just being able to make a duplicate of the disk which is 
acceptable to the 3174 controller when this disk bites the dust.

Pat
-- 
Purdue University ITAP/RCAC       --- http://www.rcac.purdue.edu/
The Computer Refuge               --- http://computer-refuge.org