yahsel kalonea lonnie

[Eboni Kleifgen]

It's working as designed, but you are missing a step. This makes a
PostScript file, NOT a PDF file.You then use Distiller, via the Distiller API, to convert the
PostScript to PDF. Details in the Acrobat SDK.I really advise strongly against what you are doing - programming
Acrobat by investigation and discovery. It is more fun, but if you
want something to support, stick to ONLY what you find in the SDK.Aandi Inston

Regarding changing the path for the PDF port, it can be done from Start>Printers. Select the Acrobat Distiller Printer and use File>Properties. Select the ports tab and create a new PDF port with a new path. Connect the Acrobat Distiller printer to the nex PDF Port. Delete the old one if you want to.
Cheers
Ian

However, I do not agree that it works as designed. The Excel method .Printout(no parameters) or .Printout(to defined filename) should both work the same way in that Distiller completes the task of printing AND converting. The fact that Acrobat Distiller printer driver stops half way through the process looks like a bug to me.

You can call it what you like, of course. I'll call it a grawl, to
avoid arguments about words which have particular meanings.Here is some more background on the Distiller printer driver.When you print to a printer driver to print, a two stage process takes
place.
1. The driver creates a file in printer language, that the printer
understands.
2. The file is sent to a "port", typically something that talks to the
printer down a cable.The end result, you get the printout. If you choose "print to file",
only step 1 takes place.The "port" need not have a printer attached. For instance there are
fax ports, where the file goes off to a fax instead. If you print to
file, no fax gets sent.Now, Adobe used to have PDFWriter, a printer driver which made PDF all
in step 1. It typically used a port of LPT1, but nothing ended up
there.Distiller works differently. It uses the tried and tested PostScript
printer driver to make a PostScript file in stage 1. In stage 2, a
"PDF port" takes the PostScript file and makes a PDF. So you can see
that if you print to file, you bypass stage 2, and get no PDF.This could probably be changed to work as you wish, rather than as it
was designed, but as it would break the code for all of the people
who've correctly used the SDK, it would hardly be a popular move.
Aandi Inston

As I do not yet know much about how Acrobat Distiller works, I took the "privileged" stand of an end-user saying that this is not logic.After your explanation of course I can judge that this is probably not a Distiller problem as such, but a problem how the Windows maker thought of defining the printer driver interface.Anyway, after you mentioned that the file is still a PostScript file, I simply used the Distiller COM objects to complete the task, no registry settings required.So after all the discussion I thank you anyway as you lead me to the solution.Thanks again.

The API (Application Programming Interface) is usally a set of functions stored in a DLL which you need to declare in your code that provide an interface to another application. Taking a VB example the code looks like...Declare Function GetProfileString& Lib "kernel32" Alias "GetProfileStringA" (Byval lpAppName As String, Byval lpKeyName As String, Byval lpDefault As String, Byval lpReturnedString As String, Byval nSize As Long)COM (Common Object Model) in the contrary refers to object classes that are registered as Windows Classes. You program with COM objects fairly different as we are talking about object oriented programming here. Again a VB example...' no declaration required as the information about the object model
' is available in the registry and the object class definition.
Set distobj = createobject("PdfDistiller.PdfDistiller")OK, you could probably simplify it in saying the API is a simpler interface type then COM, but serves the same purpose. So
if you where referring in your previous postings to the Destiller COM objects then I was misunderstanding you. For me API programming is just something completely different as opposed to COM programming.Don't get me wrong, I don't want to split hairs. When you where referring to the Distiller API I just had the Windows API in mind and I try to avoid the Windows API if I can.

Some background...An API is an Application Programming Interface, yes. It might be a DLL, a COM or OLE interface, a series of Macros to use,
a library, a documented command line, XML formatted data streams over
a network socket, a rule for using the registry - anything for
communicating from your program to a facility. The Acrobat SDK
documents many APIs in Acrobat, which use the above and some other
methods.Similarly, whatever you use to talk to Windows is an API. The "Windows
API" you mention is part of the facility. And indeed, Microsoft refer
to this historically as the "Windows API", mainly because at one time
it was the only API for Windows (before COM, before OLE, and when you
could learn it all from just one book...)The Distiller API offers the chance to control Distiller by OLE, by
command line, and some other methods.Some say that the important thing about an API is that it is
documented. This view is supported by
. I would argue that anything
just discovered - rather than read in an official document - might not
be an API but an accident, and my company's policy is to forbid any
"discovery" of APIs. We can't afford the consequences.Aandi Inston

