Newer beta ready - 2.50.9

What's the news in this new beta version

 

Just a minor issue in AMON fixed. There's almost no chance a common user could come across it before. Also some suggestions from the forum have been implemented (e.g. the on-demand scanner alert window should now appear in the foreground).

 

ok, nice work

 

I was offered the upgrade on my W98SE system while checking for an update.
Downloading and installation was going very smooth, then a reboot was required, and all is well !

===
Information about installed components
NOD32 For Windows 95/98/ME - Base
Version: 2.50.9 Beta
NOD32 for Windows 95/98/ME - Standard component
Version: 2.50.9 Beta
NOD32 For Windows 95/98/ME - Internet support
Version: 2.50.9 Beta
===

Thanks ESET !
Cheers, Jan.

 

I currently use KAV which is considered to be the best at cleaning infections (ie. disinfection instead of just delete).

How good is NOD32 at cleaning infections and has this been improved with the latest beta ?

 

heh.. Nod32 has turned against me..

Now when i tried to install new version 2.50.9 i get this error (see picture)

 

I currently use KAV which is considered to be the best at cleaning infections (ie. disinfection instead of just delete).

Cleaning trojans instead of deleting? ;-)

 

Got it!! And what can I say Still the Greatest!!

 

Hi Marcos,
Thanks for the info !

May I add a few questions (maybe you would like to talk in private about it) ?

First to let you know: I am on Windows 98 SE.


1.
Was a clean installation the appropriate way, or was the way I did it also right: I got the new upgrade offered while checking for updates and I went straight ahead by allowing it.

2.
Was there a difference between W98 and XP ?

3.
I checked with two file integrity checkers:
- NIS File Check, checking several thousands of files.
- ADinf32 Pro, checking every file.

Well, except for:
- HASH checksums changed,
- the obvious file versions changed,
- the usually file changes,
I did notice that the only change in file-size, was for:
C:\Program Files\Eset\Setup\uninst.xml
I know, I did not check for registry changes
But I was a little bit wondering that only that file uninst.xml was changed in file-size, where you wrote:

I am well aware that I might not understand things very well, and/or that I am making some mistake.


Thanks !!!
Keep up the good work !
Cheers, Jan.

 

I just downloaded the new beta, installed it over my present Nod32. Went smooth, asked me if I wanted to keep blackspears settings.

 

Removed KAV Personal 5.xx for this beta. It's running well and looking good. Eset needs to go into high competition mode. Let the great unwashed know how good this program is and will be!

 

Darn....I must not have the bestest or newest Nod...it never asked me about
Blackspears settings....just asked me if I wanted my old settings.

He he he

 

OK, my knowledge is weak in this area, so this may be really simple-minded, but... These days, what's the real difference between "deleting" and "disinfecting"?

When I think of "disinfecting", I imagine old-time EXE infectors, which I'm sure are still around (maybe?), but... Isn't modern malware mostly a matter of deleting infected files and the associated registry crap?

Maybe if I ever actually came across malware, I'd better know what I was talking about. (I've never had to clean anything up... <sniff sniff>)

 

Disinfection depends on what the malware does obviously. Some worms for instance create their own SMTP or POP engine in order to email themselves out in a mass mailing effort, some just use whatever email program is available on the compromised machine. MOST trojans simply use an executable to contact their server and do as the creator designed it do, some however do create their own network protocols and use those, it is these that would need to be disinfected as the registry entries created need to be deleted, protocols that were created need to be removed and the system returned to it's pre-infected state. Yes most trojans can simply have their executable deleted and that is the end of the story. However, there are some nasties out there that truly need a disinfection type removal.

 

Sounds like those worms create stuff that needs to be deleted to me.

There's that word... deleted.

By removed... You mean deleted?

Obviously, the terms overlap... Basically, "disinfecting" means "selectively deleting the crap". Just making sure I wasn't missing anything. OK, I've learned nothing new here.

 

Some nasties will infect valid system files or registry keys. If you just delete these files/keys, then some aspect of your system might be left unusable. It's these types of infections that need the nasty code removed and replaced by the nice code/settings. This is true "cleaning", and what I'm on talking about.

 

Hi, Defenestration

Sound like a system file check to me, anyone with their OSCD can do that.

Take Care,
TheQuest

 

With all due respect to everyone (!!!!!) :

This thread was about the new NOD32 version 2.50.9 Beta.

I know, I am on my "soap-box", but could we please stay on topic here

Thanks, Jan.

 

Hi, FanJ

No disrespect to you my Friend Jan, But I think the posts you are probably referring to are in answer to about the Beta.

Take Care,
TheQuest

 

Hello to all
and BIG thanks to all
2.50.9 Grrrrrrrrrrrrrrrrrreat
one thing though
Have noticed Windows shutdown time has increased

 

Hi

Just installed this on top of a previous version, just a quick question - the link at the start of this thread take you to the Beta download page, where new features are listed. One being XMON. I don't have XMON listed in the Control Centre, is this OK?

 

It sure is, XMON is exchangeMonitor.

Cheers

 

Cheers B for the very quick response BTW, Beta is running very very nice

 

Hi, may I know what does XMON actually do? Thanks in advance.