mbeast@tls.UUCP (Michael East) (12/01/89)
Well, here's an interesting one. Does anybody know the command line
options to print a Scripsit file under Xenix? I would like to be able
to request printouts without having to enter Scripsit. The command
line is apparently cut off so I can't derive it easily. Any takers?
UID PID PPID C STIME TTY TIME COMMAND
root 0 0 16 Dec 31 ? 1:15 swapper
root 1 0 0 Dec 31 ? 2:07 /etc/init -n
root 23566 1 0 Nov 20 co 0:01 - 9
mbeast 2878 1 0 Nov 29 01 0:11 -ksh
root 24 1 0 Nov 16 ? 14:58 /etc/update
root 61 1 0 Nov 16 ? 20:11 /etc/cron
mbeast 11581 11574 0 00:16:10 01 0:04 vi + /tmp/post011574
lp 56 1 0 Nov 16 ? 0:01 /usr/lib/lpsched
mbeast 11596 11581 0 00:21:29 01 0:00 sh -c ps -afe
root 11585 1 0 00:19:24 02 0:01 - 6 tty02
mbeast 11574 2878 0 00:15:07 01 0:02 postnews
root 11597 11596 20 00:21:31 01 0:03 ps -afe
mbeast 11594 1 0 00:21:13 01 0:01 bp /usr/scripsit/
mbeast 11595 11594 0 00:21:14 01 0:00 bp.epson
I'm running a Model 16 but the n86 machines under SCO with Scripsit
should be the same if you know it.
Thanks in advance!
--- {uunet!attcan!utzoo,lsuc}!tls!mbeast ---------------------------------
Michael B. East Manager, Technical Support
Jonas & Erickson Software, Toronto #include <std.disclaimer>root@qcdev.UUCP (12/06/89)
/* Written 11:28 pm Nov 30, 1989 by tls.UUCP!mbeast in qcdev:comp.sys.tandy */
/* ---------- "Xenix Scripsit printing." ---------- */
Well, here's an interesting one. Does anybody know the command line
options to print a Scripsit file under Xenix? I would like to be able
to request printouts without having to enter Scripsit. The command
line is apparently cut off so I can't derive it easily. Any takers?
...
I'm running a Model 16 but the n86 machines under SCO with Scripsit
should be the same if you know it.
--- {uunet!attcan!utzoo,lsuc}!tls!mbeast ---------------------------------
Michael B. East Manager, Technical Support
Jonas & Erickson Software, Toronto #include <std.disclaimer>
/* End of text from qcdev:comp.sys.tandy */
I too have needed to perform this same task at times, it can be
done with Scripsit 16/Scripsit 286 using the following routine.
Enter into Scripsit as if you were editing a document, and create a
named user key, we'll call it 'printit' for this example. Capture
or edit the user key so it looks like:
** SCRIPSIT -- EDIT USER KEYS **
User key : printit
{print}{document}{execute}{execute}{quit}q
This gives the print command, defines the entire document,
executes the current print defaults, exits the document
and scripsit.
Save the user key and type in the following at the Xenix
shell prompt:
scripsit -x printit doc-to-print <ENTER>
Where 'doc-to-print' is the name of the scripsit document
you want to print. This example uses the scripsit
defaults for the print job. If you want(need) to change any
parameters for the shell-level print, just include the changes
in the user key. In this example, we'll change the printer to
a 'dmp430' and the number of copies to '2': (scripsit 286)
** SCRIPSIT -- EDIT USER KEYS **
User key : printit.1
{print}{document}{execute}dmp430{enter}{enter}{enter}{enter}{enter}2
{execute}{quit}q
Remember to include a 'TERM' setting in the shell-script if you
will be doing this as a backgroud process initiated from your
crontab, scripsit will freak out if you don't.
Hope this helps.
Keith Ward
...{techsup,sys1}!npqc!qcdev!{root,kward}
<All of the opinions stated above cannot be mine,
as my employer tells me I have none... >