Sigh!

Acrobat 6.0 running - sort of - on 10.3.5.

We are experiencing three main problems - so far.

1: Watched folders are set up on a server, as they always have been
because that's where all data files are stored. I read where this might
not be suppoorted, though I'm at a loss to understand why. We run separate
licensed copies of Distiller on 4 machines and each uses its own watched
folders but all watched folders reside on the server where pdfs can easily
be dealt with by whichever staff member needs to deal with them without
the originator having to constantly check on distilling progress and
manually transfer pdfs to their final destination.

2: Possibly related to #1: Distiller keeps making "in/out" folders within
the watched "IN" folder and then refuses to act on files placed in the
original "in" folder.

3: Distiller processes 100% then doesn't produce a PDF due to "PDFLib
failed to initialize" error.

Since no similar problems occurred with an AD4/OS9 combo, are these
problems created by Distiller or OS X? The recent move seems to have
suddenly made life far more complicated, far less reliable and far less
efficient. Which software do we need to get rid of, replace, update? What
do we replace it with if we replace it?

If it isn't possible to have Distiller reliably work with server-based
watched folders, would it be possible to Applescript a local folder so
that Distiller can act locally then have the pdf immediately moved to the
server by the script?

--
Andy D.