Forum Moderators: not2easy
Sometimes, but not always, these files fail to load in people's IE 6 browser windows. (IE is our very capable IS department's choice of browser for all onsite PCs ... naah, let's not go there.)
The failures seem to occur on machines that use Acrobat Reader 5 or 6. The machines open the files fine if they're first saved locally and then opened in Reader.
The same file may work on one machine but not the next, similarly-equipped, machine. And ... a "problem" machine may be able to open some PDFs within the browser but not others.
( = sound = of = head = being = scratched = ).
If I refresh the PDF's link several times, it usually miraculously appears in the problem machines' browsers.
Many Google hits recommend a workaround -- to the effect of:
Open Acrobat Reader 5 and open the menu Edit/Preferences/General/Options. Disable the entry: "Allow fast web view." Save the changes and reopen the web browser and try to view the report.Open Acrobat Reader 6 and open the menu Edit/Preferences/Internet. Disable the entry: "Allow fast web view." Save the changes and reopen the web browser and try to view the report.
...which works, but a better solution would be for me to learn what's causing the problem and adjust my PDF creation procedure accordingly.
Anyone else get this? Any ideas?
Thanks.
I use Corel Draw 10 to generate PDF files.
I also had this "error reading linearized hint data" error in some cases. My workaround for it was:
- when generating the PDF file, selected the "configuration" button, "advanced" tab, and unchecked the option "optimize for the web". It worked!
I hope you can find anything similar in in the Adobe6.0 Pro/XP's PDFMaker and Distiller.
Taks
Only problem I've run into similar to this was related to security settings; they'd let the computer save but not open the file, but after a copy was saved that one could be opened. When even tweaking the security settings didn't work, installing 7.0 did. Afraid I don't know details about the security settings at my "day job"--I just know that they're quite high because of NIH requirements. But the bottom line seemed to be Reader 7.0.
Thank you both for your posts. Taks, you were right on the money with that -- I unchecked the "Optimize for Fast Web View" (that's the Mac versions wording, which I have at home -- I think the PC version at work said "Save for Fast Web View") and all was well.
From reading a little more about it online, that option "linearizes" the file, which reorders the data to facilitate its speed when working with the Acrobat Plugin for browsers. But it must be (or must have been) a bit tricky as not all examples of Reader 5 and 6 can read every file so optimized -- even ones made by Adobe products, as in my case.
Anyway, we've decided to make it our SOP not to optimize files for web anymore -- we make our PDFs for use by a wide swath of the public, many of whom will never update their Acrobat 4 until the day their power supplies kack.
Beagle, you are absolutely right. Your suggestion is fantastic. (In fact, I asked the person who brought the problem to my attention to do just that, only she's not that software-savvy and didn't want to ask IS to do it.)
Here's a side story to illustrate why your idea may be a tough sell: for two years we have had the licenses to upgrade everyone in the organization from Office 2000 to Office 2002 at no cost (well, yeah, we did pay for the licenses, so there was that cost) -- so why doesn't anyone have the Office upgrade installed? I guess it turns out that it would be a hassle for the IS guys to have to deploy. .................. Well, it is true, they are busy and do have their hands full most of the time. Oh well.
