TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
hi bill,
i encountered that problem last year.
why don't you use the adobe 4.0 driver that came with adobe acrobat for NT?
are you using postscript or true type fonts?
if you are just clicking the pdf option in the frame print dialog box, i don't
know what driver/ppd it defaults to (i know in MS Word this option for Word 97
defaults to the crappy Windows driver instead of a decent postscript driver.)
what version of adobe acrobat? we had some probs with the Acrobat 3.01 version
for NT.
my sense is that it's the postscript generation problem, not the distiller
acting up. a good, clean postscript file is the most vital part of the whole
process.
laura praderio
tech wr/ed
denver, co
lpraderio -at- aol -dot- com
*******************************
i use lowercase because my hands hurt sometimes!
******************************
Bill writes:
I'm working with a client who is trying to generate PDFs from Frame. I've
done this plenty of times and know how to take care of most problems, but I
haven't encountered this one, and I can't find any references to it in
Adobe's database.
We print the PS files using the * option to create a separate PS file for
each FM file. When we distill the files, the following error occurs:
exitserver: permanent state may be changed
Warning: Empty job. No PDF file produced.
We're using Linotronic 530 and 630 drivers on Windows NT, printing from
Frame 5.5.2. I'm not as familiar with NT printer drivers, so I couldn't
identify settings that may cause problems on that end.
Has anyone else encountered this problem before?
Bill Burns
Senior Technical Writer/Technology Consultant
ILE Communications
billdb -at- ile -dot- com