>> 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://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

Signature
MS-MVP Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"
johnho - 30 Jul 2006 10:11 GMT
Malke Wrote:
> --
> How to Troubleshoot By Using the Msconfig Utility in Windows XP -
[quoted text clipped - 36 lines]
>
> Malke
Many thanks for your trouble. Much appreciated.
johnho

Signature
johnho