|
Post by drouleau on Dec 19, 2018 22:16:02 GMT 1
Good day I'm new to this application I have been able to start my DOS application works fine But when I tried to print it just create a .asc file (LPT1.asc) And then noting else happend
in my config.txt fil I have add
LPT1 = SEL: ""
and when I print I was expecting to get a box to select my windows printer where to send the printing result but notting is happening after printing except the creation of the lpt1.asc file
My goal would be to be able to print to a network printer directly whitou having to select anything
so what I would like is for the LPT1 to be redirect to \\"domain_controler"\"printer_share_name"
Currently my application is running on a windows 2003 server and the DOS command I use is net use lpt1: \\"domain_controler"\"printer_share_name"
But I want to remove the 2003 server and make my app work on a 2012 64 bit server Currenly from the test I have done I'm only missing the printing side, if this work I will register to the networked version
The printer is configured as a lexmark e250 with universal lexmark driver and is priting fine from DOS on the 2003 server
How could I make the application automatically print to a network printer
Thanks Daniel
|
|
|
Post by Jos on Dec 19, 2018 22:38:57 GMT 1
With “LPT1 = SEL: ""” you instruct vDos to select the Windows default printer. Don’t know what that is, so neither why vDos won’t print. First loose that line, so the Windows Printer Selection dialog will popup. Select the printer driver that is connected to your printer. If that goes fine, change SEL: "" to SEL: "whatever selected in the dialog". The Lexmark e230 will be a DOS capable printer, so you could add the RAW option to get the exact output as before. However, for the long term it’s better to use Windows printing (no RAW option). Though you then probably have to experiment with the margins. Those (HORZ and VERT) are metric/European orientated . Jos
|
|
|
Post by khaleed on May 8, 2019 16:36:06 GMT 1
Good Day, im having the same issue. It only creates lpt1.asc file alone and doesn't print. Even if I remove the "lpt1=sel" line, the Printer selection dialog doesn't pop up. Any help will be appreciated.
|
|
|
Post by Jos on May 8, 2019 16:44:19 GMT 1
Could you post the #lpt1.asc and config.txt files?
Jos
|
|
|
Post by khaleed on May 8, 2019 17:20:28 GMT 1
|
|
|
Post by Jos on May 8, 2019 17:34:10 GMT 1
No problem to print your LPT1.asc file, with or w/o printer selection. Could you first install the latest 2019.05.01 version, and test again. If the issue persists, start vDos with the log option(“…vDos.exe” /log), and post the generated vDos.log file.
Jos
|
|
|
Post by khaleed on May 8, 2019 17:52:30 GMT 1
Ok, I just updated to 2019.05.01 version and I got the printer selection box. However when I select the printer which is physically Lpt1 connected, the document in queue for that printer just keeps flashing! continuously, like 10 times per second and it goes from spool to printer continuously as well. Attachments:
|
|
|
Post by Jos on May 8, 2019 18:11:18 GMT 1
Either:
Search the Internet for “local downlevel document” solutions, or Undo all you probably previously did to enable printing from DOS, or Add and use a new OKI (eg OKI-2) printer connected to LPT1, or Print to an USB or network printer.
Jos
|
|
|
Post by rahul277 on May 21, 2019 11:57:30 GMT 1
vdos hangs when i try to print thru "Microsoft print to PDF" option in windows 10 (Vdos May update used)
|
|
|
Post by Jos on May 21, 2019 13:04:33 GMT 1
You’re not the first with this issue, though it’s actually the "Microsoft print to PDF" driver hanging.
Try one of the (freeware) virtual PDF printers, like Bullzip, those are also more versatile.
Jos
|
|
|
Post by jd on Sept 17, 2019 21:43:28 GMT 1
I'm evaluating the latest version of vDos 2019-05-01 on a Win10 Pro 64bit portable. A "network" Brother printer is installed on the machine. I changed autoecxec.txt as follows: LPT1=SEL:"Brother MFC-L2720DW series Printer"
Problem: When my DOS app prints to LPT1, the Printing Dialog is shown while I expect it "not" to appear and just print since I specified the SEL: option with the name of the choosen printer. Do I mis understand the docs?
PS: I can't use the default printer SEL:"" because your docs tell me: * Default: display a printer dialog.
|
|
|
Post by Jos on Sept 17, 2019 21:57:05 GMT 1
The only reason (I can come up with) for the Printer Selection Dialog being displayed is your program printing to another port/device. Check the vDos directory that #lpt1 files are created (not for instance #lpt2).
LPTx/COMx = SEL:"" should select the default Windows printer (w/o the Printer Selection Dialog). * Default is no SEL: is specified.
Jos
|
|
|
Post by jd on Sept 17, 2019 23:35:13 GMT 1
I can assure you the #LPT1.asc and the #LPT1.txt files are created in the default vDos program directory! I now have set up a new local COM3 port in that same machine (LogiLink USB2.0 Serial Adapter USB->DB9, found by windows and configured automatically as COM3:) and attached a serial printer Epson LQ570+ to it. Printer works fine in Windows (testpage). When the dos app prints to the COM3 port, the files #COM3.txt and #COM3.asc are created in the default vDos program directory. Still the Dialog appears and shows me the default Brother Windows printer instead of the expected Epson Windows printer connected to that COM3. When I then select the Epson, the output is printed as expected. So the "Printer Selection Dialog" is popping up and this is absolutely not wanted! Of course, my autoexec.txt has a line: COM3=SEL:"Epson".
I then have changed the autoexec.txt as: COM3="COM3": Then: TYPE #COM3.asc >COM3: and also TYPE #COM3.asc >COM3 both do show me the unwanted Printer Selection Dialog...
|
|
|
Post by Jos on Sept 17, 2019 23:48:36 GMT 1
No explanation for this vDos behavior. Could you start vDos with the /log option ("…vDos.exe" /log), and post the generated vDos.log file.
<DOS device>="<Windows device>": isn’t meant for (regular) printing, a Printer Selection Dialog doesn’t even apply.
Jos
|
|
|
Post by jd on Sept 18, 2019 7:42:25 GMT 1
The log file contents is: vDos 2019.05.01 0.09 C: => (Local) C:\vDos\
Execute: LPT1.COM - =SEL:"Brother MFC-L2720DW series Printer" Program not executed/loaded (2): LPT1.COM
0.51 Execute: COM3.COM - =SEL:"Epson" 5.67 Program not executed/loaded (5): COM3.COM 31.96 Internal printing 4799 bytes 51.93 vDos ended by EXIT (-1)
Apparently the LPT1.COM and COM3.COM programs are not executed/loaded? Do I miss them?
|
|