ESET v4 Fixes

[Donaldo]

Another advantage of using fixes like NodLogin, NodEnabler & MinNodlogin - the signature database updates are rolled out to such Registered Users on priority. Folks who face update problems may try this Solution.

wait some time eset have release big update which cause server down

17.1mb

ENGINE0

version=3995 (20090408)

versionid=3995

build=4735

ESET's *big* 17 MB has not made it yet (unless it was meant for ESS.) :)

[BDX]

Well, I just got mine 3997 update. I had to click 3-4 times. I'm using box, mara- fix 1.1. I got normal update, nothing with 17 MB. Also, the strange thing is that when I click on my signature in Eset Window instead of opening web page with 3997 definitions, it opens 3948 definitions. Anyone else with the same thing?

Cheers :)

Yeah, I noticed that too. Bug in NOD32 or in trial fix?

BTW, I can't make it update from 3994. Oh well, hopefully it will automatically update anytime soon.

EDIT: Finally I got it. Had to click numerous of times. 3998.

[KotaXor]

Yeah, I noticed that too. Bug in NOD32 or in trial fix?

BTW, I can't make it update from 3994. Oh well, hopefully it will automatically update anytime soon.

EDIT: Finally I got it. Had to click numerous of times. 3998.

As what has been said, Eset servers problem.

Should be addressed, as updating is back to normal after 3994 to 3995.

Auto update to 3996, 7 and 8 without problem.. :)

[Donaldo]

Hello folks!!!!!

Just for the records, it's 3999 (if your fix didn't auto-update, maybe it doesn't deserve you.) :)

[jofre]

It`s good to have Box_Mara fix 1.1

Reasons:-

a - It auto-updates (not so easily as NodLogin, NodEnabler or MiNodLogin) , with self-defense ON. Shows 31 days left to expire trial version, 4ever.

Mine with Self-defense enabled.

b - Uses Eset Servers ( NodLogin, Nod Enabler and MiNodLogin one day can fail , because they are dependent of private servers ).

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

My preference goes to ( by order ) :

1st - NodLogin

2nd - NodEnabler

3rd - MiNodLogin

4th - Eset Box_Mara Fix 1.1.

[Donaldo]

My preference goes to ( by order ) :

1st - NodLogin

2nd - NodEnabler

3rd - MiNodLogin

4th - Eset Box_Mara Fix 1.1.

I guess it's quite a honest opinion, jofre. :)

[mara-]

Yeah, I noticed that too. Bug in NOD32 or in trial fix?

BTW, I can't make it update from 3994. Oh well, hopefully it will automatically update anytime soon.

It seems that it is the problem with the web page. You have to wait certain amount of time and it will open proper page. They probably do not update in time redirect links. Fox example I had this problem when I posted about it, but after few hours I tried to open same definitions and it opened correct page. Same happened with 3999 definitions.

Cheers :)

[Mo Husen]

My preference goes to ( by order ) :

1st - NodLogin

2nd - NodEnabler

3rd - MiNodLogin

4th - Eset Box_Mara Fix 1.1.

I guess it's quite a honest opinion, jofre. :)

Is it Bizarre to say "each to his own".

No experience of using the 1st, 2nd or 3rd above but Eset Box_Mara Fix 1.1 is doing just fine.

Apart from one hiccup updating yesterday, probably due to very busy Eset servers, everything is running smoothly here.

latest update @ 13.05 GMT - Virus signature database: 3999 (20090410) with ESS 4.0.417 on XP-SP3 Pro (x86)

[Donaldo]

Is it Bizarre to say "each to his own".

:) I like the pun - Bizarre™'s words are truly noteworthy, especially where fixes are concerned.

Check This

[Mo Husen]

Is it Bizarre to say "each to his own".

:) I like the pun - Bizarre™'s words are truly noteworthy, especially where fixes are concerned.

Check This

Hi Donaldo

I that's where I picked it up from - it's just for a

[matias067]

Version of virus signature database has reached: 4000 (20090410)

[KotaXor]

It`s good to have Box_Mara fix 1.1

