Why do you hold MS responsible for making Norton products compatible with
SP2? SP2 went RTM on 9 Aug-04 and Norton didn't release any SP2-specific
updates for any of its products until late September, IIRC.
I have come to the conclusion that, short of flattening the box and
reinstalling Windows, the only way to remove every last trace of a Norton
product is to use the appropriate removal tool (e.g., SymNRT, Rnav2003.exe)
and then followup with a "cleaner" like Easy Cleaner or CCleaner.
That's my story and I'm stickin' to it.
--
~PA Bear
Chad Harris wrote:
> Robear--
>
> I appreciate your links and always thorough posts and although I did
> happen
> on this link below and may not have read some of these articles. I have
> read a lot of Firewalll configuration articles from Norton as to not being
> able to get through to the net.
>
> http://tinyurl.com/do2je (I don't remember where I saw this--a ngp
> post--may have been yours) I spent weeks with all of the manual uninstall
> KBs from Symantec Norton.
>
> I look forward later to showing you my problem. I installed the WSH 5.6
> over 50 times but it's not havening impact on this and I manually
> uninstalled every Norton Product I had on this box including Ghost 5.0.
> Ghost 5.0 installed on SP2 will BSOD you and some times people can't get
> up
> to Windows afterward if you don't follow the 2 Norton KBs to add a line to
> boot .ini and take several other steps on an XP SP2 box prior to
> installing
> Ghost 5.0 I had the pleasure of recovering from several of them (one of
> the
> two times I've ever seen LNG work when SR wouldn't or LNG work at all--the
> other was with a Nero InCD install that went south.)
>
> During SP2 when Redmond SP2 team members were in town for meeting, I
> said
> neither you nor Symantec is dealing with the glitches and they said "Oh it
> will be well taken care of by RTM" by us and Norton (this was in June of
> 2004) and of course it wasn't.
>
> I know for a fact that there were tons of posts on conflicts with every
> Norton app and SP2 prior to it's release while it was in Beta and MSFT
> personnel read every one of them.
>
> Thanks very much,
>
> Will get the history and links up later.
>
> Chad Harris
> ____________________________________________
>
>
>
> "PA Bear" <PABearMVP@gmail.com> wrote in message
> news:O$j9Pr9WFHA.4032@tk2msftngp13.phx.gbl...
>> The Symantec page 'Uninstalling and reinstalling Norton AntiVirus 2003'
>> (http://service1.symantec.com/SUPPORT/nav.nsf/docid/2002122115120906)
>> makes reference to reinstalling Windows 5.6 Script Engine as a final
>> step.
>>
>> I discovered the above today when replying to another poster in OE6
>> newsgroup
>> (http://groups-beta.google.com/group/microsoft.public.windows.inetexplorer.ie6_outlookexpress/msg/53ae2738217156fa?hl=en
>> or http://snipurl.com/ezhq). [If you wanna see a /really/ complicated
>> NAV/NSW uninstall problem, check it out. <w>]
>>
>> References for you:
>>
>> Uninstalling and reinstalling Norton AntiVirus 2003
>> Subsection: To uninstall Norton SystemWorks 2003 if Add/Remove
>> Programs
>> does not work
>> http://service1.symantec.com/SUPPORT/nav.nsf/docid/2002122115120906
>>
>> Removing your Norton program using SymNRT (/very/ new: 17 May-05)
>> Applies to:
>> Norton AntiVirus 2004, 2005, 2004 Professional, and 2005 Professional
>> Norton Internet Security 2004, 2005, 2004 Professional, and 2005
>> Professional
>> Norton SystemWorks 2004 and 2005
>> Norton AntiSpam 2004 and 2005
>> Norton Personal Firewall 2004 and 2005
>> Norton Ghost 2003 and 9.0
>> Norton Password Manager 2004
>> http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2005033108162039
>>
>> You have my utmost sympathies, Chad. In future, I will be advising
>> anyone
>> who's uninstalling/reinstalling a Norton 2004 or higher application to
>> use
>> SymnNRT, despite what Symantec may say or how cleanly the Norton app
>> apears to uninstall. Given what I've learned recently, my prejudice
>> against Symantec products is even more adamnant and I will strongly
>> caution anyone against installing any Symantec product from now on.
>>
>> Related:
>>
>> Microsoft Windows OneCare - Press release
>> http://www.microsoft.com/presspass/press/2005/may05/05-13WindowsOneCarePR.asp
>>
>> Windows OneCare Home Page
>> http://www.microsoft.com/windows/onecare/default.mspx
>>
>> Thanks for your kind words and feedback. It is very much appreciated.
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-Windows (IE/OE) & Security
>>
>> Chad Harris wrote:
>>> Robear--
>>>
>>> I really welcome and appreciate the chance to show you this problem
>>> and
>>> forgive me for not getting back promptly. I want to tie it together with
>>> the links and remedies that have not worked, including Symantec's
>>> inability to deal with it at the highest levels of their Tech Support
>>> team in Oregon. It's NIS 2005, there have been previous versions which
>>> were meticulously manually and tool cleaned per their instructions.
>>> They
>>> have one Norton KB on scripts which basically says they have no
>>> solution--you and I have seen those before.
>>>
>>> I was left thinking that if in fact WSH 5.6 which seems to be working
>>> fine
>>> in every other context were "broken", without any scripting ability I
>>> would be powerless to fix it. It seemed to be the old case of Symantec
>>> blaming MSFT their platinum partner and now competitor and MSFT blaming
>>> Symantec. I will get this and links together. It frustrates me no end
>>> that I bought NIS and can't use it because it blocks my surfing the web
>>> no matter what I do. There h as to be a simple solution somewhere.
>>>
>>> Sometime later today I will lay out the links and *everything that we've
>>> tried* including many meticulous uninstalls of every manual Norton reg
>>> key
>>> and folder per their byzantine KBs on this. I will also list previous
>>> Norton products in and manually uninstalled. The only AV products or
>>> security products ever installed have been Norton aside from the SP2 Win
>>> Firewall I'm running now since I can't run NIS's firewall. As you know
>>> getting Norton anything in or out can at times be a problem and I've
>>> overcome all of them including Manual uninstalls and reaching for the
>>> Windows Installer Cleanup Utility when necessary. Also I don't want to
>>> forget to tell you that while Norton System Works (2003) was manually
>>> and
>>> completely uninstalled (when it wouldn't go quietly via Add/Remove) is
>>> still listed on the exceptions tab of the SP2 Win Firewall, and Norton
>>> Ghost which I had in but uninstalled at the request of Norton to try to
>>> make NIS work is listed there, NIS is not. I doubt but don't know for
>>> sure if its not showing up on the Exceptions tab matters.
>>>
>>> Thanks much,
>>>
>>>> What version of NIS? Was another Norton product ever installed and if
>>>> so what was it and what version?
>>>>
>>>> Was another anti-virus application or firewall ever installed & ditto?
>>>> --
>>>>> The message did read ole32.dll as I pasted from EV so thanks for that
>>>>> distinction because I wasn't making it. I was able to read a lot of
>>>>> MSDNese I couldn't appreciate on different sites. I am fully up on
>>>>> Win Up. I did recently install the WSH 5.6, (the other day) when I
>>>>> got script errors that were fixed by a KB here before I found it.
>>>>> The ole32.dll crashes predated that and followed it.
>>>>>
>>>>> (I ought to post the problem I have with script errors trying to fix
>>>>> NIS to browse the web here though and I probably will. Installing
>>>>> WSH 5.6 doesn't prevent script errors when I try to follow Norton KBs
>>>>> to scan the Norton firewall but another issue.) Norton's top tech
>>>>> support managers blame MSFT script host as broken, and MSFT blames
>>>>> Norton. What else is new there? If there is scripting to fix an
>>>>> actuallybroken newly installed WSH I need to learn because I have
>>>>> tried very hard to search out what I could do in that vein, since I
>>>>> don't know how to script. Thanks much for your post and your many
>>>>> helpful ones all over the
>>>>> groups so many of us have continued to learn from--and the great
>>>>> links. Maybe regegistering the correct .dll will help. I try to
>>>>> frequently spyware scan with 3--MSFT AS, Adaware, and Spybot but
>>>>> given the literature's figures on misses with any that could sure be
>>>>> an Achilles heel.
>>>>>> What were/are you doing when you get this error?
>>>>>>
>>>>>> 1. First try (re)installing 5.6 Scripting Engine
>>>>>> http://msdn.microsoft.com/library/default.asp?url=/downloads/list/webdev.asp
>>>>>>
>>>>>>> Faulting application iexplore.exe, version 6.0.2900.2180,
>>>>>>> faulting
>>>>>>> module *ole32.dll*, version 5.1.2600.2595, fault address
>>>>>>> 0x0008e1d7...
>>>>>>> I reregistered it fwiw with a REGSRV32 Oleaut32.dll command in
>>>>>>> the
>>>>>>> run box.
>>>>>>
>>>>>> 2. OLEAUT32.DLL and OLE32.DLL are two different files, Chad. Try
>>>>>> instead: Start > Run > (type in) regsvr32 ole32.dll > OK
>>>>>>
>>>>>> 3. Are you fully up-to-date at Windows Update?
>>>>>>
>>>>>> 4. Checking for/Help with Hijackware
>>>>>> http://aumha.org/a/parasite.htm
>>>>>> http://aumha.org/a/quickfix.htm
>>>>>> http://aumha.net/viewtopic.php?t=5878
>>>>>> http://mvps.org/winhelp2002/unwanted.htm
>>>>>> http://inetexplorer.mvps.org/data/prevention.htm
>>>>>> http://inetexplorer.mvps.org/data/tshoot.htm
>>>>>> http://www.mvps.org/sramesh2k/Malware_Defence.htm
>>>>>> http://defendingyourmachine.blogspot.com/
>>>>>> --
>>>>>> Chad Harris wrote:
>>>>>>> I'm on an XP SP2 box regularly SFC'd Perf Disk Defragged, Spyware
>>>>>>> scanned,
>>>>>>> and fully updates with what MSFT offers.
>>>>>>>
>>>>>>> Recently IE has been closed with an Oleaut 32.dll error that
>>>>>>> shows up in Event Viewer and on the deaktop with this error. I
>>>>>>> often can prevent IE from crashing by opening new instances of
>>>>>>> iexplore.exe or the shell explorer.exe but not with this. It
>>>>>>> closes all my browser windows. Description:
>>>>>>> Faulting application iexplore.exe, version 6.0.2900.2180,
>>>>>>> faulting
>>>>>>> module ole32.dll, version 5.1.2600.2595, fault address
>>>>>>> 0x0008e1d7.
>>>>>>>
>>>>>>> I have searched and read what's on MSFT's site and in the MSKBs
>>>>>>> on
>>>>>>> Oleaut32.dll and not found anything to prevent this including
>>>>>>> running SFC successfully.
>>>>>>>
>>>>>>> I reregistered it fwiw with a REGSRV32 Oleaut32.dll command in
>>>>>>> the
>>>>>>> run box. The IE repair tool is for IE5X offered in the MSKBs; I
>>>>>>> would have thought the fix would have been in XPRTM, SP1 or SP2.
>>>>>>> http://support.microsoft.com/?kbid=194177
>>>>>>>
>>>>>>> I also saw this fix and wonder if anyone has experience with it:
>>>>>>>
>>>>>>> http://64.233.161.104/search?q=cache:24je69fZZrQJ:www.5starsupport.com/faq/ie.htm+oleaut32.dll+MSKB&hl=en&start=8
>>>>>>> Of course MSFT hasn't found a way to link up useufl information
>>>>>>> with the error, and although they talk about improving this at
>>>>>>> Redmond and at meetings all the time, I don't expect real time
>>>>>>> error help that works to see daylight until Blackcomb rears it's
>>>>>>> head--certainly not in Longhorn. Does anyone have any practical
>>>>>>> fixes, downloads, ect to prevent this
>>>>>>> annoying IE crash.