PDA

View Full Version : Nod32 v4 Beta Compatible with Windows 7 Pre Beta!


Concepts
November 27th, 2008, 05:42 AM
I have installed Nod32 Beta 4 x64 on Windows 7 Pre-Beta x64 Version and it's running flawless. Just a heads up and I will be posting any bugs I happen to encounter in the meantime even though this software isn't meant for Windows 7 currently. Atleast we can get a head start on it if anything. I don't think to much has changed in Windows 7 compared to Vista after all it is the same Windows give or take a few goodies. :)

I have attached a screen shot below!

http://www.rigshowcase.com/pic.php?u=94yJmv8&i=14284

ASpace
November 27th, 2008, 12:34 PM
Spoiling the party ... Sorry ! :)

A bug I'd like to report . I wanted to write an email but forgot to do it and your screenshots just reminded me ;D

The other thread:
http://www.wilderssecurity.com/showthread.php?t=226432

The current thread and its screenshot can be viewed above .


The "bug" is present in Vista and concerns its experience index . After installing EAV v4 or ESS v4 , Windows reports that the Windows Experience Index must be refreshed (because of change that has occured) . I guess (and may well be wrong but...) , so I guess that Vista detects ESET's services/drivers as new devices and something might change the experience and that is why it needs refreshing .

Windows Experience Index => visit Control Panel -> System (in Windows Vista and in Windows 7)

Concepts
November 27th, 2008, 01:49 PM
I haven't seen this bug on my end at all in Windows 7 with Nod32 v3 or Nod32 v4 Beta. If it pops up I will let you know. :)

ASpace
November 27th, 2008, 02:48 PM
{QUOTE-> I haven't seen this bug on my end at all in Windows 7 with Nod32 v3 or Nod32 v4 Beta. If it pops up I will let you know. :) <-QUOTE}


But how ... have a look at your screenshots ?


Your first thread/post is about 2 hours before this one . In it you have installed EAV v3 on Windows 7 . The screenshot shows correct experience index 5.3 (no need of refreshing) .

picture here (http://spasova.my.contact.bg/2-win7_eset_beta.png)


~ 2 hours later you install v4 beta on Windows 7 and ......... have a look carefully , now the index need refreshing

picture here (http://spasova.my.contact.bg/win7_eset_beta.png)

djohn
November 27th, 2008, 03:02 PM
Hitech Good eyes there,I had to look twice then I seen it.Looks like a bug to me.:blink:

pondlife152
November 27th, 2008, 03:04 PM
{QUOTE-> The "bug" is present in Vista and concerns its experience index . After installing EAV v4 or ESS v4 , Windows reports that the Windows Experience Index must be refreshed (because of change that has occured) . <-QUOTE}

Can't comment on Windows 7, but this has not happened on my copy of Vista SP1.

ASpace
November 27th, 2008, 03:10 PM
{QUOTE-> Can't comment on Windows 7, but this has not happened on my copy of Vista SP1. <-QUOTE}


Very strange . Could you check again - reinstalling your beta version , installing the other new one , rebooting , manually checking the experience index after reboot ... It is always happening here , the last time tomorrow , when I reinstalled ESS again . I am also with SP1 , Vista Home Preminum.

CivilTaz
November 27th, 2008, 03:17 PM
{QUOTE-> I am also with SP1 , Vista Home Preminum. <-QUOTE}

Ohh, maybe it's because of that rare version u have. ;D

ASpace
November 27th, 2008, 03:30 PM
{QUOTE-> Ohh, maybe it's because of that rare version u have. ;D <-QUOTE}


I have created it myself ;D ;D ;D ;D ;D

Concepts
November 27th, 2008, 05:38 PM
{QUOTE-> But how ... have a look at your screenshots ?


Your first thread/post is about 2 hours before this one . In it you have installed EAV v3 on Windows 7 . The screenshot shows correct experience index 5.3 (no need of refreshing) .

picture here (http://spasova.my.contact.bg/2-win7_eset_beta.png)


~ 2 hours later you install v4 beta on Windows 7 and ......... have a look carefully , now the index need refreshing

picture here (http://spasova.my.contact.bg/win7_eset_beta.png) <-QUOTE}

Ahh, I see what you are talking about now. I never realized that because I updated my Nvidia drivers and thought that caused it.

pondlife152
November 28th, 2008, 01:45 PM
{QUOTE-> Very strange . Could you check again - reinstalling your beta version , installing the other new one , rebooting , manually checking the experience index after reboot ... It is always happening here , the last time tomorrow , when I reinstalled ESS again . I am also with SP1 , Vista Home Preminum. <-QUOTE}

Okay, I will try it and let you know.

pondlife152
November 28th, 2008, 04:47 PM
Okay, I haven't tried this with ESS as I only normally use EAV, but you say the problem occurs with EAV too, so here goes...

1. Checked index = okay
2. Uninstalled EAV 4.0, rebooted.
3. Checked index = okay
4. Installed EAV 3.0.672, checked index = okay
5. Rebooted, checked index = okay
6. Uninstalled EAV 3.0.672, rebooted.
7. Checked index = okay
8. Installed EAV 4.0, checked index = okay
9. Rebooted, checked index = okay.

At no point do I need to refresh the Windows Experience Index.

This is all tested on my laptop with Windows Vista Home Premium SP1.

Concepts
November 30th, 2008, 01:39 AM
I have reinstalled both Nod v3 and Beta 4 again and I didn't get the refresh index score. So I think it was caused when I updated the Video drivers.

jmc777
January 13th, 2009, 11:28 AM
One thing I've noticed is that ekrn.exe goes sky-high when you do a start menu search, slowing the appearance of search results.

Edit: either an update fixed this, or it was just a temporary glitch of some kind. The speed seems fine now. ???

XIII
January 13th, 2009, 03:15 PM
I am pleased to see that ESS 4 beta installed on the public Windows 7 beta without any errors.

However, I have not done much using Windows 7 so far, so no info on daily usage.

JRY
January 19th, 2009, 01:43 PM
I'm testing Windows 7 Beta with NOD32 4.0 Beta. The NOD beta says it will expire on March 2. What happens then? BTW, so far no issues to report.

Quitch
January 19th, 2009, 05:20 PM
Both NOD32 v3 and v4 64-bit editions fallover on my Dell XPS M1330 running Windows 7, the ESET service enters a continuous cycle of crashes and restarts.