**Warning** Norton AntiVirus 2004

[NoNoBadDog!]

Yes it does...I have four computers on my home network...3 towers and 1
laptop. I have Norton AV 2004 Pro on two, and Norton AV 2003 on two. I
have changed the pagefile size, set them, and rebooted and confirmed that
the changes indeed "stuck". I can do this on all 4 machines at home, and
the two machines I have access to at work that have NAV 2003 installed.

Upon reboot, the new pagefile size is still there. On the three towers, the
pagefile is set on the second HDD, and on the laptop, the pagefile is set to
the primary drive since it has only 1 HDD. The two machines at work only
have a local drive and mapped network drives, and of course the pagefiles
are on the local drive.

Bobby

 

[Alex Nichol]

I have verified within the registry, that every instance of pagefile size
reflects the new size (500 meg), yet the actual pagefile size (on the hard
disk) remains at 1.5 gig. Strange indeed!

Interesting. Other Norton software has interfered with the page file
setup - one well known cause of 'low virtual memory' at shutdown is down
to Live Update. It reinforces my view that I will not nowadays have any
Norton product within a mile.

 

[Dennis]

Does Automatic Update work for you in NAV 2003 ? It used to for me but
stopped
a few weeks ago. Now I have to manually start Live Update to get new
definitions.

 

[CZ]

Norton AntiVirus 2004 **DOES NOT** play well with your pagefile!

I have confirmed, on 7 different computers, that the program interferes with
changing settings of the page file. You can go into the options and choose a
new pagefile size, click the "set now" button and reboot. When the computer
boots up you will find that the pagefile is the "same" size as was
previously, yet the sizing utility indicates that the pagefile is the new
size.

I have checked, and verified, this action in many different ways. It is
repeatable on any computer when I, or others, have installed Norton
AntiVirus 2004 on their computer.

Have any others noticed this strange behavior?

Crusty:

I have it working correctly on a second computer.
Scenarios:
1) Dell C400 that it does not work on:
Win XP Pro, SP1, all MS web site updates.
C400 was used to purchased NAV 2004 and the dnload was done on this
computer.
C400 had NAV 2003 on it before the NAV upgrade; upgrade removed it.
Problems during install: Configuring dialog would not progress, so I
shutdown, uninstalled NAV 2004, rebooted, now Configuring dialog progressed
as it should.
Page file sizing problem existed before NAV activation and after activation.


2) Test computer that it does work on
Win XP Pro, SP1, no MS web site updates.
NAV 2004 dnload copied to this computer form C400, and installed as a 15 day
trial product.
Test unit had NAV 2003 on it before the NAV upgrade; upgrade remove it.
No problems with Configuring dialog progress.
No page file sizing problem (product is not activated)
I have change the file size several times, rebooted many times, and it still
works.

So, it does appear to be a compatibility problem.

BTW, I am using the NAV 2004 upgrade dnload purchased from Symantec.com (not
the full product, and not the Pro product).

Also, lurkers, I have no intention of removing any Symantec products from my
computers as several other posters have suggested. IMO, Symantec makes
excellent/powerful/useful products, and , yes, they do have problems.
Symantec will find the cause of the problem.

 

[Crusty \(-: Old B@stard :-\)]

My copy was downloaded from the Symantec store. Don't know if this means
anything at all.

I have further found out that the pagefile disappears off of my C: partition
upon, get this, every other boot - without fail!

 

[Gary Hegan]

Yes it worked in NAV 2003. It would not work in 2004 until I went to
Symantec support and they said to deleted the task in Scheduled Tasks and
reconfigure it which I did but you have to but a password because if you
don't the task will not run without it. I tried everything but I could not
get it to work without a password. My wife's works without a password. Try
opening Scheduled tasks and right click the Symantec NetDetect and select
run if it says it can't run because of a invalid user name or password then
you will know why it won't run. You will have to log into your computer with
the same password you setup in Scheduled Tasks.

 

[Dennis]

I clicked on run but there's no response. I've reconfigured the task in
Scheduled Tasks,
also adjusted the 'Express' settings in the LU window. Will see what
happens.. thnks.

 

[Gary Hegan]

Thanks I will give it a try.