   DATE:	April 1, 1993 
PRODUCT:	WordPerfect 6.0 for DOS
SUBJECT:	Master Documents/Generate Troubleshooting

TROUBLESHOOTING 
1.	Check the release date of WP. 
2.	Where is the generate failing?  What Pass/Page number? 
3.	Check for proper generate codes on the page where WP locks, or
        where it generates incorrectly.  (Proper codes means:  TOC and 
        TOA Mark codes should have a beginning and end mark.  Subdocuments 
        when expanded should have a Start Subdoc and an End Subdoc code.  
        If using a concordance file, check to see if they are using the 
        correct concordance path/filename.  For complete explanation of 
        proper generate codes, refer to manual.) 
        Delete that page and see if it will generate.  
4.	Delete current Definition mark codes (e.g., Def Mark and End 
        Def Mark) and all text in between for the particular feature that 
        is not generating properly (e.g., TOC, TOA, Index,etc...), redefine 
        definition, and then generate again to see if problem still duplicates. 
5.	Check Initial Codes in Setup and Document Initial Codes for any 
        codes that might create a conflict. 
6.	Can the problem be duplicated from a blank screen or with another 
        document? 
7.	Check INFO DOOR for similar reported problems and possible workarounds.
        Read the appropriate sections in the manual and workbook.  Tip - The
        manuals are in the INFO DOOR, e.g., -MANUALS.  
8.	Run VANILLA (e.g. CONFIG.SYS:  Files, Buffers; AUTOEXEC.BAT: Prompt, 
        Path). 
9.	Exit WP, come back in and try again. 
10.	If using expanded memory try entering WP using the /NE startup option. 
11.	Do a CHKDSK on the WP.EXE and WP.FIL to check for non-contiguous 
        blocks.  If any non-contiguous blocks are reported reinstall the 
        WP.EXE and/or the WP.FIL files and rename the .SET file.  If this 
        is done, you will need to reselect the printer and re-enter the 
        location of files in Setup.  If no non-contiguous blocks are reported, 
        but renaming the .SET file corrects the problem, have operator log as 
        an STR and send in a copy of .SET file. 

Note:  If you are having a problem in the International version of
the product, try duplicating the problem in the latest US version of 
the product.  If you can duplicate the problem in the US version, put the 
US date as the date of the product for the STR.

REQUIRED INFORMATION FOR AN STR 
1.	Date of .EXE file and .PRS file.
2.	The page number and/or pass that exhibits the problem. 
3.	Any TSRs they are running. 
4.	Brand of expanded memory and name of expanded memory manager. 
5.	Copy of the AUTOEXEC.BAT and CONFIG.SYS files. 
6.	A clear description of the problem.  Read it through before
        you save it.  Indicate every step that you have tried. 
7.	Other features used in the file (styles, graphics, fonts, tables, 
        columns).

MATERIALS TO BE SENT IN WITH AN STR 
1.	A file that duplicates the problem.   If the operator cannot 
       duplicate it, send in the file.  The shorter the file, the better.  
       (If it is a Master Document problem, you must include all 
       subdocuments being used.)  
2.	The *.SET, *.PRS file(s), and concordance file if used with an 
        Index. 

SUGGESTED INFO DOOR KEYWORDS FOR MORE INFORMATION:   generat*, "cross
referenc*", "table of content*", toc, "table of authorit*", toa, inde*,
list*, master document*, sub document*, subdoc*, expand*, condens*.  

