David Given

The 'bad USB reply' error usually means that the device and the computer have got out of sync. I still haven't figured out a way to reset them in software;...

I've just rebuilt everything, bumped the protocol number (so as to prevent client/device mismatches) and pushed the new release. It sounds like you're seeing something else going wrong, but in...

Ah! I know what's going on! I'm sorry, I should have realised this earlier... I bet the BBC drive _has no index sensor_. Many 8-bit floppy drives didn't. FluxEngine relies...

I've just pushed a change --- a new release will show up on github in a few minutes. Now you can add `--index-source=1` for fake 300RPM index pulses or `2`...

That sounds like the drive is jumpered to respond to drive #0. PC drives should be set to respond to drive #1, both of them, and the twist in the...

@ch0mik That sounds like a different issue (as it's a normal PC drive) --- could you open a different bug?

I'm sorry, I thought I'd replied to this. Spinning the motor but not stepping the heads is exactly the symptoms seem if the drive is configured internally to be on...

You either have to specify _all_ the flags, or apply a preset: ``` ./fluxengine write ibm --ibm-preset-720 -i disk1.img -d :t=0-79x2 --ibm-track-length-ms=166 ``` Note that 360kB disks aren't supported yet;...

It looks like the OSX serial driver is claiming the device, preventing the FluxEngine client from accessing it: https://medium.com/@kondal.kolipaka/error-libusb-claim-interface-failed-with-libusb-error-access-c85708c5f43

I'm afraid this is well beyond my knowledge of OSX. The issue here is that the GW exposes a serial device, which the OS is claiming, and that's preventing the...