David Given

Could you try `fluxengine test voltages` with both drives plugged in, and then just the 3.5", and then just the 5.25"? Also try reads that way. I've seen oddities with...

Honestly, that looks pretty normal. Any luck trying a read with just one drive attached?

It might be possible to recover this by using a drive which can microstep and reading the disk at 1/10th of a track intervals but I don't know of any...

What command are you using? The fact that it's saying it's read only 64 bytes is highly suspicious. That shouldn't be possible. It suggests that it's failing to read data...

Hello! Sorry about the delay... The flux image looks like almost completely standard DSDD IBM scheme disks --- the only difference between them and 720kB PC disks is the start...

That's very kind of you, but I suspect it's probably not worth it --- the main point of the project is to use an off-the-shelf development board rather than needing...

The bytecode format uses a 5-bit time field with the top two bits of the byte indicating the event type. Intervals greater than 63 ticks don't fit in the time...

I haven't touched the filesystem side of things, TBH. I have experimented a bit with FAT BPBs for another project and the disks are addressed internally by block number, rather...

I have never seen that message before --- but I haven't tried this on W7... There is, however, a very similar error message that appears on Linux if you run...

No, FluxEngine's not suitable for that --- it transfers entire tracks at a time and then decodes them offline. You're unlikely to have much luck with USB drives, or IDE...