TITLE:    Insert WP.FIL or WP Disk #2 Error Message
PRODUCT:  WordPerfect 5.1 for DOS on a Network


Problem
You are running WordPerfect 5.1 for DOS on a network, and the
error message Insert WP.FIL or WP Disk #2 appears.


Solutions
One or more of the following troubleshooting options should
correct the problem:

1    Make sure two users aren't in WordPerfect at the same time
     using the same user initials.

2    Can you duplicate the error message?  If yes, go in with
     WP.EXE /NC/NE/NH/D-C:\.  If you are running it under
     Windows, check the PIF file.  Also check disk space and the
     temp directory.

3    Check the WP{WP}.ENV file and make sure there are no volume
     names in the path of the /PS switch.

4    Increase file handles in the CONFIG.SYS file.

5    Make sure users have all rights in the SET file directory.

6    If you are on a Novell network, exit out to DOS, then use
     the CD command to change directories.  See if you have
     logged onto or attached to another server and mapped any
     drives.  Either of these could remap your drive mappings. 
     Check if you are changing drives in F5 for List Files.

7    Make sure that there are no volume names (such as SYS:) in
     any path of WordPerfect such as:

         Other directory in List Files
         Location of auxiliary files
         Path for downloadable fonts
         Typed in when using Shift-F10 to retrieve a file

8    Make sure that the program files are attribed as +R, or if
     you are on a Novell network, make sure they are flagged as
     SRO.  If they were -R, SRW, or NRW, recopy them and attrib
     them +R.  Or, on a Novell network, flag them as SRO.  Make
     sure that the files are not flagged as Hidden.

9    If you are getting the error on all stations, have the
     program files been reinstalled?

10   Check the CONFIG.SYS file: Make sure HIMEM.SYS is at the top
     of the CONFIG.SYS file.  Put a SHELL= line in the CONFIG.SYS
     file.

11   Try copying WP.FIL and WP.EXE to a local drive.

12   Increase file handles on the server.

13   Try running TESTMEM.COM on the system getting the error.

14   With the 06/29/93 or later release, try using the /NH, /NE,
     or /32 startup switches.