Contents
MediaView Compiler Help

This title provides help information for the MediaView compiler. Click one of the topics listed below to view the information.

Overviews

MediaView Compiler

Command-Line Options

Menus

File Menu

Compile Menu

Help Menu

Procedures

Opening a Project

Starting the Compile

Stopping the Compile

Messages

Compiler Messages


MediaView Compiler

The MediaView compiler builds the title (.M12) file from the set of source files for the project. When creating the title, the compiler uses the options specified in the project (.MVP) file, which lists the RTF files, baggage files, window definitions, and other settings for the project.

When compiling a title, make sure all source files are closed. For example, if you have any RTF files open in Word, save those files and close the Word sessions before starting compilation.

Error and warning messages are displayed in the message log. You can save the message log at any time during compilation. For descriptions of error and warning messages, choose the Index button and select the Error Messages index.


Command-Line Options

The MediaView compiler provides command-line options that provide different ways to start the compiler. The compiler command line has the following syntax:

WMVC [project.mvp] [options...]

You can specify an optional project-file name as well as the following options:

Option	Description

/BATCH	Builds the title and then closes the compiler automatically. The compiler stores compilation errors in a log file with the same base name as the project file and the filename extension .LOG. This option has the same effect as and overrides the BATCH option in the project file.

/MAKE=option	Specifies whether the compiler builds only the title, only the index, or box. Specify one of the following names for option:

COMPILE	Builds the title but not the index.

BAGGAGE	Builds the baggage portion of the file system, but not the title.  You must have already built the title.

INDEX	Builds the index but not the title. You must have already built the title.

FULL	Build both the title and the index.

COMPILE	This option has the same effect as and overrides the MAKE option in the project file.

SYSTEM	Builds the file system for the title.

/AUTOSAVE	Error log is automatically saved when compilation is finished.


File Menu Options

The following options are available from the File menu:

Option	Description

Open	Opens a MediaView project (.MVP) file.

Close	Closes the current project file.

Exit	Closes the compiler and cancels any compile in progress.


Compile Menu Options

The following options are available from the Compile menu:

Option	Description

Start	Starts compiling the current project.

Halt	Stops any compile in progress.


Help Menu Options

The following options are available from the Help menu:

Option	Description

Contents	Displays the Contents topic of this help file.

About	Displays information about the MediaView compiler.


Opening a Project

MediaView titles store project information in a project (.MVP) file. Before compiling a title, you must open the project file.

To open a project file

1	From the File menu, choose Open.

2	Select a project (.MVP) file.

3	Choose OK.


Staring the compile
Starting the Compile

After opening the project file, you can start the compile.

To start compiling

From the Compile menu, choose Start.

- Or -

Press F5.


Stopping the Compile

During compilation, you might choose to stop the compile to fix errors or to perform other tasks with the source files.

To stop compiling

From the Compile menu, choose Halt.

- Or -

Press SHIFT+ESC.


Saving the Error Log

You can save the error log at any time during or after the compile. You can save the log if the compiler has displayed messages in the log.

To stop compiling

1	From the File menu, choose Save Log.

- Or -

Press CTRL+S.

2	Select a file in which to save the error messages.

3	Choose OK.


MediaView Compiler Messages

Heres a list of the MediaView compiler error messages. Click on a message name to see help on that message.  You can also view an error message by pressing the Search button above and typing in the number of the error you wish to view.

1000   2000   3000   4000   5000   6000   7000   8000   9000   30,000

1000

1019: Project file extension cannot be .M12.

1023: String too long; truncating.

1030: File name exceeds limit of 255 characters.

1079: Out of file handles.

1081: Bad command line flag '%s'.

1083: Unknown command line flag.

1091: Baggage file bears reserved extension; replacing with '.BAG'

1100: Cannot open file '%s':  permission denied.

1150: Cannot overwrite file '%s'.

1170: File '%s' is a directory.

1190: Cannot use reserved DOS file name '%s'.

1230: File '%s' not found.

1292: File '%s' is not a valid bitmap.

1293: Embedded bitmap statement with no filename specified.

1319: Disk full.

1513: Bitmap name '%s' duplicated.

1536: Not enough memory to compress bitmap '%s'.

1540: Error creating |GMACROS subfile.

1541: Cannot initiate group.

1551: Cannot add group ID to group.

1561: Cannot build group.

1571: Cannot update |SYSTEM subfile.

1581: Sort failure.

1599: To build index/baggage only, the file system must already exist.

1609: Produced file will lack full-text index.

1617: Error opening .MVP file for scanning; another instance may have a lock.

1621: Bad reference to subfile (name too long): %s

1631: MAKE command line was set to an unsupported value.  Defaulting to MAKE=FULL.

1651: File input/output error

1661: Error loading baggage file: %s

1700: Unknown error matching return codes; Contact Microsoft Product Support Services.");

1709: Error opening file: %s

2000

2011: Unterminated #IGNORE directive.

2030: Comment starting at line %d unclosed at end of file.

2050: Invalid #include syntax.

2091: Bracket missing from section heading [%s].

2111: Section heading missing.

2131: Invalid OPTIONS syntax: 'option=value' expected.

2151: Incomplete line in [%s] section.

2161: Bad syntax in section heading.

2171: Unrecognized text.

2191: Section heading [%s] unrecognized.

2214: Line in ..MVP file exceeds length limit of 2047 characters.

2221: Could not load default breaker descriptions from resource file.

2287: [OPTIONS] should precede [FILES].

2291: Section [%s] previously defined.

2305: No valid files in [FILES] section.

2311: Memory allocation failure during processing of extra section option.

2352: Context string exceeds maximum length; truncating: %s

2361: Error accessing context resolution file.

2511: Unrecognized option '%s' in [OPTIONS] section.

2532: Option '%s' previously defined.

2550: Invalid path '%s' in option.

2570: Path in %s option exceeds maximum characters.

2651: Font name exceeds limit of 20 characters.

2652: Unrecognized font name '%s' in FORCEFONT option.

2661: Bad keyword footnote syntax.

2671: Duplicate keyword specification character.

2681: Null keyword footnote.

2691: Keyword set specification character not recognized.

2701: Missing '=' in [KEYINDEX] section string.

2711: Bad syntax in [KEYINDEX] section.

2721: Bad title specification for keyword set.

2731: Trailing garbage in [KEYINDEX] section string.

2741: Bad keyword set specifier.

2751: Keyword set title too long.

2831: System resource failure extracting text for phrase compression.

2832: COMPRESS option must be YES or 'NO'.

2841: Error constructing phrase file.

2842: OPTCDROM option must be 'TRUE' or 'FALSE'.

2852: Invalid TITLE option.

2893: WARNING option must be 1, 2, or 3.

2911: Invalid icon file '%s'.

2932: Copyright string exceeds limit of 50 characters.

2941: Batch option, if specified, should be set to 'TRUE' or 'FALSE'

2971: Make option, if specified, must be set to 'FULL', 'COMPILE', or 'INDEX'.

2981: System option set to unrecognized and unsupported value.

3000

3011: Maximum of 32 build tags exceeded.

3031: Build tag length exceeds 32 characters.

3051: Build tag '%s' contains invalid characters.

3076: [BUILDTAGS] section missing.

3096: Build expression too complex.

3116: Invalid build expression.

3133: Duplicate build tag in [BUILDTAGS] section.

3152: Build tag '%s' not defined in [BUILDTAGS] section.

3178: Build expression missing from project file.

3511: Macro '%s' exceeds limit of 512 characters.

4000

4011: Context string '%s' already used.

4031: Invalid context string '%s'.

4056: Unresolved context string specified in CONTENTS option.