Reasons:-

a) - It auto-updates (not so easily as NodLogin, NodEnabler or MiNodLogin) , with self-defense ON. Shows 31 days left to expire trial version, 4ever.

Mine with Self-defense enabled.

:P- Uses Eset Servers ( NodLogin, Nod Enabler and MiNodLogin one day can fail , because they are dependent of private servers ).

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

My preference goes to ( by order ) :

1st - NodLogin

2nd - NodEnabler

3rd - MiNodLogin

4th - Eset Box_Mara Fix 1.1.

Agreed with Jofre, but.......my preference is:

1st - MiNodLogin

2nd- Nodlogin

3rd- NodEnabler

4th- Box_Mara Fix 1.1

to each their own :rolleyes:

Hey Bizzare, pretend you did not see this> :locked: :beg: :whistle:

[brendon]

i have never used nodenabler, nodlogin, box or mara but i gotta say minodlogin is really good. it is the only fix i used so far and i think i will stick with it for a long time to come.

[jonahlomu]

Hi,

I've installed the version 4.0.417 with boxmara fix.

I installed the fix following the procedure, the only thing I don't understand is

why the antivirus says that the last successful update is 10 april 2009 but the

version of signature database is 19 march 2009, is this correct or not?

If it's not, how can I solve the problem?

Can someone explain me a little more about boxmara fix?

Thanks in advance for any info!!!

[jofre]

Hi,

I've installed the version 4.0.417 with boxmara fix.

I installed the fix following the procedure, the only thing I don't understand is

why the antivirus says that the last successful update is 10 april 2009 but the

version of signature database is 19 march 2009, is this correct or not?

If it's not, how can I solve the problem?

Can someone explain me a little more about boxmara fix?

Thanks in advance for any info!!!

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

About dates »»» Reboot PC.

All explanations on previous comments.

cheers

Jofre

[Hoca]

@jonahlomu

As trial versions are often knocked back in order to give paying customers a priority on updates, I think you will find ESS will report "last successful update is... " upon having successfully phoned home, and NOT having necessarily pulled in an update? ;)

Read back through the last couple of pages of comments and you will see the the ESET servers have been under pressure again due to a large update being shipped to paying folk.

The moral is... be patient :)

Providing you follow the instructions, the latest box, mara- fix seems to be working 100% ;)

Cheers

[jonahlomu]

@jonahlomu

As trial versions are often knocked back in order to give paying customers a priority on updates, I think you will find ESS will report "last successful update is... " upon having successfully phoned home, and NOT having necessarily pulled in an update? ;)

Read back through the last couple of pages of comments and you will see the the ESET servers have been under pressure again due to a large update being shipped to paying folk.

The moral is... be patient :)

Providing you follow the instructions, the latest box, mara- fix seems to be working 100% ;)

Cheers

Hoca and Joffre thanks for the fast reply.

The only thing I don't understand is why I see difference between the last successful update and the version of signature database.

[Hoca]

@box, mara-

" I " wrote...

Providing you follow the instructions, the latest box, mara- fix seems to be working 100%

I've just hit manual update on a machine powered by the 1.1 fix and got a message saying "Program Modules Updated" ??

It hasn't pulled in new sigs, they're still on 3994 (20090407) so I guess the servers are still congested, but I thought trials didn't pull in module updates? ;)

Update module: 1028 (20090302)

Virus signature database: 3994 (20090407)

Antivirus and antispyware scanner module: 1206 (20090409)

Advanced heuristics module: 1092 (20090309)

Archive support module: 1092 (20090324)

Cleaner module: 1040 (200900401)

Anti-Stealth support module: 1010 (20090302)

Personal firewall module: 1045 (20090325)

Antispam module: 1011 (20090114)

SysInspector module: 1211 (20090325)

Self-defence support module: 1005 (20081105)

Seems to be the Antivirus and antispyware scanner module that's been updated, anyone else notice this?

@jonahlomu

What is the "difference" you see? be more precise! :)

