Errors.HLP

Errors.HLP

This file contains the main DigImage error and warning messages. The messages are indexed by .number, where number is up to a four digit integer. The trailing letter indicates the type of error or message as summarised below:

      T   Terminal error      Shows error message then terminates
                              DigImage. This is the most extreme form
                              of error.
      F   Fatal error         Message shown in window.
                              Returns to MainMenu on exit.
                              Press key to continue.
      E   Error               Message shown in window.
                              Simulates the pressing of escape on exit.
                              Press key to continue.
      W   Warning             Message shown in window.
                              Message added to journal file.
                              Message suppressed by bit3 of
                              iDigiStatusFlags.
                              Press key to continue.
      M   Message             Message shown in window.
                              Message NOT added to journal file.
                              Message suppressed by bit3 of
                              iDigiStatusFlags.
                              Press key to continue.
      P   Prompt              Message does NOT use window.
                              Message added to journal file.
                              No key press required.
      Q   Prompt              Message does NOT use window.
                              Message NOT added to journal file.
                              No key press required.
      R   Prompt              Message does NOT use window.
                              Message NOT added to journal file.
                              Press key to continue.


Unknown warning or error

The requested warning or error message could not be located in HlpFiles\Errors.HLP.

Warning Message: New configuration parameters have been added for DigImage version 2.0 Please use CONFIGUR.EXE to set the appropriate values

There have been a number of new parameters added since your copy of DigImage was configured. You will need to run CONFIGUR in DigImage\LUTs to ensure the system is correctly set up. The following menu options should be entered in CONFIGUR:
       B  Number of buffers
       M  VDUScreen mode
       P  Printer configuration
       X  Procedure on quitting

For version 1.5, the following options required setting:

       N  Screen saver

For version 1.4, the following options required setting

       A  Addresses for frame grabber
       G  Beeps
       M  VDUScreen mode
       N  Screen saver
       P  Printer configuration

Autosave contents of all buffers ? (requires !!GRM0MBytes and takes approx !!RM1s) {!RM0}->

Selecting <Y> will cause the contents of all the current DigImage buffers to be saved in the file DigiBuff.DIG in the current directory. These buffers will be automatically restored next time you start DigImage. Note that this option requires 256K of disk space per byte and will slow loading and exiting DigImage.

Saving all image buffers...

DigImage is currently saving all the image buffers to a file.

Restoring all image buffers...

DigImage is currently restoring all the image buffers from a file.

DigImage is stopping!

DigImage is stopping and returning to DOS or Windows.

Warning Message: Frame grabber VSYNC interrupt not enabled. Some features of DigImage may not produce accurate timings.

DigImage uses the VSYNC interrupt generated by the frame grabber to generate some of its timings. If this is not enabled, then DigImage approximates the timings using the PC's 18.6Hz clock. As a result DigImage options which use VSYNC as the source of their timing may not operate correctly. To enable VSYNC, start the CONFIGUR.EXE utility in DigImage\LUTs and run the [A Addresses for frame grabber] option.

The VSYNC interrupt can not be detected. Terminating DigImage then restarting it may cure this problem. If problem persists, please check jumpers and configuration.

Terminate DigImage or Continue regardless ?

DigImage uses the VSYNC interrupt generated by the frame grabber to generate some of its timings.

DigImage may sometimes fail to grab control of this interrupt if a previous DigImage session terminated in an abnormal manner (e.g. closing the window while DigImage was still running). If this is the cause of the problem, Terminating DigImage then restarting it will make the interrupt available to DigImage.

If terminating and restarting does not cure the problem, then try restarting Windows. If the problem persists past this point, it may be that the interrupt is not setup correctly in the computer. If the interrupt is set up incorrectly, then it is possible the computer may crash and/or corrupt the hard disk. Please check the jumper settings correspond with the setting in CONFIGUR.EXE (in DigImage\LUTs). The settings may be found in [A Addresses for frame grabber] option.

If everything appears correct, then it may be that another card or mother board controller is attempting to use the same interrupt. For example, if you have two IDE controllers, the second on IRQ15 and a CDRom connected to it, then you may have a conflict even if the BIOS setting supposedly disables that controller. A suggestive symptom is that DigImage starts correctly first time after rebooting, but then refuses to start again.

Note that selecting the Continue option may cause your system to become unstable for some DigImage options.

The VSYNC interrupt appears to be working incorrectly or an incorrect field rate has been specified. Please check jumpers and configuration before running DigImage.

Terminate DigImage or Continue regardless ?

DigImage uses the VSYNC interrupt generated by the frame grabber to generate some of its timings. If this is set up incorrectly, then it is possible the computer may crash and/or corrupt the hard disk. Please check the jumper settings correspond with the setting in CONFIGUR.EXE (in DigImage\LUTs). The settings may be found in [A Addresses for frame grabber] option. If these settings are correct, the problem may be that the field rate (set by [F Fields per second]) has been specified incorrectly. This should be set to 50 for Europe and Australasia, and 60 for North America. If both these settings are correct, you may either have a clash with a different device using the same interrupt, or a problem with the computer's own real time clock.

This message may also be produced if the frame grabber card is taking the sync signal from an external source (rather than the onboard crystal) and this source is not connected or turned on.

Note that selecting the Continue option may cause your system to become unstable if the error is for some other reason..

The frame grabber is probably in use by another component of DigImage. Continue (frame grabber not used), Abort, or Start with frame grabber ?

DigImage has detected that another component of DigImage may be using the frame grabber card. The program you are trying to start may be started without frame grabber support, but many of the features may not be available.

A component of DigImage is probably in use in this directory. The frame grabber is probably in use by another component of DigImage. Abort, Continue (frame grabber not used), or Start with frame grabber ?

DigImage has detected that another component of DigImage may be using the frame grabber card and that there is a component of DigImage operating in the current directory. The program you are trying to start may be started without frame grabber support, but many of the features may not be available. Depending on how the two (or more) components are being used, there may be a conflict between the use of temporary and ancilary files.

Terminal Error Message: Aborting DigImage at user request - frame grabber not available

DigImage has been aborted because the frame grabber card is not available.

There are problems recognising VSync interrupt DigImage will try searching for VSync pulses using a different method Press <escape> to exit if program hangs

Something has gone wrong with the check on the frame rate seen by the frame grabber. It may be that the IRQ is missing, or there is a problem with the computer's real-time clock. Anyway, try again a different way.

DigImage with debugging turned on

DigImage is operating with debugging turned on via the /DEBUG switch.

The <tab> key has been detected. DigImage will be suspended unless <escape> is pressed. To resume a suspended command file, restart DigImage in original directory.

By pressing the <tab> key, any currently running command file will be suspended, the current status of DigImage saved then DigImage will terminate. The suspended command file may be started again by simply opening DigImage in the same directory.

Message: DigImage has detected a suspended command file. This file will be restarted unless <escape> is pressed.

DigImage has detected that a command file was suspended in this directory. This command file can be restarted by pressing any key other than <escape>.

DigImage paused by <scroll lock>

DigImage has been paused by pressing the <scroll lock> key. Execution will continue if any other key is pressed.

DigImage currently has control over the SVHS Video Recorder. Positional accuracy may be lost if the command file is suspended.

It is not possible to gaurenteee positional accuracy of the VTR when a command file is suspended as the VTR may time out or be manually altered by the user.

Press any key to suspend or <escape> to continue with command file...

Select the key to determine if the command file is to be suspended.

Message: Suspended command file will not be resumed.

If you do not wish to restore the buffers, press <escape> again

The user has specified not to continue with the command file which was suspended in this directory. The saved buffers will, however, be restored unless <escape> is pressed.

Continuing...

The current command file will be suspended once a suitable menu is reached...

The command file can only be suspended from a suitable DigImage menu. The suspension will be delayed until such a menu is reached.

Warning Message: No directory specified for !C directive

The !C directive requests that DigImage change to a new working directory. This warning indicates that the !C directive was given without specifying a valid directory.

Warning Message: No file specified for !E directive

The !E directive is used to erase (delete) files from disk. This warning indicates that no file name was specified.

Warning Message: Difficulty deleting file with !E

The !E directive is used to erase (delete) files from disk. This warning indicates that the requested file could not be deleted. The file may not exist, or it may have read only access. Alternatively, an incorrect path name may have been specified.

Warning Message: Unable to open requested macro output file

The requested macro output file (the file which is written to by the !W command) can not be opened. This may occurr due to a number of reasons. For example, the disk may be full, or an invalid path or file name may have been specified.

