home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR4
/
T2B120.ZIP
/
TXT2BIN.MSG
< prev
Wrap
Text File
|
1994-01-04
|
10KB
|
333 lines
LIST OF SUPPORTED ERROR MESSAGES
--------------------------------
Here is the list of errors that TXT2BIN may encounter. For each
error message, a brief explanation is given to help you correct
the error.
Byte value exceeds maximum of 255 at column NNNNN
The byte value was found to be more than the maximum
value of 255. Either you have too many characters
comprising the byte, or you have forgotten to insert a
space between this byte and the next.
Cannot write to output file. Disk may be full.
TXT2BIN could not write any more bytes to the output
file. The hard disk on which the output file is located
may be full. Try another disk drive, or free up some
disk space on the current drive.
Directive does not start with an alphabetic character at
column NNNNN
You must always start a directive with an alphabetic
character (e.g. DEFINE, INCLUDE, RADIX). Check the
spelling of your directive.
Invalid character at column NNNNN
TXT2BIN found a character that is not part of the radix.
The possible causes are:
(1) A typing mistake;
(2) The radix is not DECIMAL (base 10). Make sure
that the appropriate radix is specified by a
.RADIX statement.
Invalid character in directive at column NNNNN
TXT2BIN has encountered a character in the name of the
directive which is not one of the following:
(1) Alphabetic (A-Z, a-z);
(2) Numeric (0-9);
(3) Underscore (_)
Invalid character in include file name at column NNNNN
The name of the INCLUDE file is not a proper DOS file
name. The file name can only contain the following
characters:
(1) Alphabetic (A-Z, a-z);
(2) Numeric (0-9);
(3) The following characters:
~ ` ! @ # $ % ^ & ( ) { } '
Invalid character in symbol at column NNNNN
TXT2BIN has encountered a character in the name of the
symbol which is not one of the following:
(1) Alphabetic (A-Z, a-z);
(2) Numeric (0-9);
(3) Underscore (_)
Invalid character within string at column NNNNN
The character was not within the range 32-255 (decimal),
inclusive, or was not a tab character (9 decimal).
Invalid radix at column NNNNN
An invalid character was found as part of the radix
value. Only decimal numbers (0 to 9, inclusive) are
allowed.
Invalid whitespace character in expression at column NNNNN
A whitespace character other than a space or a tab
character was found in the middle of an expression.
(A whitespace character is one of either a space, tab,
formfeed, linefeed, or carriage return).
Invalid whitespace character in symbol at column NNNNN
A whitespace character other than a space or a tab
character was found in the middle of a symbol.
(A whitespace character is one of either a space, tab,
formfeed, linefeed, or carriage return).
Length of directive exceeds 32 characters at column NNNNN
You have specified the name of a directive whose length
is greater than 32. Check the list of supported
directives.
Length of expression exceeds the maximum of 255 at column NNNN
The expression in the DEFINE directive is too long.
Break up the expression into organized groups, using
symbols within the expression. For example,
.DEFINE CR 0D
.DEFINE LF 0A
.DEFINE CRLF <CR> <LF>
.DEFINE packet1 1B 27 3E 4D 2A <CRLF>
.DEFINE packet2 1B 56 90 22 1C <CRLF>
.DEFINE packet <packet1> <packet2>
Length of include file name exceeds 255 characters at column
NNNNN
The name of the include file can be up to 255 characters
in length. Make sure that this is so and retry the
program.
Length of symbol exceeds 32 characters at column NNNNN
Shorten the name of the symbol in the DEFINE directive,
such that the length of the symbol does not exceed 32.
Missing directive at column NNNNN
The name of a directive was missing after the dot (.)
character. Make sure that there are no spaces between
the dot character and the directive.
Missing include file name at column NNNNN
You did not specify a file name in the INCLUDE directive.
Missing symbol at column NNNNN
You did not specify the name of a symbol in the DEFINE
directive.
Non-terminated string at column NNNNN
A text string did not end properly with a double-quote
character (").
Non-terminated symbol at column NNNNN
A symbol was not terminated with a '>' character.
Numeric constant too big at column NNNNN
Within a text string, an octal value (\Onnn or \nnn) was
found to be more than 255 (or \O377 or \377).
Out of file stack space
TXT2BIN encountered an INCLUDE directive, and tried to
save the information of the current text file. However,
no memory was available. Make sure that you have enough
conventional memory before retrying.
Out of symbol evaluation space at column NNNNN
While evaluating the expression of a symbol, a new symbol
was encountered. TXT2BIN ran out of memory when it tried
to store the current symbol information.
Out of symbol space
TXT2BIN ran out of memory while trying to store a symbol.
Make sure that you have enough conventional memory before
retrying.
Radix is out of range at column NNNNN
You have attempted to set the radix to a value of either
less than 2 or greater than 36.
Recursion detected at column NNNNN
TXT2BIN has found a symbol whose expression also contains
the same symbol. This results in a never-ending
recursion, preventing the expression from being processed
completely.
Examples:
(1) .DEFINE ad_infinitum "5678" <ad_infinitum>
"1234" <ad_infinitum>
Result: "1234" "5678" "5678" "5678" ...
(2) .DEFINE X "1" <Y>
.DEFINE Y "2" <X>
"3" <X> "4"
Result: "3" "1" "2" "1" "2" "1" "2" ...
This is a severe error. Examine the symbols for possible
recursion, and correct the problem before retrying the
program.
Symbol does not start with an alphabetic character at column
NNNNN
Check the first character of the symbol to make sure that
it starts with an alphabetic character (A-Z, a-z).
Unable to initialize symbol table
TXT2BIN was unable to properly set up the area where all
symbols will be stored during the conversion process.
This is a severe error, and may have been caused by a
lack of memory.
Unable to open file <filespec> for input
The source text file could not be opened. The possible
causes are:
(1) the file name was misspelled;
(2) the path name does not exist;
(3) the file exists in another drive/directory.
Unable to open file <filespec> for output
The target binary file could not be opened. Possible
causes are:
(1) the file already exists, with its attribute set
as READ-ONLY;
(2) the file is the name of a directory or volume
label.
Unable to open include file <filespec> for input
The include text file could not be opened. Possible
causes are:
(1) the file name was misspelled;
(2) the path name does not exist;
(3) the file exists in another drive/directory.
Unable to re-open file <filespec> for input
TXT2BIN tried to return to a text file to continue
processing, but could not open the file.
This is a severe error, so please contact the author if
you should encounter this message.
Unable to reposition pointer on file <filespec>
TXT2BIN tried to continue processing a text file from a
specific point in the file, but failed to do so.
This is a severe error, so please contact the author if
you should encounter this message.
Unexpected EOF (End-of-File)
TXT2BIN encountered the end-of-file marker without
reaching the end of a line. Make sure that the last line
of the text file ends with a carriage return character
and a line feed character.
Unknown directive at column NNNNN
You have specified the name of a directive which is not
currently supported by TXT2BIN.
Unknown symbol at column NNNNN
The symbol was not previously defined. Use a DEFINE
directive to describe the symbol and its expression.