There are several users out there, that have problems with the latest versions of PDFCreator.
We are trying to track down a specific problem, where the printer temp path is not detected correctly and the system temp path is used. We would like to get a virtual image of a machine where this happens to be able to track it down on our end and to finally fix it.
Is someone out there that is able to create such an image or would allow us to create it on your machine? This would be best on a machine that is freshly installed, so we do not get all your personal data as well.
Please let us know when you can create a snapshot of your system we can use to track down this error.At the moment, we don't have a clue what could cause this problem and thus don't know how to solve it.
Hi Philip, Happy to help if I can. I have been using 1.3.2 for a while and all seemed OK. But in last couple of days I can't print. Select PDF Creator, press print, get icon that printing taking place but then nothing. As part of my snooping around, re-installing and the like the "Printer monitor" screen came up. I have never seen this before. But what it did show was all the unprinted jobs I had sent that day with "Printer stopped" by each one. So it sounds like the "Printer stopped" command is now the default. I run XP. Hope this helps. Martin.
could you help us out with an image of your system like decribed above?
That would be great!
Since I installed 1.4.0 I can't print anything to file.
I am using 64 bit Windows 7. I have nothing in the print queue. Also, if I try to print a test page via the print monitor, I get path/access error.
It looks like we have tracked this down. This happens, when the environment variables TMP and TEMP point to different folder. As a workaroud, please make sure that both variables point to the same folder. We will release PDFCreator 1.4.1 in a few days which will finally fix this issue.
This problem remains as detailed here: http://www.pdfforge.org/forum/open-discussion/8980-pdfcreator-v141-not-workingtemp-files-issues-win7-pro-x64
I'm not able to provide a system image as this is a production machine, but I can supervise a Crossloop or possibly work with you in some kind of live context to test the machine and attempt fixes. I believe I'm fairly savvy as the IT consultant for several small businesses. Please let me know how I can help.
thanks for your help. The problem was that you changed the system variables TMP and TEMP. PDFCreator wasn't able to handle this. This is fixed in version 1.4.2. If you want you can get a link to a test version.
That would be neat- I'll try it out on our production machine tomorrow and see if that fixes my issue. Sounds like you nailed it. Thanks! I didn't see a link on pdfforge.org or sourceforge files/SVN, but I saw the commit... I just don't know how to build it. :) PM/Email would be great, thanks!
You don't need to build it I'll send you a link. :-)
Using PDFCreator 1.4.1 I still have problems with the creation of PDF files although TEMP and TMP system variables are the same. But: the user variables TEMP and TMP point to another folder. Maybe this is the problem some people have, too. My environment looks like this:
The link to the image didn't work, trying again: http://img198.imageshack.us/img198/135/bildschirmfreigabebild.png
thank you very much for your help everybody, we were able to track down the problem and it is fixed in version 1.4.2.
I'm sorry, but problem is NOT fixed for me even in version 1.4.2...
is NOT recognized by PDFcreator.
It always writes temporary files to user's directory temp path.