As in the title, Autocad plots any layout to pdf fine first time, but when attempting to plot a second layout (or the same layout again) the blue bar goes for three segments and then the program freezes, requiring 'end task' from Task Manager to shut down the program. On re-opening autocad, the first plot works fine again and the second freezes.

I have been having an issue for a while where the second plot gives an error message relating to adobe, and I have to close 'acrotray.exe', but autocad itself would not stop responding and the program including plotting to pdf would then run without issue for the rest of the day, so did not look any further into it. But I'm thinking this may have something to do with it.

edit: After the first plot 'acrotray.exe' does appear in the task manager. If I end task, I can plot again, but this time the 'acrotray.exe' task does not appear and on the third plot it freezes as before.

We have the same issue, after Adobe was updated. We are running AutoCad 2018.
Currently we are closing the Acrotray app in the "Processes" tab and keep an eye on it in the "details" tab of the Task mamager. It appears there every time you make a PDF. If you close it you can make ONE more PDF, close it again and you can do another,

SUUUUPPPPPPERRRRR Painful and CAD freezes if you do not do it and have to restart. Really hope there is a solution found soon.
Using the Auocad to PDF Print results in a larger PDF file with lower quality which isn't really an option for us.

The Acrotray.exe is the Adobe Acrobat Distiller helper application. It is used as part of the full Adobe Acrobat product to convert documents into PDF files. Its runs in background as it converts files to PDF using other applications like AutoCAD.

Helpful Links:
AutoCAD Videos AutoCAD Crashes or Freezes AutoCAD Customer Council AutoCAD System Requirements Prepare your computer for download Autodesk Virtual Agent Clean Uninstall Steps for Setting-Up Student Software

Many apps printing to PDF will appear to freeze. What you actually have to do at that point is find the dialog box that is asking you to verify overwriting an existing file or asking where you want to plot to. It will hang that app until you tell it where to save to PDF to or if it should replace a prior file.

Do adobe and autodesk not have any discussions / testing arranged between them for those elements of their programs that interact? Given that they each have millions of paying users who rely on both companies software working together.

The autocad built in pdf .pc3 files are all functioning fine, but as 'cpriedel' notes above, they result in lower quality and higher filesize, so not really an ideal solution. Perhaps someone can help with the following issues I have with the built in drivers;

1. To get fonts to display correctly I have to check the 'convert all text to geometry' box, and then my pdf is >1mb. The adobe pdf driver displays the font correctly from the same layout with a file size of

2. When I go into the settings for an adobe pc3 file there is an option to choose the folder it saves to without having a dialog box appear, I use this with the publish feature. I can set the correct file destination on the .pc3 file for a particular drawing set, and then run publish to plot all layouts to pdf in the background with no dialog boxes appearing.

Quite disappointed with both companies overall, I would expect Adobe to test any new update works with such widely used software as AutoCAD. And I would also expect Autodesk to include a pdf driver with their own software that was at least as good as one made by a third party.

As you can see the adobe driver produces a 153kb pdf compared to 659kb from the Autocad (General Documentation) driver. To get the font to display correctly using 'text to geometry' this goes up to 885kb.

Acrotray and Distiller are background programs which adobe runs whenever it creates or edits .pdf files. You will see them launch if you save from photoshop to pdf also. Or even when you open a menu in file explorer that has the 'combine files in acrobat' option on it.

I think overall this is adobe's fault, as they have obviously changed something in the last patch and not tested it properly with AutoCAD. I will open a query on their forums. It is still frustrating however that Autodesk cant make their own pdf plot driver as good as adobe's one, so we are not reliant on third party software to have create decent drawings of a reasonable file size.

c01484d022