The PDF exporter is only producing .ps files and not the .pdf files. How do I fix this?

Hi Dale

We will contact you through separate channel of communication in order to gather some more data and to check this at your end.

I have also experienced this.

The reason in my case was that having multiple editions, 17.2, 17.4, 22.1 and 23.1 resulted in multiple versions of OrCAD_PS driver/interface interfered in some way with another. In an attempt to fix it, I deleted all the instances of OrCAD_PS only to find that they could not be found anywhere in the software folders. I then used MS_Publisher as a foundation, copied it onto a new instance named OrCAD_PS 23.1 and went on from there. But any time I switch between wanting combinations of paper prints or .PDF's of Capture schematic or PCB-Editor/Allegro the system needs to be carefully reconfigured, selecting the proper driver.

IMHO Cadence needs to adress the .PDF output function from Capture. Relying on Ghostscript is obviously not the best method. In the future, a routine that allows the user to define the name of the schematic, the location of it, color or B/W output, size(resolution) and so on is highly desirable.

I have 16.6, 17.4, 22 and 23 running with individual PS drivers with Acrobat distiller.

Honestly, there isn't a DSN file I can't open and plot from using 16.6.  It's just slower than the 17.x 64-bit rewrite.

Under >File >Export >PDF, what do you see in the dialog box?

There should be a green line under "Postscript Commands"

Do you see a green message below that box INFO(ORCAP-43006):  gcwin32c.exe is available.)

or a Red warning(ORCAP-43004:  Unable to find the executable gswin32c.exe)?

It sounds like the Converter isn't being found.  I think this caused by the distiller/converter executable path not in your Windows System search  path.

Yes, that all is green and good. I spoke with Cadence support (they even remoted in to see the issue themselves), after about an hour of nothing working, they told me that there was a patch that would fix the issue but that it hadn't been released yet. Don't know why they didn't mention that at the start. However, I believe that the issue may have more to do with the locked down computer that we have to use in my work environment. We do have a separate local admin account, but the OrCAD license is tied to the main account and it won't even let OrCAD launch under the admin account.