KryoFlux Support Forums

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-track d...

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?

sncboom2k mods drives and also sells pre-modded ones...

See thread here: https://www.lemon64.com/forum/viewtopic ... flippy+mod

This happens to me also, but slightly differently. After imaging a number of PC disks (not sure the type matters) it will start saying that all data on side 0 is unformatted. I think the head is dirty, it is not, I clean it anyway. However, reading a disk of another type (C64 for example) shows it c...

That's really nice! I can only print small stuff with mine...

This is just for my information. I know there is a difference in coercivity for DD vs HD 5.25" media, but is there any difference between an SD and a DD disk? Is it just a certification rating only (3000bpi vs 6000bpi) or nothing at all? I have some disks that are labeled as SD, and they can be form...

Could it be that you used different density line flags for g64 and d64 encoding? With the example command line in your third posting above you used -dd0 for creating g64 files. Using -dd1 may change the output... Great question! I've tried using both -dd0 and -dd1 from the same KryoFlux stream. Eit...