Adobe Acrobat Reader

Serendipity

Anybody here have problems with Adobe Reader (any version)? I thought there was something wrong with my PC as it took a long time to load up. However, it seems like the PCs at my school also suffer from the same issue.

It usually happens on a large PDF file - when you click on it, Adobe Reader takes forever to load up. And during that time the browser appears "frozen" but it isn't...Adobe Reader is just hogging up the machine.

So with that, I have to say....Adobe Reader sucks!

bobman1235

Yeah that just seems to be the nature of the beast. Newer versions are a little quicker - probably because they preload the program and leave it in memory from startup. I never did understand why that program is so intensive.

Serendipity

I find the newer versions, although they load quicker, make the PC start up MUCH slower. Probably like you said, because they preload the program during startup.

Airplay355

If it;s just reader, get a different program to read pdfs and set that as the default pdf opener.

bobman1235

If you're on a slower PC and it's a big deal, there are some PDF readers out there that are WAY quicker. I was using FoxIt for a while on my older PC with good results.

Serendipity

Nope, new PC, 2.0GHz dual core processor + 2GB of RAM and it's still slow.

Serendipity

Lasareath wrote: »

I have Adobe Acrobat 8 Professional (version 8.1.2) and it loads up in like 4 to 6 seconds.

That's because it loads the program while your PC is starting up, similar to SuperFetch in Windows Vista.

Some searching on the net uncovered the following: "This works by installing a QuickStart program which runs every time the computer is turned on, and which loads parts of Reader into memory. This can sometimes improve the loading speed of Reader, but also uses up valuable memory resources on the computer and causes longer system start-up times.

Many have also noted poor behavior in the Internet Explorer and Mozilla Firefox Acrobat plug-ins. The plug-ins do not support full asynchronous loading, thus causing browsers to appear to "lock up" until the document has been fully downloaded. To make matters worse, they apparently also fail to terminate when a document is closed, thereby leaving behind various CPU-intensive application threads that run until the next reboot."

Systems

your computer sux. give it to me.


Chuck

Serendipity

This is what it looks like when loading a big PDF file - a blank screen until the file has downloaded a little, like 1-2 megs or so.

Serendipity

I need to defrag this?

Serendipity

Okay, done.

ledhed

Quick on mine and it doesn't load in startup

Serendipity

ledhed wrote: »

Quick on mine and it doesn't load in startup

Try loading a 120MB PDF file. And then you'll see what I mean