This section lists all the possible errors that might occur when the 3.0 Help compiler is processing the RTF topic file(s).
R2001Unable to open bitmap file filename.
PROBLEM: The specified bitmap file could not be found or is not in a recognizable bitmap format. This is an MS-DOS file error or an out-of-memory condition.
RESULT: The Help file displays the “Unable to display picture” message in the compiled topic instead of the bitmap.
SOLUTION: Check to see if the file exists; if it does, check its format. If necessary save the file again in your paint or draw program, and then recompile.
R2003Unable to include bitmap 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: 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.
R2005Disk full.
PROBLEM: There is not enough disk space to write the Help file to disk.
RESULT: The compiler aborts the build.
SOLUTION: Create more space on the destination disk, and then recompile.
R2009Cannot use reserved DOS device name for file filename.
PROBLEM: The file has a reserved MS-DOS filename, such as COM1, LPT2, or PRN. This is an MS-DOS file error.
RESULT: The compiler ignores the file.
SOLUTION: Rename the file, and then recompile.
R2013Output file filename already exists as a directory.
PROBLEM: A directory in the Help project directory has the same name as the requested Help file. This is an MS-DOS file error.
RESULT: The compiler ignores the file.
SOLUTION: Move or rename the directory or the Help project file, and then recompile.
R2015Output file filename already exists as read-only.
PROBLEM: The Help compiler cannot overwrite files with a read-only attribute. For example, this error occurs if you rebuild an existing .HLP file and the .HLP file is read-only.
RESULT: The compiler aborts the build.
SOLUTION: Change the file’s read-only attribute if you want the Help compiler to overwrite the file; otherwise, rename the file.
R2017Path for file filename exceeds limit of 79 characters.
PROBLEM: The combined length of the path and filename must not be more than the MS-DOS limit of 79 characters.
RESULT: The compiler ignores the file.
SOLUTION: Shorten the path, and then recompile.
R2019Cannot open 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: The compiler ignores the file.
SOLUTION: Check to see if the file exists, and also check the amount of available memory.
R2021Cannot find 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: The compiler ignores the file.
SOLUTION: Check to see if the file exists, and also check the amount of available memory.
R2023Not enough memory to build Help file.
PROBLEM: The Help compiler does not have enough memory to complete the build process.
RESULT: The compiler does not create a Help file.
SOLUTION: To free memory, unload any unneeded applications, device drivers, and memory-resident programs. You can also turn off compression in the Help project file, replace any inline bitmaps pasted directly in the topic files with bitmap references, or compile under OS/2 rather than MS-DOS.
R2025File environment error.
PROBLEM: The compiler does not have enough available file handles to continue the build. This error is likely to occur if you are compiling in an MS-DOS box or if you are using Help Author and have Word for Windows running at the same time.
RESULT: The compiler aborts the build.
SOLUTION: If possible, increase the FILES setting in the CONFIG.SYS file to FILES=50. Then reboot your computer and recompile.
R2027Build tag tagname not defined in [BUILDTAGS] section of project file.
PROBLEM: The specified build tag has been assigned to a topic but not declared in the Help project file.
RESULT: The compiler ignores the build tag defined in the topic.
SOLUTION: Include the build tag in the [BUILDTAGS] section, and then recompile.
R2033Context string in Map section not defined in any topic.
PROBLEM: The compiler cannot find a context string listed in the [MAP] section in any of the topics in the build.
RESULT: The compiler ignores the line in the [MAP] section. If the application uses that number in the WinHelp function, Help will display the “Help topic not found” error message,
SOLUTION: Check to be sure that all the context strings listed in the [MAP] section are assigned to topics included in the build and that they are all spelled correctly. Then recompile.
R2035Build expression missing from project file.
PROBLEM: The topics have build tag footnotes, but there is no BUILD= expression in the Help project file.
RESULT: The compiler includes all topics in the build.
SOLUTION: Add a build expression to the Help project file and recompile if you want your build tags to work. Otherwise, you can safely ignore this message.
R2037File filename cannot be created, due to previous error(s).
PROBLEM: The compiler cannot continue because there are topics remaining to be processed.
RESULT: The compiler does not create a Help file.
SOLUTION: Correct the errors that preceded this error, and then recompile.
R2039Unrecognized table formatting in topic topicnumber of file filename.
PROBLEM: The compiler ignores table formatting that is unsupported in Help.
RESULT: The compiler aborts the build.
SOLUTION: Reformat the entries as text paragraphs with hanging indents or as side-by-side paragraphs, and then recompile.
R2041Jump context_string unresolved in topic topicnumber of file filename.
PROBLEM: The specified topic contains a context string that identifies a nonexistent topic.
RESULT: The Help application displays the “Help topic not found” error message when the user chooses a hot spot with the unresolved context string.
SOLUTION: Check the topic for spelling errors in the context string, and also check to see if the requested topic is included in the build.
R2043Hotspot text cannot spread over paragraphs.
PROBLEM: A paragraph marker is part of the hidden text.
RESULT: The compiler ignores the paragraph marker formatted as hidden text, so the two paragraphs will run together.
SOLUTION: Reformat the paragraph marker as plain text, and then recompile.
R2045Maximum number of tab stops reached in topic topicnumber of file filename.
PROBLEM: The maximum number of custom tab stops that can be defined for a paragraph is 32.
RESULT: The compiler uses the default tab stops after the 32nd tab.
SOLUTION: Reduce the number of tab stops to 32 or fewer, and then recompile.
R2047File filename not created.
PROBLEM: There are no topics to compile, or the build expression is false for all topics.
RESULT: The compiler does not create a Help file.
SOLUTION: Add a topic filename to the [FILES] section in the Help project file, or change the build expression so that all topics are not excluded from the build, and then recompile.
R2049Context string text too long in topic topicnumber of file filename.
PROBLEM: The context string hidden text cannot exceed 64 characters.
RESULT: The compiler ignores the context string.
SOLUTION: Shorten the context string, and then recompile.
R2051File filename is not a valid RTF topic file.
PROBLEM: The specified file is not an RTF file.
RESULT: The compiler ignores the file.
SOLUTION: Make sure that you save the topic as RTF from your word processor, and then recompile.
R2053Font fontname in file filename not in RTF font table.
A font not defined in the RTF header has been entered into the topic. The compiler uses the default system font.
R2055File filename is not a usable RTF topic file.
PROBLEM: The specified file contains a valid RTF header, but the content is not RTF or is corrupted.
RESULT: The compiler ignores the file.
SOLUTION: Resave the topic as RTF from your word processor, and then recompile.
R2057Unrecognized graphic format in topic topicnumber of file filename.
PROBLEM: The compiler supports only Windows bitmaps (.BMP) and Windows device-independent bitmaps (.DIB).
RESULT: The compiler ignores the graphic.
SOLUTION: Make sure that you have not used a metafile, a Macintosh picture format, or some other unsupported graphic format.
R2059Context string identifier already defined in topic topicnumber of file filename.
PROBLEM: There is more than one context-string identifier footnote for the specified topic.
RESULT: The compiler uses the identifier defined in the first # footnote.
SOLUTION: Remove one of the context string identifiers, and then recompile.
R2061Context string contextname already used in file filename.
PROBLEM: The specified context string was previously assigned to another topic.
RESULT: The compiler ignores the duplicate context string, and the topic has no identifier.
SOLUTION: Change the second context string so that it is unique, and then recompile.
R2063Invalid context-string identifier for topic topicnumber of file filename.
PROBLEM: The context string footnote contains non-alphanumeric characters or is empty.
RESULT: The compiler does not assign the topic an identifier.
SOLUTION: Change the characters in the context string so that it is valid, and then recompile.
R2065Context string defined for index topic is unresolved.
PROBLEM: The Index topic defined in the Help project file could not be found.
RESULT: The compiler uses the first topic in the build as the Index.
SOLUTION: Compare the context string in the INDEX option to the context string used in the Index topic to be sure they are the same. Change one of the strings to match the other, and then recompile.
R2067Footnote text too long in topic topicnumber of file filename.
PROBLEM: The footnote text cannot exceed the limit of 1000 characters.
RESULT: The compiler ignores the footnote.
SOLUTION: Reduce the length of the footnote text, and then recompile.
R2069Build tag footnote not at beginning of topic topicnumber of file filename.
PROBLEM: The build tag footnote marker, if used, has to be the first character in the topic.
RESULT: The compiler ignores the build tag footnote, and the topic is not assigned a build tag.
SOLUTION: Move the build tag footnote to the beginning of the topic, before other footnotes, and then recompile.
R2071Footnote text missing in topic topicnumber of file filename.
PROBLEM: The specified topic contains a footnote that has no characters.
RESULT: The compiler ignores the footnote.
SOLUTION: Add characters to the footnote, and then recompile.
R2073Keyword string is null in topic topicnumber of file filename.
PROBLEM: There are no characters in the keyword footnote.
RESULT: The compiler ignores the keyword footnote, and the topic does not have any keywords.
SOLUTION: Open the footnote window and type some keywords next to the keyword footnote character for the topic, and then recompile.
R2075Keyword string too long in topic topicnumber of file filename.
PROBLEM: The keyword string exceeds the limit of 255 characters.
RESULT: The compiler ignores the keyword footnote.
SOLUTION: Shorten the length of the keyword string, or add another keyword footnote for the extra keywords, and then recompile.
R2077Keyword(s) defined without title in topic topicnumber of file filename.
PROBLEM: The topic has a keyword assigned to it, but no title.
RESULT: The topic will appear as >>Untitled Topic<< in the Search dialog box and in the history list.
SOLUTION: Add a topic title footnote to the topic if you want a title to appear in the Search dialog box when the user selects this keyword.
R2079Browse sequence string is null in topic topicnumber of file filename.
PROBLEM: The browsesequence footnote for the specified topic contains no sequence characters.
RESULT: The compiler ignores the browse sequence footnote.
SOLUTION: Add sequence characters to the browse sequence footnote, and then recompile.
R2081Browse sequence string too long in topic topicnumber of file filename.
PROBLEM: The browse sequence string exceeds the limit of 128 characters.
RESULT: The compiler ignores the browse sequence footnote.
SOLUTION: Shorten the length of the sequence string, and then recompile.
R2083Missing sequence number in topic topicnumber of file filename.
PROBLEM: A browsesequence number ends with a colon (:) for the specified topic.
RESULT: The compiler ignores the browse sequence footnote.
SOLUTION: Remove the colon or enter a minor sequence number, and then recompile.
R2085Sequence number already defined in topic topicnumber of file filename.
PROBLEM: A browse-sequence footnote already exists for the specified topic.
RESULT: The compiler uses the first browse sequence footnote and ignores the duplicate footnote.
SOLUTION: Remove the duplicate browse sequence footnote, and then recompile.
R2087Build tag too long.
PROBLEM: A build tag for the specified topic exceeds the limit of 32 characters.
RESULT: The compiler ignores the build tag assigned to the topic.
SOLUTION: Shorten the length of the build tag to 32 or fewer characters, and then recompile.
R2089Title string null in topic topicnumber of file filename.
PROBLEM: The title footnote for the specified topic contains no characters.
RESULT: The compiler ignores the title footnote, and the topic does not have a title.
SOLUTION: Open the footnote window and type the title string next to the topic title footnote character for the topic, and then recompile.
R2091Title too long in topic topicnumber of file filename.
PROBLEM: The title for the specified topic exceeds 128 characters.
RESULT: The compiler truncates the title string at 128 characters.
SOLUTION: Shorten the length of the title string, and then recompile.
R2093Title titlename in topic topicnumber of file filename used previously.
PROBLEM: The specified title has previously been assigned to another topic.
RESULT: The compiler uses the first title and ignores the duplicate title.
SOLUTION: Remove the duplicate title, and then recompile.
R2095Title defined more than once in topic topicnumber of file filename.
PROBLEM: There is more than one title footnote in the specified topic.
RESULT: The compiler uses the first title footnote and ignores the duplicate title footnote.
SOLUTION: Remove the duplicate title footnote, and then recompile.
R2501Using old key-phrase table.
PROBLEM: The compiler found an existing key-phrase table for the Help file you are building, and the Help project file does not specify not to use the table.
RESULT: The compiler uses the key-phrase table that was generated from an earlier build, instead of creating a new table.
SOLUTION: To achieve maximum compression during a build, you must delete the old key-phrase table (.PH file) before each recompilation.
R2503Out of memory during text compression.
PROBLEM: The compiler encountered a memory limitation during compression.
RESULT: The Help compiler continues the build without compressing the Help file.
SOLUTION: Free more memory and then recompile. For suggestions on how to free more memory fo the build, refer to the “Getting Around Memory Problems” in Chapter 17. If you can’t overcome your memory constraints, you may have to compile without compression or remove some of the graphics in the topic files.
R2505File environment error during text compression.
PROBLEM: The compiler does not have enough available file handles to compress the Help file. This error is likely to occur if you are compiling in an MS-DOS box or if you are using Help Author and have Word for Windows running at the same time.
RESULT: The Help compiler continues the build without compressing the Help file.
SOLUTION: If possible, increase the FILES setting in the CONFIG.SYS file to FILES=50. Then reboot your computer and recompile.
R2507DOS file error during text compression.
PROBLEM: The compiler encountered a problem accessing a disk file while it was compressing the Help file. This is an MS-DOS file error.
RESULT: The Help compiler continues the build without compressing the Help file.
SOLUTION: Check to make sure you have enough free disk space or look for other MS-DOS related problems, and then recompile.
R2509Error during text compression.
PROBLEM: One of the three compression errors—R2503, R2505, or R2507—has occurred.
RESULT: The Help compiler continues the build without compressing the Help file.
SOLUTION: Check the solutions section for each of the other errors to see what the problem might be. When you have corrected the problem, recompile.
R2701Internal error.
PROBLEM: The compiler is unable to create the data structure (b-tree) containing all the titles in the Help file.
RESULT: The compiler aborts the build.
SOLUTION: Contact Microsoft Product Support Services.
R2703Internal error.
PROBLEM: The compiler cannot create the bitmap file because of a low-memory condition, lack of sufficient free disk space, or insufficient file handles.
RESULT: The compiler aborts the build.
SOLUTION: Contact Microsoft Product Support Services.
R2705Internal error.
PROBLEM: The phrase file used for compression has disappeared between the time it is created (or last checked) and when the compiler needs to use it. This will likely occur if the hard disk drive is low on disk space or if you are building the Help file over a network.
RESULT: The compiler aborts the build.
SOLUTION: Contact Microsoft Product Support Services.
R2707Internal error.
PROBLEM: The compiler has encountered a disk error other than “out of memory,” “out of disk space,” or “out of file handles.” This error may indicate a problem with your hard disk drive, such as bad sectors or too many files in a directory.
RESULT: The compiler aborts the build.
SOLUTION: Contact Microsoft Product Support Services.
R2709Internal error.
PROBLEM: The compiler can’t open the output system file. This problem should only occur if you are using a nonstandard release or beta release of Help version 3.0.
RESULT: The compiler aborts the build.
SOLUTION: Contact Microsoft Product Support Services.