Troubleshooting The "Error 0" Message

DocumentID: 638053
Revision Date: 29-Feb-96 3:04:49 PM

The information in this document applies to:
WordPerfect® 5.1 for DOS

Problem

Solutions: "Error 0" is caused by a damaged document or by DOS when no error is available or the error number DOS returned isn't included in the DOS technical reference. If it happens with only one file, then the file is probably damaged. This could have occurred in the 08/20/90 or earlier releases of WordPerfect 5.1. With the 12/31/90 release, the file could be deleted after encountering the damaged area. (This is an extremely simplified statement of what actually occurred.) In the 05/31/91 release, the error message is "File Creation Error" and the program won't delete the damaged file. Unless the user can create a file from a blank screen and immediately have the error re-occur when saving it, the error usually applies to only one file (the one that gives the error message.) If the user can't provide keystrokes that caused the problem, it would be pointless to involve Problem Resolution with STRs on the situation. If the error occurs while performing a WP feature and you can duplicate it, enter an STR under that feature name. If DOS is giving the "Error 0", it may be difficult to tell what the problem is immediately. If the error is occurring with newly created files that contain no data from the 08/20/90 or earlier dates of WP 5.1, let the customer know that Problem Resolution is interested and needs keystrokes. If the customer can provide keystrokes, pick the appropriate feature that appears to have started the problem and enter an STR. Customers who experience this problem should be updated to the latest interim release. STRs only need to be written for users who continue to have problems after updating to the 05/31/91 or later interim release. The following are some ways to work around or eliminate the "Error 0" message: 1. The customer may be able to block the document and save it. 2. If that doesn't work, the customer can try to block the document, copy it to Document 2, and save it with a new name. A variation on this option that might also work is to block the document, delete the block, restore it on the Document 2 screen, and save it. 3. The customer can try to save the document as ASCII text (Ctrl-F5, 1, 1). 4. If the customer is trying to save a document with a served filename (e.g., CON, AUX, NUL, PRN, etc.), this error message may appear. 5. The customer can set the Fast Save option (Shift-F1, 3, 5) to No. 6. Novell's network Shell version 3.02 or later allows the user to set the number of cache buffers. If the cache buffers are set to anything except zero (0), the files will not be saved correctly and the user may receive the message "Error 0" when saving files. This same problem occurs when using Novell 3.11 and 3.10a shell. If the user adds the command CACHE BUFFERS = 0 to the SHELL.CFG file, the problem will be eliminated. Note: The SHELL.CFG file should be located in the same directory as the IPX and NETx files are executed from (where x represents the number being used, e.g., Net2, Net3, etc.). The version of the Shell can be found by typing NVER at a DOS prompt. A long-term solution would be to upgrade from NET5.COM to NETX.COM (Shell 3.22). 7. A customer on a DEC PCSA network changed PCSA disk caching from open to closed to eliminate this error message. 8. The IPX version 3.02a shell interferes with WordPerfect's ability to save files. Novell now has a new Shell available that is dated 06/18/91 NETx version 3.20, the IPX is version 3.03. This update will correct the problem. To generate a new version of Shell, do the following: 1. Go into COMPUSERVE and type "GO NDD" 2. Download the file DOSUP3.ZIP 3. Use the SHELL GEN utility on this file The version of the Shell can be determined by typing NVER at a Network drive prompt. 9. If the customer is on a network, check the directory entries left on the network. There may be an insufficient number left. Using CHKVOL will help determine if this is true. 10. One customer using expanded memory worked around the error by starting WP with /NE. 11. One customer using the 05/31/90 interim release found that the error message didn't occur after renaming the .SET file or starting WP with the /X startup option. If this is the case, please write an STR with complete hardware information and ask the customer send in a copy of the old .SET file. Status: Sent to Development ***|sent to dev|*** Press Enter on link token.

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.