David Given

Sorry for the delay --- been focused on other projects... Yes, this is a known problem. You end up with a partial command in the FluxEngine's buffer which throws everything...

That does indeed sound like a bug. You do only have one drive, right? It's not somehow picking different drives for the two commands (which is still a bug, but...

Nope, they both call the same routine on the firmware, so they should produce the same result. Clutching at straws here, but you don't have a hard-sectored disk in the...

I wonder if the drive is changing speeds based on the density pin? From 360 to 300rpm or vice versa? Although that doesn't really make much sense to me as...

I'll admit, that does look strange. It looks like a good read. I believe the Kaypro II didn't use CP/M sector skew so there shouldn't be any problems there. Just...

Hello --- sorry for the delay; I've been doing a tonne of work refactoring the sourcebase to allow writes to verify that they've worked properly. That's now done. I've added...

Hmm. You're using a 300rpm drive, aren't you? That's going to make things a little awkward as I only have a 360rpm drive, which makes all the timings different. The...

Sorry, this got dropped on the floor. Currently there are problems with 360rpm drives. You'll need to edit the format to modify the clock speed and track length --- as...

Re timing: yes, quite right. I think of them as 200ms or 166ms drives myself. Currently the formats are all set up for 200ms (for 3.5") or 166ms (for 5.25")....

I'm sorry, I gave you the wrong instructions --- I got the RPMs and track lengths the wrong way round... So: the config is written to expect a 167ms 5.25"...