Straight from the Horses Mouth

[DVD+R]

Today I called ESET and asked a few questions about ESS. What I was told will astound you :o

This program has been released without rigourous testing, and the Advice straight from ESET themselves was to remove it as there are far too many issues at the moment, and wait until at least February or even March Next year before even looking at it again...

Its entirely up to you, but I for one will certainly be removing it, even though I havent experienced and irregularites untill everythings smoothed out.

DVD+R

[zapjb]

Really strange.

[AKAJohnDoe]

Generally, I eschew anything that might emit from any orifice of any equine.

[DVD+R]

-{ Quote: "Generally, I eschew anything that might emit from any orifice of any equine." }-

Generally Just its rear end huh John :dry: with bucket and Spade in Hand :shifty:

[lych]

Somehow, I doubt Eset would sell a product and inform their customers not to use it. Who did you talk to on the phone about this? Eset directly or a reseller (if so, which one)?

[DVD+R]

-{ Quote: "Somehow, I doubt Eset would sell a product and inform their customers not to use it. Who did you talk to on the phone about this? Eset directly or a reseller (if so, which one)?" }-


I could tell you, but then I would have to kill you :dry: Maybe it was Santa Clause :shifty:

[DavidCo]

Sounds like a disgruntled reseller, an Eset employee would have his/her head on the block for a quote like that.
:ouch:

[MarkJamesNodUK]

As the Senior Technician here at ESET UK, I would be very interested in who you have spoken too, perhaps you could send me a private message or leave me a phone number and I can contact you direct.

Many thanks in advance
Mark James

[trjam]

