|
|
Post by greybeard on Feb 2, 2021 18:58:45 GMT 1
Hey Jos, I am currently using a Dos application on a windows xp network, printing to a network (shared) receipt printer. I added a windows 10 computer to this network using Vdos to access the dos application. Vdos has afforded me effortless access, but am having formatting issues with the printed invoices. I added Lpt2="network printer name" RAW to my config.txt file without success. Your help will be greatly appreciated. Thanks
|
|
|
|
Post by Jos on Feb 2, 2021 19:37:05 GMT 1
RAW instructs vDos to not interpreter the printer data, but pass it as-is on to the printer driver.
That network printer is a DOS or Windows GDI printer? Could you submit an example of the formatting issues?
The syntax of Lpt2= should be:
Lpt2=SEL: "network printer name" RAW
But you probably meant that.
Jos
|
|
|
|
Post by greybeard on Feb 2, 2021 20:45:15 GMT 1
Hey Jo's, thanks for your quick response. My network printer is Dos. I will send examples soon, it is wrapping around the information and form feeding at the end.
|
|
|
|
Post by greybeard on Feb 2, 2021 21:23:41 GMT 1
Please see attachment as per your request Attachments:
|
|
|
|
Post by Jos on Feb 2, 2021 22:06:39 GMT 1
Seems like the printer driver at the server is messing up the output.
Could you verify that is a Generic Text Only driver and rendering ‘is done’ at the client side on the share tab.
Eventually copy the #lpt2.asc file generated by vDos at the Windows 10 PC to the server. And print it there, at the Windows command prompt with a COPY #lpt2.asc lpt2. Or open #lpt2.asc by notepad and print to the installed driver.
Jos
|
|
|
|
Post by greybeard on Feb 2, 2021 22:47:14 GMT 1
Hey Jo's, thanks for your quick response. My network printer is Dos. I will send examples soon, it is wrapping around the information and form feeding at the end. I am noticing that the config.txt statement is not changing the printing outcome, the result is the same without it. |
|
|
|
Post by greybeard on Feb 2, 2021 22:53:56 GMT 1
Seems like the printer driver at the server is messing up the output. Could you verify that is a Generic Text Only driver and rendering ‘is done’ at the client side on the share tab. Eventually copy the #lpt2.asc file generated by vDos at the Windows 10 PC to the server. And print it there, at the Windows command prompt with a COPY #lpt2.asc lpt2. Or open #lpt2.asc by notepad and print to the installed driver. Jos Will do and let know |
|
|
|
Post by greybeard on Feb 3, 2021 17:38:08 GMT 1
Seems like the printer driver at the server is messing up the output. Could you verify that is a Generic Text Only driver and rendering ‘is done’ at the client side on the share tab. Eventually copy the #lpt2.asc file generated by vDos at the Windows 10 PC to the server. And print it there, at the Windows command prompt with a COPY #lpt2.asc lpt2. Or open #lpt2.asc by notepad and print to the installed driver. Jos Will do and let know Hey Jos, the driver is Generic Text Only. The attached is the prints I got printing from the print Server, I also added a new printer opting to install updated driver (Generic Text Only) and the output is the same |
|
|
|
Post by greybeard on Feb 3, 2021 17:45:14 GMT 1
Seems like the printer driver at the server is messing up the output. Could you verify that is a Generic Text Only driver and rendering ‘is done’ at the client side on the share tab. Eventually copy the #lpt2.asc file generated by vDos at the Windows 10 PC to the server. And print it there, at the Windows command prompt with a COPY #lpt2.asc lpt2. Or open #lpt2.asc by notepad and print to the installed driver. Jos Will do and let know Hey Jos, the driver is Generic Text Only. The attached is the prints I got printing from the print Server, I also added a new printer opting to install updated driver (Generic Text Only) and the output is the same |
|
|
|
Post by greybeard on Feb 3, 2021 17:46:27 GMT 1
How do I include attachment?
|
|
|
|
Post by Jos on Feb 3, 2021 19:01:01 GMT 1
You can add attachments by using the Reply button at the right of the blue bar.
Could you meanwhile instead of:
Lpt2=SEL: "network printer name" RAW
Try:
Lpt2=SEL: "\\server\shared printer name" RAW
At least the printer driver at the Windows 10 PC is then not used.
Jos
|
|
|
|
Post by greybeard on Feb 4, 2021 0:31:10 GMT 1
I tried your new config statement but getting the same out come. The printer driver at the Windows 10 machine seems to be causing the issue, it's formatting the invoice at this end. Please see the attachments taken from Windows 10 computer Attachments:LPT1.asc (829 B)
LPT1.txt (1.51 KB)
config.txt (3.26 KB)
|
|
|
|
Post by greybeard on Feb 4, 2021 0:33:21 GMT 1
|
|
|
|
Post by Jos on Feb 4, 2021 9:43:34 GMT 1
The last line in config.txt reads:
LPT2=SEL:"\\Cashier\Invoice" RAW
While you sent lpt1.asc and lpt1.txt.
So your program would print to LPT1, not LPT2, and it should be:
LPT1=SEL:"\\Cashier\Invoice" RAW
It’s not the printer driver interfering, but vDos. The printout is too far to the right because the default left margin is 15 mm (0.6”), so you should have something like:
LPT1 = SEL:"\\Cashier\Invoice" horz: 6,10,80 vert: 6,10,66
If you would like to be able to print to a Windows GDI printer. But you can of course just stick with RAW.
Jos
|
|
|
|
Post by greybeard on Feb 4, 2021 17:26:26 GMT 1
Hey Jos, my printing issue has been resolved, thanks a million. I had not included the environmental variables in Vdos' Autoexec.txt...thanks again
|
|
