FozzTexx

I'm using FluxEngine hardware.

Doesn't seem like it works any better. H.SS 01234567890123456789012345678901234567890123456789012345678901234567890123456789 0. 0 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXBXBBXXXBBBBBBBXB 0. 1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX?B??XXXBBBBBBBXX 0. 2 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX?B?X?XXBBBBBXBXX 0. 3 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXBXXBXXBXBBXXXXX 0. 4 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXBXBXXXXBBBXBXXXX 0. 5 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 0. 6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX?XXXXXXXXBXXX...

I'm not using a GreaseWeazle, I'm using a FluxEngine.

Same drive, same cable. I just unplug it from the SCP and plug it into the FluxEngine. Output voltages: Both drives deselected Logic 1 / 0: 0.49V / 5.00V Drive...

Confirmed with the multimeter that all the grounds are tied to GND on the FluxEngine PCB. I did another rawread with `fluxengine rawread -d v9k-msdos-125b.flux --flux_source.drive.high_density=0` and the results aren't...

If there are electrical problems, why does the drive work fine in my PC and why does it work fine with my SuperCard Pro? It's a Sankyo YD-380 type 1711.

I am working from the master branch. The dev tag is just a tag, not a branch, and dev points to a commit from 2021 May 8. I just downloaded...

> However, I don't have one and so I'd have to do it blind. Given that something appears to be wrong with your FluxEngine hardware, would you be interested in...

@pauldevine Yes, mame has a bug that the disk image needs to be one sector short. However that isn't the issue at hand here. The problem is that the fluxengine...

@drdpj If you look at the thread the problem with reading is there even with MFM encoded disks. When using the SuperCard Pro with the same drive it is able...