![]() |
"Invalid Data" Error Opening Files With Graph |
The information in this document applies to:
WordPerfect® 6.0 for DOS
Problem
Symptoms: When a user opens WP 5.1 files containing graphics into WP 6.0, the error "Invalid Data" displays. The error has been reported with the following types of graphics files: CGM files from PrintShop Deluxe for Windows version 1.0 .WPG graphics file from AccuDraw EPS files with TIFF headers from BorderBank AutoCAD 12.0 .WPG files from WP 5.1 DOS date 03/30/90 Solutions: This problem is corrected with the 02/14/94 (6.0b) release of WP 6.0 DOS. DXF files without a header section would return an "Invalid Graphics File Format" error when converting to WP 6.0 DOS. How/Why: The "Invalid Data" error occurs when an inconsistency in a graphics file is encountered. WP 6.0 takes a much closer look at graphics files to obtain an exact font match, gradient information, etc. Some of this information was ignored by WP 5.x. WP 6.0 requires the specification be more exact. The "Invalid Data" error message can occur with any graphics format when an inconsistency in a graphics file is encountered. Because of design changes to WP 6.0, WP now looks much more closely at the graphic format when converting and importing to ensure font matching, gradient information, etc. In WP 5.x, some errors were simply ignored. However, WP 6.0 will not allow the errors. Use the following troubleshooting steps to determine (with the customer on the phone) whether this error message is valid: Try running the file through the GRAPHCNV.EXE utility. 1. If the error "Bad Format" or "Invalid Data" occurs, then you can be sure that the graphic file contains errors. 2. If GRAPHCNV converts the file, try importing the resulting file into WP 6.0. a. If the file imports, then this is the solution and GRAPHCNV successfully corrected the errors. b. If WP 6.0 will not import the file, 1) Try bringing it into Presentations 2.0 (or another third-party product) and re-exporting. a. If the graphic still will not retrieve, you can determine that the file contains errors. Note: In most cases, users can work around the problem by opening the graphics into Presentations, marking all of the objects, saving the block, then opening the graphic in a WP 6.0 document. Important: In situations where the graphic (converted, original and PR 2.0's export) will still not import into WP 6.0, please have your customer send in a copy of each of these versions of the graphic and log an STR. Files need to be sent in so the technician can see if the problem has been fixed for that individual document. Other workarounds: Embed the graphic image in a WP 5.x document and then retrieve that document into WP 6.0. The user may then need to edit the figure in the Image Editor and invert the file for it to display and print correctly. Information about Specific Graphics Files WP 5.1 DOS before 03/30/90 Starting with the 03/30/90 release of WP 5.1, changes were made to the way WP imports and stores CGM graphics images (please see memos 10747T and 15992R for details). This problem does not occur if the same file is retrieved into the 03/09/92 release of WP 5.1, saved, and then retrieved into WP 6.0. To resolve this problem, technicians can either update the user to the 03/09/92 release of WP 5.1 and have the user resave the files; or have the user delete the graphics from the document and then import them into the document after the document is retrieved into WP 6.0. PrintShop The CGM export from PrintShop does not conform to the CGM standards that WP 6.0 expects. The text string length specified in the image descriptor does not match the actual length of the text string. Because of the difference, the error occurs and is valid (WP 5.1's GRAPHCNV.EXE will not convert the file either). According to Broderbund Technical Support (manufacturer of PrintShop), this problem has been reported to their development team. They state that their manual specifically says that the CGM format may not work with all other software. They recommend that the user export in other formats (PCX, TIFF or EPS) to import into programs that have problems with their CGM format. Their basic recommendation is that users export in a PCX Large format. They indicate that this should be the most compatible format. Please refer users who have additional questions to Broderbund Technical Support. AccuDraw .WPG files from AccuDraw contain a record number 52. Version 1.0 of the WPG format does not have a record 52, but record 52 is a valid WPG 1.0e PostScript Header 2 record. The PostScript header 2 record must be followed by a PostScript data record. WP 6.0 does not return an error message because it does not handle the PostScript 2 header record. The record is skipped and the rest of the file converts properly. WP 6.0a handles the PostScript 2 header. However, if the header is not followed by a PostScript data record, an "Invalid Data" error is returned. AccuDraw has its own record numbers that do not conform to the WPG format. It also has a record number 53, which is an invalid record number in all versions of the WPG format, but it is skipped during import. Evidently, PR 2.0 does not care what follows the PostScript header record, so it is lost when it is pulled into PR 2.0. Customers experiencing this problem should contact AccuDraw and request a utility file named STRIPWPG that fixes some of the errors, thus allowing the graphics images to import into WP 6.0 and WPWin 6.0 without the error message. BorderBank (by FontBank) These EPS files are in an earlier version of EPS than what WP currently supports. The EPS files are version 1.1 and 1.0. WP 5.x supports the Adobe 2.0 PostScript version, and WP 6.0 supports this and Adobe EPS version 3.0. Because of this, the EPS files will not import into any WPCorp software. There are other third-party programs (i.e., Designer 3.1 and CorelDRAW 3.0) that the BorderBank files will not import into either. Files that do import into WP will have problems printing or cause display errors because they do not conform to the format WP supports. |
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. |