David Given

Yeah, that comment was supposed to be on a different bug... anyway, thanks for testing! Re the proposed detection logic: I think I understand how it's supposed to work now...

Wow, thanks! That's a really serious bug which I've noticed when writing disks, and I thought this was to do with the writer code... and it's not. The flux files...

Actually, I'm not sure that _is_ the problem I'm seeing, but it is indeed _a_ problem. What's happening is that sector 13.00.06 is bad. The sampling just happens to cut...

Unfortunately this doesn't solve the different between images 1 and 2. There are two bad bits, but unfortunately they're both in the same sector and cause a 0x15 to be...

I've merged the simple fix --- try release 389. This will fix image 3 but not the other two. As a workaround, crank up --revolutions to 2 or 3 and...

Whoops, completely forgot about this. I had a look at the two flux files, using the current head of git --- they both decoded fine with ./fluxengine read amiga. I...

The spec doesn't say how the varying number of sectors per track are handled. If it's storing 800kB of data for an 800kB disk then it can't be as simple...

What order is that, though? CHS, HCS, CSH... I'd be happier with a bit more specification here. But yes, the format looks nigh-trivial and should be easily supportable.

Thanks! But should that last line read C4 H1 S1?

Do you know of any Linux tools which will validate a DiskCopy image --- in particular, check the checksum?