![]() |
Adobe Acrobat Issues
I'm using Adobe PageMaker 7.0.2 and make pdfs often. We just upgraded to Adobe Acrobat 7.0 Standard (Don't as me why we didn't get professional) and I've run the updates so I have the latest version 7.0.8. Well, as expected adobe sucks my ass. I can't create one stinking pdf from pagemaker. Its got to be something I'm doing wrong, or some settings I don't have configured right, because, at least in my mind, there shouldn't be any problem with pdfing an adobe-made document. well here's the error I've been running into every time:
Quote:
Anyone have experience with acrobat and can help me. |
Just a quick question, and possibly a retarded one.. have you tried re-installing pagemaker after your install Acrobat?
|
I haven't used PM for a very long time so pardon the 8-gauge shotgun.
That's a PostScript interpreter or library complaining about a color request . Just to make sure, is it when you try to save from Distiller or when you dump it to your printer? Can you print to the Acrobat "Adobe PDF" printer? Does the same thing happen with a freshly created PageMaker doc? Have you opened Printing->Properties->PDF Settings->color to see which color model you're using? Try "convert all colors" to CMYK or RGB. |
I'm getting the same problem with word as well as PM
I've tried to create the PostScript and then create the pdf with distiller and just print to the pdf maker. I get the message above when I print directly to PDF. When I created the PostScript and tried to create the PDF in distiller my printer attempted to spit out over 100 pages of code instead of creating a PDF. I think I'm getting close, but i'm not there yet. I've installed the universal PostScript diver and copied adist5.ppd to the appropriate pagemaker folder. I've tried all the different color settings in distiller, even tried emulating Acrobat 4. No luck. same error message. Thanks for the response. |
Are you doing this with data you created before the upgrade, or with fresh data ?
|
I'll second (third?) that. Do new, small, documents save properly? Does anything save properly?
Disclaimer first. It's been a few years since I did PostScript. The stack shown by that error handler is either full of garbage or the handler is stupid (munging binary to ASCII). Could be part of App->driver communication if there's a 7/8bit issue. That'd could certainly cause angry range errors. In Distiller settings, which File Compatibility PDF version are you using? I think the default is Acrobat 5/PS 1.4. Again in Distiller, which Adobe PDF Settings are you using? The standard set, high quality, something custom? I wouldn't trust anything defined with an earlier version of Acrobat. On that note, I know you said v7 to v7.08 but what version was installed before 7? It's possible you have a dictionary incompatibility moving from old to new. Definitely back out to minimal standard settings both in Distiller and with a fresh document. If it still won't save then it might be fastest to uninstall (and completely wipe the Acrobat files) then reinstall. Or, if you get changing behaviors by forcing grayscale or other settings then we might be able to track things down without the annoying multi-step upgrade again. Adobe probably has an Acrobat debugging handler just for this kind of situation but I'm out of the loop. |
Dont know about Pagemaker, but I have Adobe Acrobat 7 and I know that if it has a hissy fit and disables itself from some programs, I can still go in thru explore or open document, right click on the filename and then it gives me the option to convert to a pdf. Hope it helps.
|
All times are GMT -8. The time now is 02:15 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
Search Engine Optimization by vBSEO 3.6.0 PL2
© 2002-2012 Tilted Forum Project