KryoFlux Support Forums

This is far from complete and also contains some errors. A lot of details also missing. If you have better information, please just let me know. I don't have the time to check every title or submission extensively. Why do you think I am asking for it here, where I know someone have technical detail...

SLC wrote: ↑Thu Dec 24, 2020 3:01 pm This is far from complete and also contains some errors. A lot of details also missing.

If you have better information, please just let me know. I don't have the time to check every title or submission extensively.

A lot of times the disk is either detected as the wrong size or has protection on it (or just bad areas). Both of these conditions make basically a blank IMG file, or one that WinImage or other programs can't detect.

They are much closer together in coercivity than 5.25 media, but it is not the same and can be unreliable. The physical disk is actually half the thickness as well. I've heard people claim that HD disks are "higher quality" and you should write DD data on them because it will actually be m...

Specialized hardware designed for that specific platform will always be ahead in features. KF can image the disk, but conversion to other formats has to be written by someone.

No, it is not offset. It is directly over the other head... 99.9% positive, although I haven't looked at it in years.

I recently discovered one of my rescue 5.25" drives is an old 40-track (41, actually). Thinking I could adjust the DTC parameters to write out disks for old 35/40 track media, I tried to do it, but could not end up with readable disks. Is it possible to write out an 84-track G64 file on a 40-tr...

These images do have track 18 where normally track 17 is located, so they are misaligned or offset by one track. I have modified nibconv so that it looks at what track it found when it tries to read track 18, so if it sees another track instead in the headers, it figures out how far off it is and ex...

Are we talking about disk images where there is some alignment problem and track 18 is not on track 18, but stepped off a half or whole track in one direction? That's a data problem, not a tool problem. I mean unless this is mastered this way on purpose with a drive that is out of alignment?

Ignore the -c2 detection, forget about it. You can't override it, and it doesn't matter!

Just read the disk as you normally would with -e77, or are you saying it will not let you even read past 41?