KryoFlux v2.20 (formerly 2.0b15) rel.1 release package
Major release for all platforms.
Changes since 2.0b14:
- full G64 support implemented, future versions will support more or different protection types, but basically everything that's in
it now should work as intented.
- verify for all write operations except IPF file type (needs more code to be written to handle all special cases); there are only few cases where verify will be automatically turned off, e.g. when writing weak bits for copy protection.
- it is possible to change the track distance of any image type, even when changing it is not allowed as long as the changed value is identical to the default value. This saves a little on typing; there is no need to delete this parameter from the command if only the image type changes.
dtc -m1 -ftest -i0 -y -ftest.d64 -k2 -i6 -l8
dtc -m1 -ftest -i0 -y -ftest.g64 -k2 -i22a -l8
can be used as commands to generate first a d64 file, then a g64 file with the exact same parameters. Using -k1 in the first command would still be an error, as that is an invalid track distance for a d64 image.
- Windows driver now digitally signed thanks to our friends at Cloanto.
- version bumped to 2.20 to match version of firmware used.
- behaviour of stream files has been changed. There are two types of stream files can be selected:
-i0 stream files, preservation
-i0a stream files, format guided
The format guided stream files behave exactly the same way as stream files used to be: they always require at least one additional image type defined as a "guide format" telling what and how to sample from the disk. The stream files in this case just record what was being selected by the other, guide formats.
Stream files in preservation mode behave as any other "real" image type selected; additional -i2 or other image types just to enforce preservation settings is no longer required. Adding -i2 should still work to keep compatibility with tools, scripts etc, just it's no longer useful. e.g. sampling a disk blindly with preservation settings, using dtc -f<streamname> -i0 is now possible. It is of course still useful to define real guide formats as usual, so errors could be detected etc. It is also possible to restrict the stream files recorded to specific sides, using the -g parameter and specific tracks using the -k paramater, setting those before the -i0 as usual.
-g0 -k2 -i0
every second track from side 0 only.
Note, that additional image types may add more tracks to the selected ones, as stream files always record any of the tracks that had to be sampled for any of the image types specified. The default selection of -i0 is to sample all tracks possible from both sides of the disk. It is highly recommended not to change that, unless e.g. the drive is incapable of reading side 1.
The selection of stream files in preservation mode always ensures the usage of preservation parameters, but as per above, the tracks recorded may get overriden. Notice, the user selection is the absolute minimum set of tracks that DTC would record; further formats can grow this set. The band analyser output is also slightly different if there is no guide format defined; a base is not available, as there is no other format defined to match the possible base bands against. However the recorded bands found by the analyser are still displayed as usual.
When stream files in presevation mode are used as an input device (not the KF hardware) the behaviour of the stream files slightly changes. If there is any guide format specified, the stream type does not set preservation settings; this way only tracks accessed by guide formats will have any output and usage as it would be expected by the user. If there is no guide format specified, all sides and tracks will be used according to the user defined or default settings of the preservation mode. This is useful to see the bands recorded from image files, without the need to define any guide format.
G64 writing requires G64 files with mastering information, which can be produced by DTC with image format 22a (<-i22a>). These G64 files should
work with all emulators. This functionality will later be replaced by IPF files with full mastering information as required. If a G64 is missing mastering information, you will receive a warning.
THIS FEATURE IS HIGHLY DEPENDANT ON THE 5.25" FLOPPY DRIVE USED. Many "modern" 5.25" drives don't write DD data correctly. Some can be switched into DD mode by setting jumpers or by setting pin 2 of the Shugart interface to the correct state. This state is controlled by parameter dd and setting it (e.g. <-dd1> or <-dd0>) will set the high density control line appropriately.
Both drives, your mastering drive, as well as the 1541 (or 1541II or 1571) on your C64 must be perfectly aligned. Otherwise advanced protections, like anything that has to do with half or fat tracks, will not work at all.
For more information, please do read page 29ff. of the manual.
Get all files here: http://www.kryoflux.com/#download