On Mon, 2008-05-05 at 16:18 -0430, Patrick O'Callaghan wrote:
[You seem to have sent this just to me, though part of the reply is
directed at a wider audience -- poc]
On Mon, 2008-05-05 at 12:13 -0700, Les wrote:
> On Sun, 2008-05-04 at 17:45 -0430, Patrick O'Callaghan wrote:
> > On Sun, 2008-05-04 at 12:44 -0700, Les wrote:
> > > On Fri, 2008-05-02 at 16:49 -0430, Patrick O'Callaghan wrote:
> > > > On Fri, 2008-05-02 at 13:41 -0700, Les wrote:
> > > > > By the way, someone recommended using Evince instead of
> > > > > is a good idea, but I don't see how to eliminate acroread
> > > > > system. So If anyone can point me to some instructions on how
> > > > > acroread and run evince, that would be appreciated.
> > > >
> > > > To remove acroread: yum erase acroread
> > > > To use Evince (or whatever): in Firefox,
> > > > (or Content, depending on FF version).
> > > >
> > > > poc
> > > >
> > > Hi, poc,
> > > I had tried that, and it didn't work the first time. However I have
> > > reset the appropriate sections in Firefox now and that seems to have
> > > alleviated the problems. The command yum erase acroread didn't seem
> > > work either, then I checked to see if it was listed in the software GUI,
> > > and it wasn't. I didn't really expect it to be there, but thought
> > > would look anyway. I downloaded the rpm from adobe and installed it.
> > >
> > > I did expect the yum erase command to work??
> > It should, if your databases are clean. You can always do 'yum clean
> > metadata' or 'yum clean all' to make sure.
> > > I now seem to have evince running and have seen better performance from
> > > Firefox. Thank you for your assistance. I had used that menu before,
> > > but forgot about it. I had tried the about: plugins operation without
> > > success.
> > OK, glad it worked out. BTW okular is also worth a look as a reader for
> > PDF and other files.
> > poc
> I'll check that out. For now Evince has me running fine, and the cpu
> slowdowns were due to a little spider making a web which was sucked into
> the cpu fan, either stopping or slowing it down. I removed the whole
> heatsink/fan assembly, vacuumed it from both ends and around the fan, so
> things are much better now. I had to run to Radio Shack for some more
> heatsink compound, because what I had here had disappeared into the maw
> of my "nest" here in my computer room. I'll find it when I nest
> things out.
> For those of you with computer slow downs, one thing that happened
> during that heavy usage (apparently caused by some bug in npviewer), the
> heatsink compound had dried up almost completely. It is supposed to get
> thick and adhere a bit in most cases (at least from my long ago
> experience in maintaining things.) but if it gets totally dry, you lose
> some of the conductivity. So for the rest of you with the npviewer bug
> issue, check your fans and cpu interface. The fan unit is usually held
> on with two clips, so you remove the clips and just lift the fan and
> heatsink off. Vacuum it well, fan, heatsink from the sides where it is
> open, and then clean the top of the processor and the bottom of the
> heatsink with a kleenex or soft cloth. Do not use any water or soap or
> spray cleaner, just wipe it clean. Place a thin layer of new heatsink
> compound on it, then replace the fan unit square with the socket
> bracket, and reinstall the clips. As long as you do not remove the cpu
> from its socket, things will be copacetic and you will not have any
> issues. There are cleaning materials you can use, and if you are
> curious you can check with your local computer parts store for their
> recommendation, but in my experience, just cleaning both surfaces well
> and recoating works well.
I've done that in the past, for slight improvement and a lot of effort,
on a Pentium IV. I believe the paste should on fact be as thin as
possibly rather than thick, at least according to the instructions.
I finally gave up and switched to a Core 2 Duo and haven't had problems
since. The Pentium seemed to be too close to its design limit for
temperature, despite an Intel-approved case and fan and an Intel mobo,
and actually crashed several times on cpu-intensive stuff like
You are right, I did mean for this to go to the list, so this reply is
so stated. I don't know if it will find its rightful place in the
I should have said viscous instead of thick for how it should appear.
Yes, a thin layer as I did state later.
My system has now been on for an hour with no signs of heating up, nor