jchin@van-bc.wimsey.bc.ca (Joseph Chin) (04/06/91)
Urgent!! I need to get in touch with anyone who has successfully print out PS files generated by FrameMaker 2.0d on the NeXT computer to Linotronic L300 imagesetters (RIP4). Problem: While trying to print out the aforementioned PS file, the L300 puked "dict full" or something to that effect. I remember a while ago, someone mentioned that NeXT DPS has a 400-entry dictionary stack whereas the RIP 4's PS has a dictionary stack limit of only 300 entries max. There are several Lino bureaus that have successfully printed from the NeXT, so, someone must have figured a way around this problem. How did the PS files get from the NeXT to the Lino? The PS files were generated from FrameMaker's print panel's Save option (with L300 selected as the output device). The files were transferred onto 1.44MB MSDOS floppies via a folder mounted by a 386PC running PC-NFS. The PS files were NOT translated in any way, shape, or form. System: NeXT 040 Cube with OD, Micropolis 660MB HD, 16MB RAM, etc. running System 2.0. Software: FrameMaker 2.0d. Imagesetter: Linotronic L300 with RIP 4. Please respond to the e-mail address listed below. I will post a summary when this problem is solved. Thanks in advance for any help or suggestion. :-) Joe jchin@van-bc.wimsey.bc.ca ansfer; bytes moved = 0x2000, resid = 0x2000, retry 5 sd0: Incomplete disk transfer; bytes moved = 0x2000, resid = 0x2000, retry 6 sd0: Incomplete disk transfer; bytes moved = 0x2000, resid = 0x2000, retry 7 sd0: Incomplete disk transfer; bytes moved = 0x2000, resid = 0x2000, retry 8 sd0: Incomplete disk transfer; bytes moved = 0x2000, resid = 0x2000, retry 9 sd0: Incomplete disk transfer - FATAL sd0: Incomplete disk transfer; bytes moved = 0x2000, resid = 0x2000, retry 1 ... etc ... System configuration: Cube with 68040 processor (upgraded in December, 1990) 16MB RAM NeXT 256MB optical drive Micropolis 1588-15 600+MB hard drive (SCSI-ID=1, terminated) HSD Scan-X Professional scanner (SCSI-ID=5, terminated, NeXT SCSI2-SCSI1 cable) System 2.0 operating system NeXT Laser Printer Dove Fax fax modem on serial port A Cube, scanner, and fax modem are hooked up to an uninterruptible power supply Both HSD and NeXT are quite puzzled at the problem. I welcome any suggestions or ideas you can contribute toward solving this problem. Thanks in advance. :-) Joe jchin@van-bc.wimsey.bc.ca -- ************************************************************** * "Kill the body and the head will die" (Hunter S. Thompson) * * NeXT --> The ultimate electronic publishing platform! * ********** Joseph Chin --> jchin@van-bc.wimsey.bc.ca *********
jchin@van-bc.wimsey.bc.ca (Joseph Chin) (04/06/91)
I suddenly noticed the last post a bit mangled. Silly me ... Just in case the last one was unreadable, here it is again: Urgent!! I need to get in touch with anyone who has successfully print out PS files generated by FrameMaker 2.0d on the NeXT computer to Linotronic L300 imagesetters (RIP4). Problem: While trying to print out the aforementioned PS file, the L300 puked "dict full" or something to that effect. I remember a while ago, someone mentioned that NeXT DPS has a 400-entry dictionary stack whereas the RIP 4's PS has a dictionary stack limit of only 300 entries max. There are several Lino bureaus that have successfully printed from the NeXT, so, someone must have figured a way around this problem. How did the PS files get from the NeXT to the Lino? The PS files were generated from FrameMaker's print panel's Save option (with L300 selected as the output device). The files were transferred onto 1.44MB MSDOS floppies via a folder mounted by a 386PC running PC-NFS. The PS files were NOT translated in any way, shape, or form. System: NeXT 040 Cube with OD, Micropolis 660MB HD, 16MB RAM, etc. running System 2.0. Software: FrameMaker 2.0d. Imagesetter: Linotronic L300 with RIP 4. Please respond to the e-mail address listed below. I will post a summary when this problem is solved. Thanks in advance for any help or suggestion. :-) Joe jchin@van-bc.wimsey.bc.ca -- ************************************************************** * "Kill the body and the head will die" (Hunter S. Thompson) * * NeXT --> The ultimate electronic publishing platform! * ********** Joseph Chin --> jchin@van-bc.wimsey.bc.ca *********
rob@lighthouse.com (Rob Kedoin) (04/06/91)
I recently had the same problem printing from FrameMaker to the Lino
equipment. My solution was to edit the PS directly before giving it
to our typesetter on Mac floppies.
When you start scrolling through the PS you'll see:
/colorimage{_NXDoImageOp}__NXbdef
/alphaimage{1 add _NXDoImageOp}def
%%EndDocument
/landscape false def
The %%EndDocument signifies the end of the NeXT printPackage and the
beginning of the Frame prologue.
I created a new dictionary after the %%EndDocument like so:
/FrameDict 300 dict def
FrameDict begin
Now search down to the "%%EndProlog". It should look something like:
<8040201008040201> (I149cf0) 14 makecontextpattern
gsave
-1 -9 translate
/__NXbasematrix matrix currentmatrix def
grestore
%%EndProlog
Add:
end %%FrameDict
before the gsave. Now go down a few lines and add
FramdeDict begin
just before "%%EndSetup". and finally jump to the bottom of the file and add:
end %FrameDict
after the "%%Trailer" line.
I hope this helps. It worked for me a couple of weeks ago. If anyone
has a better solution, I'd be interested in seeing it.
While I'm here, I'd like to recommend "Thinking in PostScript" by
Glenn Reid to anyone who'll be doing a lot of PostScript hacking - it
complements the Red,Green, and Blue books very nicely. (The
explanation of creating your own dictionaries is in there...)
Rob Kedoin rob@lighthouse.com
Lighthouse Design, Ltd
6516 Western Avenue Chevy Chase, MD 20815