-{ Quote: "As the Senior Technician here at ESET UK, I would be very interested in who you have spoken too, perhaps you could send me a private message or leave me a phone number and I can contact you direct.

Many thanks in advance
Mark James" }-
Hmm, yes lets tell him so someone can be fired for being honest. What a world we live in.

[DavidCo]

Or a disgruntled employee.

[trjam]

true, but you can also look at this 2 ways to. If it was me, I would have thought that hey, the guy is being honest and I actually appreciate that. Yeah some kinks to work out but at least he told me what was best. 2.7 is a proven winner, no one here can dispute that. So I take his advice, stick with Eset, continue to use 2.7 until I get the "word". So it isnt always a bad thing, being "honest" .

[Edwin024]

I guess that Eset should give their 3.0 customers all an extra six months or so on their licenses...

[BlueZannetti]

Folks,

Without speaking to the details that DVD+R mentions, if a user is experiencing specific issues with either a new version release (NOD32 V3) or an upgraded product (ESS V3), the prudent recommendation would be to step back to the most recent stable version (NOD32 V2.7) until the specific problems were fully sorted out. Naturally, this would involve removing the current version.

With respect to a general statement such as "remove it as there are far too many issues at the moment, and wait until at least February or even March Next year before even looking at it again...", I just don't see that as being necessarily appropriate advice to anyone regarding any product in the absence of specific and articulated issues, while that same advice could be quite prudent under other circumstances. There seems to be some context missing here, and it's not necessarily on DVD+R's side, it could be from the person on the other end of the support line.

Blue

[Big Apple]

-{ Quote: "Today I called ESET and asked a few questions about ESS. What I was told will astound you :o

This program has been released without rigourous testing, and the Advice straight from ESET themselves was to remove it as there are far too many issues at the moment, and wait until at least February or even March Next year before even looking at it again...

Its entirely up to you, but I for one will certainly be removing it, even though I havent experienced and irregularites untill everythings smoothed out.

DVD+R" }-

I really don't believe this at all!

[BlueZannetti]

-{ Quote: "I really don't believe this at all!" }-If this were written communication, the TOS would prevent disclosure unless both parties agreed, but since this was a verbal communication, there's really no way to validate the conversation.

In those cases, I generally take what was relayed as an accurate statement of the message received. It may not have been what the other party meant to convey, but let's assume that it is, in fact, the gist of the message received and go from there. It's either decent advice, decent advice with some caveats, or generally bad advice. In this case, I'd go with the middle option. There are some circumstances in which quickly implementing the initial field release of version X.0 of anything is not the best course of action.

Blue

[ASpace]

-{ Quote: "quickly implementing the initial field release of version X.0 of anything is not the best course of action" }-

And we can all agree that the very first public version of v2 hasn't been the best one . However , the latest one - 2.70.39 is really the one! Right? :thumb:

[lych]

It makes me wonder why someone who hasn't experienced any "irregularites" would call Eset's technical support ::). Desperate for friends maybe? Anyways, I find it best to not feed the trolls (even though I can't help it sometimes ;))

[stueycaster]

This is one thread I'm just going to ignore.

[agoretsky]

Hello,

Does ESET Smart Security have bugs? Certainly, just as any other piece of software which is sufficiently complex enough to do anything useful is going to have them.

Could it have been tested longer? The program could have been stayed in beta for perpetuity but that doesn't mean it would have been any better upon release. There is no question that the engineers always want to find one more thing to fix, add one more feature, et cetera. There is a specific time, though, at which you reach the point of diminishing return, where all you are left with are nonreproducible bug reports and enhancement requests that are of marginable benefit to anyone. And, as the saying goes, at some point you have to shoot the programmer and ship the code.

To state, though, that ESET Smart Security or ESET NOD32 Antivirus were released without going through rigourous testing is simply not true. The programs went through seven months of public beta testing and before that there was internal testing for a longer amount of time. During that period, hundreds of bugs and enhancement requests were logged in and addressed by the developers. This certainly does not mean that everything that could be fixed was fixed or that everything which could be added was added, there are always going to be things which cannot be addressed, but enough of them were that the programs were judged to be of sufficient quality to be released, and they were. The response from the public (customers, reviewers, et cetera) to the releases has been positive, and I consider ESET Smart Security and ESET NOD32 Antivirus v3 to be a success.

It may seem like there are problems with the programs from reading some of the messages in the product support forum, but, the thing that you have to remember is that this is a product support forum, after all! The number of people who are going to call into technical support and wait in a call queue or take the time to register an account on a forum simply to say that a program is working correctly and they don't have any problems with it is statistically very small.

One thing to keep in mind is that some of the biggest changes with ESET NOD32 Antivirus v3 (and ESET Smart Security, antispam and software-based firewalls are not new technologies to the industry, after all) are not to how the programs work but how they look and where you go to look at information in them. A lot of people, employees included, who have been used to doing things one way and one way only have had to relearn how to do those things anew with the v3 products and for some people that can cause anxiety and frustration.

What I suspect happened was that an otherwise very-competent-with-NOD3 v2.x support person who was frustrated by this chose to take it out on you, and for that I do have to apologize. I can assure you this is not the way the support personnel are supposed to communicate with a customer. Sometimes those of us who live life from beta to beta forget what it is like for those who do not, and it is clear more training is needed to make sure everybody is comfortable with the changes going on around them.

Regards,

Aryeh Goretsky

[DVD+R]

-{ Quote: "I really don't believe this at all!" }-

Dont Belive What exactly? That I Spoke to someone at ESET or that I'm going to remove it? Either way, nobody is forcing you to believe anything.

[DVD+R]

-{ Quote: "It makes me wonder why someone who hasn't experienced any "irregularites" would call Eset's technical support ::). Desperate for friends maybe? Anyways, I find it best to not feed the trolls (even though I can't help it sometimes ;))" }-

Its quite simple, because I've read all the Complaint posts, and decided to find out what all the fuss was about, and I found out :dry: Being that what I was told, I decided on a personal matter to remove the said offender untill such time as it can actually be clarified that the bugs and imperfections had been Ironed out. I havent as yet experienced such, but neither do I want to, therefore I removed it.......End.

[DVD+R]

-{ Quote: "This is one thread I'm just going to ignore." }-

Get out then Stuey, and go down the pub for a pint instead :P

[stueycaster]

-{ Quote: "Get out then Stuey, and go down the pub for a pint instead :P" }-
Not a bad idea DVD.:thumb:

[bseos]

-{ Quote: "Apart from any niggles about the products - functionality / GUI / bugs - fixed or not fixed, this is the thing that really niggles me about the way Eset have 'managed' this process. We've been here for months 'experimenting' with these Beta's, accepting the inevitable problems / crashes / inadequacies of 'pre-release' software, providing feedback...and Eset's responsiveness to that has been poor all the way through that process. It took someone at Beta Support around two weeks to respond at all to my last communication with them.

Even now, we're right on top of the final release, reading all the inevitable, 'carefully constructed' marketing hype on the Eset websites, and can they answer a simple question about the perceived 'gap' in the licence dates - No. Do they let us have a preview release as Beta testers - No. Reason - they are under too much pressure, they MUST release these products now for commercial / business reasons, whether the product is truly finished or not. They don't NEED any more feedback / moans at this stage - too late for that! That's my highly cynical take on it anyway - I have been in the industry a while, and I have seen the symptoms before.

So, as far as this forum and the Beta 'program' is concerned, make your mind up:

1) They never took this seriously anyway? Just thought they'd give it to a few people to play with 'in case anything useful' came out of it...?

2) They simply haven't got the time to worry about 'keeping us happy'...? - 'Business is Business'.

Visibly competing with the competition at this stage is crucial. Eset can no longer afford NOT to have a competitive, functional product, but they are inexperienced in that process and indeed, managing it. I hope for their sakes, that they haven't shot themselves in the foot...

Too late for me though, I've been a loyal NOD32 user for years - but no longer. Contrary to what many seem to believe, there are other products out there that are well designed, do not hog machine resource and provide excellent protection.

Take it easy... JeremyWW has left the building... :) " }-

That was a quoate taken over from the Beta forum right before ESET ESS was mad available to the public.

