Re: WSCST and conflicts

[Kirk Goins <kirkgoins@xxxxxxxxx>]

In the past all I have done in the WSCST object was to remove the :CPICOR
tags and their assc data strings. This cause the printfiles defined over 80
chars. wide to use 13.2 CPI and COR is used to rotate the page to landscape.

Don't remember the impact on other forms needed specific fonts etc.


On Tue, Jun 21, 2011 at 8:04 AM, Pat Barber <mboceanside@xxxxxxx> wrote:

> Several months ago I modified a wscst for a customer so that the laser
> printer
> would do a better job of "filling" out the page with better spacing, etc.
>
> I recall that the instructions stated that ALL printed reports would be
> modified
> by the wscst and I figured that would be fine. The print really looks
> good and
> the customer was quite happy with the results.
>
> (I have lost the instructions on what mods I made to the wscst)
>
> Things change....
>
> We are now moving the AP checks from a old Lexmark 2391 dot matrix
> to the new laser printer.....
>
> The new printer is a Lexmark X466 and it is configured as LAN printer.
>
> I ran a few tests and discovered that the AP checks need to be printed
> at 6LPI
> and when using the printer with the modified wscst, it will NOT print at
> 6LPI.
>
> Isn't there a way to have two printer device descriptions pointing to
> the same
> printer ???
>
> One device description with the wscst and one without the wscst
>
> I can only vaguely remember doing this in the past.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.