Ok, I think I've discovered the problem.
I sent this through the Symantec support site, will be interesting what they come back with.
Money hopefully for me doing their work for them - yeah and monkeys might fly out of my butt.
I happened to notice just recently that script blocking was no longer working.
I posted to a couple of techncial forums but also decided to look here at Symantec.
After reading through the many posts, I followed the articles titled:-
How to disable Script Blocking manually &
How to uninstall Norton AntiVirus 2001 manually when installed under Windows 95/98/Me.
Firstly, on my system, the following keys identified under point 8 of the first article had a second key ScriptBlockingInProcServer32 with a different value to default, deleting the default caused vbscripts to produce an error box.
HKEY_CLASSES_ROOT\CLSID\{06290BD5-48AA-11D2-8432-006008C3FBFC}
HKEY_CLASSES_ROOT\CLSID\{06A7EC63-4E21-11D0-A112-00A0C90543AA}
HKEY_CLASSES_ROOT\CLSID\{0D43FE01-F093-11CF-8940-00A0C9054228}
HKEY_CLASSES_ROOT\CLSID\{F935DC22-1CF0-11D0-ADB9-00C04FD58A0B}
After copying the second key value to the default vbscripts worked again.
After following the articles, I reinstalled NAV 2001 and began the process of LiveUpdate to download all the updates.
Basically I left the Virus defs till last.
Slowly but surely over my 56K dial up I installed updates, to NAV, Live Update, Rescue Disk and Script Blocking got installed and worked !
I kept on with Live Update always leaving the virus defs until the only thing left was the virus defs.
At this point Script Blocking was still working.
I downloaded the virus defs and POW Script Blocking no longer worked.
Today I followed the two articles again to remove NAV from my system.
I searched the hard drive for any other *Nort* or *Symant* files and found a cople of other folders that I also deleted.
I reinstalled NAV and this time before doing the final download of virus defs, I exported the registry and made copies of all the Norton and Symantec related folders.
I downloaded the virus defs and exported the registry to another named reg file.
I tediously went through the two reg files comparing keys and values and then began doing the same for all the folders and files that I had made copies of.
I came across a file in C:\Program Files\Common Files\Symantec Shared\VirusDefs\20011206.019 called SCRAUTH.DAT and decided on a whim to rename it to SCRAUTH.DAT.BAK.
I tried a vbscript and presto was presented with the Alert screen.
So, basically what is SCRAUTH.DAT as it is obviously the cause of the problem and now that I have pin pointed it down to this file maybe you can stop telling people you are unable to recreate it and fix it for good.