Have you too received a module update? Check in ESET window > Help > About and compare module versions with those I have listed here, or have your sigs been updated? if so list the version?

NO ONE should be alarmed at not receiving the very latest sigs from ESET, be patient they will arrive! you'll just have to wait your turn!

Or... dig deep and buy a licence!!! ;)

Cheers

[KotaXor]

@jonahlomu

As trial versions are often knocked back in order to give paying customers a priority on updates, I think you will find ESS will report "last successful update is... " upon having successfully phoned home, and NOT having necessarily pulled in an update? ;)

Read back through the last couple of pages of comments and you will see the the ESET servers have been under pressure again due to a large update being shipped to paying folk.

The moral is... be patient :)

Providing you follow the instructions, the latest box, mara- fix seems to be working 100% ;)

Cheers

Hoca and Joffre thanks for the fast reply.

The only thing I don't understand is why I see difference between the last successful update and the version of signature database.

Let me try to explain:

The last successful update is the date which you updates (ie your computer dates).

The version signature date is the date the virus definition is loaded for updating (ie Eset's date)

The different in time zone will cause this. Therefore if your time zone is different from Eset, your definition date will show differently.

Hope you can understand, cause I don't after reading it again.LOL! :frusty:

Simply put, its due to time zone. :sneaky:

[Donaldo]

Hope you can understand, cause I don't after reading it again.LOL! ;)

:)

LOL, kotaxor - you're a gem of a person.

The only thing I don't understand is why I see difference between the last successful update and the version of signature database.

jonahlomu, did you reboot your system?

[Hoca]

Perhaps a time zones issue may interfere with some aspects of an update, but given @jonahlomu says his sigs date is 19th March, I doubt very much this has anything to do with time zones? :sneaky: Unless ESET servers are somewhere light years away from the rest of us?! ;) LOL

I've seen this problem many times when ESET servers are congested.

A machine may begin to update but is not able to complete the download of the updated sig database, the update dries up and is unable to complete.

You are left with the same sigs you started with but you still receive the message that you have successfully updated, and given the last successful update 'date' of that day even though you may NOT have successfully received an update (and could be well overdue a sig update!)

Leaving it an hour or longer, then trying again often fixes this problem :)

As I said, the moral here is patience Grasshopper ;)

Cheers

[KotaXor]

@Donaldo,

Thanks for the compliment, I think?

LOL, I DO have this problem until I realise why in the morning there is a difference in virus definition date and successful update's date and in the evening

the successful update's dates is the same as version of signature update's dates.... ;)

It happen everyday since the day I use Nod32.(about 4 years ago). I live in the east, Eset in the west!!! as such time zone difference.wtf ;)

When Eset upload the definition (eg on the 10 April evening) In my place it is already the 11 April morning! So, what is shown on the GUI is not wrong!

But of course, one month is a bit off! :) pardon me!

It seem he has not click the update virus definition a few times to ensure it updates!

[Donaldo]

Even as we pledge to be patient, NodLogin auto-delivers 4001. Patience everybody. ;) Signature Database often makes most people go numb and speechless (even the decorated ones.) :)

Post # 1001

@Donaldo,

Thanks for the compliment, I think?

Be rest assured my friend, it's a compliment - humor is God's gift (it comes to you very effortlessly.)

[KotaXor]

Even as we pledge to be patient, NodLogin auto-delivers 4001. Patience everybody. :)

@Donaldo,

Thanks for the compliment, I think?

Be rest assured my friend, it's a compliment - humor is God's gift (it comes to you very effortlessly.)

Yap, mine updates to 4001(20090411) too, using MiNodlogin hehehe

oh..shit, I can feel 4002 coming soon......kid

[Donaldo]

Yap, mine updates to 4001(20090411) too, using MiNodlogin hehehe

oh..shit, I can feel 4002 coming soon......kid

. . . . . . . . . without even running your NodLogin, MinNodlogin & NodEnabler (as) a process - in fact without even scheduling them and hey, I feel something - (I think it's 4002.) :)