![]() |
Troubleshooting "Insufficient File Handles To |
The information in this document applies to:
WordPerfect® 5.1 for DOS
Problem
Solutions: The following troubleshooting steps may eliminate the error message "Insufficient File Handles To Run WP." 1. One customer received the message "Insufficient File Handles To Run WP" when entering WordPerfect on a non-dedicated file server on a LANtastic network. LANtastic's server has the ability to read files from the CONFIG.SYS file or from the server configuration, which is set up in NET_MGR. This server was set up to read from the network configuration file, not from the CONFIG.SYS. Once the customer changed this, the problem was eliminated. 2. Another customer, running DP 2.2, WP 5.1, and Office 3.01 on a TOPS network, received this error when shelling between DP and WP. The error "Invalid OP Code" then appears. The customer had insufficient file handles allocated on the TOPS Server. Increasing the number of files allowed to be open on the file server corrected the problem. This is a configuration problem on the server, not an application problem. 3. Another customer received the error "Insufficient File Handles" after executing WP from Shell and then exiting WP back to Shell. The customer is using an AT&T Stargroup network and Office 3.1. This problem only occurred on two specific machines which were both AT&T computers. One was a 286 machine, and the other was a 386. Running SHELL.EXE from the hard drive of the machines rather than from the network solved the problem. 4. Another customer was loading the FILES and BUFFERS into the upper memory blocks with QEMM 6.0 and received this error when entering WP. The problem was corrected by changing the statement LOADHI /R:1 FILES=+50 to LOADHI /R:1 FILES +50 (no equal sign) in their CONFIG.SYS. Update: As of January 7, 1992 QuarterDeck version 6.02 can ignore the "=" sign and correctly load the specified number of files. 5. Generally, users who receive the error message "Insufficient File Handles To Run WordPerfect" need only to increase the number of files in the CONFIG.SYS file to correct the error. However, some users may find that this does not correct the problem. If it does not, it may be possible that the computer is reading a CONFIG.SYS file found in a directory other than C:\. This could happen if the customer's hard drive has been partitioned. One way to verify that the C:\CONFIG.SYS file is being read is to add garbage characters to the CONFIG.SYS file and reboot the computer. If the C:\CONFIG.SYS file is accessed, the message "Unrecognized Command In CONFIG.SYS" will appear. If the message does not appear, the user will know that another CONFIG.SYS file is being read. The CONFIG.SYS file could be located on a ROM drive or the user may be using some other configuration to boot the system. Note: The CONFIG.SYS file is stored in a location other than the C:\ drive on TANDY 1000 (see memo 11259T) and IBM PS/1 (see memos WP51_2290C and WP51_4471B) computers. 6. A customer using a file stacker (which made his computer recognize drive C: as if it were drive D:) received the error "Insufficient File Handles To Run WordPerfect" when entering WP. The stacker modified the CONFIG.SYS and placed it on drive D. The error was eliminated by increasing the number of files in the CONFIG.SYS file on drive D: to 30. 7. Another customer had three different FILES commands in the CONFIG.SYS file. Deleting two of those commands and rebooting eliminated the error. 8. Another user received this error message because the CONFIG.SYS file had been saved in WP format. When the user entered TYPE CONFIG.SYS at the DOS prompt, the file displayed as garbage. To correct the problem, the user renamed the CONFIG.SYS file to old, created a new CONFIG.SYS file, rebooted, then retrieved CONFIG.OLD file into WP and used Ctrl-F5 to save it out in ASCII format as CONFIG.SYS. 9. A customer using a Sanyo Notebook computer received this error when entering WP. The CONFIG.SYS file was located in the computer's DOS directory, so the user created a new one in the root directory. This step eliminated the error. Simply copying the original CONFIG.SYS file to the root directory did not correct the problem. 10. The user received the error message "Error: Insufficient File Handles To Run WP" after exiting out of the network copy of WordPerfect and then trying to re-enter. The message does not appear if the user accesses the stand-alone copy of WP. The user is running IBM PC Support (Release 3) to access a Type 2 shared folder on the AS400 machine. The user can duplicate the problem by entering List Files, changing to the drive letter assigned to the AS400 machine, retrieving a file, exiting WP, and then trying to enter the program again. If the customer loaded the device driver ECYDDX.SYS into conventional memory, the problems no longer occurred. 11. This error could appear when a diskless workstation on a Novell network. The diskless workstation reads a file named SHELL.CFG. This file contains the configuration values for the workstation, including the FILES= statement. The SHELL.CFG is written in ASCII format and can be edited to increase the file handles. Users should contact the LAN administer for further details. The SHELL.CFG file tells the NET2.COM, NET3.COM or NET4.COM how many files can be open on the network. The Novell network default is 40. The SHELL.CFG file (according to Novell) should be located on the boot disk of the machine. A special file is used when a user is on a diskless workstation where the boot disk is the network. Rather than change the SHELL.CNF file, the change to be made is done in the CONFIG.SYS for that machine. Novell has a special utility called DOSGEN that generates bootfiles for diskless workstations. This includes the SHELL.CNF (if they have one) as well as CONFIG.SYS, COMMAND.COM, AUTOEXEC.BAT, and the DOS system files. 12. Another customer found part of the problem to be a 3270 mainframe emulator card in the computer. The customer was able to successfully start the program after renaming the AUTOEXEC.BAT and using a 3.0 version of DOS COMMAND.COM. CHKDSK showed the computer had 10 lost clusters. 13. Two out of 25 users received this error when starting WP from Shell. The users were on an OS/2 LanMan network. The customer added SET WPC=/NT=4/D-C:\TEMP into AUTOEXEC.BAT to correct the problem. This corrected the problem even though all environment files contained the same options and the startup command lines contained them also. |
Answer:
Details:
Product specifications, packaging, technical support and information (*Specifications*) refer to theUnited States retail English version only. Specifications for other versions may vary. All Specifications, claims, features, representations, and/or comparisons provided are correct to the best of our knowledge of the date of publication, but are subject to change without notice.OUR MAXIMUM AGGREGATE LIABILITY TO YOU AND THAT OF OUR DEALERS AND SUPPLIERS IS LIMITED. IT SHALL NOTEXCEED THE AMOUNT YOU PAID TO ACCESS THE INFORMATION. SEE LEGAL DISCLAIMER. |