|
Post by louisv on Nov 30, 2019 23:19:31 GMT 1
I have tried the following in autoexec.txt:
No print directives at all
lpt1 = dummy
lpt1 = dummy spool tio: 0 lpt1 = spool tio: 0
I am using an old DOS interpreted zBasic program that expects an old short list of dot matrix printers. vDos is doing a great job of trapping output to the #LPT1.ASC and #LPT1.TXT files. The problem is that I am not wanting any printer output. I intend to print the ASC file from a windows app. I have read the printing.pdf, but I must be missing something. That or my system itself is not cooperating.
MS Win 10 Pro 64 bit
Ver. 10.0.18363 Build 18363 Printer attached via network through router
Thanks,
louis
|
|
|
Post by Jos on Nov 30, 2019 23:31:03 GMT 1
Printer directives belong in config.txt, not autexec.txt.
If you want the printer output handled by a Windows program, it’s of course better to use the .TXT (Unicode) files. And eventually let vDos start the Windows program.
Jos
|
|
|
Post by louisv on Nov 30, 2019 23:39:50 GMT 1
Well there ya go... My eyes skipped the very clear "in config.txt" in printing.pdf. Shame on me.
thanks,
louis
|
|
|
Post by Jos on Dec 1, 2019 0:18:37 GMT 1
No sweat, realize the .ASC and .TXT files are always created, though not needed/used by vDos itself. The left hand of the “=” specifies what your program expects, to the right what vDos should do with that output. Can virtually be anything. vDos doesn’t trap printer output, it determines what to do when a DOS program prints (it’s a DOS emulator).
Jos
|
|