KryoFlux Support Forums

Best method is often using isopropyl alcohol soaked q-tips to scrub the drive heads. There are special cleaning disks too if you can find one, but sometimes a dirty disk can make such a mess on the heads that the cleaning disk doesn't really work its magic. You have to remove the drive and in some c...

The old PC -solution is probably the best in this case.

I'd write protect the floppies, make sure the surface is clean, and also clean the drive head(s) as those can and will get dirty over time and can then cause damage to the disks.

Good news then.

So was the pin dirty right from the beginning?

And Munich is a bit too far from Finland.

Having two bad cables is kinda unlikely, but all bets are in.

Writing back such dumps would require them to be converted back to KF raw files in correct low level format first. Unfortunately to my knowledge no one has made such utility yet.

The greed LED flashing when you short the pins on the board connector but not when you short them from the cable would mean the cable is faulty and has no connection all the way through to the pin on the KryoFlyx.

Here's a custom firmware to test your board. KFReadTestfw.zip Rename the firmware.bin file from where you installed the KryoFlux software. Then unpack firmware.bin from this archive to the same location so this version gets loaded on the board instead of the original file. Disconnect drive(s) from y...

I'll try to come up with some solutions to try.

This does sound like the KryoFlux somehow doesn't see anything from the read line suggesting the on board buffering chip might've become faulty. Atleast a multimeter would be handy for checking if the chip is passing data through.

Since backing to track -8 works the mod is working.

And typical C64 disk only has 35 tracks so the output is correct.