PureBytes Links
Trading Reference Links
|
PRN files are ASCI files(like TXT), but have the possibility to contain ALL of the set-up and
futher commands and instructions(fonts,with,color etc.) for a printer required to print such a
file "straight" from DOS(thus without any further programs inter-acting).
This PRN(PRiNt) stems from the ancient Dos times, as then everyone had to share a printer,
and this file type then enabled any user direct Dos "quick access" to the file and do more
multi and/or repeatatly printing jobs of the file.
ASCI files can be viewed in any word/text processing program(eg NotePad) but PRN files
as such can contain the for humans unreadable "machine language"(eg the printers set-up
commands and instructions, see above.).
In SysTest and Explorer(reports):
By selecting a single line and hit Ctrl-C, you can then paste clipboards contents to any ASCI
word-processing programs files, with Word or Excel here giving the best results(incl WordPad).
This way you can then by-pass any of the unreadable mumbo jumbo contained in a PRN file.
In Word and Excel too, you can easy 'manualy' append to a file.
Renaming a files extension from PRN into TXT would give default NotePad to open it.
(however extension changing the file type can destroy any printing setup+comm+instr., see
above).
Reg. Ton
-----Oorspronkelijk bericht-----
Van: David Duggan <mmaker@xxxxxxxxxxx>
Aan: metastock@xxxxxxxxxxxxx <metastock@xxxxxxxxxxxxx>; support@xxxxxxxxx <support@xxxxxxxxx>
Datum: zaterdag 3 oktober 1998 16:48
Onderwerp: Autorun and Metastock
>I am trying to create an Autorun exec for the system tester feature in
>Metastock 6.5.
>
>Two questions:
>1) When I run an autorun exec using the system tester and attempt to print
>the second system test report using "print to file" there are only two
>options. Option A is to create a new file. Option B is to overwrite the
>existing file. In the old DOS versions we had the option of appending to
>the file. Has this feature been removed? How can I work around this issue
>- this is my only roadblock at this point.
>
>2) Is there anyway to view a *.prn file?
>
>If anyone has any ideas I would be glad to hear from you.
>
>David Duggan
>
>
>
|