ESET v4 Fixes

[jofre]

Your trial version has expired - I could be wrong but I don't believe NodLogin works with a trial version (it requires a retail version)

------------------------------------------------------------------------------

Mine is WinXP Pro SP3 - ESS 4.0.417 (trial version) - NodLogin 9.9b and it works fine and auto-updates with Self-Defense ON. All is perfect !

[chrisTM]

Hello.

I'll try that tonight.

I do fail to see what effect that would have in my case, though. I am using the same critical setting notification as I used on .314 running mara-fix 1.5, and had no such issue at that time. My issue appears to be about NOD32 .417 notifying Security Center concerning NOD32 status and its inability to update itself while the computer is offline and running, not about any Windows system updates. I am receiving NOD32 update error/unsuccessful while offline, as I did with .314. Windows update is not set to automatically update, as before. Windows is fully patched, by the way.

There is the possibility of a flaw in the mara, box- fix related to the change in the definition notification. My real suspicion, though, is that .417 has a new communication feature with Windows Security Center that did not exist in previous versions because of the time specificity of the notification.

I guess the general presumption nowadays is that everyone is online all of the time, and that we don't know how to protect our computers.

chrisTM out.

@chrisTM

Do you have NOD32 monitoring Windows Update?

I like many others choose to be the one that adds updates to my system so I never use Windows Update :battle:

Because of this ESET will always feel there is a problem with my pc so in relation to this ESET turns the tray icon orange (I have not used NOD32 4.x so I am unsure if the system updates warning colour is also orange in just the AV product?)

Have you tried switching off the part of NOD32 that monitors system updates?

ESET > F5 > Tools > System updates > Notify about missing updates from level: set this to 'No updates'

See if that helps?

In relation to your earlier post #957

"Once again, the installation from the front page download was sketchy, at least on my end. The installer hung at the end and I had to hard boot"

What do you mean by sketchy? :s

I have never had an ESET install hang on me? ESET 4.x takes considerably longer than 3.x to install due to differences it has had to implement to please UAC in Vista / W7, and on a slow pc it can seem to take an age to install (it seems to take an age because it does! :D LOL) so you just have to be patient :)

Cheers

Hello.

The problem is not with Windows Update.

I have duplicated my earlier experience. It appears that NOD32 .417 contacts Windows Security Center at 09:00 EST, on my computer. NOD32 has been unsuccessful in auto updates as I am offline. It communicates to Windows Security Center that it is out of date. I have enclosed the necessary screenshots illustrating the condition. When back online, an update of NOD32 solves the issue. No Windows updates, etc. carried out. I do not auto update windows, either, preferring to be notified. This issue did not take place on .314 mara-fix 1.5.

As for the installation issue, only on .417 from forum front page. None previously experienced. The hang took place after installation bar indicated installation complete, and computer left on for many minutes with activity light off. Actually, it was not hanging, but locked. That was the reason for hard booting. After booting with normal option, all was well and no errors were observed.

chrisTM out.

Did you try this?

[Shahed]

Eset has fixed their servers finally. x64 is updating fine now "unlimited trial"

[mara-]

@chrisTM

There is no flaw in the fix. That is obvious from your screen shot. That must be something new with Eset .417 version.

Cheers :battle:

[bucow]

I've always used Nodlogin and just started using NodEnabler.

I was wondering when running NodEnabler, after it has done its magic, how come it doesn't terminate itself like Nodlogin or am I missing something here? The tray icon is still present. Not that it matters but it's just an added clutter.

bucow

Edit: Hmm, I think I understand why now.

[KotaXor]

For info:

NodEnabler v3.0 is working fine here, XP Pro SP3 running EAV v4.0.417.0 Business Edition

[KotaXor]

MiNODLogin v3.2.7.1

Changes in version 3.2.7.1: * Correction of bug: the insertion of the

license fails, some times, if the program is executed during the

starting of the system. To activate the option "not to validate the

present license", increases the probabilities of occurrence of the

problem.

Download:

Site: http://www.ziddu.com

Sharecode: /download/4142192/ESETAntivirusLicenceFinderMiNODLogin3.2.7.1.zip.html

[Bizarre™]

@chrisTM:

Just disable the Security Center service.

My Computer (right-click, select Manage) > Computer Management > Services and Applications > Services

[KotaXor]

MiNoglogin v3.2.7.2

Changes in version 3.2.7.2: * Correction of bug: If it is had

installed ESS the Business version, can get to be inserted a nonvalid

license.

Download:

Site: http://www.ziddu.com

Sharecode: /download/4142865/ESETAntivirusLicenceFinderMiNODLogin3.2.7.2.zip.html

[harpua]

Thanks to all for posting the updates to the license finder fixes so quickly.

[ugatme]

For info:

NodEnabler v3.0 is working fine here, XP Pro SP3 running EAV v4.0.417.0 Business Edition

Ditto that on XP pro SP2 w/ ESS v4.0.417. :dance2:

[Donaldo]

Your trial version has expired - I could be wrong but I don't believe NodLogin works with a trial version (it requires a retail version)

------------------------------------------------------------------------------

