Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!bhelf
From: bhelf@athena.mit.edu (Bill Helfinstine)
Newsgroups: comp.sys.cbm
Subject: Re: printing in direct mode?
Keywords: help
Message-ID: <1991Mar14.185749.6131@athena.mit.edu>
Date: 14 Mar 91 18:57:49 GMT
References: <1991Mar13.161420.28673@cbnews.att.com> <1991Mar13.201004.3965@nntp-server.caltech.edu>
Sender: news@athena.mit.edu (News system)
Distribution: na
Organization: Massachusetts Institute of Technology
Lines: 33

In article <1991Mar13.201004.3965@nntp-server.caltech.edu> rknop@nntp-server.caltech.edu (Robert Andrew Knop) writes:

>I believe you can avoid the problem with one more return being printed
>by using this construction:
>
>OPEN4,4,4 <return>
>CMD4:<command> <return>
>PRINT#4:CLOSE4 <return>
>
>Actually, since you've given the CMD4, you could probably get away with
>"PRINT:CLOSE4".

Actually, you can't get away with just doing a PRINT, since the printer
could care less about that last line, it is the computer that needs it.
When you use PRINT#4, it essentially cancels the effect of the CMD4
command, and tells further PRINT statements to go to the screen, rather
than the printer.  The computer gets a little confused if it thinks it
is still printing to file number 4, when that file has already been
closed.

Therefore, if you want to keep from sending that blank line to the
printer, change that last line to:

PRINT#4,"";:CLOSE4


>
>-Rob Knop
>rknop@tybalt.caltech.edu


Bill Helfinstine
bhelf@athena.mit.edu