Eset Nod 32 Fix for 3.0? (CONTINUED)

[new_age_messiah]

Hi guys, after getting tired of that f*ck of Ulessisoft, we decided to make

our own nod32 patcher.

Made by the Nodster, and me, Damian666 for asta ;)

we made it under the damned crew nick.

it works simular to Nodlogin, but updates from internet pages.

so no trouble with the server being down and crap Very Happy

check it out.

Token from other site this is not my words

Rapidshare sharecode: /files/135701461/NodEnabler_2.1_x32___x64.rar.html

Mediafire sharecode: /?gcrnusrqyhc

[jofre]

:sneaky:

;) No luck with the guide (information,explanation, tutorial, instructions, ;) ) posted by member =Kostaxor= (Page 76,Post

1515) in order to get automatic updates on mine WinXP Prof. (32 bits) , ESS 3.0.669 and NodLogin 9.6.

Tried 3 times, always starting from a clean installation, but failed.

I see on comments people had success with EAV 3.0.669 . Probably the guide was done just for EAV and not for ESS (?).

Anyway, NodLogin is working fine even with manual updates (sometimes updates twice a day).

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

Hey, New_age_messiah :

I am going to catch yours too. We never know...but meanwhile NodLogin is fine and in good health ! ;)

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

...and THANKS , of course.

