We have installed V2.0 on a 64 bit Win7 machine. We installed it without the graphics options.
The graphics profiles still show along with our own profiles. Then they disappear. Then they sometimes reappear. Our own profiles get lost too and because they do all our outputs show a dialog box asking for a save location.
Yesterday, the first file (of about 30 produced in rapid succession) saved OK but then the profile got lost and all the others showed a dialog box. This is an unattended machine running 365247 with a job scheduler so it causes major problems.
I would go back to 1.7.3 but once a new version becomes available it throws up a dialog box for each PDF (unattended machine, remember) and I can see no way to stop it.
which graphics options do you mean(do you mean a silent setup)?
We are not able to reproduce this kind of behavior here but we will have another look at it.
It is not possible to use the profiles which were created in any version below 1.9 for PDFCreator 2.0, the application was rewritten from scratch.
Did you setup your profiles with the GUI or directly in the registry?
You can revert to version 1.7.3 and disable the update warning by setting the interval for the update check to never, but we will also try to help you to get everything running as it was with the new version.
I have the same problem. All the profiles were deleted, while I was printing multiple files with the PDFCreator printer (the profile I used saved them automatically as pdf/a to a specific directory). I had only the standard profiles (I edited one profile for automatically saving the pdf/a to a specific directory). The profiles still seem to be somehow there (I can select them), but they are empty with no title. Also the profiles don’t come back by uninstalling and then reinstalling. I have now created a new profile and hope it won’t get deleted too.
it just happened again, while sending 19 documents to the PDFCreator printer. After 4 documents were printed my profile was deleted and the dialog box of PDFCreator pops up. I will now revert to 1.7.3
we have found the problem, it was a timing issue with reading/writing from/to the registry and will be fixed in the next release. Sorry for the inconvenience.