(possible) bug reports v2.0 Beta1

IMON and NMS won't stay off! I removed the beta version and installed it again; nothing was changed. During the installation I selected custom install and specifically said "NO" to IMON and "NO" to "NMS." Both of them were on after I rebooted.

I don't want to use IMON and I don't need NMS.

 

Well, of course, I had another email virus today, and IMON screwed up my OUtlook Express, the same way I described a couple of posts ago...Outlook Express would close down down as soon as it hit a certain point.

Determined to find out what the virus is, the first thing I did was totally disable ZAPRO...
That way the ZAPRO mailsafe would not interfere...

Then I had to disable IMON...

Then I started Outlook Express again, and went to the Security Settings under Tools", and then I did an on demand full system scan. I checked the box that says "all emails" or watever it says..

Lo, and behold! I have a screenshot now.!!

It didn't come as any surprise that Klez was the virus! I have been getting hit by Klez almost 2-3 times a day lately... I could not clean it from NOD and I could not quarantee it.. I could not delete it from the on demand scan (I used the "Clean" button when I scanned. What gets to me is that it would not even quarantee it. Although I can't stand Norton, Norton can quarantee Klez from an email...

So, here is the screen shot, and a MAJOR BUG That ESET has on it's hands...

 

This post is an echo to Marti's above post.. Well, yeah, I'd like to use IMON and NMS, because I HAVE to have an email virus scanner! That's where most of my viruses arrive from.. However, I would like IMON to work. I know this is a beta. If IMON is not fixed to work well, and the virus disinfection is not at least improved, by public release time, I am going to have a big problem on my hands... The way the beta works, it reminds me of the way PC-Cillin worked, when I trialed it before I bought NOD back in May...

 

I don't want to use them and they keep coming back! You ( Straight Shooter) want them and they are not working correctly. Arrggg!

 

That's what I just did...

I feel I have contributed my input to the beta. I love the look, the way the menu's flow off each other (I don't think CNET will, but who cares!) and the very low impact on system resouces.. I also like the Configurability! The NMS and IMON are very good ideas, they just need to be worked on... and in the on demand menu, you can actually fill in a checkbox to scan for emails! That's cool! I just wished I either knew how to configure or maybe that is a bug too, the idea of automatic qaurantee of a virus from email.. But since I get Klez almost twice daily (isn't that ridiculous) I HAVE to switch back to classic NOD for now.. I am looking forward to the new version!

 

>Next problem is that nod32 Scanner list all existing JAR-Files on my System like this: CRC-checksum is incorrect, file possible damaged
I can´t believe this

I am seeing the EXACT same problem. All existing JAR-Files are reported as having incorrect CRC-checksum and possibly damaged. I find that hard to believe!
W98SE

Could we PLEASE have some way of grouping the bug reports? It's getting cumbersome to go through every page like I just did to find the report about this.

 

I again repeat my request: Rather than all possible bug reports for the Beta going to this one topic, why not start another forum Nod32v2beta along side the NOD32 forum? Then the bug reports could be grouped better under their specific topics and you wouldn't need to scroll through all the posts for help with your specific problem. The current NOD32 forum (where this topic is) would be for the currently released version and the new forum for the v2.0beta.

 

I am so impressed!! I just got to see IMON in all its glory. Someone sent me yaha.N (aka yaha.K which is currently infecting Hotmail) and I was d'l a file, at the time, when suddenly IMON pops this screen up saying that it had intercepted this infected email. It gave the details and had quarantined it. Now mind you, this email got NOWHERE NEAR my inbox! THAT IS SO GREAT. I deleted it. I LOVE IMON!

I was just thinking...what if this had been a false positive? Could I read it? It never reached my inbox...so how does that work?

 

If you press close button (bottom of dialog), you will see warning message and then, IMON deliver email to inbox in original form

 

Thanks igi for the explanation. That makes sense. Now I know what to do if I want the mail delivered anyway.

 

Hi all,

thanks for all your valuable feedback - we are processing your comments to the bug list and fixing them now. I posted more at:

http://www.wilderssecurity.com/showthread.php?t=5692

We keep you informed.

Once again thanks for helping us to make NOD better for YOU!

rgds,

jan

 

