J.Pearson@CS.UCL.AC.UK (James Pearson) (02/01/90)
Set up: Sun 3/260 (running 4.0.3) using papif to send files to a LaserWriter+ via a KFP-2 Occasionally our LaserWriter refuses to print anything and gives the following messages in the (temporary) log file: papif: Starting job for james@amalthea.ps.ucl.ac.uk at Wed Jan 31 17:17:42 1990 on printer Sun LaserWriter:LazerWriter@PHOTOGRAMMETRY %%[ Error: limitcheck; OffendingCommand: framedevice ]%% %%[ Flushing: rest of job (to end-of-file) will be ignored ]%% /usr/local/cap/lw: 4934 Memory fault - core dumped (/usr/local/cap/lw is a shell script that runs papif). This error seems to happen after printing some TeX files (using dvi2ps) - although it is possible to print the same files without any problems at other times. All subsequent print jobs fail with the same message. The only way to cure the problem is to turn the LaserWriter off. The cause of the problem is probably the PostScript produced by dvi2ps, but is there any way of stopping papif core dumping? James Pearson +------------------------------------------------------------------------+ Dept. Photogrammetry & Surveying ARPA: j.pearson@cs.ucl.ac.uk University College London UUCP: ...!ukc!cs.ucl!j.pearson Gower Street JANET: j.pearson@uk.ac.ucl.cs London WC1E 6BT England
Rudy.Nedved@RUDY.FAC.CS.CMU.EDU (02/02/90)
There are two problems that I have come across in dealing with problems like this. There is one problem where certain types of memory exhaustion will fail in such a way as to cause this. Alas in some of these types, if you have a error handler loaded you can get a fatal internal error which restart the printers. Oh yea, if you don't get the fatal internal error then you have to power cycle your printer. The other problem is one that is fixed by upgrading your printer to a later PostScript version (I think 40+)...I don't know it has been a while. It seems to internally trash it memory and only a power cycle of your printer will fix the problem. -Rudy