I`ll try it later; no time for today...

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

Cheers

Jofre

[ugatme]

Had to discontinue marsu 2.5, eventually happens to all of us, no? Went with nodlogin 9.6 yesterday morning and a total of 7 updates since. For now it's the way to go IMHO.

[harpua]

Jofre,

I think the problem may be that when too much time passes between updates, the license provided by nodlogin may become invalid in the meantime and so by the time an update is available, the update fails due to the license having become invalid. Since the update fails, the scheduled run of nodlogin does not occur either. To solve this problem, I believe it is necessary to simply add in another schedule task to run external application nodlogin.exe in the eset scheduler but set this one to run at a timed interval (as was suggested by another poster earlier above). I think 2 hours is probably sufficient. This should keep you license valid at all times and the automatic updates should no longer fail.

Give that a try and see if that works.

Best regards,

harpua

:sneaky:

No luck with the guide (information,explanation, tutorial, instructions, ;) ) posted by member =Kostaxor= (Page 76,Post

1515) in order to get automatic updates on mine WinXP Prof. (32 bits) , ESS 3.0.669 and NodLogin 9.6.

Tried 3 times, always starting from a clean installation, but failed.

I see on comments people had success with EAV 3.0.669 . Probably the guide was done just for EAV and not for ESS (?).

Anyway, NodLogin is working fine even with manual updates (sometimes updates twice a day).

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

Hey, new_age_messiah

I am going to keep yours too.We never know...but meanwhile NodLogin is fine and in good health ! ;)

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

cheers

Jofre

[Quentin]

So it's not an eset servers issue? The marsufix is no more good?

[ugatme]

Good point harpua. I removed the service starting in msconfig and just went with a new eset schedule run repeatedly every 90 minutes. Changed license once in 27 some hours.

[box]

Jofre,

I think the problem may be that when too much time passes between updates, the license provided by nodlogin may become invalid in the meantime and so by the time an update is available, the update fails due to the license having become invalid. Since the update fails, the scheduled run of nodlogin does not occur either. To solve this problem, I believe it is necessary to simply add in another schedule task to run external application nodlogin.exe in the eset scheduler but set this one to run at a timed interval (as was suggested by another poster earlier above). I think 2 hours is probably sufficient. This should keep you license valid at all times and the automatic updates should no longer fail.

Give that a try and see if that works.

Best regards,

harpua

Good observation.

[harpua]

Quentin:

Re Marsu Fix

I don't know why this is so hard for people to get a handle on. It's not a one or the other kind of thing. The marsu fix is fine but it depends on evaluation servers working properly, which they are now not doing. Therefore, at the current time, the marsu fix is not going to work well.

[ugatme]

Since switching to nodlogin and converting to eset to retail, my internet is noticeably quicker. Anyone else or am I getting too much sun, lol?

[Quentin]

Quentin:

Re Marsu Fix

I don't know why this is so hard for people to get a handle on. It's not a one or the other kind of thing. The marsu fix is fine but it depends on evaluation servers working properly, which they are now not doing. Therefore, at the current time, the marsu fix is not going to work well.

Mmm. Are the evaluation servers working with a normal trial version (without any fix)?

[KotaXor]

before installing NODlogin I had a clean system. After installing NODlogin I found some DLLs (combination of numbers and letters) inside the temp and system32 folder which are started by rundll32.exe and they will be restarted everytime you kill rundll32.exe. And those DLLs are also force to be loaded from some Windows services. This is a virus behavior for me.

where didi you get nodlogin setup file from? please get it from the source or Jofre posted link.

Don't remember having rundll32.exe running, if it is updating, then I think it should be OK. Other than that rundll32.exe or any dlls should not be running.

I can't and won't discuss how nodlogin works as I am not the creator of it. Use 'reverse engineering' to get what you want.

Accordingly to the creator, nodlogin works for both EAV, ESS and even Nod32 v2.xx

Have not tried it on ESS and Nod32 v2 though or even in Vista.

Additional configuration might need to be done. Tried it out and keep the rest inform.

I am using XP Pro SP3 and everything is working well. Updates till version 3339 about an hour ago when I switch on the pc.

Sometime the license valid date will be shown and sometime it will not. It does not matter as it is the work of nodlogin.

Nodlogin will run if there is an update during the one hour or during boot-up

It will not run (I repeat) if there is no updates to be download.

[harpua]

Quentin:

Re Marsu Fix

I don't know why this is so hard for people to get a handle on. It's not a one or the other kind of thing. The marsu fix is fine but it depends on evaluation servers working properly, which they are now not doing. Therefore, at the current time, the marsu fix is not going to work well.

Mmm. Are the evaluation servers working with a normal trial version (without any fix)?

No, because Eset doesn't use the evaluation servers any more even with a normal trial version. Instead, the official trial version comes with a time limited user name and password already installed that I believe uses the same servers as the retail version. At least, that is my current understanding of the situation.

My guess, and it's just a guess (or a hunch), is that ESET is in the process of doing away with the evaluation servers entirely, but we'll just have to wait and see what happens about that.

[harpua]

before installing NODlogin I had a clean system. After installing NODlogin I found some DLLs (combination of numbers and letters) inside the temp and system32 folder which are started by rundll32.exe and they will be restarted everytime you kill rundll32.exe. And those DLLs are also force to be loaded from some Windows services. This is a virus behavior for me.

where didi you get nodlogin setup file from? please get it from the source or Jofre posted link.

Don't remember having rundll32.exe running, if it is updating, then I think it should be OK. Other than that rundll32.exe or any dlls should not be running.

I can't and won't discuss how nodlogin works as I am not the creator of it. Use 'reverse engineering' to get what you want.

Accordingly to the creator, nodlogin works for both EAV, ESS and even Nod32 v2.xx

Have not tried it on ESS and Nod32 v2 though or even in Vista.

Additional configuration might need to be done. Tried it out and keep the rest inform.

I am using XP Pro SP3 and everything is working well. Updates till version 3339 about an hour ago.

Sometime the license valid date will be shown and sometime it will not. It does not matter as it is the work of nodlogin.

Nodlogin will run if there is an update during the one hour or during boot-up

It will not run (I repeat) if there is no updates to be download.

Right, but if one schedules NLI to run on a timed schedule, say every two or four hours, it will run and will either tell you that your license is still valid and doesn't need to be updated; or, if the license is no longer valid, it will install a new valid one, so you will be ready for and able to download the next update.

[Quentin]

Quentin:

Re Marsu Fix

I don't know why this is so hard for people to get a handle on. It's not a one or the other kind of thing. The marsu fix is fine but it depends on evaluation servers working properly, which they are now not doing. Therefore, at the current time, the marsu fix is not going to work well.

Mmm. Are the evaluation servers working with a normal trial version (without any fix)?

No, because Eset doesn't use the evaluation servers any more even with a normal trial version. Instead, the official trial version comes with a time limited user name and password already installed that I believe uses the same servers as the retail version. At least, that is my current understanding of the situation.

My guess, and it's just a guess (or a hunch), is that ESET is in the process of doing away with the evaluation servers entirely, but we'll just have to wait and see what happens about that.

Are you sure of this (they are shutting down the trial servers), where you read this?

[harpua]

Quentin:

Re Marsu Fix

I don't know why this is so hard for people to get a handle on. It's not a one or the other kind of thing. The marsu fix is fine but it depends on evaluation servers working properly, which they are now not doing. Therefore, at the current time, the marsu fix is not going to work well.

Mmm. Are the evaluation servers working with a normal trial version (without any fix)?

No, because Eset doesn't use the evaluation servers any more even with a normal trial version. Instead, the official trial version comes with a time limited user name and password already installed that I believe uses the same servers as the retail version. At least, that is my current understanding of the situation.

My guess, and it's just a guess (or a hunch), is that ESET is in the process of doing away with the evaluation servers entirely, but we'll just have to wait and see what happens about that.

Are you sure of this?

Sure of what? Please be specific in the future. There is more than one statement in the post you are referring to. Obviously, I'm not sure about what I called my hunch or guess otherwise it wouldn't be a hunch or a guess.

There is very little that I am sure of in this world, however, I base my prior statement about the official trial version on the fact that when I downloaded one from Eset recently, it came with a user name and password for a time limited trial already pre-installed. If it has a user name and password, I think it likely (but I am not 100% sure and I did not bother to check further at the time) that it uses the same retail servers as the regular retail versions do.

This was also confirmed recently by an Eset spokesperson on the Eset support forum, but that guy's information and statements are not very reliable, imo, however, he just might be right about this particular point.

[Quentin]

Quentin:

Re Marsu Fix

I don't know why this is so hard for people to get a handle on. It's not a one or the other kind of thing. The marsu fix is fine but it depends on evaluation servers working properly, which they are now not doing. Therefore, at the current time, the marsu fix is not going to work well.

Mmm. Are the evaluation servers working with a normal trial version (without any fix)?

No, because Eset doesn't use the evaluation servers any more even with a normal trial version. Instead, the official trial version comes with a time limited user name and password already installed that I believe uses the same servers as the retail version. At least, that is my current understanding of the situation.

My guess, and it's just a guess (or a hunch), is that ESET is in the process of doing away with the evaluation servers entirely, but we'll just have to wait and see what happens about that.

Are you sure of this?

Sure of what? Please be specific in the future. There is more than one statement in the post you are referring to. Obviously, I'm not sure about what I called my hunch or guess otherwise it wouldn't be a hunch or a guess.

There is very little that I am sure of in this world, however, I base my prior statement about the official trial version on the fact that when I downloaded one from Eset recently, it came with a user name and password for a time limited trial already installed. If it has a user name and password, I think it likely (but I am not 100% sure) it uses the same retail servers as the regular retail versions do.

This was also confirmed recently by an Eset spokesperson on the Eset support forum, but that guy's information and statements are not very reliable, imo, however, he just might be right about this particular point.

I edited my post and specified

[ademc]

Quick question regarding NODLogin, is uninstalling as simple as deleting the nodlogin.exe from the directory or is there another way to do it because I don't see an un-installer anywhere?

Thanks

[harpua]

Quick question regarding NODLogin, is uninstalling as simple as deleting the nodlogin.exe from the directory or is there another way to do it because I don't see an un-installer anywhere?

Thanks

Quentin, No I am not sure about a hunch or a guess, that's why I said it's just a hunch or guess.

Ademc, I am not yet an expert on NLI but I believe to completely uninstall it, it would be necessary to delete nodlogin.exe and also use regedit to navigate to HKLM/software/and delete the whole ulisessoft folder (with nodlogin in it) as well. It's kind of funky that it doesn't come with an uninstaller like marsu did.

The question I have about NLI is where, exactly, do these license keys it obtains, come from?

[shought]

Quick question regarding NODLogin, is uninstalling as simple as deleting the nodlogin.exe from the directory or is there another way to do it because I don't see an un-installer anywhere?

Thanks

Quentin, No I am not sure about a hunch or a guess, that's why I said it's just a hunch or guess.

Ademc, I am not yet an expert on NLI but I believe to completely uninstall it, it would be necessary to delete nodlogin.exe and also use regedit to navigate to HKLM/software/and delete the whole ulisessoft folder (with nodlogin in it) as well. It's kind of funky that it doesn't come with an uninstaller like marsu did.

The question I have about NLI is where, exactly, do these license keys it obtains, come from?

I think a group of people rip them of sites ;) Like the License finder does, but in the case of Nodlogin all licenses go into one big database and it gets distributed.

[harpua]

Quick question regarding NODLogin, is uninstalling as simple as deleting the nodlogin.exe from the directory or is there another way to do it because I don't see an un-installer anywhere?

Thanks

Quentin, No I am not sure about a hunch or a guess, that's why I said it's just a hunch or guess.

Ademc, I am not yet an expert on NLI but I believe to completely uninstall it, it would be necessary to delete nodlogin.exe and also use regedit to navigate to HKLM/software/and delete the whole ulisessoft folder (with nodlogin in it) as well. It's kind of funky that it doesn't come with an uninstaller like marsu did.

The question I have about NLI is where, exactly, do these license keys it obtains, come from?

I think a group of people rip them of sites ;) Like the License finder does, but in the case of Nodlogin all licenses go into one big database and it gets distributed.

That's interesting. I guess it's all done via an automated process. And then once one of those keys has been appropriated (or perhaps used to d/l an update), it doesn't seem to take long for them to get invalidated.

[KotaXor]

Funny though, during the last updates, nodlogin does not run. Only the 'Regular automatic update' runs and it updates to the latest version.

I guess as long as 'Regular automatic update' can update, nodlogin does not run. (depend on the user/pass)

This has happen a few times for the last few weeks.

As shought mention, yes, there is a database of updated user/pass. The problem with previous nodlogin is not being able to connect to database.

You could try Eset Online posted by one of the member here, but you need to cut and paste the user/pass. Try it! Does not need to install anything (except EAV or ESS of course)

[maxima2k53]

Funny though, during the last updates, nodlogin does not run. Only the 'Regular automatic update' runs and it updates to the latest version.

I guess as long as 'Regular automatic update' can update, nodlogin does not run. (depend on the user/pass)

This has happen a few times for the last few weeks.

As shought mention, yes, there is a database of updated user/pass. The problem with previous nodlogin is not being able to connect to database.

You could try Eset Online posted by one of the member here, but you need to cut and paste the user/pass. Try it! Does not need to install anything (except EAV or ESS of course)

[KotaXor]

Funny though, during the last updates, nodlogin does not run. Only the 'Regular automatic update' runs and it updates to the latest version.

I guess as long as 'Regular automatic update' can update, nodlogin does not run. (depend on the user/pass)

This has happen a few times for the last few weeks.

As shought mention, yes, there is a database of updated user/pass. The problem with previous nodlogin is not being able to connect to database.

You could try Eset Online posted by one of the member here, but you need to cut and paste the user/pass. Try it! Does not need to install anything (except EAV or ESS of course)

u gotta schedule nodlogin to run...i got it scheduled after every virus signature update program component...i even got it running every 30 minutes...

30 minutes? Is it necessary? nodlogin will run when it had to and will not run if it does not need to, that's the beauty of it.

Hope it continues to work!

At least this situation makes ppl to be innovative to come up with more ways to ensure updates.

[maxima2k53]

Funny though, during the last updates, nodlogin does not run. Only the 'Regular automatic update' runs and it updates to the latest version.

I guess as long as 'Regular automatic update' can update, nodlogin does not run. (depend on the user/pass)

This has happen a few times for the last few weeks.

As shought mention, yes, there is a database of updated user/pass. The problem with previous nodlogin is not being able to connect to database.

You could try Eset Online posted by one of the member here, but you need to cut and paste the user/pass. Try it! Does not need to install anything (except EAV or ESS of course)

u gotta schedule nodlogin to run...i got it scheduled after every virus signature update program component...i even got it running every 30 minutes...

[JunkInternetMail]

Making it run that many times is fucking retarded.

People like you ruin fixes for everyone else b/c you HAMMER the NOD update servers and get logins BLACKLISTED.

Please note I said running it is fucking retarded ... not you ... I don't know if you are fucking retarded or not.