PDA

View Full Version : does not do anything


jiro99
04-14-2006, 03:31 PM
I have been using the original PrimoPDF for awhile with no problems at all (thanks). Just installed Version 2. It does NOTHING. I can send documents to the printer queue from Firefox, IE, MSWord, OOo, whatever - but nothing happens. I can see the queue, but PrimoPDF does not pop up, does not create a PDF, does not react at all. restarting the document printing does not work, either.

I am using WinXP professional.

Please help... thanks.

Frank
04-17-2006, 11:58 AM
When I "print" using PrimoPDF, nothing happens. I remove it, re-install it again. It works. But when I want to "print" again. nothing happens.
Can anyone help?
Thanks,
Frank

Tammydrie
04-27-2006, 06:59 PM
I have the same experience. PrimoPdF worked fine for a while, but now it only works when freshly reinstalled. When I ask a document to print to primopdf no message comes up asking for the filename or location, but a document does appear in the Primopdf print queue. I can't get anything in the print queue to print.

wildflowerneu
05-06-2006, 09:21 PM
I am having the exact same problem too. Is there anyone out there that can help us all?

helpme
06-20-2006, 06:02 PM
The same thing is happening to me. I have used this program for over a year now and have never had this problem until recently. Has anyone found any help?

N Morrison
07-18-2006, 01:46 PM
Using Windows XP Home, same thing - looks like it is printing but no request for filename etc and no results. Who broke it?

robjamell
07-22-2006, 08:43 AM
I have been having the exact same problem for a while.

Deanb
09-07-2006, 06:15 PM
We had the same problem, but discovered that when a user is not a local admin, PrimoPDF does not popup. Unless, you remove the tick from "Run as user". Run as user seems to use System (or something) that requires admin rights to run the exe, not the logged in users credentials.

machec
10-09-2006, 08:15 AM
I fixed this problem on my laptop running XP pro and I'm on as Admin.

These were the symptoms. On a new Primo install you could print to PDF once and if you tried it a second time it would ask if you want to overwrite the existing file, when you select yes it would beep and delete the existing file but not write the new file. If you tried to write another PDF it would go through the motions of creating a PDF yet not give you any file at all. Now, when your Primo screen comes up and you browse to a different directory to save your file it would work, but just once and you're back to the same thing. Changing to a new directory every time I want to save a PDF doesn't really work for me.

After fiddling with all the selections in the print driver this is what I did to fix it. Go into your printer folder, right click on PrimoPDF and goto properties. Select the Ports tab, the port checked should be Primoport, click Configure port. Change your Output setting to "prompt for filename", select ok and close your printer properties box.

Open a webpage or whatever and print to the Primo printer. Now before you get to the main Primo screen you'll get a new "save as" dialog box. I don't think it matters what name you give this file or where you save it because it actually doesn't create anything. Type in some garbage letters and hit save. Your main Primo screen comes up, make your selections and hit ok, it should have made a new PDF for you.

Now go back to the printer properties and change your Output setting back to "program handles output", ok it and then close the printer. Now you should be able to make a PDF where and how you want with no errors.

I unistalled and reinstalled Primo and got the same original problem, did this fix and it still works. Good luck.

rembert
10-12-2006, 08:50 AM
I was using the 2.0 version but somehow PrimoPDF didn't export more than just about four pages from longer documents. Digged this forum and found some recommendation to upgrade to the 3.0. Sounded as a good suggestion so I did just this. The weird question 'option 1 / option 2' is still asked while installing - I chose option 1.

Now using PrimoPDF was a bit more spectacular: the printer spooler crashed as soon as I tried to print anything via PrimoPDF and a short beep was sounded. (I'm using Windows XP Home)

Removed PrimoPDF. Rebooted the system. Re-installed the 3.0 version (now choosing option 2. Rebooted again. Ok, printing using PrimoPDf didn't crash the printer spooler anymore but the beep was still sounded. And now the print spooler for PrimoPDF told me it cannot connect to the printer. What-the-hack?

I followed machec's instructions and miraculem est: it does work now. And it even exports large documents, repeatedly. So Machec: thanks for your solution!

leecallen2
11-22-2006, 03:01 PM
I had the same problem referred to in this (and other) posts, and I have found a fix that worked for me (XP Pro system).

My symptoms:
PrimoPDF worked great for months, then just stopped working. I am not sure what version I was running. When I would attempt to print to PrimoPDF, nothing happened. If I looked at the PrimoPDF Printer (Start, Settings, Printers and Faxes, PrimoPDF), it showed the spoolfiles I had attempted to print, but the first spoolfile had an error.

I tried the suggested remedy - install the latest version 3.0. No luck. I also tried uninstalling and re-installing. Again no luck.

I tried the remedy suggested by MACHEC but his symptoms did not match mine, and the remedy did not work. But I noticed: When I went into the printer Properties
(Start, Settings, Printers and Faxes, PrimoPDF, Properties, Ports, Configure Port)
it referenced two programs that did not exist:
C:\Program Files\activePDF\PrimoPDF\primorun.exe
C:\Program Files\activePDF\PrimoPDF\primopdf.exe
The directory existed, but those executables were not there.

So here is what I did:
uninstall PrimoPDF (3.0)
delete the PrimoPDF printer if it still exists (it did not, for me)
run REGEDIT and delete every registry entry containing 'activepdf' or 'primopdf'
re-install PrimoPDF (3.0)

Now, those executables exist, and the program works.

Notes for PrimoPDF developers:
1. Why did those programs disappear?
2. The uninstall should clean up the registry