ESET Smart Security v3.0.669.0 released

Program updates that have been released so far contain only fixes to problems that have been reported. If you have not run into an issue while using ESS, you needn't update to the latest version manually and it's enough to wait for an automatic program update (PCU).

 

Yes, it is this thread that I am concerned with.

It is now clear to me how ESET operates.

The current public release for new clients is 669 and may cause some of the problems that are being reported on other threads of this forum.

ESET will at some time in the future notify old clients on old versions that a new version is released. I haven't seen one for some time.

In the meantime, it may be best to not upgrade/update if things are working OK now.

Based on the above, I still tend to view 669 as a sort of BETA and still don't see how this benefits new clients. My company never did things like this!

Except for the above situation, I am and continue to be very pleased with the software [650 at least]. However, I still am not certain that I am comfortable recommending new clients use 669 or any other newer version until and unless it is RELEASED TO ALL OLD CLIENTS VIA THE OFFICIAL MASS UPGRADE NOTIFICATION MEANS.

If I am off base here, please advise. I am not angry, just pointing out what I would view as a possible public relations problem that should be addresssed.

Thanks - cheers - Jim

 

Hello,

One ESET SysInspector has finished loading, try selecting File → Save Log from the main menu bar, or pressing Ctrl+S after the program has finished creating a log. You should then be prompted to save a log file.

Regards,

Aryeh Goretsky

 

how do I download latest update. I am licensed user but the username and password for my last purchase do not work in the download page

 

Hello,

As previously stated, ESET does not want to release a program component upgrade until the company is certain there are no problems reported with an installer, because, despite all the rigorous checking which goes on, there is always an "x-factor" of uncertainty. Today's Windows-based personal computers are incredibly complex and incredibly diverse and it is not always possible to verify that 100% of all software, all hardware and all configurations are going to work. Also, customers are not necessarily going to contact a company when something does work flawlessly. I do not think anyone has ever contacted technical support simply to report that the software installed properly, is operating flawlessly, provided an inventory of the system with hardware and software manifests, an ESET SysInspector log, et cetera. People normally contact technical support to ask for assistance and not to say, "Everything's working fine. No problems here."

Let's take another example: Microsoft. Microsoft releases service packs periodically for its operating systems and applications, but it does not push them out to users all at once. Typically it is available as a standalone download, then on the Windows Update or Microsoft Update and finally made available via Automatic Update. Also, service packs are not released in every language at once, they are rolled out in groups of languages. This is for the same reasons. You test as much as you can, verify as much functionality as you can, but eventually you run out of tests to run and functionality to verify. At that point, you slowly start releasing the product in phases, sit back and wait to see what happens. Very simply, with cutting out some iterative processes (having builds fail internal testing and so forth), you end with a kind of state machine model that looks some thing like this:

Code:

ASSESS → CODE 
 ↑         |
RELEASE    |
 ↑         ↓
VERIFY ← TEST 

I feel like I should apologize for not making a better figure. I am not graphically-talented and the forum software is somewhat lacking for this sort of thing.

Now, consider what would happen if this were not the case, and the company was operating with a model of just CODE and RELEASE. Each new release of software was pushed out to users without testing. You would probably see many dissatisfied users, followed by no users shortly thereafter.

Security software has several criteria which, while not unique, are rather demanding:

1. The software needs to be compatible with as many operating environments as possible.
2. The software needs to interface with at a lower level than most other types of programs do with the operating system.
3. The software needs to be as error-free as possible, because a failure could mean not just loss of data, but loss of the operating environment as well.

It might be more helpful to think of the program component upgrade not as deploying a new build of software, but as a service pack for it. Like a Service Pack, it is released far less often than patches or hotfixes are for an operating system, and intended to improvements to performance, reliability and stability and maybe some small functionality changes as well.

Regards,

Aryeh Goretsky

 

I'm having problems accessing my email accounts in both gmail and hotmail, websites like friendster, Flickr.com and multiply.com since my installation of eset smart security. I have gone thru the filtering modes but nothing seems to work. Can anyone pls assist me.

Thanks.

 

I don't know if this really has to much to do with this thread, but how do I find out when a new version of ESS comes out, so I can replace the older version?

 

I have gmail and myspace, christian.com and several others and I am running the recent version of ESET Smart Security. I get on just fine, could be something else. Hope this helps