Recipients cannot open my pdfs?

[lizzie857]

More than several folks have said they cannot open my primo-created pdfs.....

Latest feedback was....."freezes up all of our computers - Jim's at the office, Jim's at home, and mine at home as well.

wha? :)

[sicscottreed]

I am having a similar, maybe identical problem. I am creating PDF files with PrimoPDF. I am running Vista SP1 x64. I do not have Adobe Acrobat Reader installed. I can create PDFs and open the PDF I create just fine with FoxitReader. However, other users are unable to completely open the PDFs I create with PrimoPDF. They are all using Adobe Reader version 8. When they open the files, the page "draws" extremely slowly and never fully completes. I emailed the file to my home computer and was able to open the PrimoPDF created fine in Foxit Reader as well. When others try to print the document, the complete page will not print.

It almost seems like an Adobe Reader issue to me, not PrimoPDF. Anyone at PrimoPDF have any ideas?

[Jason.Stockett]

We would need some more details on what is causing the problem. If you can post a link to the file you are experiencing these problems with we can use those files in some testing.

If it were a problem with the creation of the file, it should not matter which viewer is opening it as none would be able to read it correctly.

Can those people who are having problems opening up your PDF file view others that are not created by primoPDF? If so what version of PDF are you creating?

Using the "Custom" option you have the ability to select what version of PDF you want to create. If you are creating v1.5 and they do not have a current reader they may not be able to open and view the file. If you change the selection to 1.2 or 1.3 most viewers should have no problems opening and reading those files.

[sicscottreed]

I believe installing version 4.1 of PrimoPDF resolved my problem. I was running 3.2 and did not realize there had been an upgrade in the last few days.

[RacerX]

I actually had this problem with v4 and had to uninstall and go back to v3.2 to solve this issue.