Error message - Shell_NotifyIconFail

[johnho]

I get message "Shell_NotifyIconFail". Can someone tell me what this
means?
johnho

 

[Malke]

I get message "Shell_NotifyIconFail". Can someone tell me what this
means?
johnho

Some program is set to start with Windows and to put an icon in the
Notification Area. It is failing to do so. Use the System Configuration
Utility to troubleshoot which program is the culprit.

Start>Run>msconfig [enter]

This brings up the System Configuration Utility. Look on the Startup tab and
find the probable culprit. Uncheck the box next to its name, Apply and OK
out. You don't need to restart immediately, but the next time you do you'll
get a dialog saying you've used the Utility. Just tick the box that says in
effect, "don't bother me about this again".

How to Troubleshoot By Using the Msconfig Utility in Windows XP -
http://support.microsoft.com/?id=310560

Malke

 

[johnho]

johnho wrote:
-

I get message "Shell_NotifyIconFail". Can someone tell me what this
means?
johnho-

Some program is set to start with Windows and to put an icon in the
Notification Area. It is failing to do so. Use the System
Configuration
Utility to troubleshoot which program is the culprit.

StartRunmsconfig [enter]

This brings up the System Configuration Utility. Look on the Startup
tab and
find the probable culprit. Uncheck the box next to its name, Apply and
OK
out. You don't need to restart immediately, but the next time you do
you'll
get a dialog saying you've used the Utility. Just tick the box that
says in
effect, "don't bother me about this again".

How to Troubleshoot By Using the Msconfig Utility in Windows XP -
http://support.microsoft.com/?id=310560

Malke
--
MS-MVP Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

Thanks for your reply. Unfortunately I don't have a clue which is the
"probable culprit"!!
I can drive a computer but I don't know how to fix it! Any further help
appreciated. Is it OK to just ignore the message?
johnho

 

[Malke]

Thanks for your reply. Unfortunately I don't have a clue which is the
"probable culprit"!!
I can drive a computer but I don't know how to fix it! Any further help
appreciated. Is it OK to just ignore the message?

If you read the MS Knowledge Base article I gave you, it tells you how. You
do a few things:

1. Look up what you see in the Startup tab in msconfig. Here are some links
where you can do that:

http://aumha.org/a/loads.htm - What loads at Startup?
http://castlecops.com/StartupList.html
http://www.pacs-portal.co.uk/startup_index.htm
http://www.theeldergeek.com/services_guide.htm
http://www.liutilities.com/products/wintaskspro/processlibrary/

2. On the Startup tab only (not Processes), when you've determine what the
entries are you can systematically disable non-essential things to see
which program is giving the trouble. Troubleshooting is mostly a process of
deduction.

I can't answer your question about the desirability of ignoring the message
without seeing the computer. It may be a better solution for you to take
the machine to a local professional (not a BigStoreUSA type of place) and
have them check it out.

Malke

 

[johnho]

johnho wrote:
--
How to Troubleshoot By Using the Msconfig Utility in Windows XP -
http://support.microsoft.com/?id=310560--
-
Thanks for your reply. Unfortunately I don't have a clue which is the
"probable culprit"!!
I can drive a computer but I don't know how to fix it! Any further
help
appreciated. Is it OK to just ignore the message?-

If you read the MS Knowledge Base article I gave you, it tells you how.
You
do a few things:

1. Look up what you see in the Startup tab in msconfig. Here are some
links
where you can do that:

http://aumha.org/a/loads.htm - What loads at Startup?
http://castlecops.com/StartupList.html
http://www.pacs-portal.co.uk/startup_index.htm
http://www.theeldergeek.com/services_guide.htm
http://tinyurl.com/97zn

2. On the Startup tab only (not Processes), when you've determine what
the
entries are you can systematically disable non-essential things to see
which program is giving the trouble. Troubleshooting is mostly a
process of
deduction.

I can't answer your question about the desirability of ignoring the
message
without seeing the computer. It may be a better solution for you to
take
the machine to a local professional (not a BigStoreUSA type of place)
and
have them check it out.

Malke
--
MS-MVP Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

Many thanks for your trouble. Much appreciated.
johnho