Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cs.dal.ca!ug.cs.dal.ca!digdon
From: digdon@ug.cs.dal.ca (Mike Digdon)
Newsgroups: comp.sys.cbm
Subject: Re: Reading SEQ files
Message-ID: <1991Mar4.132134.27485@cs.dal.ca>
Date: 4 Mar 91 13:21:34 GMT
References: <1991Feb27.213545.18354@nntp-server.caltech.edu> <1991Mar02.032753.23899@ddsw1.MCS.COM> <39733@cup.portal.com>
Sender: news@cs.dal.ca (USENET News)
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Lines: 20
Nntp-Posting-Host: ug.cs.dal.ca

In article <39733@cup.portal.com> CTuna@cup.portal.com (Image - BBS) writes:
>It's ok... printing to the SCREEN leaves ST intact.  If you print to a
>FILE (i.e. printer, disk), then you would want to use that code. But for
>screen alone, uou are ok.

Actually, printing to the printer doesn't make any difference either.
Since you have to read from the disk first, if a problem occurs, then you
have a chance to use ST to end the program before it gets printed.
Here is the code that I use when printing SEQ files:
10 open4,4,7:open2,8,2,"filename,s,r"
20 get#2,a$:ifst<>0thenclose2:close4:end
30 print#4,a$;:printa$;:goto20
And it runs with no problems everytime, and it always stops when it is
supposed to (IE: at the end of the text file)

-- 
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	+   Mike Digdon: digdon@ug.cs.dal.ca  + My 64 can still get the +
	+		 mike@ac.dal.ca	      + job at hand completed!! +
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+