Top Navigational Bar

Epson MX-100 Not Printing Double Line Spacing
DocumentID: 644802
Revision Date: 29-Feb-96 8:19:01 PM

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

Problem

Symptoms: The customer is using an Epson MX-100 with 11/06/89 dates. The problem is that it will not print double line spacing. It will with Standard Printer in WordPerfect 5.1. It will with the Epson MX-100 driver in WP 5.0. Solutions: The developer created the WP 5.1 driver using WPCorp's MX-80F/T printer which is the most basic of the bunch. It does not print graphics, but works correctly with the vertical motion which was used. If this driver is not working for a user, they probably have an upgraded printer and should try the MX-80 Type III or Graftrax drivers.

Still there is a work around. The problem is in "Set VMI". After [27]"A"SENDLO(VS+128), which was used in WP 5.0, is the code [27]"2". This code puts the printer right back in single space mode (at 6 lpi). This is also a code that needs to be used after the [27]"A"SENDLO(VS+128), which will set the line spacing. The customer's printer might not recognize that the codes need to be used together. If you take out the [27]"2" it should solve the customer's problem. To do this:

1.      Enter PTR, retrieve in the ALL file, and Enter to edit the printer.
2.      Go to Vertical Motion and Enter, then Enter VMI.
3.      Enter Set VMI to edit the expression box and delete the [27]"2".
4.      Exit, Save, and Update.

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.