MODULE TITLE - the title of the module

NUMBER OF POSITIONS - number of positions in the 1st song

NUMBER OF PATTERNS - total number of patterns in the module (songs use the same patterns)

NUMBER OF INSTRUMENTS - number of instruments in the module (empty or not)

NUMBER OF SAMPLES - number of samples in module

Global DSP - Yes means that the module use DSP of AHI. The DSP cannot be converted, so the XM module will sound totally different than the DBM version.

Version - Shows version of DigiBoosterPro which the module is made with. The converter is designed for v2.20. Newest versions could be different (but not have to)

In the list below the programs prints information about program jobs (ie. Preferences saved) and also about the convertion. In the second case the most important thing is the report of convertion report. Ie.:

Pattern: 0, line: 34, track: 8 (YF0 X02)

That means, in 34th line and 8th track of pattern 0 the DSP commands are found. These will not be converted because XM doesn't support such ones.
There will be another case, ie:

Pattern: 3, line: 56, track: 2 (930 836)

930 830 will not be converted, until the FORCE atribute will be chosen in prefs section. It's impossible to convert one of these commands in VolCMD column without some loss (look at the XM format description).

• DSP cannot be converted! - if the module has defined the global DSP

• Impossible correct conversions: - the raport about not exact or impossible conversion will be started with this one.

• Songs 2 - X will be lost - where X is the last song number

• Song X placed at position Y - where X is the song number and Y is the position in the module

• Song X placed at position Y - looped - jw., if Join Song is set to Yes looped and looping is done

• Song X placed at position Y - not looped - jw., jw., if Join Song is set to Yes looped and looping is not done

• pattern: X, line: Y, track: Z, (CMD1 CMD2) - impossible correct conversion of the commands in pattern X and line Y of channel Z

• Preferences loaded

• Preferences saved

• Wrong prefs file version. Using some defaults. - defaults will be used only for options not found in the prefs file

• There is no prefs file. Using defaults

• Module successfully converted

• Unable to save preferences file

• Logfile saved

• Unable to save logfile

• Module preloaded

• Modue analized

• This is NO DBM module - if the chosed file is not DBM module

• Wrong destination path

• Wrong source path

• Incomplete module. Conversion aborted. - if module file is broken

• Fatal error! MUI interface cannot be created - if some MUI components are missed or there is no availbable memory for opening GUI

• Fatal error! There is no available memory. Aplication closed. - if no memory is availble for correct program working

Analyze - for re-analise module data (patterns) for example after changing of COMMAND RULES

Save Log - saves the convertion report into the file in ASCII format. It contains all infos from report page (except program job notes)