Distiller vs. Writer

I am looking for the capability to create PDF documents with a default path and file name. It appears from my research that the Distiller has the capability to set a default path, but uses the file name of the source document. I was able to verify this on my system which has Distiller installed and it works as stated.
In some old documentation on the Writer that I saw on the internet, it appears that it has the capability I am looking for but I would like to prototype this and do not know how to get Writer installed on my system. I downloaded the trial version of Acrobat 9, Extended, thinking that it might be included, but the printer installed appears to be using the Distiller.
So my quesiton is two fold. 1) How do I get Adobe PDF Wrtier installed on my machine (even if trial) and 2) Does Writer have the ability to define the path and default file name for all PDF files that are created through it?

Thank you for the response. I had not seen anywhere that the Writer had been discontinued and the Distiller is now the only driver for Acrobat. I am simply looking to have a constant name for the path and the file name every time the Adobe PDF printer is printed to. No Save As dialog, just creates and overwrites the same file all of the time with the user only having to hit the print button from the application (Adobe PDF would be default printer). I cannot write a custom application that accesses the Adobe object model because this is running in a drug manufacturing plant and all software needs to go through a major qualification process. Adobe Acrobat on its own is already qualified.
Can this be done with Distiller "out of the box" or can it be done if I install Acrobat 5.0 and use the Acrobat Writer?

