KryoFlux^® Support Forums

There are a couple of problems here: First, PC 360k drives usually can't handle GCR. Second, the Kryoflux can not write disk images that are not index aligned. (Anything written natively by a C64 will not be index aligned) Third, I believe that the Kryoflux will force double stepping, and therefore ...

First of all "speed problems" reported by DTC have to do with the spindle motor. The linked thread has to do with the head step rate. Totally different things. There are a number of different possibilities: 1: There is "gunk" on the cookie surface, increasing friction between the...

That attched screen shot show a disk with 80 tracks, not 40 tracks. So what disk was that? Double check with a known good double sided 5.25" disk of the same density and see if you get the same results. Could you post a Preservation Stream disk dump? That might help give some extra clues what i...

Could you post the disk dump?

A mistmatch error would suggest a different sector size. That is typical when encoding differs.

The program (boom.exe) appeared to run and work in PCE when I ran it directly from the a: drive.

Although, when I tried to run the installer it complained that it was not the install disk.

The sectors on track 40 are FM encoded, and therefore can not be used by anything on a normal IBM PC. If you really wanted them in a PSI image, you would tell the PCE tools to decode track 40 by itself, as FM encoding rather than MFM and then merge the resulting PSI image with the existing PSI image...

PCE does not emulate a PCJr or Tandy 1000. Only a PC and XT. I believe this disk would also freeze on a genuine PC or XT because it is expecting a PCJr. mr.vince, The PSI format used by PCE is a sector format. That means overlapping sectors are separated out in to individual sectors. The number of s...

This decodes fine to mfm sector image with 40 tracks, 10 sectors , 512 byte. But the last 6 tracks on side 2 are missing or not formatted! Actually, they are formatted and contain the same blank data. They appear to decode OK with the PCE tools and the Kryoflux software. There is just some noise or...

In this case, it would be a good bet to start with a Preservation Stream File. That just records all of the raw signal from the drive. You can feed it back to the Kryoflux software or other tools later to decode a usable disk image using one of the other profiles. The nice thing about this is you do...

First of all, IDE does not give access to flux-level information. It is all abstacted away behdind an I/O bus that recieves commands and hands you blocks of data. Earlier "MFM"/"RLL" hard drives were a different story. Most IDE to USB interfaces require LBA addressing instead of ...