4072: Context string/hotspot macro exceeds limit of 512 characters.

4005: Error creating context cross-check file.

4113: Unresolved jump or popup '%s'.

4131: Hash conflict.

4196: Jumps and lookups not verified.

4211: Footnote text exceeds limit of 1023 characters.

4251: Browse sequence not in first paragraph.

4272: Empty browse sequence string.

4281: File I/O error during browse sequence resolution.

4292: Missing sequence number.

4312: Browse sequence already defined.

4331: Title not in first paragraph.

4352: Empty title string.

4372: Title defined more than once.

4393: Title exceeds limit of 128 characters.

4412: Keyword string exceeds limit of 240 characters.

4433: Empty keyword string.

4441: File I/O error processing keywords.

4452: Keyword(s) defined without title.

4461: Error creating keyword system map file.

4471: Build tag footnote not at beginning of topic.

4492: Build tag exceeds limit of 32 characters.

4551: Entry macro not in first paragraph.

4561: Duplicate keyword: '%s.'

4616: File '%s' is not a valid RTF topic file.

4632: Invalid argment '%s' (Byte offset %lxh (topic #%ld) of %s)

4633: Unmatched curly brace: missing '%c' (Byte offset %lxh (topic #%ld) of %s)

4634: Error in RTF.

4649: File '%s' contains more than 32767 topics.

4652: Table formatting too complex.

4662: Side by side paragraphs not supported.

4671: Table contains more than 32 columns.

4680: Font %d not in RTF font table.

4686: Style sheet, '%s', redefined; first definition used.

4692: Unrecognized graphic format.

4733: Hidden page break.

4753: Hidden paragraph.

4763: Hidden carriage return.

4774: Paragraph containing %s exceeds limit of 32K.

4792: Non-scrolling region defined after scrolling region.

4813: Non-scrolling region crosses page boundary.

4821: Bad embedded window command syntax.

4823: Embedded window command too long.

4831: Error outputting embedded window.

4834: Embedded bitmap size limitation of 64k exceeded

4841: Syntax error in embedded {alias} command.

5000

5001: Error loading bitmap into file system: %s

5002: WARNIGNORE must be the first section in the project file.

5004: Build of |MVINDEX subfile failed!

5009: File system write failure!

5035: No topics encountered or processed.  File '%s' not created.

5059: Not enough memory to build system file.

5115: Write failed.

5139: Aborted by user.

6000

6000: UNKNOWN ERROR\n\t\tContact Microsoft Product Support Services

6019: Error initiating full-text index.

6029: Error loading phrase table.

6039: General failure initiating catalog.

6059: Indexing failure!

6069: Error building catalog.

6076: Error building full-text index.

6089: No default word breaker loaded.

6099: Unknown command encountered during indexing.

6109: Error loading word breakers."

6129: Can't load breaker DLL.

6139: Insufficient memory to initiate catalog.

6141: Bitmap unavailable for indexing.

6151: Bitmap corrupted: bad header.

6161: Can't unpack bitmap for indexing.

6171: Error indexing SHED coldspot text.

6176: No words in titled topics found to index; Result file will lack full-text index.

6181: Specified word breaker unable to process word: %s.

6182: Failure of Dll breaking function.

6211: Missing '=' in [WWHEEL] string.

6221: Bad [WWHEEL] string; left of '=' must be 'wwheel'

6231: Bad [WWHEEL] string syntax.

6247: Error initializing word wheel build structure.

6257: Error building word wheel subfile.

6267: Failure adding field string to word wheel.

6271: Failure initializing word wheel.

6281: Word wheel name overflow: %s

6291: Failure building word wheels.

6311: Missing '=' in [SEARCHDLG] section string.

6313: Bad [SEARCHDLG] section string; left of '=' must be 'ebox' or 'near'.

6321: Bad syntax in [SEARCHDLG] section string.

6331: Bad data type number in project file string.

6341: Bad title string in [SEARCHDLG] section string.

6351: Subfile name too long in project file string.

6361: Title specification too long in [SEARCHDLG] section string.

6371: Subfile specified in [SEARCHDLG] string without field specifier.

6381: Duplicate word wheel name.

6391: Extra parameters following subfile specification.

6401: Bad field specification in string.

6411: Extensions not allowed in word wheel subfile names; it will be stripped.

6421: '!' missing in icon subfile specification.

6431: Specified NEAR value not in positive integer range: %s.

6511: Index DLL: out of far memory.

6521: Index DLL: insufficient disk space.

6531: Index DLL: word too long.

6541: Index DLL: bad component version number.

6551: Index DLL: too many stop words in stop word file.

6561: Index DLL: too many documents.

6571: Index DLL: word exceeds maximum stem length.

6581: Index DLL: file I/O error reading.

6591: Index DLL: bad argument to API call.

6601: Index DLL: group id too large.

6611: Index DLL: hardware insufficiency detected.

6621: Index DLL: Internal assertion failure.

6631: Index DLL: specified file does not exist.

6641: Index DLL: bad or corrupted FS file.

6661: Index DLL: I/O seek error.

6671: Index DLL: I/O error during file creation.

6681: Index DLL: file I/O error writing.

6691: Index DLL: out of file handles.

6721: Index DLL: bad character table file format.

6731: Index DLL: bad dtype argument format.

6741: Index DLL: bad dtype value.

6751: Index DLL: bad word breaker reference.

6761: Index DLL: unmapped error.

7000

7113: Unterminated {vfld} token in the RTF source.

7123: Unterminated {dtype} token in the RTF source.

7131: Field string too long in RTF source.

7141: Bad selector into alias table.

7151: Numbers 1..9 are reserved field specifiers.  Ignoring reference.

7161: Field specs must be positive numbers.

7163: Unknown parameter in dtype string in absence of authoring platform.

7509: Failure sorting browse sequence strings.

7519: Cannot open browse sequence file.

7529: Failure sorting context string file.

7539: Cannot open context string file.

7549: Insufficient system resources for browse resolution.

8000

8001: Bad syntax in group specification.

8021: Bad left side of group specification.

8031: Bad right side of group specification.

8041: Entry/Exit macro specification overflow!

8051: Entry/Exit macro specification too long.

8061: Bad sequence of lines in [GROUPS] section.

8071: Duplicate group specification in [GROUPS] section.

8081: More than one group footnote set for this topic.

8091: Group footnote appeared too late in topic to be processed.

8101: Unterminated group footnote; group footnotes must end with ';'

8111: Browse sequence must be first group specified for a topic.

8131: Unable to add topic to browse sequence.

8141: Inconsistent use of sequence numbers in browse sequence.

8151: Bad default browse position; sequence spec must be :ddd...

8161: Bad group reference; all groups must be declared in the project file.

9000

9001: Missing '=' in breaker string.

9011: Bad syntax left-hand side of breaker string.

9021: Breaker index out of range.

9031: DLL name missing from right-hand side of breaker string.

9041: '!' missing from right-hand side of breaker string.

9051: Routine name missing from right-hand side of breaker string.

9061: Bad syntax right-hand side of breaker string.

9071: Breaker routine not available: %s

9077: Can't load breaker %d.

9107: Unable to initialize stop list.

9109: Cannot open stop list subfile: %s

9117: Cannot open specified DOS stop word file.

9127: Cannot build stop word subfile in result file system.

9137: Cannot open specified DOS character table file.

9139: Cannot open character table subfile: %s

9147: Cannot initialize character table.

9157: Cannot build character table subfile.

9262: Undeclared data type: %d; ignoring.

9272: Illegal data type specification.

9281: Error initializing localized operator table.

9291: Error building localized operator table.

9301: Could not open ligature table associated with dtype 0 character table; will use default.

9313: Ligature table associated with dtype 0 character table too big.  Using default instead.

9302: %s option must be ON/OFF

9303: Unknown option: %s

9304: Nested include not allowed

9507: Cannot open specified alias file.

9511: Entry in alias file exceeds maximum allowable length.

9521: Bad syntax for selector in alias entry.

9531: Illegal selector number in alias entry.

9541: Non-consecutive selector.

9551: Missing data type specifier in alias entry.

9561: Bad data type specifier in alias entry.

9571: Data type specifier out of range in alias entry.

9581: Data type not registered in .MVP file.

9591: Missing field specifier in alias entry.

9601: Bad field specifier in alias entry.

9611: Field specifier out of range in alias entry.

9613: Empty alias word list.

30,000

30009 - 30079: Various fatal errors

30009: Compilation failure during scratch file allocation.

30019: Compilation failure during main structure allocation.

30029: Compilation failure during main structure initialization.

30039: Compilation failure during .MVP parsing.

30049: Compilation failure due to file system verification error.

30059: Compilation failure during compression buffer allocation.

30069: Compilation failure during file system creation.

30079: Compilation failure during baggage loading.


1019: Project file extension cannot be .M12.

You cannot use a project file with a .M12 extension. Normally, project files have an .MVP extension.


1023: String too long; truncating.

On the specified line of the project file, the MediaView compiler encountered a string that is too long. The string was truncated to its maximum allowable length.


1030: File name exceeds limit of 255 characters.

The combined length of a filename and path is longer than maximum legal length. Shorten the path before recompiling.


1079: Out of file handles.

The MediaView compiler did not have enough file handles available to continue. Close one or more applications and recompile. If this doesnt work, increase the FILES= setting in your CONFIG.SYS file, then restart your computer and recompile.


1081: Bad command line flag '%s'.

The flag specified in the command line is not valid. Valid flags are \BATCH, \MAKE, and \SYSTEM. Check the flag and recompile.


1083: Unknown command line flag.

The MediaView compiler does not recognize the flag in the command line, or the syntax is incorrect. Check the flag and recompile.


1091: Baggage file bears reserved extension; replacing with '.BAG'

You cannot use the following extensions for files listed in the [BAGGAGE] section of your project file: .STP, .TBL, .GRP, .WWT, .WWM. Replace the extension with a different one.


1100: Cannot open file '%s':  permission denied.

The MediaView compiler didnt have the permission level required to open the requested file.


1150: Cannot overwrite file '%s'.

The MediaView compiler could not overwrite the specified file with the .M12 file because the specified file was read-only. Rename the project file or change the files attribute before recompiling.


1170: File '%s' is a directory.

A subdirectory of the project directory had the same name as the desired .M12 file. Move or rename the subdirectory. This error is caused by an MS-DOS file error.


1190: Cannot use reserved DOS file name '%s'.

A file had a device name such as COM1, LPT2, or PRN. Rename the file before recompiling.


1230: File '%s' not found.

The MediaView compiler could not find or read the specified file. This error can occur if the specified file does not exist in the project directory or the directories referenced by the ROOT option. It can also occur if you use extended characters (ASCII 128 through 255) in a filename. If neither of these conditions are true, the cause is probably an out-of-memory condition. Make sure the file exists and that the compiler has enough memory available to compile the title.


1292: File '%s' is not a valid bitmap.

The MediaView compiler could not find the specified bitmap file or recognize its format. This error might be caused by an MS-DOS file error, an out-of-memory condition, or a bitmap file not in .DIB format.


1293: Embedded bitmap statement with no filename specified.

The specified topic contains a bitmap-reference {bmc} statement that omits the filename of the image.


1319: Disk full.

The MediaView compiler could not write the .M12 file to disk. Create more space on the destination drive.


1513: Bitmap name '%s' duplicated.

Youve already used the specified bitmap elsewhere in the title. This is just an informational message.


1536: Not enough memory to compress bitmap '%s'.

Insufficient memory was available to compress the specified bitmap file. The bitmap file was copied directly to the .M12 file without compression.


1540: Error creating |GMACROS subfile.

The MediaView compiler could not create the |GMACROS subfile within the .M12 because of an I/O error with the .M12, or with temporary files. Rebuild the title.


1541: Cannot initiate group.

The MediaView compiler failed while processing the [GROUPS] section of the project file, due to an I/O error such as out of disk space, or out of temporary file handles.


1551: Cannot add group ID to group.

The MediaView compiler could not add the group ID, which is used internally, to the group due to an I/O error. Rebuild the title.


1561: Cannot build group.

The MediaView compiler could not build the group due to an I/O error. Rebuild the title.


1571: Cannot update |SYSTEM subfile.

The MediaView compiler could not update the |SYSTEM subfile due to an I/O error. Rebuild the title.


1581: Sort failure.

An error occurred while sorting a keyword index. Contact Microsoft Product Support Services.


1599: To build index/baggage only, the file system must already exist.

The project file specifies a MAKE=INDEX option. To specify this option, you must have first built the .M12 file using the MAKE=COMPILE option.


1609: Produced file will lack full-text index.

The title was successfully built, but the MediaView compiler could not create the index subfile. This error often occurs when the title has no indexable text (no topics contain title footnotes, or the topics dont contain any text that can be indexed).


1617: Error opening .MVP file for scanning; another instance may have a lock.

The project file has been opened by another application or by another instance of the MediaView compiler. Close the project file and then restart compilation.


1621: Bad reference to subfile (name too long): %s

The specified baggage filename must be less than 25 characters in length.


1631: MAKE command line was set to an unsupported value.  Defaulting to MAKE=FULL.

An invalid value was specified for the MAKE= command-line option. The default value (MAKE=FULL) will be used.


1651: File input/output error

A file I/O error occurred while reading the specified file. Make sure the file is not missing or damaged, then rebuild the title.


1661: Error loading baggage file: %s

An error occurred while reading data from the specified source file to the baggage file.


1700: Unknown error matching return codes; Contact Microsoft Product Support Services.");

An unknown error occurred. Contact Microsoft Product Support Services.


1709: Error opening file: %s

An error occurred while attempting to open the specified file.


2011: Unterminated #IGNORE directive.

An #IGNORE statement does not have a matching #ENDIGNORE in your project file. Check the project file and recompile.


2030: Comment starting at line %d unclosed at end of file.

The MediaView compiler reached the end of the project file unexpectedly. The project file might have an open comment or an included file.


2050: Invalid #include syntax.

The correct #include syntax is #include filename. Correct the syntax and rebuild the title.


2091: Bracket missing from section heading [%s].

The right bracket (]) was missing from the specified section heading. Insert the bracket and rebuild the title.


2111: Section heading missing.

The section heading on the specified line was not complete. The MediaView compiler also reports this error if the first entry in the project file was not a section heading.


2131: Invalid OPTIONS syntax: 'option=value' expected.

An option given in the [OPTIONS] section of the project file had incorrect syntax.


2151: Incomplete line in [%s] section.

The entry on the specified line was not complete. As a result, the MediaView compiler skipped the line.


2161: Bad syntax in section heading.

The section heading contains a syntax error such as a missing bracket. Check syntax and recompile.


2171: Unrecognized text.

The MediaView compiler could not recognize text in the project file. As a result, the compiler skipped the line.


2191: Section heading [%s] unrecognized.

The project file included a section heading that the MediaView compiler did not recognize. As a result, the compiler ignored the line.


2214: Line in ..MVP file exceeds length limit of 2047 characters.

A line in the .MVP file exceeded the maximum length of 2,047 characters. Shorten the line and recompile.


2221: Could not load default breaker descriptions from resource file.

The MediaView compiler lacked the memory required to load word-breaker information from disk.


2287: [OPTIONS] should precede [FILES].

The project file lists the [FILES] section before the [OPTIONS] section. Move the [OPTIONS] section to the beginning of the project file.


2291: Section [%s] previously defined.

The project file has more than one section with the given heading. The MediaView compiler ignored the lines in the duplicated section and resumed processing at the next valid section heading.


2305: No valid files in [FILES] section.

The [FILES] section was empty or contained only invalid files.


2311: Memory allocation failure during processing of extra section option.

There was insufficient memory to process the IGNORESECTION option.


2352: Context string exceeds maximum length; truncating: %s

The maximum size for a context string is 255 characters. The specified context string exceeds the size limit.


2361: Error accessing context resolution file.

A temporary file used for context-string resolution was locked or missing. Rebuild the title.


2511: Unrecognized option '%s' in [OPTIONS] section.

An unrecognized option was used. The MediaView compiler skipped this line.


2532: Option '%s' previously defined.

The specified option was defined previously in the [OPTIONS] section. The MediaView compiler uses the first definition.


2550: Invalid path '%s' in option.

The specified option specified an invalid filename path. The MediaView compiler used the current working directory instead of this path.


2570: Path in %s option exceeds maximum characters.

The given option specified a path longer than the MS-DOS limit of 66 characters. The MediaView compiler ignored the path and used the current working directory as the root path.


2651: Font name exceeds limit of 20 characters.

The font name you specified is longer than the 20 character limit.  Choose a font that has a shorter name or rename the font.


2652: Unrecognized font name '%s' in FORCEFONT option.

The font name you used in the FORCEFONT option was unrecognized.


2661: Bad keyword footnote syntax.

The keyword syntax you specified is incorrect.  The correct syntax is KIndex:keyword1,keyword2,...


2671: Duplicate keyword specification character.

An entry in the [KEYINDEX] section of the project file uses a keyword-index identifier character previously used by another entry. Each keyword index defined in the [KEYINDEX] section must specify a unique identifier character.


2681: Null keyword footnote.

A keyword footnote in the specified topic contains no keywords.


2691: Keyword set specification character not recognized.

The keyword-index identifier character specified in the keyword footnote does not correspond to a keyword index defined in the [KEYINDEX] section of the project file. Any keyword indexes referenced in topics must be defined in the project file (except for the main keyword index, which has identifier character 0).


2701: Missing '=' in [KEYINDEX] section string.

An entry in the [KEYINDEX] section omits the equal sign (=) following the keyword. The entry was ignored.


2711: Bad syntax in [KEYINDEX] section.

An entry in the [KEYINDEX] section contains a syntax error.


2721: Bad title specification for keyword set.

The [KEYINDEX] entry on the specified line either omits the index title or omits the quotation marks around the title.


2731: Trailing garbage in [KEYINDEX] section string.

The [KEYINDEX] entry on the specified line contains some unexpected text following the title string for the keyword index. This text was ignored.


2741: Bad keyword set specifier.

The [KEYINDEX] entry on the specified line contains an invalid keyword-index identifier. The identifier must be a single character.


2751: Keyword set title too long.

The [KEYINDEX] entry on the specified line contains a keyword-index title that is too long. The maximum length of a keyword-index title is 50 characters.


2831: System resource failure extracting text for phrase compression.

During phrase compression, the MediaView compiler ran out of memory or disk space or encountered some other system-resource failure.


2832: COMPRESS option must be YES or 'NO'.

The COMPRESS option on the specified line of the project file uses an invalid compression option. Change the value to NO, FALSE, or 0 (for no compression); MEDIUM,  YES,  TRUE, or 1 (for block compression).


2841: Error constructing phrase file.

During phrase compression, the MediaView compiler ran out of memory or disk space or encountered some other system-resource failure.


2842: OPTCDROM option must be 'TRUE' or 'FALSE'.

The OPTCDROM option on the specified line of the project file has an invalid value. Change the value to TRUE or FALSE. The MediaView compiler is using a default value of FALSE.


2852: Invalid TITLE option.

The title defined by the TITLE option exceeds the maximum length of 50 characters. The MediaView compiler truncated the title to 50 characters.


2893: WARNING option must be 1, 2, or 3.

The WARNING option can only be set to 1, 2, or 3. The MediaView compiler defaults to full reporting (level 3).


2911: Invalid icon file '%s'.

The file referenced by the ICON option is not a valid icon file.


2932: Copyright string exceeds limit of 50 characters.

The copyright string specified in the COPYRIGHT option exceeds the maximum length of 50 characters. The MediaView compiler truncated the copyright string to 50 characters.


2941: Batch option, if specified, should be set to 'TRUE' or 'FALSE'

The BATCH option specifies an invalid value. Change the value to TRUE or FALSE. The MediaView compiler is using the default value of FALSE.


2971: Make option, if specified, must be set to 'FULL', 'COMPILE', or 'INDEX'.

The MAKE option specifies an invalid value. Change the value to FULL, COMPILE, or INDEX. The MediaView compiler is using the default value of FULL.


2981: System option set to unrecognized and unsupported value.

The SYSTEM option specifies an invalid value. Change the option to PC. The MediaView compiler is using the default value of PC.


3011: Maximum of 32 build tags exceeded.

The [BUILDTAGS] section defines more than 32 build tags. The MediaView compiler ignored the excess tags.


3031: Build tag length exceeds 32 characters.

The build tag on the specified line of the project file exceeded the maximum of 32 characters. The MediaView compiler skipped this entry.


3051: Build tag '%s' contains invalid characters.

The build tag on the specified line of the project file contains a character other than an alphanumeric character or underscore (_). The MediaView compiler skipped this line.


3076: [BUILDTAGS] section missing.

The BUILD option in the [OPTIONS] section of the project file specified a conditional build, but the project file did not have a [BUILDTAGS] section. The MediaView compiler included all topics in the build.


3096: Build expression too complex.

The build expression on the specified line of the project file contained too many logical operators (~, &, and |), or the logical symbols were too deeply nested.


3116: Invalid build expression.

The build expression on the specified line of the project file had one or more logic or syntax errors.


3133: Duplicate build tag in [BUILDTAGS] section.

The build tag on the specified line of the project file was already defined earlier in the [BUILDTAGS] section. The duplicate entry was ignored.


3152: Build tag '%s' not defined in [BUILDTAGS] section.

The specified build tag assigned to a topic was not declared in the [BUILDTAGS] section of the project file. The MediaView compiler ignored the tag for the topic in which it was defined.


3178: Build expression missing from project file.

A topic has a build-tag footnote, but no BUILD option was defined in the [OPTIONS] section of the project file. The MediaView compiler is including all topics in the build.


3511: Macro '%s' exceeds limit of 512 characters.

A topic-entry command contains a command string exceeding 512 characters. The MediaView compiler ignored the footnote. Try breaking the command string into multiple topic-entry footnotes.


4011: Context string '%s' already used.

The specified topic contains a context string that was already assigned to another topic. The MediaView compiler ignored the duplicate string, so this topic has no identifier.


4031: Invalid context string '%s'.

In the specified topic, a hot spot or context-string footnote contains an empty or invalid context string. Context strings can consist of the characters A  Z, a  z, numbers, periods, and underscores. The MediaView compiler did not create the context identifier or hot spot.


4056: Unresolved context string specified in CONTENTS option.

The MediaView compiler could not find the context string specified by the CONTENTS option in the project file. The compiler is using the default contents topic (the first topic in the first RTF file listed in the [FILES] section).


4072: Context string/hotspot macro exceeds limit of 512 characters.

The context string or command string specified with the hot spot exceeds 512 characters. The MediaView compiler ignored the hot spot.


4005: Error creating context cross-check file.

Could not create temporary file due to lack of system resources.  Close other applications,  create more disk  space, and try again.


4113: Unresolved jump or popup '%s'.

The specified topic contains a jump or popup hot spot that specifies a non-existent context string. Check the spelling of the context string, and make sure the desired topic is included in the build.


4131: Hash conflict.

The hashing algorithm used to generate unique identifiers for context strings generated the same hash value for the specified context strings. Change either of the context strings and rebuild the title.


4196: Jumps and lookups not verified.

The build process ran low on memory, and it continued building the title without checking the validity of standard jumps and jumps to popup windows.


4211: Footnote text exceeds limit of 1023 characters.

A footnote exceeded the limit of 1,023 characters. The MediaView compiler ignored the footnote.


4251: Browse sequence not in first paragraph.

A topic-group/browse sequence (+) footnote was not in the first paragraph of the topic. The MediaView compiler ignored the browse sequence.


4272: Empty browse sequence string.

The topic group/browse sequence (+) footnote for the specified topic contained no topic-group names.


4281: File I/O error during browse sequence resolution.

The MediaView compiler could not access a temporary file used for generating browse sequences. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


4292: Missing sequence number.

The topic group/browse sequence (+) footnote contains a browse sequence name ending with a colon (:), but no browse-sequence number was specified. Remove the colon or add a sequence number.


4312: Browse sequence already defined.

A topic group/browse sequence (+) footnote was already defined for the specified topic. The MediaView compiler uses the first footnote encountered in the topic.


4331: Title not in first paragraph.

The title ($) footnote does not appear in the first paragraph of the topic. Move the footnote to the first topic paragraph. The MediaView compiler ignored the footnote, so no title is defined for the topic.


4352: Empty title string.

The title ($) footnote contains no title text. As a result, the MediaView compiler did not assign a title to the topic.


4372: Title defined more than once.

The topic defines more than one title ($) footnote. The MediaView compiler uses the first title footnote.


4393: Title exceeds limit of 128 characters.

The title ($) footnote contains a title that exceeds the limit of 128 characters. The MediaView compiler truncated the topic title to 128 characters.


4412: Keyword string exceeds limit of 240 characters.

A keyword specified in the keyword (K) footnote exceeds the limit of 255 characters. The keyword was ignored.


4433: Empty keyword string.

A keyword (K) footnote in the specified topic contained no keyword text.


4441: File I/O error processing keywords.

The MediaView compiler was unable to access a temporary file used for building the keyword index. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


4452: Keyword(s) defined without title.

The specified contains keyword (K) footnotes, but the topic does not contain a title ($) footnote. The topic will appear as Untitled Topic in the History, Index, and Search Results dialog boxes.


4461: Error creating keyword system map file.

An error occurred while constructing the keyword index. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


4471: Build tag footnote not at beginning of topic.

The build-tag (*) footnote must appear as the first element in the topic (at the beginning of the first topic paragraph).


4492: Build tag exceeds limit of 32 characters.

A build tag for the specified topic exceeded the maximum of 32 characters. The MediaView compiler ignored the tag for this topic.


4551: Entry macro not in first paragraph.

A topic-entry command (!) footnote did not appear in the first paragraph of the topic. Move the footnote to the first topic paragraph. The MediaView compiler ignored the footnote.


4561: Duplicate keyword: '%s.'

The keyword (K) footnote contains a duplicate keyword.


4616: File '%s' is not a valid RTF topic file.

The specified file listed in the [FILES] section is not an RTF file. Make sure you have saved the topic from your text editor in RTF format.


4632: Invalid argment '%s' (Byte offset %lxh (topic #%ld) of %s)

The RTF argument you used at the specified topic and byte offset is invalid.


4633: Unmatched curly brace: missing '%c' (Byte offset %lxh (topic #%ld) of %s)

The curly brace character shown by <c> is un matched in your RTF source.  Check your rtf source at the topic and byte offset shown, and re-compile.


4634: Error in RTF.

The specified file contains an invalid RTF code.


4649: File '%s' contains more than 32767 topics.

An RTF file had more than the maximum legal number of topics. Reduce the number of topics and rebuild the title.


4652: Table formatting too complex.

The MediaView compiler encountered a table with borders, shading, or right justification. Remove the unsupported formatting and rebuild the title.


4662: Side by side paragraphs not supported.

The MediaView compiler does not support side-by-side paragraph formatting. Use tables instead. The compiler ignored the text using the side-by-side formatting.


4671: Table contains more than 32 columns.

A table within the topic file used more than the maximum legal number of columns. Reduce the number of tables and rebuild the title.


4680: Font %d not in RTF font table.

A font referenced in the specified RTF file was not defined in the font table for that file.


4686: Style sheet, '%s', redefined; first definition used.

The compiler displays this message when it finds a style with the same name of character style number in two different RTF source files, but the styles differ in some way, or if two similar styles have different character style numbers in two different style sheets.

This problem can be caused by RTF files edited using Microsoft Word for Windows. Word does not have any concept of character styles across documents. You can "copy" a style from one document to another, but within each individual RTF files stylesheet, Word will assign a character style number to a style; this number can easily differ for each document. Thus, you might have a "Topic Text" style in two different RTF files, but Word will assign one of them as "cs77" and the other as "cs23".  When you compile the M12 file, the MediaView compiler gives a warning about character styles with the same names but different attributes.

If you know that all of the styles are identical across all of the source files, then you should be able to safely ignore this message. You can add 4686 to the [WARNIGNORE] section of the titles project file. The title should then compile just fine using the first instance of the style named in the message. (Note that you should be careful of this if the title player application for the title depends in some way upon style names and numbers - e.g. using fSetCharStyle.)

To fix this in the source files, the work-around is to edit the RTF files as text. You will need to edit the RTF files as TEXT, and replace all character style references appropriately.

Note that as a consequence of this work-around Microsoft Word for Windows will display the "Invalid Style" message when you load the file back into Word as RTF. If you then read the RTF file into Word as RTF and write it back out as RTF, Word will "fix" the invalid style message, but may also make up new character style numbers which will get the files out of synch again.


4692: Unrecognized graphic format.

A picture inserted directly in the specified RTF file has an unrecognized graphic format. MediaView supports bitmaps and metafiles.


4733: Hidden page break.

The MediaView compiler found a page break formatted as hidden text. The compiler ignored the page break, so the hidden page break does not separate two topics.


4753: Hidden paragraph.

The MediaView compiler found a paragraph marker formatted as hidden text. The compiler ignored the paragraph marker.


4763: Hidden carriage return.

A carriage return in the topic file was formatted as hidden text. The MediaView compiler ignored the carriage return.


4774: Paragraph containing %s exceeds limit of 32K.

A single paragraph in the topic file had more than 32K of either text or graphics. Break the paragraph into smaller paragraphs.


4792: Non-scrolling region defined after scrolling region.

A paragraph formatted using the Keep With Next option appeared following other topic paragraphs that arent formatted as Keep with Next. The MediaView compiler ignored the Keep With Next attribute and treated the paragraph as regular text. As a result, the paragraph is part of the regular topic text rather than non-scrolling text. Non-scrolling paragraphs must appear at the top of the topic and must be contiguous.


4813: Non-scrolling region crosses page boundary.

A topic file used keep-with-next paragraph formatting across a page break. Reformat the page break and any keep-with-next text or graphics after the page break and rebuild the title.


4821: Bad embedded window command syntax.

An embedded-window {ewx} command is missing the DLL name, window-class name, or author-data string or is missing the commas that separate these elements. The embedded window wont appear in the compiled title.


4823: Embedded window command too long.

An embedded-window {ewx} command exceeds the maximum length of 1,023 characters.


4831: Error outputting embedded window.

An error occurred while writing embedded-pane information to the title. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


4834: Embedded bitmap size limitation of 64k exceeded

An image inserted using the bitmap-reference {bmx} command exceeds the maximum size of 64K. Use an {ewx} command with MVDIB12.DLL instead of the {bmx} command.


4841: Syntax error in embedded {alias} command.

An {alias} command in the specified topic has incorrect syntax.


5001: Error loading bitmap into file system: %s

There were not enough system resources to load the bitmap into the MediaView file system.  Free disk  space, shut down other applications, and try again.


5002: WARNIGNORE must be the first section in the project file.

The WARNIGNORE section must come first in the project file.  Move this section to the beginning of your project file and recompile.


5004: Build of |MVINDEX subfile failed!

An error occurred while creating the subfile for the title index. Rebuild the title.


5009: File system write failure!

An error occurred while opening a system file required for the keyword index. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


5035: No topics encountered or processed.  File '%s' not created.

Because there are no topics to compile, or a build expression was false for all topics, the MediaView compiler did not create a .M12 file.


5059: Not enough memory to build system file.

The MediaView compiler did not have enough memory to build a .M12 file. To free up memory, close any unneeded applications, device drivers, or memory-resident programs, then rebuild the title.


5115: Write failed.

An error occurred while writing to the disk. Check to make sure sufficient disk space is available for compilation.


5139: Aborted by user.

You stopped the compilation. The .M12 file was not generated.


6000: UNKNOWN ERROR\n\t\tContact Microsoft Product Support Services

A serious internal error occurred.  Contact Microsoft Product Support Services.


6019: Error initiating full-text index.

The indexer was unable to initialize the full-text index. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


6029: Error loading phrase table.

The MediaView compiler was unable to access the phrase compression table during index. This error results when the author changes the COMPRESS option between building the title (using the MAKE=COMPILE option) and indexing the title (using the MAKE=INDEX option).


6039: General failure initiating catalog.

The MediaView compiler was unable to create a subfile required for indexing. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


6059: Indexing failure!

Indexing failed. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


6069: Error building catalog.

The MediaView compiler was unable to create a subfile required for indexing. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


6076: Error building full-text index.

This error message is generally displayed in conjunction with another, more-specific message. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


6089: No default word breaker loaded.

The default word breaker (for data type 0) has been overwritten with a invalid one. Check the syntax of the DTYPE0 statement specified in the [FTINDEX] section of the project file.


6099: Unknown command encountered during indexing.

The title file was corrupted. Rebuild the title.


6109: Error loading word breakers."

The word-breaker routine identified on the specified line in the project file is not available in the specified DLL. Check the spelling of the word-breaker name and DLL name.


6129: Can't load breaker DLL.

The MediaView compiler cant find the word-breaker DLL identified on the specified line in the project file. Check the spelling of the DLL name.


6139: Insufficient memory to initiate catalog.

There was insufficient memory to create a system file needed for indexing. Free some memory by closing unneeded applications and then try again.


6141: Bitmap unavailable for indexing.

The MediaView compiler could not find the specified image file, so any searchable text in the image was not indexed.


6151: Bitmap corrupted: bad header.

The specified image has a bad header. Recreate the bitmap.


6161: Can't unpack bitmap for indexing.

The MediaView compiler couldnt access the specified image file, so any searchable text within the image was not added to the index.


6171: Error indexing SHED coldspot text.

The MediaView compiler could not extract text from the Hotspot Editor.


6176: No words in titled topics found to index; Result file will lack full-text index.

The title contained no topics with topic titles, or the topics contained no indexable text, so no index was created.


6181: Specified word breaker unable to process word: %s.

The word-breaker routine specified for a topic phrase was unable to process a word within the phrase. Check to make sure any numeric or date data types are formatted correctly.


6182: Failure of Dll breaking function.

A critical error occurred in a word-breaking function. Restart Windows to ensure the word-breaker DLL has been cleared from memory, then rebuild the title. If the error occurs again, contact Microsoft Product Support Services or, if the DLL was written by a third-party developer, contact the third-party developer.


6211: Missing '=' in [WWHEEL] string.

The WWHEEL entry on the specified line in the project file is missing the required equal-sign (=) following the WWHEEL keyword. The entry was ignored.


6221: Bad [WWHEEL] string; left of '=' must be 'wwheel'

An entry in the [WWHEEL] section uses an invalid keyword. The keyword must be WWHEEL. The entry was ignored.


6231: Bad [WWHEEL] string syntax.

The WWHEEL entry on the specified line of the project file is missing the word-wheel subfile name, the field number, or both. The entry was ignored.


6247: Error initializing word wheel build structure.

An error occurred while initializing the word wheels for the title. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


6257: Error building word wheel subfile.

An error occurred while building the word wheels for the title. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


6267: Failure adding field string to word wheel.

The MediaView compiler was unable to add a field string to a word wheel. This error is generally caused by a lack of disk space.


6271: Failure initializing word wheel.

An error occurred while initializing the word wheels for the title. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


6281: Word wheel name overflow: %s

The filename constructed for a word-wheel subfile is longer than the allowable limit. Reduce the size of the subfile name to 20 characters or less.


6291: Failure building word wheels.

An error occurred while building the word wheels for the title. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


6311: Missing '=' in [SEARCHDLG] section string.

The [SEARCHDLG] entry on the specified line in the project file is missing an equal sign (=). The entry was ignored.


6313: Bad [SEARCHDLG] section string; left of '=' must be 'ebox' or 'near'.

The [SEARCHDLG] entry on the specified line of the project file has an invalid keyword. [SEARCHDLG] entries can only specify EBOX or NEAR.


6321: Bad syntax in [SEARCHDLG] section string.

The [SEARCHDLG] entry on the specified line of the project file is missing a field or contains other syntax errors. The entry was ignored.


6331: Bad data type number in project file string.

The [SEARCHDLG] entry on the specified line of the project file contains an invalid data-type number. The entry was ignored.


6341: Bad title string in [SEARCHDLG] section string.

The [SEARCHDLG] entry on the specified line of the project file is missing the category title, or the category title is not enclosed in quotation marks. The entry was ignored.


6351: Subfile name too long in project file string.

The [SEARCHDLG] entry on the specified line in the project file uses a word-wheel subfile name that is longer than the maximum allowable 20 characters. The entry was ignored.


6361: Title specification too long in [SEARCHDLG] section string.

The [SEARCHDLG] entry on the specified line in the project file contains a category title that exceeds the maximum allowable 50 characters. The entry was ignored.


6371: Subfile specified in [SEARCHDLG] string without field specifier.

The [SEARCHDLG] entry on the specified line of the project file specifies a word-wheel subfile name but does not specify the number of the field from which to build the word wheel. The entry was ignored, and the word wheel will not be built.


6381: Duplicate word wheel name.

The [SEARCHDLG] or [WWHEEL] entry on the specified line of the project file specifies a word-wheel subfile name that was already used by a preceding entry. The duplicate entry was ignored, and the word wheel will not be built.


6391: Extra parameters following subfile specification.

The [SEARCHDLG] or [WWHEEL] entry on the specified line of the project file contains unexpected text following the word-wheel subfile name. The unexpected text was ignored.


6401: Bad field specification in string.

The [SEARCHDLG] or [WWHEEL] entry on the specified line of the project file contains an invalid field number. The entry was ignored.


6411: Extensions not allowed in word wheel subfile names; it will be stripped.

The [SEARCHDLG] or [WWHEEL] entry on the specified line of the project file specifies a filename extension for a word-wheel subfile name. Extensions are not allowed. The MediaView compiler replaces the specified extension with its own .WWL extension.


6421: '!' missing in icon subfile specification.

The [SEARCHDLG] entry on the specified line of the project file contains an icon filename that omits the exclamation point (!). Icons for search categories are not implemented in the MediaView run time, so the third field in an EBOX entry should be empty.


6431: Specified NEAR value not in positive integer range: %s.

The NEAR option on the specified line of the project file uses an invalid NEAR value. Specify a positive integer with a maximum value of 32767.


6511: Index DLL: out of far memory.

The indexer DLL had insufficient memory to complete the indexing. Close some applications and then try compiling again.


6521: Index DLL: insufficient disk space.

The indexer DLL had insufficient disk space to complete the indexing process. Free some disk space by deleting unneeded files. Temporary files for the indexer are stored in the directory referenced by the TEMP environment variable.


6531: Index DLL: word too long.

The indexer encountered a topic word that is too long.


6541: Index DLL: bad component version number.

The version number of the indexing .DLL you are using is incorrect.  Rerun setup to correct the installation.


6551: Index DLL: too many stop words in stop word file.

The title contains more topics than the maximum allowable 4,294,967,295 topics.


6561: Index DLL: too many documents.

The stop-words file contains more than 1,024 stop words. Reduce the number of stop words.


6571: Index DLL: word exceeds maximum stem length.

The indexer encountered a topic word with a stem that is too long.


6581: Index DLL: file I/O error reading.

An I/O error occurred while reading indexing data. Rebuild the title.


6591: Index DLL: bad argument to API call.

You tried to use an argument containing an invalid data type.  Contact Microsoft Product Support Services.


6601: Index DLL: group id too large.

The number of topics in this group is greater than 524280.  Reduce the number of topics and rebuild the title.


6611: Index DLL: hardware insufficiency detected.

The indexer only runs on PCs equipped with an 80386 processor running in protected or enhanced mode.


6621: Index DLL: Internal assertion failure.

A serious internal error occurred.  Contact Microsoft Product Support Services.


6631: Index DLL: specified file does not exist.

The indexer was unable to find the specified file.


6641: Index DLL: bad or corrupted FS file.

You tried to build an index for a file that is not a valid .M12 file.


6661: Index DLL: I/O seek error.

An I/O error occurred while performing indexing. Rebuild the title.


6671: Index DLL: I/O error during file creation.

An I/O error occurred during indexing. Rebuild the title.


6681: Index DLL: file I/O error writing.

An I/O error occurred during indexing. Rebuild the title.


6691: Index DLL: out of file handles.

The indexer ran out of MS-DOS file handles. This problem is generally caused by the MS-DOS SHARE utility. Check your AUTOEXEC.BAT or CONFIG.SYS files to make sure any SHARE commands include the parameters /F:4096 /L:50 (for example, C:/F:4096 /L:50).


6721: Index DLL: bad character table file format.

The specified character-table file has an incorrect format.


6731: Index DLL: bad dtype argument format.

Topic data marked with a data type is incompatible with the specified data type.


6741: Index DLL: bad dtype value.

A numeric data type or date data type has an incorrect value.


6751: Index DLL: bad word breaker reference.

The filename you used to specify your word breaker .dll was not found.  Check the spelling, path name and existence of the file, and try again.


6761: Index DLL: unmapped error.

An unexpected internal error occurred.  Contact Microsoft Product Support Services.


7113: Unterminated {vfld} token in the RTF source.

A field statement is missing the right brace.


7123: Unterminated {dtype} token in the RTF source.

A data-type statement is missing the right brace.


7131: Field string too long in RTF source.

Text marked within {vfld} statements exceeds the maximum size of 127 characters. The MediaView compiler truncated the field text to 127 characters.


7141: Bad selector into alias table.

An {alias} statement in the specified topic references an non-existent alias-file entry.


7151: Numbers 1..9 are reserved field specifiers.  Ignoring reference.

A field statement in the specified topic uses a reserved field number. Change the field number to an integer greater than or equal to 10.


7161: Field specs must be positive numbers.

A field statement in the specified topic uses an invalid field number. Field numbers must be positive integers greater than or equal to 10.


7163: Unknown parameter in dtype string in absence of authoring platform.

Unexpected text followed the specified entry in the [FTINDEX] section.


7509: Failure sorting browse sequence strings.

An error occurred while sorting browse sequence strings.  This error is probably due to a lack of  system resources.


7519: Cannot open browse sequence file.

An error occurred while opening a temporary file used for browse sequences. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


7529: Failure sorting context string file.

An error occurred while sorting context strings. This error is probably due to a lack of disk space.


7539: Cannot open context string file.

The MediaView compiler was unable to open a temporary file used for storing context strings. The system ran out of file handles.


7549: Insufficient system resources for browse resolution.

The MediaView compiler ran out of memory, disk space, or file handles while constructing browse sequences.


8001: Bad syntax in group specification.

The [GROUPS] section entry on the specified line in the project file has incorrect syntax.


8021: Bad left side of group specification.

A GROUP= entry on the specified line of the project file has incorrect syntax. Check to make sure the group title is enclosed in quotation marks, and that no unexpected characters are following the group title.


8031: Bad right side of group specification.

A GROUP= entry on the specified line of the project file has incorrect syntax. Check to make sure the group title is enclosed in quotation marks, and that no unexpected characters are following the group title.


8041: Entry/Exit macro specification overflow!

The MediaView compiler allocates a maximum 32K of data for storing the text of group entry and exit commands. The entry and exit commands defined in this title, when combined with a small amount of overhead data required by MediaView, exceeds this 32K limit. To reduce the amount of group-command text, use command abbreviations, or reduce the number of group entry and exit commands.


8051: Entry/Exit macro specification too long.

The entry or exit command on the specified line of the project file exceeds the maximum allowable 512 characters.


8061: Bad sequence of lines in [GROUPS] section.

The [GROUPS] section entries for a topic group must appear in the following sequence: GROUP= entry first, followed by all ENTRY= entries, followed by all EXIT= entries. Dont mix ENTRY= and EXIT= entries.


8071: Duplicate group specification in [GROUPS] section.

The group defined on the specified line of the project file has the same name as a previously defined group. The duplicate group specification was ignored.


8081: More than one group footnote set for this topic.

The specified topic contains multiple topic-group/browse sequence (+) footnotes. The MediaView compiler used the first topic-group footnote and ignored the rest.


8091: Group footnote appeared too late in topic to be processed.

Topic group/browse sequence (+) footnotes must appear in the first paragraph of the topic. The footnote was ignored.


8101: Unterminated group footnote; group footnotes must end with ';'

The group footnote you specified  was not terminated with a semicolon (;).  Add a semicolon and rebuild the title.


8111: Browse sequence must be first group specified for a topic.

A browse-sequence number (a colon following a topic-group name) was named for one of the topic groups in the topic-group (+) footnote, but the topic group is not the first entry in the footnote. The browse-sequence name must appear as the first topic-group name in the footnote.


8131: Unable to add topic to browse sequence.

The MediaView compiler could not add a topic to a browse sequence. This error might be caused by lack of disk space, by a low-memory condition, or by a lack of available MS-DOS file handles.


8141: Inconsistent use of sequence numbers in browse sequence.

The browse sequence named in the topic-group (+) footnote specified a browse-sequence number, while earlier topics using that browse sequence do not (or vice-versa).


8151: Bad default browse position; sequence spec must be :ddd...

A sequence number specified for the default browse sequence contains a non-numeric character. The sequence number should consist only of numbers.


8161: Bad group reference; all groups must be declared in the project file.

The topic-group (+) footnote in the specified topic names a topic group that is not defined in the [GROUPS] section of the project file. The undefined group was ignored.


9001: Missing '=' in breaker string.

The [FTINDEX] section entry on the specified line of the project file is missing the equal sign (=) following the DTYPEn keyword. The entry was ignored.


9011: Bad syntax left-hand side of breaker string.

The [FTINDEX] section entry on the specified line of the project file uses an invalid keyword format. The keyword should specify DTYPEn, where n is a number from 0 through 15. The entry was ignored.


9021: Breaker index out of range.

The [FTINDEX] section entry on the specified line of the project file specifies an invalid data-type number. The keyword should specify DTYPEn, where n is a number from 0 through 15. The entry was ignored.


9031: DLL name missing from right-hand side of breaker string.

The [FTINDEX] section entry on the specified line of the project file omits the required DLL-name field. The entry was ignored.


9041: '!' missing from right-hand side of breaker string.

The [FTINDEX] section entry on the specified line of the project file omits the required exclamation point (!) separating the DLL name from the word-breaker routine name. The entry was ignored.


9051: Routine name missing from right-hand side of breaker string.

The [FTINDEX] section entry on the specified line of the project file omits the required word-breaker routine name following the exclamation point (!). The entry was ignored.


9061: Bad syntax right-hand side of breaker string.

The [FTINDEX] entry on the specified line of the project file contains an extra comma. The entry was ignored.


9071: Breaker routine not available: %s

The word-breaker routine identified on the specified line in the project file is not available in the specified DLL. Check the spelling of the word-breaker name and DLL name.


9077: Can't load breaker %d.

During indexing, the MediaView compiler encountered a {dtype} statement that references an undefined data type.


9107: Unable to initialize stop list.

An I/O or system error occurred while creating the stop word subfile. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


9109: Cannot open stop list subfile: %s

An I/O or system error occurred while opening the stop word subfile. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


9117: Cannot open specified DOS stop word file.

During indexing, the MediaView compiler was unable to open a stop-word file. The file might be locked by another process. This error might also be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


9127: Cannot build stop word subfile in result file system.

An I/O or system error occurred while creating the stop word subfile. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


9137: Cannot open specified DOS character table file.

During indexing, the MediaView compiler was unable to open a character-table file. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


9139: Cannot open character table subfile: %s

During indexing, the MediaView compiler was unable to open a character-table subfile. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


9147: Cannot initialize character table.

During indexing, the MediaView compiler was unable to initialize a character-table file. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


9157: Cannot build character table subfile.

An I/O or system error occurred while creating the character table subfile. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


9262: Undeclared data type: %d; ignoring.

The specified topic contains a data-type {dtype} tag that references an undefined data-type number. Data types must be defined in the [FTINDEX] section of the project file. The tag was ignored.


9272: Illegal data type specification.

The specified topic contains a data-type {dtype} statement that uses an invalid data-type number. You must specify a number from 0 through 15, and the number must be defined in the [FTINDEX] section of the project file. The tag was ignored.


9281: Error initializing localized operator table.

During indexing, the MediaView compiler was unable to initialize an operator-table file. This error is often caused by a lack of available MS-DOS file handles. It might also be caused by a lack of available disk space or by a low-memory condition.


9291: Error building localized operator table.

During indexing, the MediaView compiler was unable to build an operator table. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


9301: Could not open ligature table associated with dtype 0 character table; will use default.

The MediaView compiler encountered a file I/O error while attempting to load the ligature table. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


9313: Ligature table associated with dtype 0 character table too big.  Using default instead.

The ligature table exceeds the maximum allowable size of 128 bytes.


9302: %s option must be ON/OFF

The value for the option you specified is incorrect.  The option must be set to either ON/OFF, TRUE/FALSE, YES/NO, or 1/0.


9303: Unknown option: %s

The option you specified is invalid.  See the documentation for valid [OPTIONS] section entries


9304: Nested include not allowed

The MediaView compiler only allows #INCLUDE in the .MVP file.  Remove the #INCLUDE directive from all files but the project file.


9507: Cannot open specified alias file.

The MediaView compiler was unable to open the specified alias file. This error might be caused by a low-memory condition, by a lack of available disk space, or by a lack of available MS-DOS file handles.


9511: Entry in alias file exceeds maximum allowable length.

The specified alias-file entry is longer than 16,383 characters. The alias table was ignored.


9521: Bad syntax for selector in alias entry.

The specified alias-file entry is missing the colon (:) following the alias number. The alias table was ignored.


9531: Illegal selector number in alias entry.

The alias number in the specified alias-file entry contains non-numeric text. The alias table was ignored.


9541: Non-consecutive selector.

The alias number in the specified alias-file entry is not consecutive to the number of the preceding entry. Alias-file entries must be numbered consecutively, and you cant skip numbers. The alias file was ignored.


9551: Missing data type specifier in alias entry.

The specified alias-file entry is missing the semicolon (;) following the data-type number, or no data-type number was included. The alias table was ignored.


9561: Bad data type specifier in alias entry.

The data type number in the specified alias-file entry contains non-numeric characters. The alias table was ignored.


9571: Data type specifier out of range in alias entry.

A data-type number in the specified alias-file entry is outside the range 0 through 32767. Data-type numbers are limited to values 0 through 15 and must be defined in the [FTINDEX] section of the project file.


9581: Data type not registered in .MVP file.

The data-type number in the specified alias-file entry is not defined in the [FTINDEX] section of the project file. The alias table was ignored.


9591: Missing field specifier in alias entry.

The specified alias-file entry is missing the semicolon (;) following the field number. The alias table was ignored.


9601: Bad field specifier in alias entry.

The field number in the specified alias-file entry contains non-numeric characters. The alias file was ignored.


9611: Field specifier out of range in alias entry.

The field number in the specified alias-file entry is outside the range 0 through 32767. The alias table was ignored.


9613: Empty alias word list.

The alias text in the specified alias-file entry is missing. The alias table was ignored.


30009 - 30079: Various fatal errors

Fatal error messages (error numbers 30009 through 30289) indicate the MediaView compiler encountered an unrecoverable error and is halting compilation. The specific message identifies the exact point at which compilation was halted. Fatal error messages are accompanied by a preceding message that indicates the exact reason for failure.


30009: Compilation failure during scratch file allocation.

The compilation failed due to a lack of disk space or an out of memory condition.  Shut down applications, free disk space, and try again.


30019: Compilation failure during main structure allocation.

The compilation failed due to a lack of disk space or an out of memory condition.  Shut down applications, free disk space, and try again.


30029: Compilation failure during main structure initialization.

The compilation failed due to a lack of disk space or an out of memory condition.  Shut down applications, free disk space, and try again.


30039: Compilation failure during .MVP parsing.

The compilation failed due to an unrecoverable error within the project file.  Repair the error and recompile the title.


30049: Compilation failure due to file system verification error.

The compilation failed due to a lack of disk space or an out of memory condition.  Shut down applications, free disk space, and try again.


30059: Compilation failure during compression buffer allocation.

The compilation failed due to a lack of disk space or an out of memory condition.  Shut down applications, free disk space, and try again.


30069: Compilation failure during file system creation.

The compilation failed due to a lack of disk space or an out of memory condition.  Shut down applications, free disk space, and try again.


30079: Compilation failure during baggage loading.

The compilation failed due to a lack of disk space or an out of memory condition.  Shut down applications, free disk space, and try again.