eharmon
Well-known member
I've been using my Greaseweazel to read 720k and 1.44mb IBM floppies and Amiga 880k floppies successfully, but 800k Mac floppies seem to be failing.
Obviously they're GCR which normally causes problems, but if I understand the docs correctly, the flux image is read at sufficient rate you can piece back together the data from the flux image on the computer side.
If I ask the Greaseweazel to verify the read I get the following:
If I don't, it reads, but tools like HxC can't make any sense of it either.
Some posts indicate that PC drives sometimes damage the flux data stream for GCRs, but this feels like more of a rumor than something concrete. That said, I can't really find any information on this drive, an Alps DF354H914C, so...maybe?
Or am I just doing something wrong?
Obviously they're GCR which normally causes problems, but if I understand the docs correctly, the flux image is read at sufficient rate you can piece back together the data from the flux image on the computer side.
If I ask the Greaseweazel to verify the read I get the following:
Code:
$ gw read --format mac.800 /tmp/test.scp
Reading c=0-79:h=0-1 revs=1.3
Format mac.800
T0.0: Ignoring unexpected sector C:1 H:0 R:3 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:9 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:4 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:10 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:5 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:11 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:0 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:6 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:1 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:7 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:2 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:8 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:3 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:9 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:4 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:3 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:9 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:4 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:10 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:5 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:11 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:0 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:6 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:1 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:7 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:2 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:8 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:3 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:9 F:0x22
T0.0: Ignoring unexpected sector C:1 H:0 R:4 F:0x22
T0.0: Macintosh GCR (0/12 sectors) from Raw Flux (65377 flux in 259.10ms)
.....a bunch of retries....
T0.0: Giving up: 12 sectors missing
If I don't, it reads, but tools like HxC can't make any sense of it either.
Some posts indicate that PC drives sometimes damage the flux data stream for GCRs, but this feels like more of a rumor than something concrete. That said, I can't really find any information on this drive, an Alps DF354H914C, so...maybe?
Or am I just doing something wrong?