Mine is WinXP Pro SP3 - ESS 4.0.417 (trial version) - NodLogin 9.9b and it works fine and auto-updates with Self-Defense ON. All is perfect !

Good to hear that - it's another NodLogin advantage (Being a Licensed User, I've always had access to the ESET retail (registered) version installer. :dance2:

[Hoca]

@chrisTM

I think I will have to second the comment made by @Bizarre™ and also suggest that you disable the Windows Security Centre.

I did not realise this is the effect you were describing :s. I think you will find what ESET is doing now it ALWAYS should have! this is the whole purpose of WSC :dance2:

Here's a guide on how to switch WSC off in Vista (I'm guessing from the screen-shots you're using Vista?)

http://www.howtogeek.com/howto/windows-vista/disable-security-center-popup-notifications-in-windows-vista/

Hope that helps

Cheers

[Donaldo]

Hello.

I'll try that tonight.

I do fail to see what effect that would have in my case, though. I am using the same critical setting notification as I used on .314 running mara-fix 1.5, and had no such issue at that time.

Keep an open mind, mate - just try it & report back (check my reply to mara-.)

@chrisTM

There is no flaw in the fix. That is obvious from your screen shot. That must be something new with Eset .417 version.

Cheers :s

mara-

:dance2: I believe your fix is alright as far as chrisTM's issue is concerned. You're also right about 4.0.417.0, ESET has changed many things - it would almost qualify for an 'upgrade' instead of 'update' (just check the difference in size of the installers.)

[KotaXor]

MiNODLogin 3.2.7.3

Changes in version 3.2.7.3: * Correction of bug: the insertion of the

license fails, some times, if the program is executed during the

starting of the system. To activate the option "not to validate the

present license", increases the probabilities of occurrence of the

problem. * Correction of bug: The desinstalación of the previous

version does not begin during the present installation.

Download

Site: http://www.box.net

Sharecode: /shared/ce6zm7nlkc

[Migz]

For info:

NodEnabler v3.0 is working fine here, XP Pro SP3 running EAV v4.0.417.0 Business Edition

Kotaxor have you got a dl link for NodEnabler v3.0 Cheers EDIT:ive just got it on p51 cheers :dance2:

[shanijee]

i have seen some error in nodenabler v3.0

on Vista without service pack and using ESS v4.0.417

when unchecking and check these option i seen error

[KotaXor]

Yeah, saw your post in Asta........ let the makers solve it for you.

[jofre]

For info:

NodEnabler v3.0 is working fine here, XP Pro SP3 running EAV v4.0.417.0 Business Edition

-----------------------------------------------------------------------

Mine is WinXP Pro SP3 (32bits) .

NodEnabler 3.0 and ESS 4.0.417 ( Home Edition ) working fine here too.... :dance2: ...All is perfect :- Self-Defense ON and Auto-updates. NodEnabler with Uninstaller included.

------------------------------------------------------------------------

Download NodEnabler 3.0 here at Page 51.

cheers

Jofre

[Bizarre™]

Finally, the makers of NodEnabler decided to release a new version :dance2:

[chrisTM]

Hello.

Of course all this is true. I am running it all hooked up to properly evaluate the product. I've repaired/fixed so many computers and may want to use the product in the course of my repairs and troubleshooting. Also, evaluation/input may help ESET to further refine their product.

Something else I've noticed- torrent(s) don't appear to work nearly as well under NOD32 .417 on Vista sp1 as with my previous AVG. NOD32 seems much more secure, so secure that it hampers certain activities. Vista sp1 protocols override some of NOD 32 A/V browser capabilities, as noted in some of other nsane forums, and somewhere in the interactions, torrent activity suffers. This may be particular to hotspot internet hookup as opposed to dedicated connections; however, the process seemed to work much better in AVG. I'll keep fiddling until I figure it out.

ESET apparently knows, by the way, but the issue is relatively low on their priority list at this time. I hope the RIAA pressure is not seeping into the mindsets of the designers...

Thanks anyway.

chrisTM out

@chrisTM:

Just disable the Security Center service.

My Computer (right-click, select Manage) > Computer Management > Services and Applications > Services

[KotaXor]

MiNodlogin just verify and inserted a new license today,

there was a small 'flash' in the middle of the screen which last for a mini second and the license is now update to July 18.

Virus definition updated to 3988.

MiNodlogin v3.2.7.3 working fine. No inconvenience cause.

Using EAV v4.0.417 Business Edition with XP Pro SP3

[Donaldo]

Good show kotaxor - it's great to learn that MinNodlogin and NodEnabler are keeping up with NodLogin.

[KotaXor]

@ Donaldo,

Yes, I find MiNodlogin indeed good!

On another machine using MiNodlogin, the new license inserted valid till Sep 22. (although it could be blacklisted later :w00t: )

In this machine, there is no 'flash' at all when inserting the u/p, or maybe I miss it.

[Noddy]

GreetingsZ kotaxor & Donaldo,

Long time no hear no see!!!

I'm on Ulisess Seguridad 9.92b (playing it safe.) It archives the latest versions of most of the leading fixes and enables one to migrate swiftly to another fix in case of malfunction. Love to use MinNodlogin, NodEnabler & NodLogin.