Warning Message: Unknown variable

The indicated variable is not defined for this expression.

Warning Message: Unknown variable

The indicated variable is not defined for this expression.

Warning Message: Divide by zero in expression - ignore

The indicated expression includes a divide by zero. This division is ignored.

Warning Message: Exponentation of negative number gives complex result; modulus of result used

The indicated expression includes a non-integer exponentation of a negative number (i.e. a^b with a<0 and b non-integer). The correct result of this expression would be a complex number. However, as DigImage only deals with real values, the modulus of the complex value will be returned instead (i.e. ABS(a)^b).

Warning Message: Unknown operation

The indicated operation is not known by the DigImage interpreter.

Warning Message: Unmatched ( - ignore top level of expression

The indicated expression contains an unmatched left bracket. It is not possible to complete the expression. The outer most level of the expression is ignored.

Warning Message: Null expression - set to zero

The indicated expression does not contain a valid expression. The result is set to zero.

Error Message: Jump label not found

The destination for a conditional or unconditional jump could not be found in the current command file or plot file.

Error Message: Can not open nested command file

The current command file issued a !P directive to open a nested command file. This could not be complied with as DigImage was not able to find the requested command file.

Error Message: Log expression of negative arguement

The indicated expression requires that the logarithm, base 10, of a non positive value is required.

Error Message: Natural log expression of negative arguement

The indicated expression requires that the natural logarithm of a non positive value is required.

Error Message: Unknown function type

The indicated function is not defined for the DigImage expression interpreter.

Error Message: Square root of negative number

The indicated expression requires that the square root of a negative number is required.

Message: Can not jump to label as not using a command file

DigImage can not jump to the specified label as there is no command file active. Jumps may only be used in a command file. This line will be ignored.

Unknown command file directive

The indicated directive is not known. Consult the system overview for known directives.

Warning Message: Directive unknown or illegal in plot file

The indicated directive is either not known or may not be used in a plot file. Consult the system overview and DigiPlot users guide for known directives.

Warning Message: Invalid redirection of variable

Array structures may be synthesised in the DigImage command language structure through the !!_n syntax. Whereas !!n accesses variable n, !!_n accesses the variable pointed to by !!n. Thus if !!n contains the value 12, then !!_n points to !!c (c <=> 12). This warning message is generated if the contents of !!n are negative or greater than 35, in which case !!_n does not point to a valid variable.

Warning Message: Divide by zero - ignore

The !!n/=expression syntax has been used where expression evaluates to zero. DigImage is thus requested to divide !!n by zero, an invalid operation. The division assignment will be ignored.

Warning Message: Invalid logical output buffer specified for !!C - buffer not changed.

The !!C system variable is a read/write variable reflecting the current logical output buffer. This warning indicates that an invalid buffer number was specified through a !!C:= (etc.) command. Valid buffer numbers range from 0 to the value stored in !!M.

Warning Message: Invalid video multiplexer channel specified for !!H:=...

The !!H system variable is a read/write variable returning or seeting the current DT-2859 video multiplexer channel. There are eight channels: 0 to 7. This warning indicates a value outside this range was specified.

Warning Message: Invalid logical output look up table specified for !!O:=...

The !!O system variable is a read/write variable reflecting the current logical output look up table. This warning indicates that an invalid output look up table number was requested through !!O:= (etc.).

Command file suspended until next menu

The current active command file has been suspended. It will not be restarted until a menu is next entered or re-entered, or !P is typed from the keyboard.

Command file suspended until next [Q Return to parent menu]

The current active command file has been suspended. It will not be restarted until a [Q Return to parent menu] option is seleted, or !P is typed from the keyboard.

Command file suspended until !P is typed

The current active command file has been suspended. It will not be restarted until !P is typed from the keyboard.

Message: No active command file to suspend or resume

DigImage is not currently executing a command file so it is not possible to either suspend or resume it.

Message: Can not start a command file while one is suspended. To resume suspended file, type !P

It is not possible to start a command file while there is one suspended. You must resume the current command file or terminate it before trying to start a new one.

Message: !P ignored. Can not start a command file while recording journal file

The !P request will be added to the active journal file, but it will not be executed at this stage.

Warning Message: !P ignored. Can not start a command file from within plot file. Use R plot instruction instead.

You may not start a command file from within a plot file with the !P directive. However, you may access much the same functionality by starting the same file using the R plot instruction.

Warning Message: Invalid variable number

This warning is generated as the result of a request to set the value of an invalid variable during [;ZV Set DigImage variable value(s)].

Warning Message: Invalid value for variable - ignored

This warning is generated as the result of a request to set a DigImage variable to an invalid value during [;ZV Set DigImage variable value(s)].

Error Message: Closing quote missing for string parameter

The !P call attempted to pass a string value to the nested routine. However, the closing quotes (") marking the end of the string were missing.

Warning Message: Unable to reopen Journal file

A DigImage module is in the process of being initialised as the result of chaining from a previous module. In that previous module a Journal File was opened and should be reopened to allow output to be continued by this module. This warning indicates that reopening is not possible. The most probable cause is that the disk is full.

Warning Message: Nest file read error: Local variables not properly restored

Every time a command file calls another command file, DigImage creates a nest file (NEST####.DIG) in the current working directory. On return from the called command file, DigImage uses this nest file to restart the original command file, and restore the original contents of !!0 to !!9. This warning message is generated if it is unable to recover all the data from the nest file. This may be the result of the file having been deleted, or the disk full.

Warning Message: Unable to open command file

This warning is generated if DigImage is unable to open the command file requested by [;ZF Take input from a file]. This will normally be due to the file not existing (on the specified path).

Error Message: Unable to reopen nested command file

Every time a command file calls another command file, DigImage creates a nest file (NEST####.DIG) in the current working directory. On return from the called command file, DigImage uses this nest file to restart the original command file, and restore the original contents of !!0 to !!9. This warning message is generated if it is unable to open the nest file. This may be the result of the file having been deleted, or the disk full.

Error Message: Unable to continue with parent command file

Every time a command file calls another command file, DigImage creates a nest file (NEST####.DIG) in the current working directory. On return from the called command file, DigImage uses this nest file to restart the original command file, and restore the original contents of !!0 to !!9. This warning message is generated if it is unable to restart the original command file. This may be the result of the file having been deleted, or the disk full.

Fatal Error Message: Current activity terminated at user request

The current activity is being terminated at the request of the user as the result of an error in the command file. All open files will be closed and control returned to the main menu.

Warning Message: Unable to open !{READSTR ...} file

The file specified by the !{READSTR ...} command in a command file could not be opened.

Warning Message: Not enough lines in !{READSTR ...} file

The file specified by this command does not contain the line specified by the command.

Warning Message: Invalid !{...} command

DigImage does not recognise the specified !{...} command.

Warning Message: Closing brace not found in !{...} command

The closing brace (}) was not found for a !{...} command.

Warning Message: Invalid parameters in !{READSTR ...} command

Invalid numeric parameters were found for the !{READSTR ...} command. The syntax of this command is:
       !{READSTR iLine iColumn nChars file_name}

where iLine,iColumn gives the position of the string (of length nChars) in the specified file.

Warning Message: Invalid parameters in !{LEFTSTR ...} command

Invalid numeric parameter was found for !{LEFTSTR ...} command. The syntax of this command is:
       !{LEFTSTR iLength string}

where iLength is the number of characters to be taken from the left-hand end of the string.

Warning Message: Invalid parameters in !{RIGHTSTR ...} command

Invalid numeric parameter was found for !{RIGHTSTR ...} command. The syntax of this command is:
     !{RIGHTSTR iLength string}

where iLength is the number of characters to be taken from the rightt-hand end of the string.

Warning Message: Unable to open !{READNUM ...} file

The file specified by the !{READNUM ...} command in a command file could not be opened.

Warning Message: Not enough lines in !{READNUM ...} file

The file specified by this command does not contain the line specified by the command.

Warning Message: Invalid parameters in !{READNUM ...} command

Invalid numeric parameters were found for the !{READNUM ...} command. The syntax of this command is:
       !{READNUM iLine iColumn file_name}

where iLine,iColumn gives the position of the numeric value in the the specified file.

Warning Message: Unable to read requested value from !{READNUM ...} file

The value requested by the !{READNUM ...} command could not be read as either the end of the file was reached or an invalid number was encountered on the requested line.

Warning Message: Invalid parameters in !{FILEPATH ...} command

Invalid numeric parameter was found for !{FILEPATH ...} command. The syntax of this command is:
       !{FILEPATH iComponent file_name_and_path}

where iComponent determines the part of the file name/path to be returned. iComponent <= 7 Return

       bit 0           Base file name
       bit 1           Extension
       bit 2           Directory

iComponent > 7 Return

       8               Directory (excluding rest of tree)

Warning Message: Unable to save command file return values

DigImage is unable to save the current values of the command file variables and string parameters when closing the current level of the command file. Due to this failure, the !!Pn and !Pn return value psuedo-variables will not return correct values.

Error Message: Unable to read command file return value

DigImage is unable to read a variable value saved in the CmdRetrn.DIG file (in the current directory). This failure may be because there was no nested command file to return values to the current command file (in which case the CmdRetrn.DIG file will not be created), or because of a failure while writing this file.

Warning Message: Invalid parameter or requested column not in !{NUMSTRING ...} string

The !{NUMSTRING iColumn String} expects there to be at least iColumn values in the specified String. If there are fewer values, or iColumn is not a valid integer, then this error is produced.

Warning Message: Invalid parameter in !{CHARACTER ...}

The iCharacter integer in !{CHARACTER iCharacter} or !{CHARACTER iCharacter character_list} is not valid.

Warning Message: Invalid number for !{FORMAT value format} command

The value to be output in a formatted form could not be read in by DigImage.

Warning Message: Unable to write value as specified by !{FORMAT value format}

The format specified is probably invalid.

Warning Message: Unable to open !{SEARCHFILE ...} file

The file specified by the !{SEARCHFILE ...} command in a command file could not be opened.

Warning Message: Invalid parameters in !{SEARCHFILE ...} command

Invalid numeric parameters were found for the !{SEARCHFILE ...} command. The syntax of this command is:
       !{SEARCHFILE [iLine] iColumn number file_name}

where iColumn indicates which column contains the requested number in file_name. If the optional iLine is given, then the search starts from the corresponding line in the file.

Enter value/string to be inserted

A command file error has occurred and you have elected to insert a value, string or character before the incorrect line in the command file. Enter this line here.

Enter replacement value/string

A command file error has occurred and you have elected to replace the incorrect line with the value/string entered here.

Enter alphanumeric string from keyboard

A !K string input request has been found in the current command file. Please enter the appropriate response.

Enter buffer number

A !!B buffer number input request has been found in the current command file. Please enter the required buffer number.

Invalid buffer number - try again

Only valid buffer numbers will be accepted for a !!B command file input prompt.

Enter numerical value from keyboard

A !!K numeric input request has been found in the current command file. Please enter the appropriate response.

Invalid numeric value entered - please try again

The !!K input request requires a numerical value. Please enter an appropriate response.

Enter time value (minutes:seconds or ::fields)

A !!T time input request has been found in the current command file. Please enter the appropriate response.

Invalid time value entered - try again!

The !!T input request requires a numerical (time) value. Please enter an appropriate response.

Conditional STOP found...

The comand file has been terminated as the result of a conditional STOP command.

Command file closed...

The active command file has been terminated. Control is returned to the keyboard.

DigImage command mode. Please enter Command or Comment:

DigImage has entered command mode due to either a # or ! being detected. Please complete the command or enter a blank line.

Warning Message: Unable to change to directory specified by !C

The directory specified for the !C command was not valid or does not exist.

Write macro output to what file ?

Output has been requested by the !W directive, but there is no macro output file open. Please specify the name of the file to be opened.

Warning Message: Incorrect parameters for MAP??TO? command

The MAPXYTOI, MAPXYTOJ, MAPIJTOX and MAPIJTOY commands all require two real parameters representing either x,y or i,j.

Warning Message: Must have variable values for !{EVAL val val ... key expr} command

DigImage could not find any valid numeric values. At least one must be given.

Warning Message: Buffer out of range - using buffer 0

An attempt was made to access an invalid buffer. DigImage will continue the operation using buffer 0.

Warning Message: Unable to find specified input look up table

The LUTs\Input##.LUT file associated with the requested input look up table could not be found. The multiplexed table will not be changed.

Warning Message: Unable to find specified output look up table

The LUTs\Output##.LUT file associated with the requested output look up table could not be found. The multiplexed table will not be changed.

Warning Message: Unable to find specified result look up table

The LUTs\Result##.LUT file associated with the requested output look up table could not be found. The multiplexed table will not be changed.

Warning Message: Unable to save temporary output look up table

DigImage was unable to make a copy of the current output look up table in %TMP%\SavOut.LUT. As a result it may not be possibe to resore to the current output look up table once the current operation has finished. This warning generally indicates the disk is full.

Warning Message: Unable to restore temporary output look up table

DigImage was unable to restore the previously saved output look up table from %TMP%\SavOut.LUT. This warning may indicate that the look up table was not correctly saved, the disk is full, or the required file has been deleted.

Warning Message: Unable to save temporary input look up table

DigImage was unable to make a copy of the current input look up table in %TMP%\SavInp.LUT. As a result it may not be possibe to resore to the current input look up table once the current operation has finished. This warning generally indicates the disk is full.

Warning Message: Unable to restore temporary input look up table

DigImage was unable to restore the previously saved input look up table from %TMP%\SavInp.LUT. This warning may indicate that the look up table was not correctly saved, the disk is full, or the required file has been deleted.

Warning Message: Unable to save temporary result look up table

DigImage was unable to make a copy of the current result look up table in %TMP%\SavRes.LUT. As a result it may not be possibe to resore to the current result look up table once the current operation has finished. This warning generally indicates the disk is full.

Warning Message: Unable to restore temporary result look up table

DigImage was unable to restore the previously saved input look up table from %TMP%\SavRes.LUT. This warning may indicate that the look up table was not correctly saved, the disk is full, or the required file has been deleted.

Error Message: Invalid result look up table

The requested result look up table is not known to DigImage.

Error Message: Invalid input look up table

The requested input look up table is not known to DigImage.

Fatal Error Message: Unable to find output look up tables

DigImage is not able to find the normal output look up tables in LUTs\Output##.LUT. Please check that these tables exist. If not, restore them from floppy disk. Also check that the %DIGIMAGE% environment variable is correctly specified.

Fatal Error Message: Unable to find input look up tables

DigImage is not able to find the normal input look up tables in LUTs\Input##.LUT. Please check that these tables exist. If not, restore them from floppy disk. Also check that the %DIGIMAGE% environment variable is correctly specified.

Fatal Error Message: Unable to find result look up tables

DigImage is not able to find the normal result look up tables in LUTs\Result##.LUT. Please check that these tables exist. If not, restore them from floppy disk. Also check that the %DIGIMAGE% environment variable is correctly specified.

Name of file containing results look up table ?

A user-specified results look up table is required. Please enter the name of the look up table file. A default extension of .LUT will be added if none is specified.

Name of file containing input look up table ?

A user-specified input look up table is required. Please enter the name of the look up table file. A default extension of .LUT will be added if none is specified.

Name of file containing output look up table ?

A user-specified output look up table is required. Please enter the name of the look up table file. A default extension of .LUT will be added if none is specified.

Warning Message: Video multiplexer not installed

The DT2859 video multiplexer is not installed or has not been configured using DigImage\LUTs\Configur.

Result value to be set to zero (0-511) ?

Specify the nine-bit value for the result which will be set to zero in the output buffer.

Result value to be set to 255 (0-511) ?

Specify the nine-bit value for the result which will be set to 255 in the output buffer.

Saturate or Wrap around ?

Values falling outside the 0 to 255 8-bit range may either be saturated to the limits of this range, or wrapped around into this range.

9-bit result value for next change ?

The 8-bit output image will be given a constant value for 9-bit results between the current value and that specified at this prompt.

Intensity for output image until this next change specified ?

This specifies the 8-bit intensity to be used for the output image until the 9-bit result specified at the previous prompt.

Result look up table formula as a function of the 9-bit result P ?

Specify the formula reslating the 9-bit result of the ALU combination of two buffers to give the 8-bit output image.

Wrap or Saturate if function outside 8-bit (0-255) range ?

If the specified function evaluates outside the 8-bit range, then the function may either be saturated to the limits of the 8-bit range, or wrapped (using modulo arithmetic) back into this range.

Input value to be set to zero (0-255) ?

Specify the 8-bit value for the digitised intensities which will be set to zero in the A-arm of the ALU.

Input value to be set to 255 (0-255) ?

Specify the 8-bit value for the digitised intensities which will be set to 255 in the A-arm of the ALU.

Saturate or Wrap around ?

Values falling outside the 0 to 255 8-bit range may either be saturated to the limits of this range, or wrapped around into this range.

Incoming digitised 8-bit value for next change ?

The 8-bit value passed to the A-arm of the ALU will be given a constant value for 8-bit digitised intensities between the current value and that specified at this prompt.

Intensity for A-arm of ALU until this next change specified ?

This specifies the 8-bit intensity to be used for the A-arm of the ALU until the 8-bit digitised intensity specified at the previous prompt.

Input look up table formula as a function of the 8-bit digitised P ?

Specify the formula reslating the 8-bit digitised value to that passed to the A-arm of the aritmetic logic unit (ALU).

Wrap or Saturate if function outside 8-bit (0-255) range ?

If the specified function evaluates outside the 8-bit range, then the function may either be saturated to the limits of the 8-bit range, or wrapped (using modulo arithmetic) back into this range.

Invert which buffer ?

Specify which buffer is to be inverted. The inversion takes the form of replacing the intensity P of each pixel with 255-P.

User defined LUT

A user defined output look up table has been requested.

Mask this buffer using what buffer as a mask ?

Specify the buffer containing the mask to be applied.

Positive mask, Negative mask or Quit ?

The mask may be applied as a positive (keep bits of the image corresponding to mask values of 255) or negative (keep bits of the image corresponding to mask values of 0).

Warning Message: FunctKey.HLP missing

The HlpFiles\@FuncKey.HLP file is missing. This file normally contains a brief summary of the function keys and is displayed by <ctrl><f1>. If absent, it should be reinstalled from the DigImage installation disks.

Warning Message: File handle has already been released

DigImage automatically allocates file handles when opening a file. Normally the first available file handle in the range 10 to 50 will be used. When the file is closed, DigImage records that the handle is available for use by another file. This warning is generated if there is an attempt to close the file more than once.

Warning Message: Unable to reopen Journal File after shutdown

If DigImage experiences a fatal error, untrapped error or <ctrl><break> condition, all the open files are closed. If prior to this condition a Journal File was in use, on restart DigImage attempts to reopen the Journal File and write an appropriate message to that file. This warning is generated if DigImage is unable to reopen the file sucessfully. This may be due to the disk being full, or the shut down resulting from an array writing outside its bounds.

Fatal Error Message: Unable to open menu file

DigImage is unable to open the menu file associated with the chosen activity and is thus unable to continue execution of this activity. Please check that this file exists and restore from floppy disk if necessary. If problems persist for the supplied DigImage modules, please contact DL Research Partners (fax: (44)(1223) 232768, e-mail: s.dalziel@damtp.cam.ac.uk) giving full details.

Fatal Error Message: Unable to save menu data

DigImage is unable to open a temporary file on the %TMP% path into which the current menu is written. The probable cause is that the disk is full.

Fatal Error Message: Unable to find module name file

DigImage is unable to find the file Menus\Modules.MNU which stores the names of the various DigImage modules. Please check that this file exists, or restore it from floppy disk.

Error Message: Unable to open index file

DigImage is unable to find the file Menus\Index.MNU which stores the DigImage alphabetical feature index. Please check that this file exists, or restore it from floppy disk.

Error Message: Unable to create index command file

When an index item has been selected from the DigImage index, a command file is created in %TMP% to access the corresponding feature, help text or menu. This error occurs when DigImage is unable to create the command file. This is probably due to the disk being full.

1309F ObtainFileHandle No more file handles available! To aviod accidental duplication of Fortran file handles, DigImage automatically assigns the first unused file handle in the range 10 to 50 when an open file is requested. This error indicates that there are no more file handles available. This error may occur in user-written modules where the files have not been closed by the CloseFile(..) call.

Fatal Error Message: OpenFile parameter error

The parameters passed to the DigImage OpenFile subroutine are invalid. Please correct your code and recompile.

Fatal Error Message: Open File error - consult Fortran manual for details

DigImage is unable to open the requested file for some unexpected reason. For full details, refer to the errors listing of your MicroSoft Fortran manual, using the error number indicated. A common error is 6700 ("heap space limit exceeded") which indicates that DigImage does not have sufficient memory to open the requested file.

Error Message: Difficulty deleting file

The requested file can not be deleted. The most probable cause is that the file does not exist or an invalid file/path specification has been given.

Warning Message: Trk2Func.HLP missing

The HlpFiles\Trk2Func.HLP file is missing. This file normally contains a brief summary of the function keys and is displayed by <ctrl><f1>. If absent, it should be reinstalled from the DigImage installation disks.

Warning Message: Incorrect DigImage version

DigImage has detected an incorrect version number for one of its support files (.DIG and configuration files). The most probable causes are that the support file has been corrupted or that it was created by a more recent version of DigImage. DigImage will attempt to continue execution regardless. However, this may cause the computer to hang.

Error Message: Trouble writing to printer

DigImage is attempting to close the PRN printer file. On closing this file it copies its contents to the printer specified in the CONFIGUR utility. This error message is generated when the write fails for some reason.

Warning Message: Difficulty renaming file

It was not possible to rename the requested file. This may be caused by the file not existing, or it being open.

New or Append ?

DigImage is creating an output file. If this file already exists, should it be deleted and a New one created, or append to the existing file.

Requested option not registered with DigImage... Please specify name of module to be run.

The requested option has not been registered in the UserMenu\Modules.MNU data base. You will need to manually enter the name of the corresponding program.

Warning Message: Unable to create DigiNext.BAT chain file

DigImage is unable to create the DigiNext.BAT file which is used to start the next DigImage module.

Blank file name given. Please enter a new file name.

DigImage is not able to open the file as the file name is blank. Please enter a new file name.

This file is already connected to another unit. Please enter a new file name.

Access is denied. The "file" may be a directory. Please enter a new file name.

Error Message: Unable to find section in file specified for copying

The specified section in the requested file could not be found for including in the current output file.

Warning Message: No intensity calibration mapping function has been generated

This warning message is produced by the dynamic intensity calibration facility. It indicates that an attempt to utilise the calibration has been made before it has been determined from the intensities in the image.

Warning Message: No intensity calibration mapping function has been generated

This warning message is produced by the dynamic intensity calibration facility. It indicates that an attempt to utilise the calibration has been made before it has been determined from the intensities in the image.

Warning Message: No intensity calibration mapping function has been generated

This warning message is produced by the dynamic intensity calibration facility. It indicates that an attempt to utilise the calibration has been made before it has been determined from the intensities in the image.

Warning Message: Unable to save intensity calibration

DigImage is unable to open the CalInten.DIG file in the current directory. The current dynamic intensity calibration information is normally saved in this file. This failure will prevent the information from being saved. This warning is normally generated by a full disk.

Warning Message: Maximum number of windows already specified

The dynamic intensity calibration system is capable of determining the current intensity of up to ten reference windows and map these onto their reference values. This warning indicates that the maximum number of windows have already been specified.

Warning Message: The maximum number of coefficients have been specified

The dynamic intensity calibration system is capable of linear least squares fits of up to five coefficients. This warning indicates that this maximum has already been reached for the intensity mapping function.

Warning Message: The maximum number of coefficients have been specified

The dynamic intensity calibration system is capable of linear least squares fits of up to five coefficients. This warning indicates that this maximum has already been reached for the concentration mapping function.

Warning Message: Unable to save transfer function to Transfer.DIG

Once it has been specified, the [;PIX Specify hardware transfer function] is converted to an input look up table which is saved in the file Transfer.DIG in the current directory. This warning is generated if DigImage is unable to save the data to this file. This is generally caused by the disk being full.

Error Message: Minimum and maximum concentrations equal

When rendering concentrations as intensities in an image it is necessary to specify the concentration to be rendered with intensity 0 and that to be rendered with intensity 255. This error is produced if the two concentrations are equal.

Error Message: Minimum and maximum concentrations equal

When rendering concentrations as intensities in an image it is necessary to specify the concentration to be rendered with intensity 0 and that to be rendered with intensity 255. This error is produced if the two concentrations are equal.

Warning Message: Invalid threshold - point ignored

The threshold specified for the permanent reference point is equal to the intensity at the cursor. It is not therefore possible to determine whether the reference point is brighter or less bright than the threshold. The point will be ignored.

Warning Message: Unable to open file. Sending data to terminal

It is not possible to write the permanent reference point data to the requested file. The data will insteady be written on the terminal.

Warning Message: Too few reference points found for specified transformation

Not all of the permanent reference points were located on the current image: the number of coefficients required for the mapping exceeds the number of reference points found and so it is not possible to generate the mapping.

Error Message: Unable to open reference points file

DigImage is unable to open the requested reference points file. The most probable cause is that the file does not exist on the specified path.

Error Message: Unable to save permanent reference points in file

DigImage is unable to open the requested file in which the permanent reference points are to be saved. This may be due to an invalid path or file name being specified, or the disk is full.

Warning Message: Unable to save current 2D world calibration points

DigImage normally saves the pixel and world coordinates of the points used to determine the pixel-world coordinate transformation in the file CalWldPt.DIG. This message is generated if DigImage is unable to save the data. This may be due to a full disk.

Error Message: Unable to create CalWldPt.DIG in current directory

DigImage stores the raw information about the world coordinate system in the file CalWldPt.DIG in the current directory. This error is produced while executing [;PWI Initialise world coordinate mapping] if DigImage is not able to create the CalWldPt.DIG file. The most probable cause of this is that the disk is full.

Error Message: World coordinates file not found

DigImage is unable to open the requested file containing details of the world coordinate system. The most probable cause is that the file can not be found on the specified path.

Error Message: Unable to save world coordinates in file

DigImage is unable to open the requested file to which details about the world coordinate system are to be written. The most probable cause is that the disk is full, or an invalid path or file name has been specified.

Warning Message: Too few world points to generate a coordinate mapping

A minimum of three points must be specified using the [L Locate world coordinate points] before a mapping function may be generated.

Warning Message: Unable to change to new directory

Function key sequence <ctrl><f2> is used to change to a new directory. This warning message is issued if it is not possible to change to the directory requested (eg. the directory does not exist).

Warning Message: The requested output LUT does not exist

Function key sequence <ctrl><f4> is used to select an output look up table. This warning is generated if the specified table does not exist.

Error Message: Unable to save memory during function key operation

It was necessary to save all the work space used by DigImage to sucessfully execute the function key operation specified. However, this work space could not be saved in the file FnKeyMem.DIG. The most probable cause is that the disk is full.

Name of new working directory ?

<ctrl><f2> has been pressed in order to change directory. Please enter the name of the new working directory. All files generated by DigImage will, by default, be saved to this directory from now on.

Use which output look up table ?

The <ctrl><f4> function key combination has been pressed to change output look up tables. Please enter the table to switch to.

Text to be positioned (blank to avoid) ?

The <ctrl><f5> function key combination has been pressed to print text on the frame grabber buffer. Please enter the text here.

Name of Journal file to be opened ?

<f6> has been pressed to open a journal file. Please enter the name of the journal file to be created. The file will default to a .JNL extension.

Message: Unable to open Journal file

The Journal file requested by <f6> could not be opened.

Start from Main or Current menu ?

The journal file may start recording activity either from the current location or the main menu.

Include full comments ?

Answering Yes will cause DigImage to record many of the input prompts and other associated information as comments in the <f6> journal file.

Message: Journal File closed

The journal file opened by <f6> has now been closed.

Message: No Journal File was open

The request to close the journal file was ignored as there was no journal file open.

Name of file to be listed ?

<ctrl><f6> has been pressed to list the contents of a file. Please enter the name of the file.

Name of file to be deleted ?

Enter the name of the file to be deleted by pressing <alt><f6>.

Apply hardware transform to this buffer ?

<shift><f7> applies the hardware transform specified in [;PI: Intensity coordinates].

Erase this buffer ?

Enter the number of the buffer to be deleted by <ctrl><f8>.

Screen dump as Postscript, Laserjet or paintJet image ?

<ctrl><f9> can print the current image as a PostScript, a LaserJet or a PaintJet image. Please select the one you wish to use.

Name of output file (PRN to send directly to printer) ?

Enter the file name for the image print file to be created, or PRN if you wish to send the image directly to the printer.

Title for screen dump ?

Enter the title (if any) for the screen dump.

Size of low pass kernal (0 to suppress filtering this buffer) ?

The [;FL Fast low pass filter] has been invoked using <f10>. Please enter the size of the kernal to be used.

Duplicate Odd, Even or No lines ?

The duplication interlace filter has been invoked with <shift><f10>. Please indicate the mode of operation.

Average Odd, Even or No lines ?

The averaging interlace filter has been invoked with <ctrl><f10>. Please indicate the mode of operation.

Copy this buffer to where ?

<f11> will copy the current output buffer to that specified at this prompt.

Copy what buffer to this buffer ?

<shift><f11> will copy the buffer specified here to the current output buffer.

Disable screen saver ?

<alt><f11> can enable or disable the screen saver.

Current directory: !RM0!RM1!RM2!RM3!RM4 Listing of which directory/files (blank for current directory; finish with \ for whole specific directory) ?'

Enter the name of the directory to be listed.

Enter MS-DOS command

Enter the MS-DOS command to be executed or COMMAND to start an embedded session.

Screen Saver Type: A Animated particles B DigImage random walk Q Cancel request

This entry lists the available screen savers. Try them and see!

Warning Message: Video multiplexer not installed

An attempt to access the DT-2859 video multiplexer was made using [;GY Select multiplexed input]. However, as the multiplexer is not installed, such access is not possible.

Warning Message: Unable to open specified file to save buffer in

The [;GS Grab sequence] facility has the option of automatically writing the buffers acquired to a sequence of files file_name.###, where ### is the buffer number. This warning is generated if DigImage is unable to perform the required save. This may be because the disk is full, or an invalid path or file name has been specified.

Warning Message: Unable to open specified file to save buffer in

The [;GA: ALU Acquire] facility has the option of automatically writing the buffers acquired to a sequence of files file_name.###, where ### is the buffer number. This warning is generated if DigImage is unable to perform the required save. This may be because the disk is full, or an invalid path or file name has been specified.

Error Message: Unable to grab real colour image to buffer 0 - use another buffer

The [;GR Real colour grab] option is not able to place the resultant full colour image in buffer zero. You must specify a different buffer.

Error Message: Can not open PaintJet output file

DigImage is unable to open the requested file to which a PaintJet version of the specified buffer is to be written. This may be due to an invalid path or file specification, or the disk is full.

Error Message: Can not open PaintJet output file

DigImage is unable to open the requested file to which a PaintJet version of the specified buffer is to be written. This may be due to an invalid path or file specification, or the disk is full.

Error Message: Can not open PCL5 output file

DigImage is unable to open the requested file to which a LaserJet version of the specified buffer is to be written. This may be due to an invalid path or file specification, or the disk is full.

Producing PostScript screen dump...

DigImage is producing a PostScript screen dump of the image.

Producing PCL5 screen dump...

DigImage is producing a PCL5 screen dump of the image.

Producing PaintJet PCL screen dump...

DigImage is producing a PCL screen dump for a PaintJet printer.

Name of output PostScript file (blank to suppress; .PS for printable PostScript .EPS for encapsulated PostScript, or .DPS for data only PostScript) ?

Specifying a file in response to this prompt will cause a PostScript description of the output to be placed in the file. The file will subsequently need to be transfered to a suitable PostScript printer to enable the hard copy to be produced. Entering a blank line suppresses the production of the PostScript file.

Encapsulated PostScript (.EPS) and Data Only PostScript (.DPS) can not be printed directly, except using DigiFile. Normally they would be included within some other package (eg. a word processor) to be printed. The .DPS file is a special version of .EPS which does not contain the normal DigImage\PostScr\Header.PS and DigImage\PostScr\GraphVDU.PS header files. These may need to be added to the PostScript prolog used by the application into which the .DPS file is inserted.

If no extension is specified, then the default PostScript type specified in [;P Printers] in CONFIGUR.EXE will be produced, and the appropriate extension added.

This file may be sent to the printer immediately by specifying PRN as the file name.

Default, Line, Greyscale or Colour printing using DigImage or Printer translation?

DigImage is able to produce either grey-scale or colour PostScript files.
        Default                 Colour type specified in Configur.EXE
        Line                    Greyscale images and dashed line types
        Greyscale               Greyscale images and greyscale lines
        Colour                  Colour images and colour lines - requires
                                Level 2 PostScript. DigImage translates from
                                RGB to CMYK.
        Printer translation     As for Colour, but the printer is responsible
                                for the translation from RGB to CMYK.

Plot layout index ?

The plot layout index controls the number of plots per page and their precise location on the page. Standard values are:
       0   One plot, portrait.
       1   One plot, landscape.
       2   Two plots, portrait.
       3   Three plots, portrait.
       4   Four plots, landscape.

Values of the index 10-14 give the same number and orientation of plots, but with additional spacing between them to allow for the Alternate Axes - see DigiPlot user guide.

Name of output PostScript file (blank to suppress; .PS default extension; use .EPS for encapsulated PostScript or .DPS for data only PostScript) ?

DigImage can write the plot or screen dump to a PostScript file. The nature of this file depends on the extension given. For a standard (printable) PostScript file, specify .PS. For Encapsulated PostScript (which MUST be embedded in another document), specify .EPS. For the special Data-only PostScript file, specify .DPS.

Default, Line, Greyscale or Colour printing using DigImage or Printer colour translation ?

DigImage is able to produce either grey-scale or colour PostScript files. The Default option is controlled by the setting in the Configur.EXE utility. If colour is selected, then the file MUST be printed on a level 2 (or higher) PostScript printer.

Constructing PostScript...

DigImage is constructing the PostScript file.

Error Message: Running Windows not at full screen - can not change video mode

DigImage supports graphics modes on the computer screen only from DOS or when the application is running full screen.

Warning Message: You must ensure the application is running full screen

DigImage is only able to use graphics modes when running under Windows if the application is running full screen.

DigiPlot has finished!

DigiPlot has finished rendering the requested plot. To continue, press any key.

Warning Message: Invalid range specification for plot instruction

The range specification, bracketed by { }, is invalid.

Warning Message: Invalid buffer. Setting to zero.

The buffer number specified at a /B switch is invalid. Buffer zero will be use in its place.

Warning Message: Unable to find font metrics. Substituting font 2

The metrics information for the requested font could not be found. Font 2 will be substituted in place of the requested font. You should check that the correct font was requested.

Error Message: Unable to open file to which window was to be written

This message is issued if DigImage was unable to open the file to which the contents of a window within a buffer was to be written. This may be due to an incorrect path/file specification, or the disk full.

Warning Message: Unable to open file from which window is to be read

This message is issued if DigImage was unable to open the file from which the contents of a window are to be read. The most common cause is that the required file does not exist.

Warning Message: Compressed images must be loaded in their original location

DigImage supports a number of different file formats for storing the contents of buffers. The requested file was saved using the adaptive bit-plane run-length encoding technique. Such images are always entire buffers and can thus not be loaded as windows. DigImage will load the image to the entire buffer with the origin at the top left.

Warning Message: Unable to load entire image

There is less data in the file than indicated by the file header. DigImage is thus not able to reconstruct the image fully. The buffer will contain as much of the image as DigImage was able to retrieve. This warning is generally due to the file having been truncated, partially overwritten, the disk full, or by an inconsistency in the file system (run the MS-DOS CHKDSK to check).

Warning Message: Unable to open specified file

DigImage was unable to open the file to which the compressed buffer was to be written. This may be due to an incorrect path/file specification, or the disk is full.

Warning Message: Unable to open specified file

DigImage was unable to open the file from which the compressed buffer was to be read. The most probable cause of this warning is that the requested file does not exist (or the path specified incorrect).

Warning Message: Unable to load entire image

There is less data in the file than indicated by the file header. DigImage is thus not able to reconstruct the image fully. The buffer will contain as much of the image as DigImage was able to retrieve. This warning is generally due to the file having been truncated, partially overwritten, the disk full, or by an inconsistency in the file system (run the MS-DOS CHKDSK to check).

Error Message: Error while writing window file

DigImage was unable to complete the creation of the requested window file. The most probable cause is that the disk is full.

Error Message: Error while writing window file

DigImage was unable to complete the creation of the requested window file. The most probable cause is that the disk is full.

Error Message: Error while saving compressed buffer

DigImage was unable to complete the creation of the requested compressed buffer file. The most probable cause is that the disk is full.

Error Message: Windows 3.x .BMP file not valid format

The file specified can not be loaded as a Windows 3.x bit map as it does not have a valid header.

Fatal Error Message: Windows 3.x .BMP file - Invalid number of bits

DigImage supports Windows 3.x bit map files with 1, 4 or 8 bits per pixel. The call to SaveWindowsBMPFile requested a different number of bits.

Error Message: Unable to open output GIF file

This message is issued if DigImage was unable to open the file to which the contents of a window within a buffer was to be written. This may be due to an incorrect path/file specification, or the disk full.

Error Message: Unable to open input GIF file

This message is issued if DigImage was unable to open the specified .GIF file.

Error Message: Unrecognised GIF file

The GIF file signature should be either GIF87a or GIF89a. Other signatures are not recognised by DigImage.

Error Message: Invalid code size

It is not possible to decompress this GIF image. The file may be corrupt.

Error Message: Unable to open specified TIFF file

DigImage was unable to open the specified TIFF file. The most probable cause is an incorrect file specification.

Error Message: TIFF files must have lo byte first

DigImage can only read TIFF files with the low byte stored first (Intel and DEC Alpha architectures). These are identified by the first two characters of the file being 'II'. Files with the high byte stored first (eg. Sun, SGI & HP workstations) have 'HH' as the first two characters of the file.

Error Message: Only TIFF version 2Ah supported

At the time of writing, ALL valid TIFF files have a version number 2Ah. If a different version number is detected, then this probably indicates a corrupt TIFF file.

Warning Message: Maximum width of TIFF image is 512 pixels

DigImage can not process images larger than 512x512 pixels (512x480 in North America). The image will be truncated to 512x512 pixels.

Warning Message: Maximum height of TIFF image is 512 or 480 pixels

DigImage can not process images larger than 512x512 pixels (512x480 in North America). The image will be truncated to 512x512 pixels.

Error Message: Only 8-bit TIFF images supported

This version of DigImage only supports 8-bit TIFF images. Both greyscale and palettised images may be used.

Error Message: Compressed TIFF images not supported

This version of DigImage only supports uncompressed TIFF images.

Error Message: 24-bit RGB TIFF images not supported

DigImage does not support images with more than 8 bits per pixel.

Error Message: Unable to open file to which window was to be written

This message is issued if DigImage was unable to open the file to which the contents of a window within a buffer was to be written. This may be due to an incorrect path/file specification, or the disk full.

Warning Message: Unable to open intensities output file

DigImage was unable to open the requested output file to which the intensities in the current row and/or column were to be written. This may have been caused by an invalid path or file specification, or the disk full.

Error Message: Unable to save iMemory in Drag Text submenu

When entering the Cursor submenu for text dragging, the font to be used must be cached in the iMemory array. To prevent this corrupting the previous contents of iMemory, the option exists to write the iMemory array out to %TMP%\iMemory.TMP. This error is generated when DigImage is unable to open this file. The most probable cause is that the disk is full, or %TMP% is incorrectly specified.

Set text in current position or Cancel ?

The text may be either Set in its current location or cleared.

Specify using Pixel or World coordinates ?

For manual cursor positioning, the location may be specified using either pixel (<P>) or world (<W>) coordinate systems.

New row for cursor ?

Enter the pixel row number where the cursor should be positioned.

New column for cursor ?

Enter the pixel column where the cursor should be positioned.

New x coordinate for cursor (!RM0) ?

Enter the new x world coordinate for the cursor.

New y coordinate for cursor (!RM0) ?

Enter the new y world coordinate for the cursor.

Name of file to write intensities to (.DAT default extension) ?

The intensities along the cursor row and column will be written out to the file specified here.

Both, Horizontal or Vertical section(s) ?

The intensities in the horizontal, vertical or both directions will be written to the file, depending on the response here.


Pixel          :                       pixels       Intensity :
Pixel-Reference:                       pixels         Average :
World          :                       !RM0           Std  dev :
World-Reference:                       !RM0               Zoom :
Polar World-Ref:

--- Top Left Slow ---

+++ Top Left Fast +++

--- Bottom Right Slow ---

+++ Bottom Right Fast +++

*** Using Mouse ***

Warning Message: Requested fast low pass filter does not exist

DigImage defines a number of fast low pass convolution filters utilising the frame grabber's ALU hardware to perform the computations with eight bit precision. Such a filter has been requested. However, the particular filter requested is not known by DigImage. No filtering will be done.

Error Message: Specified filter not available

The specified convolution filter is not available. This probably indicates the Menus\Convolut.MNU file has been corrupted.

Error Message: Fourier domain filter type unknown

The requested FFT filter is not known by DigImage. This probably indicates the Menus\FourFilt.MNU file has been corrupted.

Fatal Error Message: Least squares matrix not big enough for work space

The matrix passed to the least squares routines must contain at least two more columns than are actually used to contain the matrix coefficients and right hand sides. This extra space is used as work space.

Fatal Error Message: Least squares matrix not big enough for work space

The matrix passed to the least squares routines must contain at least two more columns than are actually used to contain the matrix coefficients and right hand sides. This extra space is used as work space.

Fatal Error Message: The size of the coefficients matrix is smaller than the number of coefficients required

After the least squares problem has been solved, the resulting coefficients are copied into an array with one column for each right hand side. This error is produced if there is insufficient space in this coefficient matrix.

Fatal Error Message: The xData vector contains fewer dimensions than the specified number of variables

There is an error in the data structures passed to this routine. More independent variables have been specified in the xDataKey array than have been passed as xData.

Fatal Error Message: Too many independent variables

The routine is limited to 16 independent variables. More than this were specified.

Fatal Error Message: Too few variable keys specified

The length of the xDataKey string, used to specify the letters for accessing the x data in the expressions, is shorter than the number of independent variables specified by nxVar.

Fatal Error Message: Coefficient array has mCoeff<nyVar

Each dependent variable requires its own set of coefficients. The column dimension of the coefficient array is too small to store the coefficients.

Warning Message: Illegal weighting function based on dependent variables - ignore weighting

The least squares weighting function should normally be based on the independent "x" variables. You may use a weighting function based on the dependent "y" variables if and only if it does not also depend on the independent variables and there is only one dependent variable being fitted. If these conditions are violated, then unity weighting will be used.

Error Message: Too many expressions in colon separated list

The number of expressions in the colon separated list exceeds the maximum number allowed in this call. (The maximum number is ABS(nExp) when nExp<0.)

Warning Message: Negative LOG(x-xOff)

The data or axes to be plotted require the evaluation of the log of a negative number in the x direction. This is not valid. Correct axes scales, data or whatever.

Warning Message: Negative LOG(y-yOff)

The data or axes to be plotted require the evaluation of the log of a negative number in the y direction. This is not valid. Correct axes scales, data or whatever.

Warning Message: Negative LOG(x-xOff)

The data or axes to be plotted require the evaluation of the log of a negative number in the x direction. This is not valid. Correct axes scales, data or whatever.

Warning Message: Negative LOG(y-yOff)

The data or axes to be plotted require the evaluation of the log of a negative number in the y direction. This is not valid. Correct axes scales, data or whatever.

Error Message: Invalid PostScript file specification

The specified PostScript file is not valid. It may be that a blank name was specified.

Error Message: Unable to open PostScript plot file

DigImage is unable to open the specified PostScript output file. The disk may be full, or an invalid file or path may have been specified.

Warning Message: Unable to use required output look up table

DigImage is unable to use the requested output look up table. An invalid table may have been requested, or the %LUT%\Output##.LUT file may have been deleted.

Warning Message: Current xMin < xOff for Log axis - ignore

The requested axis minimum is smaller than the Log axis offset so that xMin-xOff is negative. This would require the logarithm of a negative number. The offset will be ignored.

Warning Message: Current yMin < yOff for Log axis - ignore

The requested axis minimum is smaller than the Log axis offset so that yMin-yOff is negative. This would require the logarithm of a negative number. The offset will be ignored.

Error Message: y axis limits equal

The minimum and maximum y values are equal. It is not possible to create the axes.

Error Message: x axis limits equal

The minimum and maximum x values are equal. It is not possible to create the axes.

Error Message: 3D Surface plot type not implemented

The requested type of 3D surface plot is not implemented. Please use types 0 to 6.

Error Message: 2D Polygons limited to 16 vertices

DigImage only allows polygons of up to 16 vertices to be drawn and filled directly. More complex polygons should be specified as a sequence of simpler graphic entities.

Error Message: 3D Polygons limited to 16 vertices

DigImage only allows polygons of up to 16 vertices to be drawn and filled directly. More complex polygons should be specified as a sequence of simpler graphic entities.

Error Message: Polygon fill limited to 16 vertices

DigImage only allows polygons of up to 16 vertices to be drawn and filled directly. More complex polygons should be specified as a sequence of simpler graphic entities.

Error Message: Internal polygon fill error

The polygon fill attempts to fill outside the bounding box.

Error Message: Unable to find PostScript header file

DigImage is unable to find the requested PostScript header file in PostScr. Please check this file exists and restore from floppy disk if necessary.

Error Message: Failure in writing PostScript header to file

DigImage was unable to write all the PostScript header file to the required output file. This may indicate that the disk is full.

Error Message: Unable to open output PostScript file

The requested PostScript output file could not be created. This may be due to the disk full, or an invalid file/path specification.

Error Message: Unable to open font file

DigImage is unable to open the requested font file. Please check this file exists and copy from floppy disk if required.

Error Message: Invalid font

The specified font is invalid.

Error Message: Duplicate font save aborted at user request

A duplicate font was detected during a save operation. You have requested not to continue with the save.

Error Message: Could not read in entire font

DigImage was unable to read in all of the requested font. The file requested may not have been a valid font, or the file may have been corrupted.

Error Message: Can not replace the menu entry for U

It is not possible to replace the [U User specified file] entry in the Font Selection Menu.

Error Message: Illegal key character for font

The key character for font selection must be an upper case letter. Digit fonts are reserved for use by DL Research Partners.

Error Message: Unable to open output font file

DigImage is unable to open a file to write the font to. This probably indicates the hard disk is full.

Error Message: Unable to write entire font file

DigImage is unable to write out the entire font file. This probably indicates the hard disk is full.

Warning Message: Unable to undo last (any) copy/erase operation

DigImage is unable to undo the last copy or erase operation, either because there have not been any such operations, or the font file has been manipulated since the copy/erase.

Error Message: Buffer does not contain valid font

The specified buffer does not contain a valid font. Valid font buffers contain only intensities 0 and 255 (in the font cell), and 127 and 128 as the background.

Error Message: Unable to open FontMetr.MNU font metrics file

The font metrics file is used to determine the which fonts are used as superscript, subscript etc.

Error Message: Unable to prepend plot file

The specified plot file could not be found for including in the current output plot file. If not in the current directory, this file should be in the %DigImage%\PostScr directory.

Warning Message: Unable to write PlotFile output to PostScript

The current plot was not able to be written out to a PostScript file. This may be because the disk drive is full, or an invalid file name was specified.

Error Message: Unable to find section in file specified for copying

The specified section in the requested plot file could not be found for including in the current output plot file. If not in the current directory, this file should be in the %DigImage%\PostScr directory.

Error Message: Unable to find plot file to be copied

The specified plot file can not be found in either the current directory or %DigImage%\PostScr.

Error Message: Unable to write output plot file

DigImage was unable to open the required output plot file.

Error Message: Unable to find DigiPlot.PLT

The DigiPlot initialisation file, PostScr\DigiPlot.PLT could not be found. You will need to reinstall this file.

Error Message: Unable to open plot file

The specified plot file could not be found

Warning Message: Invalid parameter for polygon fill - ignore command

An invalid parameter was given for the PL or PL3 plot commands.

Warning Message: Invalid parameter for R3 command

An invalid parameter was given for the indicated R3 surface plotting command.

Warning Message: Unable to open 3D surface file

DigiPlot could not open the specified file for plotting a 3D surface.

Warning Message: Plot files nested too deeply - ignore new level

Plot files may be nested up to a maximum of ten levels. If an attempt is made to nest deeper, then the new plot file will be ignored.

Warning Message: Unable to open nested plot file

DigiPlot was unable to open the specified nested plot file (requested by the R instruction). This may be because it could not find the file.

Warning Message: Unable to complete R3 file command

DigiPlot was unable to find sufficient records in the file specified by the R3 command. The remaining entries are set to (xMax,yMax,zMin).

Warning Message: Too many expressions for number of data items

DigiPlot has been requested to fit a formula using least squares (SF plot instruction) which has more unknown coefficients than there are data items to be fitted.

Warning Message: No least squares fit to plot

The SP plot instruction has failed because there has not been a least squares fit generated by an SF instruction. This may be because there is no SF instruction, or the fitting procedure itself failed.

Warning Message: Unknown least squares plot instruction

The indicated plot instruction was not recognised.

Error Message: Unable to create screen dump PostScript file

DigImage was unable to create the PostScript file to which the screen dump was to be written. Possible causes are an invalid filename or path, or the disk drive is full.

User specified font file: Use what file ?

Specify the name of the file containing the user-specified font.

Error Message: Unable to open LeastSquares input data file

DigiPlot was unable to open the specified file from which the least squares data was to be read.

Fatal Error Message: Unable to open SVHS Video Menu file

DigImage is unable to open the file containing the menu controlling the SVHS Video. The most probable cause is that the file has been deleted. Reinstall from floppy disk.

Warning Message: The VTR will be placed in record mode

The [;VR Record buffers on tape] option has been chosen. The video will be placed in record mode then each buffer will be recorded for the required number of frames. The VTR will not be taken out of record mode until some other operation is requested. Note that the frame count will be inaccurate during and after the record operation.

Error Message: The specified tape operation does not exist

A call to SVHSOperation (responsible for basic control of the VTR) was made requesting an unknown tape operation. Correct the program concerned then recompile.

Error Message: SVHS: Invalid buffer specified!

A call was made to SVHSAcquireALUConstantSequence with an invalid buffer number (ie. negative or greater than the last buffer). Correct program concerned then recompile.

Error Message: SVHS: Mask buffer must be onboard

The mask buffer specified to the SVHSAcquireALUConstantSequence routine must be an onboard buffer to enable the frame grabbers ALU hardware to access it. If specified as -1, then the current contents of each of the onboard buffers will be used as the mask. Correct program concerned then recompile.

Error Message: SVHS: Start buffer must be onboard

Sequences of constantly spaced buffers acquired with computer control of the video may only be acquired to buffers on the frame grabber card. This error indicates that the first buffer to be acquired is in extended memory - this is not allowed. Correct program concerned then recompile.

Warning Message: VTR not responding - check REMOTE switch

The computer is unable to obtain the required response from the AG7330 VTR. This may indicate that the video is unable to respond due to the position of OPERATION switch (it should be in the REMOTE not the LOCAL position), or that the serial cable between the computer and video has become disconnected.

Fatal Error Message: DigImage built for different video type

DigImage has been built for the indicated video type, yet the video stated by the VIDEO environment variable is different. Correct the SET VIDEO=... in AUTOEXEC.BAT (and reboot), or rebuild DigImage using DigiLink.BAT for the correct video type.

Fatal Error Message: VTR status unknown

The VTR responded with an unknown status. Check the power is on and the VTR is connected, then try again.

Fatal Error Message: Unknown SVHS command

An unknown SVHS command has been issued. Please check your program.

Error Message: SVHS is turned off

The SVHS VTR is turned off at the front panel. Please turn on.

Warning Message: No tape in VTR

DigImage is unable to initialise the VTR as there is no tape in it. Please put a video cassette in the VTR.

Error Message: Record tab not in video cassette

The tab at the back of the cassette allowing recordings to be made has been removed. To enable recordings, cover the tab position with some tape.

Error Message: Record tab not in video cassette

The tab at the back of the cassette allowing recordings to be made has been removed. To enable recordings, cover the tab position with some tape.

Error Message: Record tab not in video cassette

The tab at the back of the cassette allowing recordings to be made has been removed. To enable record and audio dub operations, cover the tab position with some tape.

Error Message: No LTC user code specified

No linear time code user code was specified. DigImage is not able to complete this option.

Error Message: Invalid LTC user code specified

The linear time code user code specified contained one or more invalid characters (only numbers are allowed). DigImage is not able to complete this option.

Warning Message: Unable to open time code error report file

DigImage is unable to open the specified file for a time code error report. This may be due to an invalid file name or insufficient disk space.

Error Message: VTR in warning condition

The VTR has signalled that there is a problem with it. Consult the VTR manual for further details.

Error Message: Drum condensation

The VTR has signalled that there is condensation (moisture) on the drum. Consult VTR manual for further details.

Error Message: No tape in VTR

There does not appear to be a tape in the VTR.

Warning Message: Could not correctly reset field count for BRS822

There is an error in the BRS822 routine for setting the field count to a specified value. This could be caused if the VTR is in FF or REW while attempting to do this. The error condition is that the value read back from SVHSFieldCount does not agree with the specified value.

Warning Message: Invalid time code - period not even

DigImage has detected a time code period which does not represent an even number of fields. This period is invalid and can not be used. Re-record the time code pulses. The present time codes will be ignored.

Warning Message: Invalid time code - period out of range

The time code pulses should be once every 8 to 16 fields. The default is 8. Spacing outside this range gives this warning message and the time codes will be ignored.

Warning Message: Inconsistent time code - ignore time codes

DigImage has detected audio clicks which do not yield a consistent time code period. It will therefore not use these clicks.

Error Message: Can not have zero new velocity error!

It is necessary for DigImage to have some nonzero measure of the amount of error to be expected in estimates of particle velocities for particles having no previous velocity history. Consult user guide for details.

Warning Message: The new paths velocity error is very large for the size tracking window you are using. Please check this value and/or the tracking window and sample spacing

DigImage checks the new paths velocity error you have entered against the current size of the tracking window and the requested sample spacing. If the new paths velocity error equates to a distance greater than 1/10 of the size of the window over a period of one sample, i.e.
       (i.e. dt*(u+v) > 0.1 * window diagonal)

then this warning message is generated. Typically the new paths velocity error will be substantially less than this limit, although on some occassions it may be greater. Note that this error may indicate either the new paths velocity error is inappropriate, the tracking window has not been set up correctly, or the sample spacing is inappropriate.

Warning Message: Can not track more than 32767 samples. Either increase sample spacing or decrease tracking period

The maximum number of samples which may be tracked by DigImage is 32767 (i.e. the maximum positive number which may be stored in an INTEGER*2 variable). You must either decrease the tracking period, or increase the sample spacing.

Warning Message: The interlace filter is currently turned on ([;USTI: Interlace filter]). This restricts the minimum vertical size to be 4 pixels or more.

This is necessary to ensure subpixel resolution. If the flow is slow enough, then turn off the interlace filter. Note that if you use a frame integration camera in conjuction with a mechanical shutter then it is not necessary to use the interlace filter even for fast flows. Consult Document\Cameras.DOC or DL Research Partners for details. The current setting, which is less than the four pixel minimum, will be ignored.

Warning Message: The minimum vertical size ([;USLY Minimum vertical size]) of a particle must be at least four pixels when an interlace filter is in use.

This is necessary to ensure subpixel resolution. If the flow is slow enough, then turn off the interlace filter. Note that if you use a frame integration camera in conjuction with a mechanical shutter then it is not necessary to use the interlace filter even for fast flows. Consult Document\Cameras.DOC or DL Research Partners for details. The current setting, which is less than the four pixel minimum, will be ignored.

Warning Message: Velocity time step less than 4*sample spacing - check configuration

It is normal to calculate the velocity on four or five time steps from the particle tracking. The generation of this warning indicates that a shorter time interval is currently specified. You may wish to check your configuration.

Help on the requested topic is not yet available.

The requested help file could not be found. It may either not be available yet or has accidentally been deleted. If this occurs for a standard DigImage component, then check to see if it has been deleted.

Help: <up> <down> <PageUp> <PageDn> <home> <end> or <Q>uit

This prompt shows the keys which may be used to navigate around the help file.

Help: <up> <down> <PageUp> <PageDn> <home> <end> <key> or <Q>uit

Index: <up> <down> <PageUp> <PageDn> <home> <end> <enter> or <escape>

Pause: Press any key to continue (no pause when in .CMD command file)...

Pressing any key (except <escape>) will allow DigImage to continue execution.

Which buffer now ?

DigImage is requesting a list of buffers to be input. Please enter the desired buffer number.

Another buffer ?

Answering Yes will allow another buffer to be entered in the list.

Use what intensity ?

Enter the intensity to be used.

Set, And, Or or Xor intensity ?

Specify the manner in which the requested intensity is to be combined with that already in the image.

History:

Press key to select

Press the appropriate key to select a particular member of the history list.

Enter valid integer

An invalid integer was entered. Please enter a correct one.

Enter valid real number

An invalid real number was entered. Please enter a correct one.

Enter valid time (hours:minutes:seconds or ::fields)

An invalid time value was entered. Please enter a correct one.

Starting screen saver...

The DigImage screen saver is starting

Warning Message: Problem evaluating light sheet

There has been a problem evaluating the light sheet when correcting for the attenuation and divergence. DigImage calculates that the light sheet should increase in intensity along the light rays, whereas physic suggests it should decrease. The most probable cause of this is that the current window contains the image of something other than the LIF flow.

Main Menu

DigImage User Documentation


Stuart Dalziel, last page update: 19 February 1996