Works fine here under win2k, but i can't get it to work at all under 98SE
Creates problems with Naviscope, Spyblocker and my browser quits on me.
I have gif's posted at Becky's http://www.morelerbe.com/cgi-bin/ubb-cgi/ultimatebb.cgi?ubb=get_topic&f=14&t=001770&p=

 

Another idea for the beta - version 2

I've heard this from others, and frankly, I think it's a good idea to ..

add a progress meter or progress indicator for the on demand scanner...

Like you know, 13,333 files scanned, 23% complete...

or something like that..

 

My only complaint about the Beta was this (tested for about 10 days) is that the default on demand scan was faster (about 2 and half minutes rather than 3 and half with the regular NOD32) but the full scan was signicantly longer (22 minutes instead of 12 minutes with the current version).

Otherwise I found the new interface to be a vast improvement.

My specs:
P4 1.5ghz
Intel 850GB
512megs PNY RD800
60gig WD600AB

 

I'm glad to see that I am not the only one who has gone from about 9 minutes for a full on demand scan with the current version to 22 minutes for the same with the beta version. I do have more files (about 18,000 dbx backup files that I didn't exclude), than when I last did an on demand scan with the current version, still 22 minutes is much longer than I expected for a total of 58,000 files. That's approaching NAV 2003's record slowness.

W98SE
Pentium III
450MHz

 

Ya, but it doesn't even touch AVP 4.0's record of 42-46 minutes. It was even slower with the most recent build. That's when I pulled the plug (it was also getting buggy).

But still 12 to 22 is a big jump.

Other specs
27gigs(just under 90,000 files) of drive spaced used at time of those scans

 

i have an annoying problem with NOD's beta that MUST be simple to solve, I gotta be overlooking it. Whenever I reboot (or turn on) my computer, NOD32 does a scan with ALL profiles. Believe me that it gets pretty annoying if you have alot of profiles. Between AMON and a daily scan of my C drive (not to mention my other scans), A scan of anything more than memory and the MBR is unecessary. How do I turn off the scans at boot?

 

Don't know if this was mentioned..upon first boot of the day, update works fine. Any subsequent checks do nothing. Hitting abort pops up a box but doesn't change the "Abort" button back into "Update"

PIII 700m and AMD 1.4
XP SP1
512, 384 RAM

R

 

Actually IMON creates problems as well under win2k.
I have tried every possible way i could think of.
But if i activate it then i get message that it can't create listener socket with error 10106.
Then Spyblocker is affected with port 80
Naviscope also

There is a conflict at the winsock and sockets level

 

maybe thats why sb-chat client will not connect either

Ruben

 

Funny thing too - when using SamPal - kind of Proxy - I get two messages that nod has checked the email --))

Ruben

 

This new NOD32 beta causes News Interceptor to crash on my computer now when I double click on a news item to open in my browser (which is Opera 7, beta too, hehe).

I am running WinXP Pro SP1
Athlon XP 2.38ghz
1 gb 380mhz ddr ram

 

The following was cut and pasted (at Paul's request) from my post in the "OE deleted items folder" thread in this forum:

>Mele queried, "Dumb question, but if you have IMON enabled, and an email with a virus is downloaded, why does IMON put it into Deleted Items.dbx? Why isn't the file removed from the system? "

Not a dumb question IMO at all. If IMON had a "delete and send to total oblivion" option that would not retain the infected emails in the Deleted Items mailbox, there would be no chance for someone running into what Mele encountered. (Or what evidently what Blackspear's friend encountered too.)

That's something I think Eset should consider as a user friendly option that prevents this sort of thing from happening.

So far I can see potential users reading this thread and another at BBR and thinking, "Whoa, NOD can't delete an infected email without deleting the whole mailbox?? I'm staying away from that POS AV." The finer points of how it happens will be missed, but the end result of the mishap will be remembered.

So why not design IMON (or even AMON if it works similarly) so that "delete" means truly deleted from the email client? And not, as at present, where "delete" only means it's sent to the deleted item folder and the true deletion you have to do yourself?

From the consumer's point of view, I think when a scanner offers to delete an infected email, my first choice is that I want it deleted from my email client altogether so that I don't have to go back and manually "delete" it again myself. It's easier for the users. And since the users pay the bills, why not accommodate the users?