Will the Eset be going to compensate for his users?

All of we know that the version RC1 was much better than the version 3.0.xxx while a few they did not suffer any injury others suffered a true war.


1 - How there is possible a version RC1 to be better than the version 3.0.xxx " final "?


2 - Are it how what an enterprise of high level of products let become careless and to show us a version worse than his RC1?


3 - It be what the Eset hurled itself?


4 - Will it be that it should of is a RC2 or up to a RC3 until everything to be a worthy version of personal and business use?


5 - How it will be able to be possible the internal tests of the Eset they say that they continue at the front of the competition? Will they have any special version?


6 - Some persons indicate that the resource consumption of his pc increased in comparison with the version 2.7. The one that owes to herself this increase? Will it be of an optimized badly compiled?


7 - Today we had not any official piece of news of because and of the reason of this disaster of his version launched to 5 of November. What the reason will be?


8 - Knowing which some enterprises they always pass over a bad face in his life the Eset does it give guarantees that all the moderate mistakes will be answered?



9 - When we will have a worthy version to use will we be warned?


10 - If we go by a new GUI appearance to the Eset what she would find of that?


11 - Will it be still that the Eset manages to surprise us it shears that it makes positive?


12 - What I provide the Eset with a bridge is it disposed compensating for the users of this hasty version?


13 - In the site of the Eset.com.au be written the next sentence: "The with any new program, these first release versions may not be 100 % bug-free!" would it be necessary the things had been done as they should have been done?



You ask someone which some users would like doing before the Eset.

I apologise if my English will not be understandable

 

If you have problems with Version 3, you can use version 2.7.

 

Easy answer, but not the right solution in this stage. Version 3.0 is released and has problems, so this should be fixed very quickly. Only if protection is really failing badly, you should return to 2.7

 

They are working on fixing any outstanding issues. Perhaps for the next Beta product, users won't ask , Is it ready? Is it ready? Is it ready? every five minutes.

 

That's not the point. The point is that the product was of inferior and possibly not saleable / merchantable quality. That itself is grounds for litigation. The product did not perform as advertised, it has / had flaws which interfere with the operation of a computer. I hope the next release build contains a lot of fixes and somewhat improves on the image of ESET and it's latest product.

 

what a lame answer

 

Right about asking every 5 minutes, it's no good, but releasing this new Nod32 is worse!

 

Do you have a better one? Look, I'm not a rep for Eset. They are working on fixing outstanding issues. What else can be said?

 

ESET's released product is now on many thousands of production machines, many of which have been operating erratically since the new release. So who can blame people who paid perfectly good money and got less than they expected and now expect a fix asap.

Lesson for ESET. If it isn't ready. Don't ship it.

 

Bet you're not using Nod32?

 

I second that completely!

 

No hell no. Not ATM.

But I'm pissed that I spent a lot of money on a product and I can't use it.

 

I meant this question for Thankful, sorry!

 

I am using the AV version and have had few problems.

 

Cheers.

I think we should expect to see an official word from Mr Ayreh Goretsky.

 

you're one of the few, maybe.

 

Many people are running the new version without incident. However, I understand that provides little relief to those who aren't.

 

so who and where are the "many people running it without incident" ??

 

Correct thought, I agree with your point of view.

There is a dictation what he says: "The one who does not know does not move, the one who spoils has to arrange and the one who never moved ever will come knowing what it would happen if it was moving".

 

Me.

 

Well aside from multiple tag lines in Outlook I have no problems at all

 

But for a final and stable version was not it in order that they all were enjoying what the Eset always lived in us?

All that is done is a product of this wingspan in order that they use all and not only for someone.

I use it nod32 from of the version 2.5 and there was never a 'sloppiness' of this dimension directed by the Eset

 

Same here. Been playing with ESS since beta 1, and though there were various annoying niggles about how the program worked and the same old qualm with the detection rates, nope, no incident whatsoever.

 

Got to love this disclaimer from ESET.com.au

http://www.eset.com.au/download/download.html

 

For some this version works for others it won't. I’m one of them. It's a complex problem, because every system is different. If you take a look at all of the new topics in this section, there are many more problems.