Similar Messages

  • Acrobat X Pro--problems after 6/14/11 update

    Has anyone else seen problems with the print cycle after doing the 10.1 (6/14/11) update to Acrobat X Pro?
    These only started happening with that update: uninstalling the updated AXPro and reinstalling from the original distribution causes the problems to go away.  But letting the update run from the automatic download always causes these problems to reappear.
    (This is on Windows 7 Ultimate 64-bit; 8-processor i7 with 8Gb RAM and 2.5Tb of disk space; so hardware is not a problem.)
    What I'm seeing are two, seemingly related, things:
    1) Having Distiller (from any app or browser) write a PDF into a 'normal' folder with "View Adobe PDF results" checked, causes the PDF to go into that directory as expected.  However, acrobat.exe does not appear to start, and if you go to the output folder and double-click on the file, Reader reports that the file is locked.
    On bringing up Windows Task Manager as administrator, going to the Processes tab and then having it "Show processes from all users" reveals that acrobat.exe is indeed running, but it's running as a SYSTEM process, not a user process.  Now, under Windows, SYSTEMS processes cannot be brought forward into the USER space in which the GUI is running (it can't access the user's desktop), so that copy of acrobat.exe cannot come to the desktop.
    The solution is to use Task Manager to slam the process (right-click on "Acrobat.exe *32" [*32 means it's still a 32-bit executable], then click 'terminate process'), which kills the hidden Acrobat session.  This frees the PDF so that it can then be hand-opened with a USER-level copy of Acrobat.  This is a royal PITA to have to do after every print job!
    2) Setting Distiller to write the output into an encrypted folder causes the same problem as in 1), however, Distiller also writes bad security data (or errantly causes that bad security data to be written) into those files.  This means that, even after killing the headless Acrobat process, the generated PDF's cannot be opened, no matter how high your security level.  (Nor can you open them if you move them from that encrypted into an unencrypted folder, if the system will permit you to do the move--sometimes it won't because of those screwed up SID's [security ID's].)
    I've worked with the internals of the Vista/7 security mechanisms in Windows, but cannot find a way to fix these files.
    The only solution is to delete those corrupt PDF files and reprint, this time into a non-encrypted folder, then follow the "solution" for 1).
    I filed a bug report on these conditions last week, but haven't received any acknowledgement of that.

    Not here. All I can suggest is to DL and install the HP Update 2.6. Photosmart C4680.

  • Print to .pdf from Access2000

    Hi Forum, I have Office 2000 running on xp pro sp3 and Acrobat 5.0.
    When trying to get Access to print a report as .pdf automatically, I need to be able to see a Printer called Adobe PDF with Model called Adobe PDF Converter.
    We have Distiller and Writer showing as Printers but no Converter.
    Is there a way to get this printer showing??
    Appreciate any guidance

    At some point the Adobe PDF printer replaced the "Writer".
    I think this was with Acrobat 6.x.
    I've a vague recollection that there was something about both for Acrobat 5 & the install CD but maybe not - 5.x is a lot of water under the bridge.
    If you have the Acrobat 5 install CD you might want to look through it and view any readme files.
    Be well...

  • PDF writer and distiller do not appear as available in windows 7 using Acrobat 5

    Trying to install my Acrobat 5 with Windows 7. The pdf writer and distiller appear to instal after satisfying the syetm requirement for a postscript driver.  The software then installs fully but the pdf writer and distiller do not show up under printers.  There is a warning that a compatibility issue exists, how can this be fixed please?

    Acrobat 5 is not supported on Windows 7. You need to upgrade. Sorry about that.
    Ken Friedman

  • How can I programati​cally control the names of files output from Labview into .pdf format (ie with Adobe PDF Writer or Distiller)​?

    I would like to save some data forms for a standard test controlled with labview in a pdf format. Due to the large number of forms and test reports, I would like to have Labview automatically assign the .pdf file name based on test number already contained in the labview code. How can I do this.
    Note: This question is very similar to:
    "Labview and Adobe Acrobat output" posted by John Balone on 1/26/2000. The reponses offered good suggestions but it is not clear to me how to implement them.

    This information is essential if you plan to use the Acrobat Distiller printer driver and any of the examples listed here:
    http://zone.ni.com/devzone/devzone.nsf/webcategori​es/EADE78F29101E8DB862567AC0058596B?opendocument&n​ode=DZ52095_US
    -Graeme, rayodyne.com
    Attachments:
    1_-_Printer_Configuration_with_Acrobat_Distiller.jpg ‏64 KB
    2_-_Printer_Configuration_with_Acrobat_Distiller.jpg ‏33 KB

  • How can I set Firefox to print to PDF, the only otions I have are (1) My Canon printer, (2) Fax or (3) Microsoft XPS document writer. There is no option for PDF

    A couple of weeks ago, from the file menu, in my print options was to print a web page to PDF, that facility is no longer there. does anyone know how can I set Firefox to print to PDF.
    The only options I have are (1) My Canon printer, (2) Fax or (3) Microsoft XPS document writer. There is no option for PDF

    Firefox generally displays the printers in Windows' Printers folder (Start orb > Devices and Printers). If it is missing one of the printers listed there, could you indicate which one it is, for example, Adobe Distiller, PrimoPDF, CutePDF Writer, etc.?
    If you previously had an add-on which added print-to-PDF functionality just to Firefox, perhaps it got disabled. You could check here:
    orange Firefox button ''or'' classic Tools menu > Add-ons > Extensions
    Also, are you really running Firefox 8.0.1? That version from last November is no longer secure and has been superseded by Firefox 11. If you browse the web widely, you should update for your security.

  • Acrobat 8.1.2 - PDF Printer still not working & Distiller crashes on startup!!!

    Hello,
    when 8.1.2 update was released my hopes where great but now I'm realy disappointed!!!
    After 3 times reinstalling CS3 Suite (incl. clean cs) and updateing for hours NOTHING seems to be fixed! Oh, well, the bouncing icon seems to be but maybe just because I'm not using Acrobat any more...
    Here's a summary of my specs and the problems I have:
    OSX 10.5.2 on a Intel 8-core MAC Pro w. 4 GB Ram
    Suitcase Fusion (also for System Fonts)
    CS3 Premium w. latest Update(s)
    Xpress 7 + Love Bundle
    Country settings: Lang. German, country Austria
    Installed Hardware:
    Superdrive
    ATI Radeon graphic card
    Mighty Mouse wireless + New wireless Apple keyboard
    24" DELL TFT monitor
    2 x 500 Gb HDD's
    The main problem is that I HAVE TO create print PDFs from Xpress doc's wich is impossible without Distiller!
    The 8.1.2 update seems to fix the "pausing PDF printer Problem", now the PDF printer sends the PS file to Distiller wich just crashes!
    Here's the Distiller crash log (looong):
    Process: Distiller [1022]
    Path: /Applications/Adobe Acrobat 8 Professional/Acrobat Distiller.app/Contents/MacOS/Distiller
    Identifier: com.adobe.distiller
    Version: 8.1.2 (8.1.2)
    Code Type: X86 (Native)
    Parent Process: launchd [76]
    Date/Time: 2008-02-20 09:50:33.461 +0100
    OS Version: Mac OS X 10.5.2 (9C31)
    Report Version: 6
    Exception Type: EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
    Crashed Thread: 11
    Thread 11 Crashed:
    0 com.adobe.DistillerLib 0x010fcf49 os_strcmp + 10
    1 com.adobe.DistillerLib 0x01112942 PSRIPAppendHostSearchDir + 385
    2 com.adobe.DistillerLib 0x01112b01 PSRIPAppendHostSearchDir + 832
    3 com.adobe.DistillerLib 0x01136c09 RgstUnixStoDevFileNameProc + 90
    4 com.adobe.DistillerLib 0x010e8aae StoDevCreateStm + 253
    5 com.adobe.DistillerLib 0x010e5476 CreateFileStm + 25
    6 com.adobe.DistillerLib 0x0115562d PurgeFilterStorageTempFiles + 129
    7 com.adobe.DistillerLib 0x01147210 FiltersInitProc + 500
    8 com.adobe.DistillerLib 0x01148065 RegisterFiltersInit + 79
    9 com.adobe.DistillerLib 0x0122f379 PSRealTime + 230
    10 com.adobe.DistillerLib 0x0122f752 InitPostScript + 607
    11 com.adobe.DistillerLib 0x012be9a6 AwaitAllPSPages + 1802
    12 com.adobe.DistillerLib 0x012bece0 HPGLInterpreter + 192
    13 com.adobe.DistillerLib 0x011122c7 PSRIPInitialize + 1165
    14 com.adobe.DistillerLib 0x00efa598 DistillerPSRip::PSInit(void*) + 256
    15 ...ple.CoreServices.CarbonCore 0x95705409 CooperativeThread + 309
    16 libSystem.B.dylib 0x90bf7c55 _pthread_start + 321
    17 libSystem.B.dylib 0x90bf7b12 thread_start + 34
    Thread 11 crashed with X86 Thread State (32-bit):
    eax: 0x00000000 ebx: 0x011128b4 ecx: 0x00000000 edx: 0xffffffd1
    edi: 0x16e03248 esi: 0xb05d8440 ebp: 0xb05d8418 esp: 0xb05d8414
    ss: 0x0000001f efl: 0x00010202 eip: 0x010fcf49 cs: 0x00000017
    ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
    cr2: 0x00000000

    I posted this elsewhere, but I thought it couldn't hurt to repost here:
    I had a similar problem and finally figured out why (and now to fix it).
    Permissions were messed-up on ~/Library/Application Support/Adobe/Acrobat
    I did not have read-write permissions in it and Distiller was failing to create the ~/Library/Application Support/Adobe/Acrobat/Distiller 8/FontCache subdirectory.
    I simply changed the owner and permission on ~/Library/Application Support/Adobe/Acrobat and the problem went away.

  • Win Encore 5.1 won't write to LG Blu-ray burner

    Encore 5.1 (CS5.5) and Win7 Pro new computer I just built. Trying to burn a DVD in Encore.
    When I choose "Build" I see the drive (it's the only one on the computer) Everything seems fine. It builds the movie then gets ready to write and Encore says "Cannot Erase Disk."  I put in another DVD blank try it again, and when it comes to write it says "Please insert DVD media and then close the tray and click OK." Of course the tray is closed and there is good DVD media in it.  Next I try another disc and it errors out with "Encore was unable to complete the operation because of a hardware error (sense code 52102). Please contact the hardware manufacturer for more information."  I give up.
    So I use Encore to output an ISO file, I drag it into Nero burning rom and it burns perfectly on the first try using the same LG drive and one of the discs that Encore failed on.  I've seen others say that this is the way you have to do it with Encore, but I refuse to back down to this. I've used encore CS4 for years and it burned great. Has the product gotten worse instead of better?  My LG is BH14NS40 on Win7 Pro, Asus p9X79 WS, i7 3930 and 16 gigs of ram.  Why won't Encore work with my drive when Nero does so beautifully?  Can I expect any different results when I install CS6?

    You're saying, software wise, that it's whoever gets to the drive first owns it and no one else can get in
    That pretty much distills the issue.
    What happens with most "packet-writing" software is that it is set up to load at boot, and actually before most of the OS loads. It then reports to the OS that the multi-drive/burner is NOT a multi-drive/burner, but is, instead, a removable hard drive. Nero and Roxio have packet-writing software, that, when installed, will "hook" the multi-drive/burner. Windows Burning Utility, can do the same. The OS believes that packet-writing software, and just flags the multi-drive/burner AS a removable HDD.
    Encore (and other Adobe programs, that can burn to DVD) looks to the OS for instructions, and the OS tells it, "there are NO burners on this system - just a removable HDD." That is all that En sees, so will refuse to Burn to Disk, as no burner is reported.
    Now, other burning utilities, like the free ImgBurn, do not query the OS. Instead, they go to the hardware level, and look for an APTI for a multi-drive/burner. They do not care what the OS reports, as they work at the hardware level. They can get one around such problems.
    This ARTICLE goes into more detail, and also links to the FAQ Entry, that John T. has already mentioned.
    One way around this is to go to MSCONFIG and in StartUp, and Services, uncheck the packet-writing module, to keep it from loading at boot. Another method is to uninstall the offending program, say Nero, and then reinstall it in "advanced," or "manual" mode, and just do not install the packet-writing module. I have Nero on my computers, but it was installed without those modules. I have no issues.
    Now might also be a good time to check for any firmware updates for your LG, as they issue those fairly often. Be SURE to read the full instructions, and make SURE that you understand them completely, before you update the firmware. I recommend printing those instructions out, and having them handy, following EACH step, in perfect order.
    Good luck,
    Hunt

  • BUG report: Distiller v.8.1.0 erroneously execute i/o-operations in PostScript programms

    Distiller v.8.1.0 erroneously execute i/o-operations in PostScript programms (WinXP SP3 & Win2K3 RC1 SP2 platform).
    Execution of the PS-code, contained file i/o operaions (see
    i PLRM 3rd edition
    , pp.73-87)
    c %*************************** PS-File *********************************
    c (c:\\temp\\File1.txt) (w) file closefile % Open file for write and close it
    c %*********************************************************************
    (or others file write ops.) produce invalidfileaccess error:
    b =============== Distiller LOG =====================
    > %%[ Error: invalidfileaccess; OffendingCommand: file ]%%
    > Stack:
    > (w)
    > (c:\\temp\\file1.txt)
    > %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    > %%[ Warning: PostScript error. No PDF file produced. ] %%
    b ==================================================
    Execution of the file read operations (file exist!)
    c %*************************** PS-File *********************************
    c (c:\\temp\\File2.txt) (r) file closefile % Open existing file for reading
    c %*********************************************************************
    or
    c %*************************** PS-File *********************************
    c (c:\\temp\\File2.ps) run % execute existing PS-program
    c %*********************************************************************
    produce undefinedfilename error:
    b =============== Distiller LOG =====================
    > %%[ Error: undefinedfilename; OffendingCommand: file ]%%
    > Stack:
    > (r)
    > (c:\\temp\\file2.txt)
    >
    >
    > %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    > %%[ Warning: PostScript error. No PDF file produced. ] %%
    b ==================================================
    b =============== Distiller LOG =====================
    > %%[ Error: undefinedfilename; OffendingCommand: run ]%%
    > Stack:
    > (r)
    > (c:\\temp\\file2.ps)
    > %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    > %%[ Warning: PostScript error. No PDF file produced. ] %%
    b ==================================================
    It doesn't matter, in what folder operation is carried out system %TEMP% or User %TEMP% (not in %HOMEPATCH%!) file i/o
    b don't work.
    With mentioned [in KB http://www.adobe.com/devnet/acrobat/downloads/Acrobat_SDK_readme.html ] command line switch «-F» all works correctly.
    This "feature" of the Acro8 (and Acro9? see http://www.adobeforums.com/webx/.59b69fa1 ) does impossible execution of the PostScript programs of variable data print.
    What to do that Distiller the beginnings it is correct to work (file i/o into %TEMP%-folders) without «F»-switch?

    I don't use Acrobat SDK, i make PostScript-programs for the var.data print, f.e. labels with wire name, numbers, barcode etc.; Distiller plays role RIP, carrying out the program.
    As a data source at execution of these programs files of various formats can be used: ANSI/UNICODE text, binary (f.e. PhotoShop-RAW data), PostScript (f.e. «print-in-file» from Illustrator) file and others. The same programs can write what or given on a disk (tmp-files), for example the pointer to the data in a source file or the debug information.
    For me has surprised that in 8 Acrobat'е all it has suddenly ceased to work, though in early versions and ghostScript all is fulfilled correctly. I have assumed that obviously developers had been limited possibility of data write/reading a disk and, most likely by a TEMP-folder. However even in the TEMP-folders setted by means of a variable %TEMP% of write operation at execute of PostScript-program by Distiller it was not possible to make. Also attempt to read/execute a file which is in a TEMP-folder was unsuccessfully completed also.
    During search in the Internet I have found article specified above ( http://www.adobe.com/devnet/acrobat/downloads/Acrobat_SDK_readme.html ) in which it is underlined possibility by default operations of file I/O in a TEMP-folder, however impossibility it to make contrary specified in this article, have forced me to write to this forum so it is read by Acrobat developers.

  • HELP...Distiller works with all apps including office2007 with the exeption of publisher 2007

    I have adobe 4.0
    It worked with all apps before the office upgrade.
    Now it works with everything except publisher 2007.
    I don't get any error. The entire print box is grayed out.

    Not sure. How are you trying to print? You may have to remind us what some of the options are. I have 4 versions of Acrobat installed on different machines, but not back to AA4. I might actually have access to that on another machine if needed, but don't have Office2007 on that machine. The combination is a bit strange and we might have to guess.
    When you say it works, I am assuming you have the Acrobat Distiller printer (or what ever the printer was) listed and you print to that. If not, please explain exactly what you are doing. There are too many options, particularly back when a lot of folks use PDF Writer rather than the Acrobat Distiller printer that is preferred.

  • Howto run Distiller in unsafe mode?

    Hi,
    I have to convert a Postscript file into PDF which, during the distillation process, creates and writes to intermediate, named text files using the
    filename (w) file
    Postscript operator. However, this requires Distiller to be run in unsafe mode. Otherwise an `invalidfileaccess' error is raised. Ghostscript provides the `-dNOSAFER' command line option for this purpose. Does there exist an equivalent option for Distiller as well?
    Thanks for your suggestions. Regards,
    Alexander Grahn

    Unfortunately option /F doesn't seem to have any effect, because Distiller (7.0) still issues the error message:
      %%[ Error: invalidfileaccess; OffendingCommand: file ]%%
    Stack:
    (w)
    (lorenz.dat)
    /statefile
    %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    %%[ Warning: PostScript error. No PDF file produced. ] %%
    Alexander

  • ARGH!!! Distiller 8 refuses to see Watch Folder!?!

    Okay, this whole Acrobat 8 hoo-har is driving me nutso! I have to finally admit defeat and ask for help...
    We've been running Mac OS Acrobat 4 through OS X Acrobat 7 with virtually no problems whatsoever for years. And now the second we switch over to Intel Macs and Acrobat 8, we have nothing but one problem after the next...
    Since all I've experienced are Distiller ioerror issues (myself and other people on this forum) with Intel Macs and Leopard, I decided to throw in the towel and downgrade back to Tiger for our production stations and attempt to create a valid workflow with CS3 and Tiger, since there seems to be far too many unresolved issues with Distiller 8 and Leopard.
    Now I'm no dunderhead when it comes to setting up Distiller workflows, I've been doing this for years for our newspaper and others in our group. But every single time I set up a watch folder in Distiller 8 or the 8.1.2 update, the resulting .ps file is passed from the Inbox straight to the Outbox without an error and without a PDF being produced.
    Here's the log file entry:
    >>>>>>>>>>>>>>>>>>>>>>>>>>
    Distilling: 63011115.AD.ps
    Start Time: Tuesday, June 3, 2008 at 4:10 PM
    Source: /Users/craigwright/Desktop/PDF FILES TO LONDON/In/63011115.AD.ps
    Destination: /Users/craigwright/Desktop/PDF FILES TO LONDON/Out/63011115.AD.pdf
    Adobe PDF Settings: /Users/craigwright/Desktop/PDF FILES TO LONDON/folder.joboptions
    Distill Time: 7 seconds (00:00:07)
    **** End of Job ****
    >>>>>>>>>>>>>>>>>>>>>>>>>>
    It's the weirdest thing. You can see the output file in the listing above, but there's never a PDF produced.
    Dragging the .ps file onto the Distiller window itself produces a perfect PDF, but Watch Folder workflow is completely broken.
    Here's an example log from a postscript file dragged onto the Distiller window:
    >>>>>>>>>>>>>>>>>>>>>>>>>>
    Distilling: 63011115.AD.ps
    Start Time: Tuesday, June 3, 2008 at 4:07 PM
    Source: /Users/craigwright/Desktop/63011115.AD.ps
    Destination: /Users/craigwright/Desktop/63011115.AD.pdf
    Adobe PDF Settings: /Users/craigwright/Library/Application Support/Adobe/Adobe PDF/Settings/London Free Press.joboptions
    Processing prologue.ps...
    Done processing prologue.ps.
    Processing epilogue.ps...
    Done processing epilogue.ps.
    Distill Time: 18 seconds (00:00:18)
    **** End of Job ****
    >>>>>>>>>>>>>>>>>>>>>>>>>>
    ...you'll notice that the file dragged onto the Distiller window had its prologue.ps and epilogue.ps files processed. This was not processed by the Watch Folder method. And YES, I did check the settings file under the Watch Folder options and they ARE set to process the file's prologue and epilogue.
    The settings for the "folder.joboptions" and "LONDON FREE PRESS.joboptions" files are absolutely identical.
    Now, I can remove the folder from the Watch Folder queue, destroy the folder on the desktop and create a new one, adding it to the Watch Folder list in Distiller every time, and it does the same thing every time.
    I've tried re-installing CS3, I've tried fixing permissions, I've tried updating and downgrading Acrobat and Distiller to and from the latest fixes. I've tried font cache rebuilds (I know it's not related, but I'm clutching at straws here). Nothing works.
    Does anyone have any clues?

    Hi Jon...
    Thanks for your help, but...
    I checked the privileges on the files I'm generating. All of the .ps files I'm creating from QXP 7.3 are read-write.
    I'm not quite sure what you mean by getting users to log into the server as the server name. We're using Distiller on a per-client machine basis, not a server scenario with users sending files to a remote station for processing. The client stations use an ad tracking application to pull ad content from our server farm to their station, they work on the ad and create a PDF by sending a postscript file to a watch folder on the desktop. Each station has its own copy of Acrobat 8 Pro.
    Once the PDF is produced, they send the ad back to the storage server.
    I've also checked the drive, fixed permissions, and even destroyed the plist files, forcing Distiller to recreate them from scratch.
    I've created a new watch folder, added the current Distiller settings file to it - nothing.
    I've destroyed the watch folder and its attached settings, created a new folder to watch with a different naming convention, and added a new Distiller setting set to it manually. Nothing.
    I've tried erasing the drive, installing Tiger from scratch, installing the latest builds of CS3, QXP and Suitcase, creating a new folder, adding a new watch queue with the parameters I need. Same thing happens.
    I've tried Diskwarrior, Onyx and AppleJack permission/directory fixes. Nothing has been found and nothing was fixed.
    I've also tried different font configurations, in case there was some underlying corruption.
    All ads we send to the Distiller inbox have all of their fonts verified as good by FontDoctor. I've even created a dummy ad with a few coloured boxes and no fonts to see if that will distill. Nothing.
    In every occurrence, Distiller processes the .ps file's epilogue and prologue, passes the .ps file to the outbox and creates no PDF.
    If I drag the postscript files from whatever location I place them into the Distiller window, they process and render perfectly.
    I have configured two machines and both of them do the exact same thing.
    Both machines are brand new Intel dual-core PowerMacs with 2GB RAM. All machines have brand new Tiger installs and run the latest builds of CS3, along with Quark Xpress 7.3. Both machines used to run Leopard, but since all we saw was Distiller 8 ioerrors running CS3 under that OS we downgraded in favour of Tiger, hoping the bugs would go away.
    This is truly awful. We can't use these machines the way we want and I have no idea what to do next... And I'm CERTAINLY not going to start creating custom scripts to make Distiller work the way it should out of the gate...
    Has anyone heard of this problem at all?
    Jon: Do you think I should be calling Adobe technical support about this?

  • Recently Installed Adobe 9 Pro Wont Create/Write Pdfs (only read them...)

    Windows XP where Version 8 was first completely removed then Adobe 9 Pro was installed.  The XP machines can no longer write/create pdfs whereas previously with v8 there were no issues.  No pop error message...simply the pdf generation process does not start or complete.  Strangely, there are no relevant entries in the application or system event viewer logs either.  Has anyone else experienced this?  Have you found a solution?

    You did not indicate how you are trying to create the PDF. Open a document in an application and select the print to the Adobe PDF printer. Before printing, select print-to-file and then complete the process (be sure you note where the file went and the name). Start Distiller and open the file you just created in Distiller. If that creates the PDF, then check for AcroTray running in the background. If it is not running, then start it.

  • Error message in customizing Distiller's job options settings

    I'm trying to customize job options settings in Distiller 8.1.0. I'm on Mac OS 10.4.9, and taking postscript files created in Quark 6.0 to Distiller to create PDFs. I have vendors who have provided settings and I want to transfer those specific customized settings from Distiller 6.0 standard to Distiller 8.1.0 professional.
    If I try to customized 8.1's presets, I get the message "An error occurred trying to save the job options." Has anyone run into this error or this situation?

    I ran into the same problem. If I try and save the settings file to a different location than the Settings folder (which is located under User_Home\Library\Application Support\Adobe\Adobe PDF\Settings\)
    then it actually works. But if you try and save to the Settings folder it will not save and gives you the error. This only happens with non-administrator users. If you try with an administrator account it saves fine. I checked the folder settings for permissions and changed it to read and write for all groups and it still gives the same error (the default setting is read and write for the user). I also tried updating to 8.1.1 but it does not touch Distiller with that update. I have tried deleting the Settings folder and recreating it this does not work. What did work was a mistake on my part but it worked. I deleted the Settings folder before closing Distiller and tried saving. It saved the settings file in the original Settings folder which was in the trash! I pulled the folder out and the setting file was in it. This means there is some kind of permissions issue with Distiller and not just the OS I think. Just so you know I did do a permissions repair before I tried all of this.
    The only solution right now for people who can't save to that folder is to save it to a different location and then adding the settings file to your settings folder User_Home\Library\Application Support\Adobe\Adobe PDF\Settings\
    One other thing to note. Version 8.0.0 does not do this. It only happens after updating to 8.1.0
    I did this in 10.4.9 and also 10.5.1

  • Write PDF file to client's machine using Applet

    Hi all,
    I want to use Java Applet to write a PDF file into the client's computer when he/she double click the URL in browser. Can I do that and HOW. I heard that i need to signed the applet and make security manager enable, but how to do it?
    Also, is it any different to do this for IE5X and NS4X browser?
    Thanks for your information.

    Hi,
    I don't know how to do that with a signed applet (excepting if you want to write in the PDF format), but you can do this with a script (like asp) and an active X written with VB. You can build and manipulate Word or Excel Object with VB and so build dynamically your document.
    When your document is ready (in the active X), you can use the distiller from acrobat (you need a license to use it) and you can create a new file on your hard drive (server side).
    Your script will do the following:
    1) load (createobject) the active X
    2) call the method in the active x
    3) redirect the client to the correct page (the new document you created)
    I don't have any code to give you, but I did the same thing last year and it worked...
    I think that you can also interact between an applet and an active X (I saw something like that in the forum)...
    Of course this solution is running server side (the file will be created server side) but the client will be able to see his document in his browser and will be able to save it.
    I hope that it can help you even if it is not with java...
    Blaise

Maybe you are looking for