|
Post by jjjoseph on Apr 14, 2019 3:01:42 GMT 1
Many discussion threads mention a "printing.pdf" file to find more information on directing output. I don't see that file in my vDOS files. How do I find a copy of this file?
Thanks!
|
|
|
Post by Jos on Apr 14, 2019 9:53:53 GMT 1
Printing.pdf is installed in the vDos directory. Before version 2016.06.01 there was DOSPrinter.pdf.
Jos
|
|
|
Post by jjjoseph on Apr 14, 2019 21:50:24 GMT 1
I downloaded and installed a fresh vDOS, and my directory contains only the following: DPTEST autoexec.txt config.txt Readme.pdf vDos.exe
Checked through previous installs and archives, searched the entire system, and I don't see any "Printing.dbf". I have an old copy of DOSPrinter.pdf, but the register/purchase link goes only only to a dead-end page that says "Shop Closed".
|
|
|
Post by Jos on Apr 14, 2019 22:04:45 GMT 1
It's "Printing.pdf", one of the five files installed in the vDos directory. You could first delete the (present/old) vDos directory, but I don't see the relevance. The "Printing.pdf" document is always installed.
Jos
|
|
|
Post by jjjoseph on Apr 15, 2019 4:18:56 GMT 1
Thanks for being patient with my question and my spelling mistake. If Printing.pdf is installed, where is it? Or is there another way to read it? I don't want to delete the old vDOS directory because then I'll have _NO_ printing information and no link to the DOSPrinter application. Searching for DOSPrinter brings up an application called "Printfil". Is that the same as DOSPrinter? At least I have something from the old install files.
To my thinking, if I can't see it therefore I can't read it. Or am I mistaken?
|
|
|
Post by jjjoseph on Apr 15, 2019 6:30:14 GMT 1
I forgot to mention that my vDOS install directory has only 4 files (not 5 files):
autoexec.txt config.txt Readme.pdf vDos.exe
and a "DPTEST" directory
|
|
|
Post by Jos on Apr 15, 2019 7:10:07 GMT 1
If there’s no Printing.pdf file in the vDos directory, I guess it is deleted. Anyway, here it is. The website of DOSPrinter is www.dosprinter.net. Printfil (www.printfil.com) is another print processor. It’s at the top of Google because they pay for advertisement. It appears the developer of DOSPrinter has ended his relation with SWREG. I'll delete the two purchase links; one will have to contact the developer “for further details about prices and purchasing options”. Jos Attachments:Printing.pdf (50.7 KB)
|
|
|
Post by jjjoseph on Apr 26, 2019 6:28:36 GMT 1
Thanks for sending the Printing.pdf file. After all that correspondence, I find that my DOS application (VP-Info/SharkBase) is able to handle most of the Windows printer challenges by optionally spooling output to a specified folder as a plain txt file, which can then be easily re-formatted with any Windows tools if needed. Saves a lot of paper!
FWIW, the suggested vDOS font (consola.ttf) is not that good. I'm using cousine+.ttf which works much better in VP-Info, including the extended characters. Don't know where I found it several years go, but it's useful.
Your help is appreciated.
|
|
|
Post by Jos on Apr 26, 2019 8:37:20 GMT 1
The Windows Consolas font is only mentioned in an example how to set another font than that of vDos itself. While the latter resembles Cousine, it’s more optimized for DOS usage and more complete.
You’re actually using vDos 2018.05.01, or an older version?
Jos
|
|
|
Post by jjjoseph on Apr 28, 2019 16:56:43 GMT 1
I'm using vDOS 2018.05.30, but the default font & the Consolas font are very difficult to use in business apps so I'm constantly on the lookout for a better font.
|
|
|
Post by Jos on Apr 28, 2019 18:41:04 GMT 1
|
|
|
Post by jjjoseph on May 1, 2019 0:32:51 GMT 1
Checked thru dozens of the fonts at FontSquirrel, but most have one defect or another. Boxes instead of lines/arrows, for example, un-dotted zeros, or dashed lines instead of continuous lines. Still the best I've found is COUSINE+.TTF, which is much better than the standard COUSINE fonts group, except I don't know where I found it! I can send you a copy if you're interested.
|
|
|
Post by Jos on May 1, 2019 0:48:45 GMT 1
Thanks, but no. The internal vDos font is optimized for DOS screen/raster dimensions, beyond what COUSINE+.TTF or any other font can offer. Dotted/slashed zeros are a personal preference (I myself don’t like that DOS legacy at all). Lines should be forced by a preceding minus sign to the font file name.
Jos
|
|