BURATI@ULOWELL.CSNET ("Michael R. Burati") (05/23/86)
I have a new version of GNU emacs with the apollo information included,
but when I try to install (make) it, I get an error on
#include <nlist.h>
I looked and couldn't find nlist.h in either the bsd4.2 or sys5 include directories. Where is it supposed to be, and why don't I have one?
-------------------------------------
I've been hearing that sr9.2 is supposed to clear up my problems with tcp/ip
(the servers die or hang on a regular basis), and also v2 has been discussed
a lot on the net (available with 9.2).
When (if it's not already) is sr9.2 supposed to be released. It seems
that a lot of sites out there already have it; Are those sites beta-test, or
did Apollo forget to send me one. If it has already been released, I'll call
them and find out why I didn't receive it yet, otherwise I guess I'll just
have to wait (and restart the gateway tcp daemons almost daily).
------------------------------------
Has anybody seen any device drivers for DEC printers? We have a couple that
are being used around the net, but I had to fool prsvr into thinking that they
are GE printers. None of the other supported device drivers will work on the
DEC LA100s for some reason. The main problem with the GE driver is that it
sends only LF's to the printer, not CR/LF. This can be fixed after prsvr has
started and has printed the first couple lines with 'tctl -line # -cvt_nl',
but this never seems to work, unless typed by hand. ( The server hasn't had
time to start by the end of startup.xxx script, thus the tctl command dies
because the file /dev/sio# is in use. After prsvr has been initialized,
the command works fine (ie sit there and type it in by hand every time).
Also, since these printers do have graphics capabilities, it would be nice
to be able to do 'prf -plot' to them. I realize that all the documentation
for writing personal drivers is there, but at the moment I don't have the
time to write one. Any help would be appreciated.
-------------------------------------
At the moment, I am starting to port TeX to the apollos from our
VAX 750 (ultrix (bsd4.2)). In moving the files, I noticed info files for
vax, suns..., but not for apollos. Does anybody have any experience moving
TeX to the apollos or foresee any problems?
Oh, on the matter of printers and TeX, I have successfully used
a QMS 800 laser printer off an apollo (they are Laserwriter compatible, but
supposedly better quality). It worked fine with the apollo-supplied
laser-writer driver.
-------------------------------------
A long time ago, I asked about non-supported tape drives and their
reliability. I received several replies mentioning success with the Kennedy
drive and Ciprico controller (6250 drive) combination from Danford. Just
about that time, apollo started supporting a CDC tape drive (6250), but
the price was a little high for the budget we had left. We bought a Cipher
drive (1600/3200,6250 density) and Ciprico controller (note apollo only
supports the 1600 Cipher drive) for an extremely low price, compared to even
the 1600bpi Cipher drive dist. by apollo. We have had no problems since the
day I installed it (self-installation took 10 minutes). I would recommend
this drive to anybody looking for an inexpensive, fast, high-density drive.
------------------------------------
Thanks for listening to my complaints, requests and information.
I didn't realize I had that much to say, but it's too late now.
Michael Burati
University of Lowell
Computer Science Dept.
UUCP: .. { apollo }
.. { wanginst }
.. { ci-dandelion }
.. { masscomp } !ulowell!burati
.. { vaxine }
.. { datacube }
CSNET: burati@ulowell.csnetMark_Giuffrida@UMich-MTS.MAILNET.UUCP (05/23/86)
# Has anybody seen any device drivers for DEC printers? We have a couple that
# are being used around the net, but I had to fool prsvr into thinking that they
# are GE printers. None of the other supported device drivers will work on the
# DEC LA100s for some reason. The main problem with the GE driver is that it
# sends only LF's to the printer, not CR/LF. This can be fixed after prsvr has
# started and has printed the first couple lines with 'tctl -line # -cvt_nl',
# but this never seems to work, unless typed by hand. ( The server hasn't had
# time to start by the end of startup.xxx script, thus the tctl command dies
# because the file /dev/sio# is in use. After prsvr has been initialized,
# the command works fine (ie sit there and type it in by hand every time).
----------------------------
I would suggest the following line in your startup file:
cps /com/sh -n <taskname> tctl -line <n> -cvt_nl;prsvr /sys/print/<config_file>
Mark Giuffrida (U of Mich)
markg%umich-mts@mit-multics.arpa