From: "DON HARDIE" <don on
I just installed a new harddrive and transferred all my personal documents
into it. When I start XP I get the message "Scheduled Agent - Cannot create
shell notification icon." When I click on OK the message dissapears and
everything seems to work as before.
Is this a real problem and how can I get rid of this message?
Don H


From: Colin Barnhorst on
You do not say what edition of XP you are using. Is it Home or Pro and does
it have Service Pack 1 or Service Pack 2 installed (or neither)? The reason
I ask is that I did a knowledgebase search on the phrase "cannot create
shell notification icon" and one of the few documents that showed up was
http://support.microsoft.com/default.aspx?scid=kb;en-us;811113
which is the incredibly long list of fixes in Service Pack 2. If you have
not yet upgraded to SP2 I recommend that you do so and see if the problem
persists. If you go to the link you will see why I did not exhaustively
search through it. It is so long that after it loaded my vertical slider
was only a quarter of an inch long. But somewhere on that list is the
phrase "cannot create shell notification icon". (Adding "Scheduled Agent -
" only pulled up one document and it was the same kind of list but for one
of the Windows 2000 service packs.)

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"DON HARDIE" <don hardie(a)iprimus.com.au> wrote in message
news:usfUIbGJFHA.2928(a)TK2MSFTNGP10.phx.gbl...
>I just installed a new harddrive and transferred all my personal documents
> into it. When I start XP I get the message "Scheduled Agent - Cannot
> create
> shell notification icon." When I click on OK the message dissapears and
> everything seems to work as before.
> Is this a real problem and how can I get rid of this message?
> Don H
>
>


From: "DON HARDIE" <don on
Colin

I am using XP Pro with Service Pack 1, but since I posted the query I have
started my computer 3 times and the message has not come up. I will wait and
see if it happens again and let you know.

Don Hardie


"Colin Barnhorst" <colinbarharst(nojunk)@msn.com> wrote in message
news:OwgdsFHJFHA.572(a)tk2msftngp13.phx.gbl...
> You do not say what edition of XP you are using. Is it Home or Pro and
does
> it have Service Pack 1 or Service Pack 2 installed (or neither)? The
reason
> I ask is that I did a knowledgebase search on the phrase "cannot create
> shell notification icon" and one of the few documents that showed up was
> http://support.microsoft.com/default.aspx?scid=kb;en-us;811113
> which is the incredibly long list of fixes in Service Pack 2. If you have
> not yet upgraded to SP2 I recommend that you do so and see if the problem
> persists. If you go to the link you will see why I did not exhaustively
> search through it. It is so long that after it loaded my vertical slider
> was only a quarter of an inch long. But somewhere on that list is the
> phrase "cannot create shell notification icon". (Adding "Scheduled
Agent -
> " only pulled up one document and it was the same kind of list but for one
> of the Windows 2000 service packs.)
>
> --
> Colin Barnhorst [MVP Windows - Virtual Machine]
> (Reply to the group only unless otherwise requested)
> "DON HARDIE" <don hardie(a)iprimus.com.au> wrote in message
> news:usfUIbGJFHA.2928(a)TK2MSFTNGP10.phx.gbl...
> >I just installed a new harddrive and transferred all my personal
documents
> > into it. When I start XP I get the message "Scheduled Agent - Cannot
> > create
> > shell notification icon." When I click on OK the message dissapears and
> > everything seems to work as before.
> > Is this a real problem and how can I get rid of this message?
> > Don H
> >
> >
>
>


From: Colin Barnhorst on
You might start a new thread when you do. In the meantime you should
install Service Pack 2. It is not just a bug fix and roll-up service pack.
This time they recompiled most of the system files to enable some important
new measures, such as Data Execution Prevention to keep hackers from
injecting machine code into the cpu through a data stream. Some new
software is already requiring SP2. Not much yet, but its coming.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"DON HARDIE" <don hardie(a)iprimus.com.au> wrote in message
news:eKMpPdSJFHA.576(a)TK2MSFTNGP15.phx.gbl...
> Colin
>
> I am using XP Pro with Service Pack 1, but since I posted the query I have
> started my computer 3 times and the message has not come up. I will wait
> and
> see if it happens again and let you know.
>
> Don Hardie
>
>
> "Colin Barnhorst" <colinbarharst(nojunk)@msn.com> wrote in message
> news:OwgdsFHJFHA.572(a)tk2msftngp13.phx.gbl...
>> You do not say what edition of XP you are using. Is it Home or Pro and
> does
>> it have Service Pack 1 or Service Pack 2 installed (or neither)? The
> reason
>> I ask is that I did a knowledgebase search on the phrase "cannot create
>> shell notification icon" and one of the few documents that showed up was
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;811113
>> which is the incredibly long list of fixes in Service Pack 2. If you
>> have
>> not yet upgraded to SP2 I recommend that you do so and see if the problem
>> persists. If you go to the link you will see why I did not exhaustively
>> search through it. It is so long that after it loaded my vertical slider
>> was only a quarter of an inch long. But somewhere on that list is the
>> phrase "cannot create shell notification icon". (Adding "Scheduled
> Agent -
>> " only pulled up one document and it was the same kind of list but for
>> one
>> of the Windows 2000 service packs.)
>>
>> --
>> Colin Barnhorst [MVP Windows - Virtual Machine]
>> (Reply to the group only unless otherwise requested)
>> "DON HARDIE" <don hardie(a)iprimus.com.au> wrote in message
>> news:usfUIbGJFHA.2928(a)TK2MSFTNGP10.phx.gbl...
>> >I just installed a new harddrive and transferred all my personal
> documents
>> > into it. When I start XP I get the message "Scheduled Agent - Cannot
>> > create
>> > shell notification icon." When I click on OK the message dissapears and
>> > everything seems to work as before.
>> > Is this a real problem and how can I get rid of this message?
>> > Don H
>> >
>> >
>>
>>
>
>