ipggi
11-29-2004, 07:43 PM
I don't know if this has been pointed out before but ..
I have used PrimoPDF in the past with no problems. On my current installation I tried using it and it simply wouldn't work. There was no error messages and the installation was completed successfully. But when I tried printing a file from any program, it would fail. The print dialog would come up, you would okay it all, it would say it's printing and then nothing.
Well after a bit of trial and error I managed to trace the problem. According to this log of the primopdf port. The driver was looking for the a windows directory in my tempary directory that couldn't be found so it halted. Well a realised I changed both my TMP and TEMP paths to D:\TEMP in the control panel/system/advanced settings and this was causing the PrimoPDF to halt. The simple fix was to create a 'windows' in the temp directory and then the driver worked without a hitch.
Only problem is that this kind of problem I guess is anything but obvious and it took me a good hour or two to trace. Maybe in a future version the install program or the application itself could detect that all the required directories it needs are there, and if not then create them?
Regards Ben
I have used PrimoPDF in the past with no problems. On my current installation I tried using it and it simply wouldn't work. There was no error messages and the installation was completed successfully. But when I tried printing a file from any program, it would fail. The print dialog would come up, you would okay it all, it would say it's printing and then nothing.
Well after a bit of trial and error I managed to trace the problem. According to this log of the primopdf port. The driver was looking for the a windows directory in my tempary directory that couldn't be found so it halted. Well a realised I changed both my TMP and TEMP paths to D:\TEMP in the control panel/system/advanced settings and this was causing the PrimoPDF to halt. The simple fix was to create a 'windows' in the temp directory and then the driver worked without a hitch.
Only problem is that this kind of problem I guess is anything but obvious and it took me a good hour or two to trace. Maybe in a future version the install program or the application itself could detect that all the required directories it needs are there, and if not then create them?
Regards Ben