jeffy@csustan.UUCP (Jeffrey Youngstrom) (05/10/89)
This has probably been hashed out before, but... I'm having some trouble getting our NeXTlaser to print from WriteNow. It works fine 'lpr'ing ascii files, or screen-dumping from 'Scene', but when I try to print from WriteNow (or Edit) it doesn't print and I get mail that says : >Your printer job (printOutput442895.ps) >was not printed because it was not linked to the original file Huh?? Any suggestions?? Thanks in advance for any help. Don't bore everyone, please email to -- Jeffrey Youngstrom Everything in the world jeffy@altair.csustan.edu means the world to me or and I find this to be csustan!jeffy@lll-winken.llnl.gov mathematically correct -- Cole Swensen
flur@gt-eedsp.UUCP (Peter W. Flur) (05/18/89)
I have had nothing but heartaches as far as printing goes in release 0.9.
This is the story:
On the first machine I brought up, I didn't realize I needed to use netinfo/
niload so it was hopeless. On the second machine, I did, and I can get
it to print with no problems. This is what the printcap looks like after the
nidump (machine name ncstate):
--------------------this will print to np--------------------------
NextLaser|np: \
:lp=/dev/null:sd=/usr/spool/np:lf=/usr/adm/np-log: \
:af=/usr/adm/np.acct:re:mf:if=/usr/lib/NextPrinter/npcomm: \
:ty=NeXT 400 dpi Laser Printer:
lp|np|1|ps|ncstate|postscript|PostScript|NeXTLaser: \
:lp=/dev/null:sd=/usr/spool/np:lf=/usr/adm/np-log: \
:af=/usr/adm/np.acct:re:mf:if=/usr/lib/NextPrinter/npcomm: \
:ty=NeXT 400 dpi Laser Printer:
lp2|2|howardu|LaserWriter2|ps2|postscript2|PostScript2: \
:lp=:rm=howardu:rp=howardu:sd=/usr/spool/lp2:pl#66: \
:ty=NeXT 400 dpi Laser Printer:lf=/usr/spool/logfiles/lpd-errs:
lp3|3|wake|LaserWriter3|ps3|postscript3|PostScript3: \
:lp=:rm=wake:rp=wake:sd=/usr/spool/lp3:pl#66: \
:ty=NeXT 400 dpi Laser Printer:lf=/usr/spool/logfiles/lpd-errs:
lp4|4|duke|LaserWriter4|ps4|postscript4|PostScript4: \
:lp=:rm=duke:rp=duke:sd=/usr/spool/lp4:pl#66: \
:ty=NeXT 400 dpi Laser Printer:lf=/usr/spool/logfiles/lpd-errs:
--------------------this will print to np--------------------------
This prints to np and howardu, which is still running 0.8. No problem.
So then, I go and (can you believe it?) try to fix the first system
and the printer doesn't work no matter what I do. Ok, give up and re-buildisk.
Meanwhile, back at the ranch, I posted my first message about NPD and
got a good suggestion about setting the Public Window Server. So, on
the next machine, I tried that, but no matter what I do, it will not
print anything.
This is what the nidump looks like on the second machine (called duke):
-------------------this won't print worth crap--------------
NextLaser|np: \
:lp=/dev/null:sd=/usr/spool/np:lf=/usr/adm/np-log: \
:af=/usr/adm/np.acct:re:mf:if=/usr/lib/NextPrinter/npcomm: \
:ty=NeXT 400 dpi Laser Printer:
lp|np|1|ps|duke|postscript|PostScript|NeXTLaser: \
:lp=/dev/null:sd=/usr/spool/np:lf=/usr/adm/np-log: \
:af=/usr/adm/np.acct:re:mf:if=/usr/lib/NextPrinter/npcomm: \
:ty=NeXT 400 dpi Laser Printer:
lp2|2|howardu|LaserWriter2|ps2|postscript2|PostScript2: \
:lp=:rm=howardu:rp=howardu:sd=/usr/spool/lp2:pl#66: \
:ty=NeXT 400 dpi Laser Printer:lf=/usr/spool/logfiles/lpd-errs:
lp3|3|wake|LaserWriter3|ps3|postscript3|PostScript3: \
:lp=:rm=wake:rp=wake:sd=/usr/spool/lp3:pl#66: \
:ty=NeXT 400 dpi Laser Printer:lf=/usr/spool/logfiles/lpd-errs:
lp4|4|ncstate|LaserWriter4|ps4|postscript4|PostScript4: \
:lp=:rm=ncstate:rp=ncstate:sd=/usr/spool/lp4:pl#66: \
:ty=NeXT 400 dpi Laser Printer:lf=/usr/spool/logfiles/lpd-errs:
-------------------this won't print worth crap--------------
When I try to print (using lpr) to np on duke (#2), nothing prints.
When I try to print (using lpr) to ncstate on duke (#2), it usually works.
When I try to print (using lpr) to np on ncstate (#1), it usually works.
When I try to print (using lpr) to duke on ncstate (#2), nothing prints.
By nothing printing, I mean that the queue shows the job, the status
says "Printing", but it just sits in the queue. Oh yes, running the Test
in PrinterApp on all machines does successfully print a big blob.
I would appreciate any and all help or suggestions....
Peter
----------------------------Peter Flur----------------------------
USMAIL: Box 32500
Georgia Tech, School of Electrical Engineering, Atlanta, GA 30332
USENET: ...!{allegra,hplabs,ihnp4,ulysses}!gatech!clemson!flur
INTERNET: flur@clemson.gatech.edu, gt2500a@prism.gatech.edu
PHONE: (404) 894-2955
abe@mace.cc.purdue.edu (Vic Abell) (05/19/89)
In article <642@gt-eedsp.UUCP>, flur@gt-eedsp.UUCP (Peter W. Flur) writes: > > I have had nothing but heartaches as far as printing goes in release 0.9. Me, too. Mostly I have found that I must restart npd and lpd every time I want to print. I can print mutiple jobs consecutively, but, if I leave the printer idle for a while, I can't print anything again until I restart npd and lpd. I have had so many bugs with the printer driver and the printer application under 0.9 that I almost wish I could return to 0.8.
NMKATZ@pucc.Princeton.EDU (Nicholas M. Katz) (05/19/89)
In article <2410@mace.cc.purdue.edu>, abe@mace.cc.purdue.edu (Vic Abell) writes: >In article <642@gt-eedsp.UUCP>, flur@gt-eedsp.UUCP (Peter W. Flur) writes: >> >> I have had nothing but heartaches as far as printing goes in release 0.9. > >Me, too. Mostly I have found that I must restart npd and lpd every time I >want to print. I can print mutiple jobs consecutively, but, if I leave the >printer idle for a while, I can't print anything again until I restart npd >and lpd. > >I have had so many bugs with the printer driver and the printer application >under 0.9 that I almost wish I could return to 0.8. I have also had trouble printing in 0.9, and remembered reading somewhere that in 0.9 being low on toner caused no printing (instead of the "low toner" warnings I had been seeing i under 0.8). So I opened the printer, took out the toner cartridge and shook it around; whin I put it back and closed up the prin ter, it started to print, and for the first time the "Printer" application actu ally launched, instead of just turning white for a while and then barfing. It's a pretty clumsy workaround! Anyone else have suggestions? On another topic, has anyone succeeded in printing mac-generated postscript stu ff to print on the neXt printer under 0.9. Steve Dorner(dorner@pequod.cso.uiuc. edu) had posted a sed script that cleaned up the apple laserprep file to the sa tifaction of 0.8, but 0.9 is unwilling to accept his cleanup. Are you there, st eve? Thanks in advance for any help, Nick Katz nmkatz@pucc
joe@mathcs.emory.edu (Joe Christy) (07/01/89)
Since the problem I'm having seems to be chronic, I thought I'd post to the net and see if it was idiosyncratic as well. Last night my machine rebooted itself, irritatingly aborting the auto backup script which happened to be running at the time. A perusal of the system messages revealed the following: Jun 30 21:43:49 suzette vmunix: np0: serial command parity error Jul 1 02:39:07 suzette vmunix: panic: (Cpu 0) np_serial_cmd: can't flush printer status ... and then the reboot. This is happening with annoying consistency [about once a day]. Does anyone else have this problem? My theory is that this might be caused by my habit of leaving the Printer app running constantly with the Test... window open [so as to catch "toner low" messages]. By the way, has anyone discovered a more graceful way to discover when the printer thinks [erroneously] that the toner is low, or to convince it that the toner is only low when the toner is actually low? On an unrelated topic, is there a way to get the Workspace to open a Terminal window as console when it launches, similar to the way that it opens various apps in the dock on launch? I find it annoying to have to periodically Edit /private/adm/messages to look at the console messages. I know about Terminal -Console YES & from a command line, but what like to do this automatically.