NOD32 2.5 Final Will Be Released May 6th

I quit NOD32 and restart it again and works.

Now came back to 32bit...

Thanks

 

Marcos,

I had this problem on my wife's machine using 24-bit display modes, but not 16-bit or 32-bits - do you have any more information on it other than change display mode to 16-bits and it will go away?

cheers

Greg

 

No, I can't tell why the Catalyst drivers suffer from this issue.

 

Tonnes of Graophic cards used to have this quirk... they won't work well above 16 bit display... dunno why.

 

I have the exact same issue. Sent it in to Mark and also posted on the 2.50.7 thread.

I have Radeon drivers, but they are set to 32bit. Shouldn't have to drop down to 16bit for this to work. No skinning apps used.

I see this as more of an Eset issue than a ATI issue. Didn't see this with 2.12.3 and don't have this problem with any other apps. Seems to me this is more of a bug in 2.5.x than a driver issue.

 

Well I do have my NOD32 setup to upgrade the program if it is available. But I wonder, do you think I am just better off performing a clean install?

That is my normal/preferred method. I am just wondering if anyone else has ever had a problem with NOD32 and auto program updates.

Thanks,

Jag

 

Yeah maybe I will roll with that as well.

If we do a clean install, I assume we can still use the same username and pw to enter for updates with this new version?

 

Yes it's true. NOD32 2.12.3 doesn't have this problem.

 

I don't have this issue on version 2.12.3 and previous, but only in these beta...

On these beta, NOD32 added support for xp themes, so this could be a problem of NOD32 and not of ATI since I didn't see this issue on another program...

 

Sounds like there is a common theme here Marcos. If this was happening with other apps, I could see it being a driver issue, in this case though, methinks someone needs to look at the code again.

 

NOD32 only uses functions provided by the oper. system. Then, oper. system uses graphic card drivers to output the result to the monitor. If it was a fault of NOD32, it would be driver independent and would happen on all computers regardless of VGA cards installed.

 

Then it's a compatibility issue between NOD32 and Catalyst. Regardless, given the fact that we don't have issues with 2.13.x (same drivers) and we aren't seeing this with any other apps whatsoever the breadcrumbs lead us to only one place... the problem lies with 2.5.

Seems to me if there was a bigger issue with Catalyst drivers it would impact more apps. Isn't there some kind of new skinning feature with 2.5? Perhaps that's the source of the issue.

 

ok - just to make it a little more interesting... my wife's machine with the display problems has a matrox video card... a matrox millennium g550agp driver is the 5.93.9 microsoft signed matrox driver.

I can't find a more up-to-date driver - http://www.matrox.com/mga/support/drivers/certified/home.cfm

Looks like that *IS* the latest driver... I'm just checking the new .9 beta in 24-bit mode to see if the display problem we had is still around.... requires a reboot though ...

 

nope - 24-bit after a reboot and nod's control centre is full of gaps... I hope I managed to attach the screenshot properly - apologies that it's wider than necessary, this machine only has ms-paint and I'm not a regular ms-paint user...

 

Yet more evidence it isn't a driver issue. Thanks web.

 

About question as to whether or not computer should be restarted after a program update:

Yes tazdevl. I think it is a sensible question considering that Nod32 under Type of update - offers under Restart after component upgrade - the following options:

. Never restart computer.
.offer computer restart if necessary.
.if necessary, restart computer without notifying.

 

Common sense dictates that it will require a restart since it is more than a signature update.

I just find it odd that you find it a questionworthy question. Reboots are somewhat common with Windows and in most cases when you update or apply patches, a reboot is required. Click yes, wait for Windows to come up again. Pretty straighforward.

 

I sometimes get that white areas while running Steam. Not sure why. A restart will return the colours back. Maybe this info. could help.

 

Hmm....It could be something related to DirectDraw or DirectX and the drivers. I've had those in Steam too, but thats the *only* app that ever does this.

 

Well this issue does not give me any warm fuzzies about this upgrade.

I have an ATI 9800 Pro running the Catalyst 5.1 drivers.

 

Haven't seen this on Steam... Cat 5.4.

 

I have a GeForce FX 5900. I saw this bug with some of the early 6x.xx (mostly unofficial) drivers and one 70 series driver (unofficial), but thats all. Other drivers work well.

 

Which drivers the Omega's by chance?