Nortons Personal Firewall 2005 - Install probs

[Grey]

WinXpPro Sp1
Anyone know how to install this piece of rubbish? I can't.

I'm getting this worthless and meaningless (5001,354) error message. Which
when I manage to stop it, I get a Configuration Failure when I attempt to
run it.

Here's the story...
Originally, I had Norton's Antivirus 2003 with latest definitions installed.
Removed that, and all directories. Run, but not installed SystemWorks, to
clean the registry.
Turned off XP firewall setting.
Attempt to install NPF2005 and get (5001,354)'ed half way through.
Download Symantec's knowledge base instructions.
Attempt to delete registry key entries - don't exist.
Empty out the %temp% directory.
Restart Windoze with System Services and original Boot.ini settings as in
msconfig.
Attempt to install NPF2005 and get (5001,354)'ed half way through.
Go into HKEY_LOCAL_MACHINE\Software\Symantec and delete all keys.
Uninstall, reboot
Attempt to install NPF2005...and completed without errors.
Reset Msconfig and reboot to normal settings.
NPF tried to run the setup wizard-type thing and "Config failure
(5001,354)".
Pull out hair.
Look for any NPF patches - none at this time.

Anyone else had this type of grief?
Anyone got any ideas?

Graham

 

[R. McCarty]

I could try and give you the convoluted steps to fit the "Square
Peg in a Round Hole", but even with it working your system is
going to experience a performance hit.
Return the product for full refund, get either Zone Alarm Free
of Sygate Personal firewall ( also Free).
To properly clean up after Symantec is almost a 6-Pack type of
job and certainly time intensive. Best to image your machine, as
untangling Symantec/Norton can result in some serious Registry
issue(s).

 

[Juan C. Reyes]

Graham,

The 2005 products are major resource hogs. I had my own problems with this
product and ended up reformatting to completely remove it. Go with another
company. Check out alt.comp.anti-virus for suggestions on free and
fee-based versions. There are some good ones out there that won't cause you
these kinds of problems.

Good luck.

Juan
| WinXpPro Sp1
| Anyone know how to install this piece of rubbish? I can't.
|
| I'm getting this worthless and meaningless (5001,354) error message. Which
| when I manage to stop it, I get a Configuration Failure when I attempt to
| run it.
|
| Here's the story...
| Originally, I had Norton's Antivirus 2003 with latest definitions
installed.
| Removed that, and all directories. Run, but not installed SystemWorks, to
| clean the registry.
| Turned off XP firewall setting.
| Attempt to install NPF2005 and get (5001,354)'ed half way through.
| Download Symantec's knowledge base instructions.
| Attempt to delete registry key entries - don't exist.
| Empty out the %temp% directory.
| Restart Windoze with System Services and original Boot.ini settings as in
| msconfig.
| Attempt to install NPF2005 and get (5001,354)'ed half way through.
| Go into HKEY_LOCAL_MACHINE\Software\Symantec and delete all keys.
| Uninstall, reboot
| Attempt to install NPF2005...and completed without errors.
| Reset Msconfig and reboot to normal settings.
| NPF tried to run the setup wizard-type thing and "Config failure
| (5001,354)".
| Pull out hair.
| Look for any NPF patches - none at this time.
|
| Anyone else had this type of grief?
| Anyone got any ideas?
|
| Graham
|
|

 

[Guest]

When you removed the old Symantec/Norton directories, did you also check to
make sure that you removed hidden directories? If not, do a search for all
folders named "Symantec" or "Norton" and make sure that the option to search
hidden files and folders is enabled.

In any event, it is a real bear to remove Symantec products from an XP
system. My routine (yes, I have done it many times) is to run the uninstall
program, then remove the hidden folders (they do exist, and you aren't going
to find them unless you are specifically looking for them), then run
regedit.exe and remove all references to Symantec and Norton from the
registry. Then reboot the computer. Even after all this, I cannot
guarantee that your system is going to be as good as it was before you added
Symantec in the first place.

 

[Guest]

I have enough problems with Norton products at work. I've seen too many
people with Norton get viruses that cannot be removed. Other issues are
performance hits and conflicts with other programs. As R. McCarthy said,
wipe the drive and start over. The free firewall programs he mentioned do
work but they have issues.

At home, I use McAfee VirusScan and McAfee Personal Firewall and have no
problems. Since using McAfee, viruses never infect my machine. Everything is
caught and stopped. Everything about it is good. It's easy to use. The 2005
version even has an antispyware feature.

 

