Panasonic KX-P2130 dot matrix printer skips every 3rd form..

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Rob wrote:
> Software: SoftPro 8.5.1 peer to peer server configuration
>
> OS: Windows XP Pro (all machines), 4 clients, 1 server
>
> Printer: Panasonic KX-P2130 tractor/pin feed dot matrix
>
> Blank Checks: tractor/pin continuous feed 9.5" Wide x 7" High
> sequentially numbered in check stub followed by check repeating
> configuration
>
> Problem: Printing pending checks from ProTrust results in first check
> stub and companion check printing properly, second check stub form is
> skipped entirely and its check stub information is printed on the
> second check form, third check stub form is printed with second
> check's information, third check form is skipped entirely, fourth
> check stub and companion check prints properly once again...continues
> in this cycle
>
> ie. stub, check, missed stub, check printed with stub info., stub
> printed with previous check info., missed check, stub, check, missed
> stub, check printed with stub info., etc.
>
> should be: stub, check, stub, check, stub, check, etc.
>
> Jaquelin sp? from SoftPro acknowledged this problem occuring with
> Windows XP Pro combined with any dot matrix printer after having me
> try alternative compatable printer drivers Epson LQ860, IBM
> Proprinter x24e, Panasonic KX-P2123, 2124, 2023, 1124i, and creation
> of a "Custom Form" via Printers and Faxes, File, Server Properties,
> Create a New Form, English Units, Width: 9.5", Height: 7". This
> "Custom Form" once created only appears as an option for the IBM
> Proprinter x24e driver which only prints jibberish, and the Panasonic
> KX-P2023 which appears to have no effect.
>
> Interestingly, the KX-P2023 driver is the one used successfully with
> this same hardware configuration (clients, server, printer), but
> running on the Windows 98 operating system in another office.
>
> I have tried many other software and hardware printer settings to no
> avail.
>
> Do you have any suggestions?
>
> Thanks,
> Rob

Your vendor has not updated the driver for WinXP, or you have not
purchase the WinXP update.

Q