thanks Sharon... I always appreciate your input... I think I am going to use
that error as a good error.. a warning that the program or whatever is not
one compatible... thanks.. Rainy
"Sharon F" <sharonfDEL@ETEmvps.org> wrote in message
news:ugiGGjj5FHA.2600@tk2msftngp13.phx.gbl...
> On Thu, 10 Nov 2005 15:24:50 GMT, Rainy wrote:
>
>> ps. one question I would like answered please, is why the error gave a
>> false
>> path?
>
> I think the answer to that question is somewhere in here:
>> like I said the path C Program files Symantec does not exist. I
>> use AVG for my antivirus and I am very comfortable with it..unlike the
>> way I
>> feel when Symantec is guarding the door.. Symantec has let a few
>> nasties
>> come through... However I do have a Norton's product.. Windoc... so maybe
>> that is why it gave the error from Symantec.
>
> It's been several years since I've used Symantec products but I believe
> "symevent" is tied into their Live Update or maybe just system
> notifications from Norton products. If not used by the software you have
> installed (apparently not since you don't have the file), it may just be a
> reference in the registry that is added "just in case" there's a "full
> suite" install. A "one size fits all" registry entry, if you will -- There
> if you need it. Doing no harm if it isn't.
>
> --
> Sharon F
> MS-MVP ~ Windows Shell/User