[Guest]

I use the 2004 version. Not sure if 2005 has problems but I would buy McAfee
again.

 

[R. McCarty]

One more step, that helps. Along with your procedure it's a good idea
to open Device Manager, Click View - Check/Tic "Show Hidden
Devices". Expand the Non-Plug and Play category. If you check thru
the listing you'll likely find 6 to perhaps 8 "Orphaned" service entries
left by Symantec/Norton. Many are coded as Sym---. Just be sure
before nicking them to check the Driver details box to verify the vendor
as Symantec. The number and names vary depending on which product(s)
you had on your system.

 

[MyndPhlyp]

WinXpPro Sp1
Anyone know how to install this piece of rubbish? I can't.

I'm getting this worthless and meaningless (5001,354) error message. Which
when I manage to stop it, I get a Configuration Failure when I attempt to
run it.

Here's the story...
Originally, I had Norton's Antivirus 2003 with latest definitions installed.
Removed that, and all directories. Run, but not installed SystemWorks, to
clean the registry.
Turned off XP firewall setting.
Attempt to install NPF2005 and get (5001,354)'ed half way through.
Download Symantec's knowledge base instructions.
Attempt to delete registry key entries - don't exist.
Empty out the %temp% directory.
Restart Windoze with System Services and original Boot.ini settings as in
msconfig.
Attempt to install NPF2005 and get (5001,354)'ed half way through.
Go into HKEY_LOCAL_MACHINE\Software\Symantec and delete all keys.
Uninstall, reboot
Attempt to install NPF2005...and completed without errors.
Reset Msconfig and reboot to normal settings.
NPF tried to run the setup wizard-type thing and "Config failure
(5001,354)".
Pull out hair.
Look for any NPF patches - none at this time.

Anyone else had this type of grief?
Anyone got any ideas?

