This section lists all the possible errors that might occur when the 3.0 Help compiler is processing the Help project file.
P1001Unable to read file filename.
PROBLEM: The specified file could not be found or is unreadable. This is an MS-DOS file error or an out-of-memory condition.
RESULT: If the file not found is an RTF topic file, the compiler ignores the file. If the file is a bitmap file, the built Help file displays the “Unable to display picture” message in the topic instead of the bitmap.
SOLUTION: Check to see if the file exists, and also check the amount of available memory.
P1003Invalid path specified in Root option.
PROBLEM: The compiler cannot find the path specified by the ROOT option.
RESULT: The compiler uses the current working directory.
SOLUTION: Correct the path in the ROOT option, and then recompile.
P1005Path and filename exceed limit of 79 characters.
PROBLEM: The combined length of the path and filename must not be more than the MS-DOS limit.
RESULT: The compiler ignores the file.
SOLUTION: Shorten the path, and then recompile.
P1007Root path exceeds maximum limit of 66 characters.
PROBLEM: The specified root path exceeds the MS-DOS limit.
RESULT: The compiler ignores the path and uses the current working directory.
SOLUTION: Shorten the path, and then recompile.
P1009[FILES] section missing.
PROBLEM: The [FILES] section is required.
RESULT: The compiler aborts the build.
SOLUTION: Create a [FILES] section that lists the topic files to include in the build, and then recompile.
P1011Option optionname previously defined.
The specified option was defined previously. The compiler ignores the attempted redefinition.
P1013Project file extension cannot be .HLP.
PROBLEM: You cannot specify a Help project file with a .HLP extension. Project files must use the .HPJ extension.
RESULT: The compiler aborts the build.
SOLUTION: Rename the Help project file, and then recompile.
P1015Unexpected end-of-file.
PROBLEM: The compiler has unexpectedly come to the end of the Help project file. There may be an open comment in the Help project file or in an include file.
RESULT: The compiler aborts the build.
SOLUTION: Close any open comments within the Help project file, and then recompile.
P1017Parameter exceeds maximum length of 128 characters.
PROBLEM: An option, context name or number, build tag, or other parameter on the specified line exceeds the limit of 128 characters.
RESULT: The compiler ignores the line.
SOLUTION: Shorten the line, and then recompile.
P1021Context number already used in [MAP] section.
PROBLEM: A context number in the [MAP] section of the Help project file was previously mapped to a different context string.
RESULT: The compiler ignores the line with the duplicate context number.
SOLUTION: Check all context numbers to make sure that they are unique. Remove or reassign any duplicate context numbers, and then recompile.
P1023Include statements nested too deeply.
PROBLEM: The #include statement on the specified line exceeds the maximum of five include levels.
RESULT: The compiler aborts the build.
SOLUTION: Simplify the #include statement so that it nests fewer than five include levels, then recompile.
P1025Section heading sectionname unrecognized.
PROBLEM: The Help project file includes a section heading that the compiler does not recognize or does not support.
RESULT: The compiler ignores the section heading.
SOLUTION: Check all bracketed headings in the Help project file for typographical or other errors. Fix the section heading, and then recompile.
P1027Bracket missing from section heading sectionname.
PROBLEM: The right bracket (]) is missing from the specified section heading.
RESULT: The compiler ignores the section heading on this line.
SOLUTION: Insert the right section heading bracket, and then recompile.
P1029Section heading missing.
PROBLEM: The section heading on the specified line is not complete, or the first entry in the Help project file is not a section heading.
RESULT: The compiler ignores the section heading on this line and all succeeding lines until it encounters a valid section heading.
SOLUTION: Insert a valid section heading at the appropriate place in the Help project file, and then recompile.
P1030Section sectionname previously defined.
PROBLEM: The compiler found more than one section with the specified heading in the Help project file.
RESULT: The compiler ignores the duplicate section and continues from the next valid section heading.
SOLUTION: Remove or rename one of the duplicate section headings, and then recompile.
P1031Maximum number of build tags exceeded.
PROBLEM: The maximum number of build tags that can be defined is 32.
RESULT: The compiler ignores the additional tags.
SOLUTION: Reduce the number of build tags to 32 or fewer, and then recompile.
P1033Duplicate build tag in [BUILDTAGS] section.
PROBLEM: A build tag appears more than once in the [BUILDTAGS] section.
RESULT: The compiler uses the first build tag and ignores the duplicate build tag.
SOLUTION: Remove or rename one of the duplicate build tags, and then recompile.
P1035Build tag length exceeds maximum.
PROBLEM: The build tag on the specified line exceeds the limit of 32 characters.
RESULT: The compiler ignores the build tag.
SOLUTION: Shorten the build tag to 32 or fewer characters, and then recompile.
P1037Build tag tagname contains invalid characters.
PROBLEM: Build tags can contain only alphanumeric characters or the underscore (_) character.
RESULT: The compiler ignores the line with invalid characters.
SOLUTION: Correct the build tag so that it contains only valid characters, and then recompile.
P1039[BUILDTAGS] section missing.
PROBLEM: The BUILD option declares a conditional build, but there is no [BUILDTAGS] section in the Help project file.
RESULT: The compiler includes all topics in the build.
SOLUTION: Add a [BUILDTAGS] section to the Help project file, if you want to perform a conditional build, and then recompile.
P1043Too many tags in Build expression.
PROBLEM: The Build expression on the specified line has used more than the maximum of 20 build tags.
RESULT: The compiler ignores the line.
SOLUTION: Reduce the number of build tags to 20 or fewer, and then recompile.
P1045[ALIAS] section found after [MAP] section.
PROBLEM: When used, the [ALIAS] section must precede the [MAP] section in the Help project file.
RESULT: The compiler ignores the [ALIAS] section.
SOLUTION: Move the [ALIAS] section so that it precedes the [MAP] section, and then recompile.
P1047Context string contextname already assigned an alias.
PROBLEM: The specified context string has already been assigned an alias in the [ALIAS] section. A context string can have only one alias. That is, you cannot map a=b and then a=c in the [ALIAS] section.
RESULT: The compiler ignores the attempted reassignment on this line.
SOLUTION: Correct the alias string mapping, and then recompile.
P1049Alias string aliasname already assigned.
PROBLEM: You cannot alias an alias. That is, an alias string cannot, in turn, be assigned another alias. You cannot map a=b and then b=c in the [ALIAS] section.
RESULT: The compiler ignores the attempted reassignment on this line.
SOLUTION: Correct the alias string mapping, and then recompile.
P1051Context string contextname cannot be used as alias string.
PROBLEM: A context string that has been assigned an alias cannot be used later as an alias for another context string. That is, you cannot map a=b and then c=a in the [ALIAS] section.
RESULT: The compiler ignores the attempted reassignment on this line.
SOLUTION: Correct the alias string mapping, and then recompile.
P1053Maximum number of font ranges exceeded.
PROBLEM: The maximum number of font ranges that can be specified is five.
RESULT: The compiler ignores additional ranges.
SOLUTION: Remove the additional font ranges so that there are five or fewer, and then recompile.
P1055Current font range overlaps previously defined range.
PROBLEM: A font size range overlaps a previously defined mapping.
RESULT: The compiler uses the first range and ignores the second mapping.
SOLUTION: Adjust one or both of the font ranges to remove any overlapping.
P1056Unrecognized font name in Forcefont option.
PROBLEM: The compiler has encountered a font name that it does not recognize or support.
RESULT: The compiler ignores the font name and uses the default MS Sans Serif font.
SOLUTION: Change the font name to a supported font, and then recompile. For the list of supported fonts, refer to Chapter 16, “The Help Project File.”
P1057Font name too long.
PROBLEM: Font names cannot exceed 20 characters.
RESULT: The compiler ignores the option on this line.
SOLUTION: Shorten the font name to 20 or fewer characters, and then recompile.
P1059Invalid multiple-key syntax.
PROBLEM: The MULTIKEY option must specify a single capital letter other than the letter K.
RESULT: The compiler ignores the attempted keyword-table assignement on this line.
SOLUTION: Correct the syntax, and then recompile. The correct syntax is:
MULTIKEY=char
P1061Character already used.
PROBLEM: A character used for indicating the alternate keyword table (MULTIKEY=char) was previously used.
RESULT: The compiler ignores the duplicate keyword-table assignment on this line.
SOLUTION: Change the duplicate character to one that has not been used, and then recompile.
P1063Characters ‘K’ and ‘k’ cannot be used.
PROBLEM: These characters are reserved for Help’s standard keyword table.
RESULT: The compiler ignores the attempted keyword-table assignment on this line.
SOLUTION: Choose another character for the alternate keyword table, and then recompile.
P1065Maximum number of keyword tables exceeded.
PROBLEM: The [OPTIONS] section contains more than five MULTIKEY entries, which exceeds the limit of five keyword tables.
RESULT: The compiler ignores the additional keyword tables.
SOLUTION: Reduce the number of keyword tables to five or fewer, and then recompile.
P1067Equal sign missing.
PROBLEM: An entry in the [OPTIONS] section is missing the equal sign, or it has some other syntax error.
RESULT: The compiler ignores the invalid option on this line.
SOLUTION: Check the syntax of each option used in the [OPTIONS] section. Fix the incorrect option, and then recompile. For the correct syntax, refer to Chapter 16, “The Help Project File.”
P1069Context string missing.
PROBLEM: A line in the [MAP] or [ALIAS] section is missing a context string before the equal sign.
RESULT: The compiler ignores the line with the invalid context string.
SOLUTION: Check all context strings to the left of the equal sign. Correct any missing or invalid entries, and then recompile.
P1071Incomplete line in sectionname section.
PROBLEM: An entry in the specified section is incomplete.
RESULT: The compiler ignores the incomplete line.
SOLUTION: Check the section for any incomplete lines and correct them. Then recompile.
P1073Unrecognized option in [OPTIONS] section.
PROBLEM: The compiler does not recognize or support the specified option.
RESULT: The compiler ignores the unrecognized option.
SOLUTION: Check the [OPTIONS] section for typing errors or invalid options, and then recompile.
P1075Invalid build expression.
PROBLEM: The syntax used in the build expression on the specified line contains one or more logical or syntax errors.
RESULT: The compiler ignores the line with the invalid expression.
SOLUTION: Correct the entry, and then recompile. For the correct syntax and information about build expressions, refer to Chapter 16, “The Help Project File.”
P1077Warning level must be 1, 2, or 3.
PROBLEM: The warning reporting level can be set only to 1, 2, or 3.
RESULT: The compiler uses full reporting (level 3).
SOLUTION: Correct the entry, and then recompile.
P1079Invalid compression option.
PROBLEM: The COMPRESS option specifies an incorrect value.
RESULT: The compiler uses the default value off.
SOLUTION: Correct the entry, and then recompile. The correct syntax is:
COMPRESS=[off, 0, no, false] or [on, 1, yes, true]
P1081Invalid title string.
PROBLEM: The TITLE option defines a string that is empty or contains more than 32 characters.
RESULT: The compiler truncates the title at 32 characters.
SOLUTION: Add a title if the option is empty or shorten the title if it is too long, and then recompile.
P1083Invalid context identification number.
PROBLEM: A context number in the [MAP] or [ALIAS] section is empty or contains invalid characters.
RESULT: The compiler ignores the line with the invalid context number.
SOLUTION: Check the format of all context numbers. Context numbers can be specified as decimal or hexadecimal. Correct any invalid numbers, and then recompile.
P1085Unrecognized text.
PROBLEM: The compiler found some text in the Help project file that it can’t recognize.
RESULT: The compiler ignores the line with the unrecognized text.
SOLUTION: Remove the unsupported text from the Help project file, and then recompile.
P1086Invalid font-range syntax.
PROBLEM: The font range syntax used is invalid. A font range consists of a low and high point size, separated by a hyphen (-).
RESULT: The compiler ignores the option.
SOLUTION: Correct the syntax, and then recompile. The correct syntax is:
MAPFONTSIZE=m[-n]:p
P1089Unrecognized sort ordering.
PROBLEM: You have specified an ordering that is not supported by the compiler.
RESULT: The compiler uses the default English (U.S.) sorting order.
SOLUTION: Correct the entry, and then recompile. The correct syntax is:
LANGUAGE=scandinavian