![]() |
"Incompatible File Format" Retrieving Convert |
The information in this document applies to:
WordPerfect® 6.0 for DOS
Problem
Symptoms: WP 6.0 files converted from supplemental dictionary files using the SPELL.EXE utility for WP 6.0b do not retrieve into WP 6.0b. Instead, the error "Incompatible File Format" displays. (Note: The files do retrieve into WP 6.0a (09/13/93) without error, and will also add to WP 6.0b main dictionary successfully.) Steps to Duplicate: 1. Using WP 6.0b SPELL.EXE, choose option S to Convert Supplemental Dictionary to WP 6.0 file 2. Enter the name of the WP 6.0b .SUP file, and then enter a name for the new file 3. Exit SPELL.EXE, start WP 6.0b, and try to retrieve the new file The "Incompatible File Format" error displays. Solutions: As a workaround, it is possible to get access to the file by using Convert (CV.EXE). The following steps outline how this can be accomplished: 1. Launch CV.EXE from a DOS prompt (CV.EXE should be located in the WP 6.0 program directory) 2. Select Insert Job 3. Enter the converted supplemental dictionary filename from SPELL.EXE into the Source File field 4. Enter a new name for the Target File field 5. Select Auto-Detection for Source File Format 6. Select WordPerfect 5.2/5.1 for Target File Format 7. Select OK 8. Select Convert 9. When the conversion is complete, Press F7 10. Start WP 6.0b and retrieve the new file created with CV.EXE 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. |