My problem is resolved. Essentially, I was having the problem with NIS 2012 working (as previously described). Wanting to make sure that my XP Pro Sp 3 was working properly, I attempted to do a Windows Update. That was not working either. So, I came to the conclusion that may have been a related issue. The second log capture routine that you suggested (i.e. the MS one), required .Net Framework SP 4. As the normal Windows Update was not working, I finally found a copy of the stand alone installer for that SP on the MS support site. However, even though I could install in another XP Pro computer in the office, it still would not install on the problem computer.
I then uninstalled NIS 2012 and then installed NIS 2011 directly from the oriignal CD. Problems with NIS and Windows Update continued. While researching the Windows Update problem, I was directed to the Windows Installer Clean Up utility, which I later found that MS had discontinued. However, I found out about another program, which was available through www.reimage.com. After installing NIS 2011 (which still produced the NIS probem) and leaving the error dialog boxes open, I downloaded Reimage and used it do analyze the problem computer. It found no threats -- which NIS should have found anyway. However, during the stability analysis, it found several problems. As this program also repairs and replaces damaged MS components from their online database, once I paid for a license key, I ran the repair utilities. Upon rebooting and completing the repair, I waited for the NIS errors to reapair. THEY DIDN'T.
Next I started running Windows Upate. As I had removed all .Net programs, obviously I needed ot get them re-installeded. Reimage did not fix that problem. Even when I used MS FixIt, the installation issue was not fixed. However, I found a stand alone copy of Windows Installer 4.5. Once I installed that and rebooted, I was able to use Windows Updater to initially install 42 updates (to include several security patches.) Since then I have run Windows Update several times, it continues to find additional updates. I believe that I needed 63 in all. Of course, I ran the NIS 2011 updater several times and completed the quick scan. Tonight I will run the complete scan.
Bottom line: This computer's XP Pro SP3 installation had been severely damaged. This probably was the result of virus or spyware activity that damaged the software even though NIS caught some of them prior to damage occuring. I have been and continue to be a big Norton fan. However, Norton is far from perfect -- as evidenced by my recent experience and the loads of comments made in this community. Reimage -- and further work to get Windows Update working and install all of the recommended updates -- has helped me repair the damage.
I appreciate the help from all the community users (and the help from the Norton staff). Apparently this problem was extremely severe. While I was tempted to completely zap the hard drive and start afresh, that was a costly alternative. The loads of postings on this community and on the MS site were very helpful. They pointed me in the right direction. Unfortunately, this computer was out of commission between Nov 8 and Nov 22. I am estatic that the problem has been resolved and I have not lost any data or programs.