It looks like you're new here. If you want to get involved, click one of these buttons!
I installed PDFCreator recently using admin account. It worked just fine for a couple of days. But today I had a little problem when saving a document to a network location (network connection was lost after I pressed the Save button in PDFCreator). The printer hunged up (it could not show the "Save as" dialog).
After restoring the network connection I tried to print the document again. PDFCreator shows all dialogs as usual, even shows the process bar after Save As dialog, but no pdfs are created.
I tried to change default location to My Documents, tried Auto save - nothing helps.
The spooler window shows that a document is being created (with the tmp extension) and when the list becomes empty, but no PDF appears anywhere.
I tried to switch off Antivirus (free Avast), reinstalled PDFCreator - no result.
I'm pretty much sure the problem started when the Save As dialog could not start because of lost network connection. Is there a registry key or an ini setting that prevents PDFCreator from creating PDFs?
If this is a bug. I'm free to make a dump or collect registry settings.
System: Windows XP x86 on Intel Core processor.
I turned logging on and it seems to be a bug in PDFCreator:
C:\Documents and Settings\Root\Local Settings\Temp\PDFCreator\PDFCreatorSpool\~PSA4.tmp
08/08/2011 10:55:32: Error: GPL Ghostscript 9.02: **** Could not open the file C:\Documents and Settings\Root\??? ?????????\Testpage - PDFCreator.pdf .; **** Unable to open the initial device, quitting.;
08/08/2011 10:55:32: Time for converting [PDF without encryption]: 00:00:00:137
As I see, PDFCreator uses wrong code page for file name and path, that's why non-ASCII characters are replaced with ????.
I confirm that my PC is not with a standard configuration - my system is Windows XP Professional Russian, ANSI codepage is 1251, while OEM is 866, default language is USA English and country is Cyprus. That's why I can make logs and provide any other information that could fix the bug.