PDISK FILES HAVE EXTRA PRINTER INFO IN BODY (AREV Specific)
At 19 JAN 1998 08:49:45PM Jim Dierking wrote:
When we pdisk output there are usually printer code scattered
in the output. Has anyone else had this problem? Any suggestions
are appreciated. TIA, Jim Dierking
At 19 JAN 1998 11:17PM Don Bakke wrote:
Jim,
Are you pdisking coded print routines or list statements or what?
At 21 JAN 1998 03:58AM Jim Dierking wrote:
I am having the problem with coded print routines.
TIA for your help on this and other questions from
the past. Jim
At 21 JAN 1998 09:45AM Aaron Kaplan wrote:
PDISK will output whatever would have been sent to the printer to the chosen file. So, if the program would have sent some sort of initialisation string or font formatting or something to the printer, it would show up in the file. You wouldn't see it on the paper, since the printer would eat the strings to do whatever it is it wanted to do, you know, like set page length or orientation or something like that.
You'll have to look through the code and see if your sending these strings through a common routine or if you are using Revelation's printer formatting stuff. If you are, set up a new printer for file writes and kill all formatting options.
At 27 JAN 1998 11:05AM Victor wrote:
In addition to Aaron's comment, don't forget that the @() function in R/BASIC operates differently to screen than to the printer. When used with the printer, control codes could be sent to the printer, depending upon the settings of your printer configuration in Arev.