Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
This looks very similar to the issue posted here:
http://community.norton.com/norton/board/message?board.id=Norton_360&message.id=154#M154
I am locking this thread; please post your info to the above thread, and check that thread for follow-up information. Thanks!
Has anyone here heard of an issue of the Excel XP process still running after exiting the program with Norton 360 v2 installed with XP Pro SP3?
yes of course. This is likely related to the zombie issue (as others have coined). Basically, programs remain listed in Windows Task manager even though you have closed them down in the ordinary way. The problem is not specific to Excel but is seen across so many programs. If you want to prove that the problem is Norton, you would need to
Go to Start -> Run, and type drwtsn32.exe, and click "OK". Check all boxes in the "Options" section of Dr. Watson for Windows when the dialog appears. Note the value in the "Crash Dump" box. OK the changes in Dr. Watson.
Then, please kill all instances of Excel and launch a new instance of Excel and exit it. The Excel process should "hang around". Note the PID of this instance. Then, from a CMD prompt, type the following command:
drwtsn32.exe -p <pid of autoruns.exe, noted earlier>
then you investigate the dump information.
Otherwise, take it that this is a problem, with Norton 360 v2.
Clive