Uninstall. Manually nuke any leftovers. Download and install WinXP SP2.
Reinstall NPF, then SW both in normal mode. If you have non-administrative
users on the WinXP machine, be sure to go through each and every
configuration point in both NPF and SW (don't forget AV) before letting the
non-administrative types in.

Ran into this problem myself with a WinXP SP1 system. Major PITA and
Symantec's so-called KB didn't have anything. Through trial and error, and a
lot of futility, I discovered SP2 allowed the bundle to install.

 

[Guest]

I know Ken is going to give me some (or a lot) of grief about using a
"registry cleaner" but this is a type of problem that some of them are really
good at. Not all references to program remnants are searchable by the
original program's name ie. Norton, Symantec, etc. and manually trying to
find them is a nightmare. Most if not all of these programs rate what is safe
to remove and allow you to manually go through them if you're worried about
it.

 

[Guest]

I know Ken is going to give me some (or a lot) of grief about using a
"registry cleaner" but this is a type of problem that some of them are really
good at. Not all references to program remnants are searchable by the
original program's name ie. Norton, Symantec, etc. and manually trying to
find them is a nightmare. Most if not all of these programs rate what is safe
to remove and allow you to manually go through them if you're worried about
it.

Homer, I'll give you a pass on this one.

When it comes to Symantec, I suspect that the even bigger problem might be
orphaned .dll files in a Windows folder or subfolder, but I don't know for a
fact that they actually get left behind. I certainly am not going to trust a
"disk cleaner" to find these .dll files, either.

My usual solution to bad Symantec uninstalls is to clean-install Windows XP.
Drastic, I know, but effective. I have it down to a science -- two to
three hours tops to restore XP, updates, software, and data, but without all
the additional crud left behind by my relentless tinkering, experimenting, ad
nauseum (of which Symantec has often been part over the years).

Ken

 

[Guest]

Thanks Ken for the pass. If you do the tinkering I do (a lot) you should get
yourself an imaging prog. like ghost or drive image. The new ghost 9.0
doesn't allow you to make boot floppies (that I know of) so I stick with the
older versions (at least until MS changes file systems again). The same thing
about tinkering I also apply to viruses, spyware, trojans, keyloggers, etc.
Why waste a lot of time trying to find what some hacker or cracker has
installed on your OS and whether it's truly clean after a fix. If you have an
up to date image that you know is clean, use that.

 

[Guest]

I need to learn more about imaging programs, how they actually work, and
whether they are reliable. I used one years ago (in the Windows 9x days),
but for some reason it didn't work.

Having said that, the truth is that I am a relentless tinkerer, meaning that
often I want to do an XP clean install to clean up (no pun intended) a whole
multitude of things, rather than just one set of tweaks or one major
install/uninstall such as Symantec. I'm kinda getting close to that point
even as I type.

 

[Guest]

I used to use Drive Image a lot (because of the boot floppies) but since
PowerQuest was swallowed by Symantec (a pity) I reluctantly use Ghost 9.0
because it offers additional features such as incremental backup to image.
But I still keep a boot-flopy accessible image so I can load an image with
Ghost 9.0 already installed and then work from there. I have never, ever
experienced a problem with either of these two programs. I am trying out the
Acronis product (TrueImage) because it creates the boot floppies and have not
experienced any problems either. The reason I might have taken a
(very-slight) exception your opinion about registry cleaners was because I
knew that if I totally nuked the registry, I always had (multiple) images to
restore the OS.

 

[Grey]

One more step, that helps. Along with your procedure it's a good idea
to open Device Manager, Click View - Check/Tic "Show Hidden
Devices". Expand the Non-Plug and Play category. If you check thru
the listing you'll likely find 6 to perhaps 8 "Orphaned" service entries
left by Symantec/Norton. Many are coded as Sym---. Just be sure
before nicking them to check the Driver details box to verify the vendor
as Symantec. The number and names vary depending on which product(s)
you had on your system.

Aaagghhh! I have HAD it with this! In yet another failed attempt to install
it, I had decided not to install it as its not worth the bother. So I tried
to reinstall NAV03 back onto my system - guess what? More config errors.
Tried manually cleaning registry and dir's, still no joy.
So I have been forced to restore my entire C: drive from a backup I made
before I started this misadventure and I'm back where I started.

What is it with these Norton products? It seems they fail at a basic
fundamental level in being more complicated than they need to be whilst
sacrificing stuff like stability and basic installation issues. It seems
this stuff has a long line of bugs, but they seem reluctant - or lazy - to
offer patches or worthwhile data on their knowledge bases to help the
beleaguered user - who has to resort to disc formatting in order just to
remove them.

Graham

 

[R. McCarty]

I have a David Letterman style Top-10 List:

10. Using Norton sales to fund their move into the Enterprise
market - Eventually abandoning Home users.
9. Yearly renewal charges are too expensive - the additional
$10 fee to upgrade to Version 200x is like playing Russian
Roulette with a full chamber.
8. No Telephone support - without paying a $29.95 fee
7. Closed Customer Forums - No outlet for frustrated customers
to vent or communicate with each other
6. Can't Write code - But buys it instead (Veritas, PowerQuest)...
Quit acquiring & Start coding - Rewrite NAV from scratch.
5. Product line is too broad - Drop SystemWorks, instead
create a Disk Management package with Partition Magic &
Ghost 9.0
4. Stopped innovating - Just marginal yearly changes & new
ideas like Password Manager or AntiSpam that are of dubious
value.
3. Can't upgrade over their own previous version - Buy the
software and hire a Technician to help you get it running.
2. Product Activation is the root cause of these Registry issue(s),
uninstall remnants and orphaned services........

And the Number One reason that Symantec software is ____
(Pick your own favorite derogatory term)

1. Excessive System loading ( Way too many Services/Processes).
Buy Symantec/Norton - Get a free 256-Megabyte memory
upgrade to run it.

 

[Chris King]

I know that Norton can be a pain to remove and is more a pain when it goes
wrong.
I must have been one of the lucky ones, since I have used Norton Antivirus
2002, 2003 ,and now use 2004.
With the firewall I have only ever used up to 2002, since I have a router
with built in firewall, and never bought the follow ons. my Norton
Antivirus/Systemworks has never give me any problems, and I have over time
found some utils from Symantec themselves that remove old versions when they
cause issues.

I currently have the NAV remover here, which removes all registry
entries/traces of versions up to and including 2003, I think somewhere I
have the Firewall version remover, cant remember which version it runs up
to.
These are avail from Nortons site, if you dig deep enough, but if you want I
can email you them (I have to dig them out of a CD if you do). I continue to
use NAV 2004, and two of my friends are now using them, with no problems or
issues, but I do agree with older versions leaving stuff behind that cause
problems when moving to the new versions, as one of my friends had that
problem too, luckily one run of the program I mentioned above, and it was
all sorted!

I dont have any complaints on McAfee, Norton or any others, my firm have
moved between the two, and change about depending on the best deals they can
get with them directly.

Chris