acrobat reader and netscape

oupei

Senior member
Jun 16, 2003
285
0
0
after having acrobat reader run in netscape, after I close netscape, reader doesn't close. the extra memory hog doesn't bother me too much, but when I close netscape, there's some major conflict going on as netscape runs at 100% cpu util for like 20 secs.

anyone know why?

aside: I've been using netscape over mozilla because I'm used to it's look and feel. As far as I know, they are the same. am I correct?
 

thegorx

Senior member
Dec 10, 2003
451
0
0
I never have liked the acrobat reader pluggins
there should be a setting where you can just have the acrobat reader open when you click on a pdf link.
also I've found that acrobat reader 6 is either buggy or has got too many oars in the water
 

screw3d

Diamond Member
Nov 6, 2001
6,906
1
76
Let me guess.. Acrobat Reader 6?

Try downgrading to Acrobat Reader 5.x and see if it works better?

Edit: Netscape and Mozilla is *almost* the same, but not quite. I'll hand the advantage to Mozilla because it is much newer and updated.
 

VirtualLarry

No Lifer
Aug 25, 2001
56,587
10,225
126
Originally posted by: oupei
after having acrobat reader run in netscape, after I close netscape, reader doesn't close. the extra memory hog doesn't bother me too much, but when I close netscape, there's some major conflict going on as netscape runs at 100% cpu util for like 20 secs.

anyone know why?

aside: I've been using netscape over mozilla because I'm used to it's look and feel. As far as I know, they are the same. am I correct?

I used to have that problem a lot too, but not anymore, for some reason. I'm running Firefox 0.8 nightly build 2004-04-07-09, and Acrobat reader 5.1.0 9/17/2002, all on W2k SP2.

When I close a browser window with the embedded Acrobat Reader plug-in, it apparently actually closes now as well, because if I browse to another .PDF file, I see the A.R. loading splash-screen again. I used to have to start Task Manager to kill off acroread.exe, because I couldn't close Mozilla properly. I'm not sure what has changed, either bugfixes in Reader, or in Mozilla, but this combination "works for me".