KryoFlux Support Forums

What exactly was the command you used to image the disk in the first place?

And you can create imagefiles from the preservation files without re-reading the disk.

The current hardsector supported DTC is also more strict about the index and gives up more quicker than the previous ones, but the would result it reporting no index signal detected instead of the no comms error.

I'd say the ready signal is not used, but it could be some signal from the drive isn't activated until the head is loaded and settled and KF somehow times out.

If that's the case there's not much to do than to see if there are any ways to configure the drive somehow differently.

Not sure off the head, but try placing the -e68 after -i4.

Could there been some change in Windows making it detect the board incorrectly when the firmware is loaded on the first use?

Is it still visible as KryoFlux Disk System after issuing dtc -c2?

If the floppies are 5.25" and HD and still readable via normal dos you might have to add -v360 before -i4, if you used command line dtc to interpret them at correct RPM.

If the drive is 5.25" the disk might not spin freely in its sleeve.

Helps detecting if a submitted dump is from a disk that was mastered using KryoFlux. And people have already been selling counterfeit originals on ebay.

What's the exact size of the .img file you need to write?

There is a way to create raw stream files from standard nonprotected DOS disk .img imagefiles using HxCFloppy software and then writing from those using KryoFlux.