flux2imd

flux2imd processes Kryoflux files into an IMD file. Due to current limitations of IMD it cannot store some historic disk formats, in this case flux2imd saves a hex dump of the sectors for post analysis.

usage

flux2imd -v|-V | [-b] [-d[n]] [-f format] [-g] [-h[n]] [-p] [-s] zipfile|rawfile]+

Note ZDS disks and rawfiles force -g, as image files are not created

raw filenames should be named in the following format

[prefix] [2 digit cylinder] . [1 digit head] . raw

e.g GW500203.1.raw where the prefix is GW5002, cylinder is 3 and head is 1.

To process a whole disk, include the raw filenames for all cylinders into a single zip file. This is includes those for both heads, if a double sided disk.

Current limits for the types of disk supported are

• 2 heads, 0 or 1
• 84 cylinders. 0 - 83
• 52 sectors. Sectors should be consecutively numbered but need not start at 0.
• FM, MFM or M2FM encoding
• soft sector formats and a limited set of hard sector formats. See forcing a disk format below.
• 250kb/s or 500 kb/s transfer rate. (5¼" and 8" disks).

logged information

When processing a file, flux2imd creates a log file that is named after the input file, with .raw or .zip replaced by .log. The log file contains information about the processing and will include additional information as follows, dependent on the options selected

forcing a disk format

Normally flux2imd can determine the disk format, however for poor quality disks, it may be necessary to explicitly declare the disk format. The -f option supports this and as noted -f help shows a summary of the predefined formats and how to create a custom one. The current list is

Note ** formats will auto adapt based on detected sectors / encoding

Current predefined multi formats are

Bespoke multi formats can be created using a comma separated list of formats. A prefix is used to determine when the format applies; they are in precedence order

if there is no match then flux2imd will attempt to auto detect the format

debug options

Although flux2imd supports a level of debugging, for the non DEBUG build, -d can only be used to echo log file information to the screen, as the tool processes the data.

In the DEBUG build, the -d option takes a hex value argument, which is the sum of the options below. Most of these are primarily of interest during analysing new disk formats.

Where