So, YES, this program was rushed, it was released without rigorous testing and with many bugs and issues identified in beta which were not resolved in the final release so to rush it out the door.

[bseos]

-{ Quote: "
What I suspect happened was that an otherwise very-competent-with-NOD3 v2.x support person who was frustrated by this chose to take it out on you, and for that I do have to apologize. I can assure you this is not the way the support personnel are supposed to communicate with a customer. Sometimes those of us who live life from beta to beta forget what it is like for those who do not, and it is clear more training is needed to make sure everybody is comfortable with the changes going on around them.

" }-

No!, what i suspect happened was a reputable support person giving his honest opinion on the product!
It is exactly how i would want support personnel to communicate with me, and not just feed me the garbage the company tells them to.

[ASpace]

-{ Quote: "No!, what i suspect happened was a reputable support person giving his honest opinion on the product!
It is exactly how i would want support personnel to communicate with me, and not just feed me the garbage the company tells them to." }-


Oh , dear , it seems you don't understand business practises . What would happen if all Symantec employees were honest - I guess Symantec wouldn't be number 1 in sales then :P

[poutine]

-{ Quote: "The programs went through seven months of public beta testing and before that there was internal testing for a longer amount of time. During that period, hundreds of bugs and enhancement requests were logged in and addressed by the developers. This certainly does not mean that everything that could be fixed was fixed or that everything which could be added was added, there are always going to be things which cannot be addressed, but enough of them were that the programs were judged to be of sufficient quality to be released, and they were.

Regards,

Aryeh Goretsky" }-

I find it very hard to see how such glaringly obvious bugs were missed then, like Outlook Express quitting out on launch, i tried NOD 3 on 6 different setups all running XP Pro and all suffered from the dreaded "BING" bug on launch.
I even tried it on a cleanly just installed Test machine with no extras running and again it failed, later i discovered read reciepts couldnt be sent, and that account names in sent items were missing, what i'm saying here is, if i could find all this in less than a day, how come after all the rigorous testing eset put in, none of these (now admitted by eset) bugs didnt come to light. ? Doesnt make any sense to me.

[stueycaster]

-{ Quote: "Oh , dear , it seems you don't understand business practises . What would happen if all Symantec employees were honest - I guess Symantec wouldn't be number 1 in sales then :P" }-
Symantec is good at sucking up to Microshaft and all the big name computer makers.

Go here: http://www.techdirt.com/ and read up on what big business is up to. It's amazing how greed rules the world.

[stueycaster]

-{ Quote: "That was a quoate taken over from the Beta forum right before ESET ESS was mad available to the public.

So, YES, this program was rushed, it was released without rigorous testing and with many bugs and issues identified in beta which were not resolved in the final release so to rush it out the door." }-
That quote was nothing but one man's opinion.

[stueycaster]

-{ Quote: "Get out then Stuey, and go down the pub for a pint instead :P" }-
Sorry DVD buddy.:ouch: I thought I could stay out of it but I can't.

[larryb52]

-{ Quote: "Today I called ESET and asked a few questions about ESS. What I was told will astound you :o

This program has been released without rigourous testing, and the Advice straight from ESET themselves was to remove it as there are far too many issues at the moment, and wait until at least February or even March Next year before even looking at it again...

Its entirely up to you, but I for one will certainly be removing it, even though I havent experienced and irregularites untill everythings smoothed out.

DVD+R" }-

I'm sorry I seriously doubt that there's any credibility to that story, seems a bit of a stretch...

[nodyforever]

-{ Quote: "Today I called ESET and asked a few questions about ESS. What I was told will astound you :o

This program has been released without rigourous testing, and the Advice straight from ESET themselves was to remove it as there are far too many issues at the moment, and wait until at least February or even March Next year before even looking at it again...

Its entirely up to you, but I for one will certainly be removing it, even though I havent experienced and irregularites untill everythings smoothed out.

DVD+R" }-




Update information:

-{ Quote: "There should be a new version before Christmas if all goes well." }-

[ASpace]

-{ Quote: "Update information:" }-

-{ Quote: "There should be a new version before Christmas if all goes well." }-


Ho - Ho - Ho !!! Merry Christmas ! ;D :thumb:

[nameless]

-{ Quote: "Today I called ESET and asked a few questions about ESS. What I was told will astound you[.] This program has been released without rigourous testing[.]" }-
That isn't astounding at all. Based on my brief* experience with ESS RC1, I couldn't believe they were even considering it a release candidate. And some of the issues I mentioned were totally ignored.

* Brief, because I didn't need much time to determine that the software was too buggy to continue using.

[poutine]

-{ Quote: "That isn't astounding at all. Based on my brief* experience with ESS RC1, I couldn't believe they were even considering it a release candidate. And some of the issues I mentioned were totally ignored.

* Brief, because I didn't need much time to determine that the software was too buggy to continue using." }-

you were lucky !! the finished one was far far worse than the RC1. ;D