NoT satisfied with the Performance fuction

Rating to the feature of Norton 2010: Performance Fuction: 5/10

 

Why:

Reason no:1

 

Wrong information given when installing

 

Reason no:2

 

Another Bug:

Every hour,it DOES deleting of CPU/memory usage

Even if I surf now for more than 1 hour, every 1 hour NAV deletes the information about the cpu usage.

 

Look at that:

 

funbeta.jpg

 

<<Edit: Image resized for better fit>>

 

 

 

Message Edited by JerryM on 09-27-2009 09:48 AM

what do you mean wrong information given when installing? some apps install some additional stuff that you are not even aware off - that might be why when you install 1 app it shows you installed e.g. 3. I, yesterday installed the new Itunes - thinking ok - 1 app - and yet it came with 4 other smaller apps - I only noticed it when I looked at the performance…

Look at my thread on information is wrong.

can't find your other thread - can you post a link?

 

nvm found it - nice sig btw :smileyvery-happy:

Message Edited by cinek on 09-27-2009 11:57 AM

Ok.

Here it is:

 

Please Click here

 

 

 

 

Now my rating is 6/10

LOL @ some of ur posts

 

no offence m8 but if you're going to post something, tell us why - else it doesn't make any sence - maybe you're just trying to get your post count up??

Posts kinda remind me of a '75 Jack Nicholson movie


cinek wrote:

LOL @ some of ur posts

 

no offence m8 but if you're going to post something, tell us why - else it doesn't make any sence - maybe you're just trying to get your post count up

 

 

_________________________________________

 

 

No. Trying to help me to this BUG!

 

__________________________________________

 

 

 

 


funbeta wrote:
Now my rating is 6/10

 

What is this rating that you are referring to?

About the functionality of the  Performance feature.

and what has changed your mind? before it was 5/10 now it;s 6/10. As far as I know there was no patch released for this and the latest version is *.136 so nothing has changed since your last post …

The no.2 bug was resolved.