The following messages result from problems in the use of Word for Windows formatting in one or more topic files.
4616 File 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.
4639 Error in file filename at byte offset 0xoffset.
PROBLEM: The specified file contains unrecognized RTF at that byte offset. Unrecognized RTF includes any formatting the Help compiler does not recognize, including mismatched braces or nonstandard RTF produced by applications other than Word for Windows. This message should not appear if Word for Windows, Word for the Macintosh, or PCWord is used.
RESULT: The compiler aborts the build.
SOLUTION: Open the file in Word for Windows and save the file again as RTF, and then recompile. If you are using Word for the Macintosh, transfer the file to the PC again, and then recompile. If the problem persists, open the file without converting it to .DOC format, and look for errors in the source RTF.
4649 File filename contains more than 32767 topics.
PROBLEM: The maximum number of topics allowed in one RTF file is 32,767.
RESULT: The compiler aborts the build.
SOLUTION: Reduce the number of topics in the file by dividing it into two or more topic files, and then recompile.
4652 Table formatting too complex.
PROBLEM: The compiler encountered a table with borders, shading, or right justification.
RESULT: The compiler ignores the formatting.
SOLUTION: Remove the unsupported formatting, and then recompile.
4662 Side by side paragraph formatting not supported.
PROBLEM: The side-by-side paragraph formatting is not supported in Windows Help version 3.1.
RESULT: The compiler ignores the side-by-side paragraphs.
SOLUTION: Convert the side-by-side paragraphs to a table by opening the file in Word for Windows and saving it.
4671 Table contains more than 32 columns.
PROBLEM: The maximum number of columns in one table is 32. Some word processors may have different limits for the number of columns supported.
RESULT: The compiler treats the additional columns as one table cell.
SOLUTION: Reduce the number of columns to 32 or fewer, and then recompile.
4680 Font fontname in file filename not in RTF font table.
PROBLEM: A font not defined in the RTF header has been entered into the topic.
RESULT: The compiler uses the default system font.
SOLUTION: Check to be sure the font you are using is supported by the word processor. Then save the file again as RTF and recompile.
4692 Unrecognized graphic format.
PROBLEM: The compiler supports only Windows bitmaps (.BMP), Windows device-independent bitmaps (.DIB), Windows metafiles (.WMF), segmented hypergraphics (.SHG), and multiresolution bitmaps (.MRB).
RESULT: The compiler ignores the graphic.
SOLUTION: Make sure that you have not used Macintosh picture format or some other unsupported graphic format.
4733 Hidden page break.
PROBLEM: The page break is part of the hidden text.
RESULT: The compiler ignores the page break formatted as hidden text, so the two topics will not be separated.
SOLUTION: Reformat the page break as plain text and recompile.
4753 Hidden paragraph.
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 recompile.
4763 Hidden carriage return.
PROBLEM: A carriage return is part of the hidden text.
RESULT: The compiler ignores the carriage return formatted as hidden text and does not create a new line.
SOLUTION: Reformat the carriage return as plain text and recompile.
4774 Paragraph exceeds limit of 64K.
PROBLEM: A single paragraph has more than 64K of text or 64K of graphics. If the paragraph contains an inline graphic (pasted directly into the topic in Word for Windows) or a bitmap reference stored with data (bmcwd, for example), the paragraph size cannot exceed 64K. This limit does not apply to graphics stored separately from the topic data using the standard bitmap references bmc, bml, or bmr.
RESULT: The compiler aborts the build.
SOLUTION: Replace any inline graphics with bitmap references, or reduce the amount of text in the paragraph, or reduce the size of the graphic, and then recompile.
4792 Non-scrolling region defined after scrolling region.
PROBLEM: A paragraph that was authored as Keep With Next is not the first paragraph in the topic.
RESULT: The compiler ignores the Keep With Next attribute; the paragraph is treated as regular text and will be part of the topic text displayed in the scrolling region.
SOLUTION: Format the first paragraph(s) as Keep With Next and remove the Keep With Next formatting from the subsequent paragraphs. Then recompile.
4813 Non-scrolling region crosses page boundary.
PROBLEM: The Keep With Next paragraph formatting crosses a page break boundary.
RESULT: The topic includes a nonscrolling region, whether or not one is intended.
SOLUTION: Check the file to be sure that all topics end with a hard carriage return immediately before the page break. Remove the Keep With Next formatting attribute from any unwanted paragraphs, and then recompile.
4000 UNKNOWN ERROR, Contact Microsoft Product Support Services
PROBLEM: This error message is the equivalent of an assertion failure.
RESULT: The compiler aborts the build.
SOLUTION: Contact Microsoft Product Support Services.