StewartFluney
Sun Apr 13 08:28:01 PDT 2008
Ken Blake:
The matter of eliminating the LimeWire icon in the System Tray has now been
resolved.
Through an oversight, I didn't notice this option was available through the
Tools, Options, System Tray of the LimeWire program. I have used that option
in this case.
Many thanks for your response and advice in this respect.
Stewart Fluney
--
Stewart Fluney
"Ken Blake, MVP" wrote:
> On Sat, 12 Apr 2008 12:24:00 -0700, Stewart Fluney
> <StewartFluney@discussions.microsoft.com> wrote:
>
> > Ken Blake:
> >
> > Thank you for your response.
>
>
> You're welcome. Glad to help.
>
>
> > I have noted your advice and have tried to eliminate the LimeWire icon in
> > the System Tray in the manner you outlined; i.e., through the program itself;
> > however, that option doesn't appear to be available unless I missed it.
> > Therefore, I have resorted to eliminating the icon through the Startup
> > section of the System Configuration Utility window. Do you agree?
>
>
> Normally, yes, I would agree. But note Leonard Grey's comment: "You
> may have a problem there because LimeWire is a known source for
> viruses and spyware." I have no experience with LimeWire myself, so
> I'll defer to others who know more about it than I do. But if he is
> right, that may complicate the issue.
>
>
>
>
>
> > "Ken Blake, MVP" wrote:
> >
> > > On Sat, 12 Apr 2008 09:04:01 -0700, Stewart Fluney
> > > <StewartFluney@discussions.microsoft.com> wrote:
> > >
> > > > Can you advise me how to dispose of an icon in the bottom right-hand corner
> > > > of the Task Bar? In an effort to do this, I removed the shortcut of the
> > > > program from my screen, but an icon still persists in appearing at start-up
> > > > in the Task Bar.
> > > >
> > > > I didn't want to eliminate the program to achieve the above.
> > >
> > >
> > > First, two points:
> > >
> > > 1. This area, near the clock, is called the System Notification Area,
> > > or informally, the System Tray.
> > >
> > > 2. The icons there represent running programs (normally programs
> > > running in the background.
> > >
> > > So presumably what you want to accomplish is not simply removing the
> > > icon, but stopping the program from starting automatically. Here's my
> > > standard post on stopping programs from starting automatically:
> > >
> > > First, note that you should be concerned with *all* programs that
> > > start automatically, not just with those that go into the tray. Not
> > > all autostarting programs manifest themselves by an icon in the tray.
> > >
> > > On each program you don't want to start automatically, check its
> > > Options to see if it has the choice not to start (make sure you
> > > actually choose the option not to run it, not just a "don't show icon"
> > > option). Many can easily and best be stopped that way. If that doesn't
> > > work, run MSCONFIG from the Start | Run line, and on the Startup tab,
> > > uncheck the programs you don't want to start automatically.
> > >
> > > However, if I were you, I wouldn't do this just for the purpose of
> > > running the minimum number of programs. Despite what many people tell
> > > you, you should be concerned, not with how *many* of these programs
> > > you run, but *which*. Some of them can hurt performance severely, but
> > > others have no effect on performance.
> > >
> > > Don't just stop programs from running willy-nilly. What you should do
> > > is determine what each program is, what its value is to you, and what
> > > the cost in performance is of its running all the time. You can get
> > > more information about these at
> > >
http://castlecops.com/StartupList.html. If you can't find it there,
> > > try google searches and ask about specifics here.
> > >
> > > Once you have that information, you can make an intelligent informed
> > > decision about what you want to keep and what you want to get rid of.
> > >
> > >
> > > --
> > > Ken Blake, Microsoft MVP - Windows Desktop Experience
> > > Please Reply to the Newsgroup
> > >
>
> --
> Ken Blake, Microsoft MVP - Windows Desktop Experience
> Please Reply to the Newsgroup
>