There are a couple of potential gotchas. Either or both (or
neither...) could be the cause of your problem. Or it could
be related to your practice of configuring from existing
images rather than doing clean installations (which I have
always found to be a much more trouble-free approach).
Unless you have a specific reason to stick with Windows 2000,
you might want to consider starting over with a clean XP
installation; Microsoft no longer actively supports Win2000
which means that they are no longer making any effort to
plug any more of its security holes (although the freedom
from all those "critical" security update notices may be a
welcome thing to many users...).
Anyway, the two common Acrobat upgrade gotchas:
The name of the Acrobat virtual printer was changed after
Acrobat 5.0. New versions of Acrobat name it "Adobe PDF"
rather "Acrobat Distiller", and if your FrameMaker installations
may still be looking for the older name.
The Acrobat 7.0 installation has been known to corrupt the
definition of the default FILE: port, which appears to be
necessary for the Save As PDF feature to work properly. Make
sure that there is a port defined with exactly that name:
FILE: (in all caps and with a full colon after it).
And at the risk of restarting a minor holy war, I assume that
you are aware of the drawbacks of using the Save As PDF
mechanism with on a Windows box with versions of FrameMaker
prior to 7.0. Even with 7.0, there are still some funky issues,
and my personal recommendation is to use the free SetPrint
plugin from Sundorne Communications (www.sundorne.com)
which allows you to set the Adobe PDF printer as FrameMaker's
default printer regardless of what printer you have set as your
Windows default.
My opinions only; I don't speak for Intel
Fred Ridder
Intel
Parsippany, NJ
From: John Pitt <[EMAIL PROTECTED]>
To: [email protected]
Subject: OT: Can't get AcroPro7 to distill or Save As PDFs from Frame
Date: Sun, 12 Nov 2006 12:29:32 +1100
I've finally upgraded from Acro5 to 7 Pro. But while my new Dell XP Pro
laptop happily produces PDFs from Frame and other apps, I cannot get PDF
output from Frame using my win2k home PC.
Both boxes previously ran with Acro5 (which was upgraded from v3 to v4 then
v5).
The win2k box, a 2-year-old P4 with loads of space, RAM, etc., was built
using the mirror of my previous PC (which was built from the mirror of the
one before that). So it has had a large amount of s/w loaded and unloaded
over the years.
When I use Save As PDF in Frame 6.0, 7.0 and 7.1, the screen flickers, but
there is no output. When I try to print to a ps file (using Adobe PDF), I
get the following message:
"Cannot write to specified print file"
Everything is local, I have loads of space, an empty Recycle Bin, and no
other problems.
Moreover, I can use both methods to produce PDFs in all the MS apps I have
tried so far.
Does anyone have any idea what's wrong?
jjj
--
_________________________
John Pitt, technical writer
47 Gottenham St
Glebe NSW 2037
Ph: 02 9692 8096
Mob: 0438 92 8096
[EMAIL PROTECTED]
www.pitt.net.au
_________________________________________________________________
Get today's hot entertainment gossip
http://movies.msn.com/movies/hotgossip?icid=T002MSN03A07001
_______________________________________________
You are currently subscribed to Framers as [EMAIL PROTECTED]
Send list messages to [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.
