printing in windows 10 x64

[ochango]

hello group, hello jos

i am using vdos 05/19/2022 in a w10 x64, and trying to print to an usb epson lx350

my config.txt printer statement is

lpt1 = sel:"EPSON LX-350"

as simple as that

vdos recognizes the printer and as i order a printout, monitoring the print queue shows that it fills up, shows that it starts printing but, never closes, the printer does not print the aplication's report

the application is a payroll in clipper 5.03, and tested on a w10 x32 prints as it is expected to

if you need more detail, please ask for it; i am almost (or in fact) out of options

regards 

octavio

[ochango]

i have used the tio:5 and the raw options with the same result

[Jos]

Probably you cannot print to the Epson from any Windows application.
If so, clear the print queue and eventually restart the PC if one or more documents remain in there.

Jos

[ochango]

i haven't tried other than the test page

right now i'll doing that test

the print queue, as i said; fills up with the print job i (the clipper program) send, it is received, it appears to print, but never gets cleared; that has to be done manually

after i test a window program, i'll be getting back to you

thank you

octavio

[emendelson]

There's a Windows printer driver available from Epson that says it's compatible with 32-bit Windows. It's possible it will work under 64-bit Windows, but there's no way to know that without trying it:

epson.com/Support/Printers/Impact-Printers/LX-Series/Epson-LX-350/s/SPT_C11CC24001

Use the drop-down menu under Operating System and choose Windows 10 32-bit. (It says nothing is available for 64-bit.)

[ochango]

Jun 3, 2022 14:04:00 GMT 1 Jos said:

Probably you cannot print to the Epson from any Windows application.
If so, clear the print queue and eventually restart the PC if one or more documents remain in there.

Jos


jos, other than the test page, i printed an excel document

i'm attaching both

as i mentioned earlier

the print queue has been cleaned and creared every time with every test, it remains not cleared at the end of the printing with vdos

Attachments:

[ochango]

Jun 3, 2022 15:33:28 GMT 1 emendelson said:

There's a Windows printer driver available from Epson that says it's compatible with 32-bit Windows. It's possible it will work under 64-bit Windows, but there's no way to know that without trying it:

epson.com/Support/Printers/Impact-Printers/LX-Series/Epson-LX-350/s/SPT_C11CC24001

Use the drop-down menu under Operating System and choose Windows 10 32-bit. (It says nothing is available for 64-bit.)


======

mendelson

as of this moment i'll try anything

and this driver will be no exception, thanks for the tip, i'll be commenting the outcome

this tip, jos's answer and changing the driver for a text-only (which i dont want to do); will be my last effort before telling my client that all (ALL) the efforts and all of the solutions available "DID NOT WORK"


thanks for all the help received form both of you

octavio

[Jos]

I never heard of such a problem, other Windows apps not having the same issue.

As you mentioned you could eventually assign the Text Only driver to the Epson. And use lpt1 = sel:"EPSON LX-350" RAW. In combination with the RAW option, the driver doesn’t matter. But Text Only is a well established factor.

Jos

[Jos]

One more test comes to mind: What if you rem-out the lpt1 = line, and at printing select a virtual printer like Microsoft Print to PDF.

Jos

[ochango]

jos

thank you for your pointers; i'll be trying all three options as of today, tomorrow i shall reporte again