If it ain't broke, don't fix it!!!!

[ioniancat21]

The title of this message should be a slogan around Eset, unfortunately it's not. Up until this week I had been using NOD32 v2.7. I had tried v3.0 over a year ago and had various issues with updating, services quitting or not initializing and every other error under the sun so I totally bypassed the 3.0 version as the junk it was. On Monday, I attempted to try v4.0.437(latest build) of NOD 4 hoping the problems of v3 were resolved and furthurmore, Eset had some time to get this latest product ready for primetime, unfortunately, it's not starting off well. My first install had to be removed and reinstalled due to "Failed to Initialize" errors stopping me from updating. After reinstalling the trial, it took almost an hour to get the updates to complete successfully with failing due to error. Luckily, they at least resolved the issue where some websites hung as in v3.0 but I fear the day when they retire v2.7 as I only updated 3 machines to test v4.0.

My question is...........will, or better, can Eset finally get their stuff together and build a working product again or have the developers that created the perfect v2.7 working for someone else now???

[Cudni]

Unfortunate experience but on few installs I have seen the 4.0 works well (excluding the episode with Vista SP2)

[SmackyTheFrog]

Sounds like you have hardware problems. I'm running close to 600 v3 and v4 clients without incident and I appreciate the better detection rates compared to v2.

[ioniancat21]

Well, I'm keeping my hopes up. On the bright side, the client has been stable for a couple of days since the initial installation issues and still runs with a light footprint. I also would like the better virus detection as v2.7 was getting a little long in the tooth when testing as newer viruses are able to damage NOD with increasingly greater success, which didn't occur in years past which prompted my trial of 4.0. I would really hope that Eset does get this one right as I'd hate to turn back to Symantec, which I used before my years with Eset (last used Symantec Corporate Edition v7.5)

Just to add, I'm using Symantec Endpoint Protection 11 MR4 at work and I also can add that Symantec has definitely improved upon lightening the bigfoot-sized Symantec Antivirus Corporate 10, which hung around your machine like a dead weight with it's massive footprint.

[tanstaafl]

One thing...

If you are attempting to do an in-place UPGRADE - meaning, install the new version ON TOP OF the old version, this is most likely your problem.

Doing this can cause problems with almost any software. I'm comfortable doing in place upgrades with respect to MINOR updates, but not major ones.

[siljaline]

I have personally recommended, installed and maintain V 4.0.437.0 on at least a dozen client machines, both home & business.
ESET gets my vote of confidence :thumb:

[trjam]

-{ Quote: "I have personally recommended, installed and maintain V 4.0.437.0 on at least a dozen client machines, both home & business.
ESET gets my vote of confidence :thumb:" }-
That is great! I am sure they appreciate it.:thumb:

[siljaline]

-{ Quote: "That is great! I am sure they appreciate it.:thumb:" }-
I hope so, as well - ESET AV Rocks ;)

[ioniancat21]

After some more time to play around with this 4.0 version I have more to report. As I said earlier, it was troublesome to update those clients initially, however reinstalls fixed those issue. I a now embarked on fixing a new issue with some of my machines failing on install with the "ESET NOD32 Antivirus Setup Wizard ended prematurely" messages. Iin all, I've attempted to upgrade 12 machines with only 5 completing successfully. I had similar issues with version 3 as well which is why I'm still running v2.7 mostly.

I'm contemplating rolling everyone back to v2.7 just because I'm not happy with the instability of this product right now and I shake my head in disbelief and wonder if Eset is run by the same people or has this company changed hands? Version 2.7 was perfect in practically every way and a reliable, stable, easy to install product with an extremely light footprint and great detection abilities, that all changed when version 3.0 came along!!! Ever since then, this product has been difficult to install, unreliable with realtime protection stopping and BSOD's and installation and removal errors forcing me to manually clean up after. This product has become a burden and bares no resemblance to the former 2.7 product in terms of quality.

ESET - WAKE-UP AND GET YOUR STUFF TOGETHER!!!

[The Hammer]

ioniancat21 The scrolling message is inventive though.

[ravenise]

I have found every single Nod32 product (post 2.79) increasingly bulky, slowed windows boot times, scanned and runs slower and with more of a memory print, and was graphically overkill... directed towards the target main stream fad fans. IMHO, I like nod32 2.79 as I like using winamp + classic skin, it is small slick and does the job perfectly. Nod32 2.70.39 is flawless as far as I can tell, however, I would like to know what the fundamental differences between 2.70.39 and 4+ are? Is it mostly the GUI? Or are the scanner kernels so different that 2.70.39 is considered a security risk? Do they continue to update 2.70.39's abilities to keep up to par with 4.0 as well?

[siljaline]

I've said what I feel needs expressing in these sorts of threads, ESET has made great strides of late and continues to do so :shifty:
http://www.wilderssecurity.com/showpost.php?p=1510017&postcount=6

[gugarci]

I went from 2.7 to 4.0 and have yet to have any issues.
Probably some other software of hardware is conflicting with ESET.

I no longer loose sleep over any software conflicts. If one doesn't work on your PC, and you can fix it, use another one. I love ESET but there a lot of other good AV out there including the new from MS, but it's still beta.

Good luck.

[ioniancat21]

I hope Eset understands that my harsh criticism is only due to the fact that it frustrates me how NOD32 could go from a top-notch product to this problematic inferior piece of work. If they had produced garbage like McAfee since day one for example, I wouldn't be here complaining because I've written that product off as a mess almost a decade ago so my expectations are zero.....

[siljaline]

-{ Quote: "I hope Eset understands that my harsh criticism is only due to the fact that it frustrates me how NOD32 could go from a top-notch product to this problematic inferior piece of work. If they had produced garbage like McAfee since day one for example, I wouldn't be here complaining because I've written that product off as a mess almost a decade ago so my expectations are zero....." }-
Perhaps a suggestion would be to take your issues to ESET directly ?

[rnfolsom]

ioniancat21:

In Message 5, tanstaafl wondered whether your installations were an "in-place UPGRADE - meaning, install the new version ON TOP OF the old version."

I may have missed it, but I don't think you answered that question in any of your posts, and I'm very curious about your answer.

At http://kb.eset.com/esetkb/index?page=content&id=SOLN2116, Eset notes that for a truly clean install you need to uninstall not only the currently installed version [e.g. 2.7], but you need also to delete the installation folder and some Application Data folders.

To that I'd add a reminder that according to the NOD32 version 2.7 Installation Guide, "Appendix C: Uninstalling NOD32," page 51, you need to uninstall version 2.x using the uninstall file in the NOD32 v2.x installation folder. (That uninstall file can be reached using a standard start menu shortcut, usually located in the NOD32 start menu folder.)

From some other document that I do not recall, I have notes that state unambiguously that NOD32 v2.x should NOT be uninstalled using Windows Control Panel Add/Remove programs.

(However, my understanding is that Add/Remove can be used to uninstall NOD32 v3.0 and 4.0, because they were installed using a Windows *.msi installer.)

Although I have had some trouble learning what some of the NOD32 AV 4.0.437 settings do, I've successfully installed NOD32 AV 4.0.437 on one Win2kSp4 computer, and it is working well with no problems. I will soon put NOD32 AV 4.0.437 on a second and third Win2kSp4 computer. But I realize that's cold comfort to someone running a large herd of computers, as I gather you are.

Best wishes and good luck.

Roger Folsom

[rnfolsom]

-{ Quote: " . . . Nod32 2.70.39 is flawless as far as I can tell, however, I would like to know what the fundamental differences between 2.70.39 and 4+ are? Is it mostly the GUI? Or are the scanner kernels so different that 2.70.39 is considered a security risk? Do they continue to update 2.70.39's abilities to keep up to par with 4.0 as well?" }-
Ravenise:

You may be interested in a thread from March 2009, "What are the Major detection differences between 4.0 and 2.7?" at http://www.wilderssecurity.com/showthread.php?p=1436970#post1436970

More accurately, that link takes you to message 11 from me to Marcos (responding to message 7 from Marcos to me), because I don't know how to convert a link to a particular message (which I had saved, including its source) into a link to a thread's beginning. But if you scroll up, and down, you will find many (but not all <grin>) of the messages in the thread interesting, and my recollection is that this thread 's messages include some links to other threads or messages that discuss differences between NOD32 AV 2.7, 3.0, and 4.0.

Roger Folsom

P.S. The "AH" in some posts means "Advanced Heuristics."

[ioniancat21]

sorry for the late response;

My final personal resolution was to leave the successful installations of 4.0 alone to see how they go long term while halting the upgrade of my remaining clients.

I don't view this as a loss as I still like the reliability of the 2.7 client over any of the 3.x and 4.x versions. I haven't been having any kind of problems with virus so not upgrading hasn't had a negative effect on security. I guess I'll keep checking out the future client updates with VMware for now until I find something I feel confident in to continue my upgrade. If they were to stop support for the 2.7 client, I may then excercise my option to call for support. Also, search the forum for "installation ended prematurely" and/or Google "NOD32 4.0 Setup Wizard ended prematurely", you'll find many users who have similar problems with both the 3.x and 4.x versions

Just to add I always do clean installation upgrades when they are full version as I figured upgrading from 2.7 to 4.0 wouldn't be a desirable upgrade path. I've failed with this error on both Windows XP and Vista machines (32-Bit). Also again, what angers me is that, as the title of this message states, "If it ain't broke, don't fix it!!!!". Sometimes there's no reason to reinvent the wheel, maybe it's fine as it is..........

[rnfolsom]

-{ Quote: "sorry for the late response;" }-
You responded in less than a day! Nothing to be sorry about.

-{ Quote: "I always do clean installation upgrades when they are full version as I figured upgrading from 2.7 to 4.0 wouldn't be a desirable upgrade path." }-
Thanks for answering my question. I suspected you were experienced enough to do clean installs, but this thread and tanstaafl's message 5 gave me an opportunity to tell anyone reading this thread that it's necessary not only to uninstall version 2.x but to uninstall it using version 2.x's own uninstaller rather than Windows Add/Remove programs --- which Eset's own documentation doesn't make completely clear --- and necessary also to delete folders.

Thanks also for explaining where you are going from here.

Eset may continue supporting version 2.7 with signatures, because I'd guess that Europe, especially Central and Eastern Europe, still may have a lot of Windows 9x computers running, and since 9x can't use version NOD32 3.0 or 4.0, Eset could lose a noticeable amount of revenue and profit if it abandoned version 2.7. But Eset is privately held, so this paragraph is pure guesswork, totally uncorrupted by any actual information.

According to Wikipedia, Eset is headquartered in Bratislava, Slovakia, with branch offices in San Diego, California; Wexford, Ireland; London, UK; Buenos Aires, Argentina; and Prague, Czech Republic. Thanks to you, I just now got around to looking that up, which I'd been meaning to do for some time.

Roger Folsom

[ioniancat21]

I continue my rant over here in the Smart Security section with a user suffering a similar fate. Read along if you're having similar issues.
http://www.wilderssecurity.com/showthread.php?p=1512708

[siljaline]

No thanks :shifty: Vent @ ESET, perhaps.

[GldRush98]

I have to wonder what O/S and SP level the people running version 4 and having no problems are on?
Every Vista SP2 machine I have seen so far has had problems caused by version 4 and have had to uninstall it from all of my Vista machines ::)
Running with no antivirus because of Eset's lack of attention to the Vista SP2 compatibility issue FTL:-[

[Cudni]

-{ Quote: "I have to wonder what O/S and SP level the people running version 4 and having no problems are on?
Every Vista SP2 machine I have seen so far has had problems caused by version 4 and have had to uninstall it from all of my Vista machines ::)
Running with no antivirus because of Eset's lack of attention to the Vista SP2 compatibility issue FTL:-[" }-
Since the fix issued by Eset for Vista SP2 no problem at all. Never a need to remove it even before the fix. No need to run without an AV when there are decent free ones

[moorejack]

-{ Quote: "I continue my rant over here in the Smart Security section with a user suffering a similar fate. Read along if you're having similar issues.
http://www.wilderssecurity.com/showthread.php?p=1512708" }-
Hi-for what it might be worth to you in isolating the problem, my experience - I have been using NOD32 for three years now with absolutely no problems. In fact, it has jumped in and saved me from a virus a couple of times while browsing. (I tried Symantec IS way back - never again a Symantec product for me. Tried Spybot (problems), tried AVG both free and paid version, (problems).
About two years ago I settled down with the following protection systems (only), and there have been no problems: NOD 32 av, Spysweeper Antispyware, and only the Windows firewall.
(I always download and install the new versions without uninstalling the old one. However, I do disable the other protection program before installing the download, (but not the Windows firewall). (I run XP home on a Toshiba Satellite laptop.) Luck. A.

[moorejack]

Forgot to mention - I have always installed the latest MS Service Packs and security updates. A.

[ioniancat21]

I too am having the majority of my issues with Vista machines similar to GldRush98's experiences above. What scares me is that Windows 7 is being released shortly and if NOD32 is having issues running on Vista, how is Windows 7 going to look being that they can't get it running error-free on the older Windows versions.

Do yourself a favor all, skip the 4.0 series completely and stick with 2.7 until the wheels fall off as I've been advising to others I know who use NOD32. I've seen on the WWW that NOD32 4.0.437 is being touted by some as a "final". If this is their "final" stable build and there is truth to these statements, Eset is in big trouble as this current version is definitely not ready for primetime.

It saddens me to have to make comments like these and I really do wish that version 4.0 was 10000% better than 2.7, unfortunately it's not. It shouldn't be too hard to make me a believer Eset, simply make a product as reliable as the 2.7 version and I'll gladly update all my messages related to this here with happy-joy, sugar sweet reviews about just how great NOD32 is.

[rnfolsom]

Possible synthesis or summary of the "I'm having problems with Eset NOD32 AV 4.0.437" posts here:

Not everyone here has made clear what Windows version he is running, or whether he is installing Eset NOD32 AV 4.0.437 on multiple computers using
a) a Workgroup (peer-to-peer) network
or
b) a domain (server-client) network

In fact, I don't think anyone who is dealing with multiple computers has mentioned which network type he is using, but it's likely b).

So I'll go out on a limb and guess that most users who have trouble installing Eset NOD32 AV 4.0.437 are installing it on computers running Windows Vista (messages 2 and 22 above refer to Vista Sp2), and/or are using some type of network (probably Domain) to install Eset NOD32 AV 4.0.437 on multiple computers, perhaps on a collection of client computers using different operating systems or at least different service packs.

Of course, that guess does not deny, in any way, that Eset needs to explain in greater detail how to avoid these (apparently mostly network) installation problems, and if necessary to fix any bugs that are causing them.

My own network is a workgroup (peer-to-peer) with all computers using Win2kSp4, but with only three machines I'll install Eset NOD32 AV 4.0.437 manually on each computer. I've had no problem with the first installation (on the computer on which I am writing this), and I don't anticipate problems on the remaining two computers. But that's cold comfort to someone trying, over a network, to install on multiple computers.

Given that this is message 27, I'm locking the stable door after the horse is out, but I hope that any additional posts on this thread, regardless whether they are reporting success or failure, give a fairly complete description of the environment: installing manually on separate computers or using a network to install on multiple computers; workgroup or domain network; operating system and service pack information about the source computer and client computers; and method used and steps taken (including folder deletion) to uninstall the previous antivirus software (e.g. my message 16).

Roger Folsom

[ioniancat21]

I just wanted to add in some positive information for others testing out there. Within my test lab, it seems that NOD32 v4.0.437 installs and runs just fine on Windows 7. So far all installations on this operating system have had no issue. I only have Windows 7 in the lab and on Vista and XP, where I actually need it to work, it doesn't which is why many of us have refused to upgrade from 2.7.

Looking on the bright side though, it's been nice to actually see the client running correctly for once. Just to add, version 2.7 also runs fine in Windows 7 so those who are stuck in the past like myself can continue on this path.

[ioniancat21]

Just to keep all updated;

I kept the few 4.0 clients in place that would install without issue and unfortunately, I had to roll back to v2.7 on 2 of those 5 remaining clients. The two clients I rolled back suffered from the unfixable "Analysis of application protocols will not function" issue. Despite reinstalling, using the Eset uninstaller or anything else I tried, was unable to get those clients to ever work after that issue. So..........now there are only 3 clients left. I'm laughing with a friend here and were making bets on how long these 3 clients will run until they also fail.

I've said it before...................GET YOUR STUFF TOGETHER ESET, IT'S TIME TO EITHER FIX THESE CORNY ISSUES OR DUMP THE WHOLE 4.0 JUNK APPLICATION AND RELEASE 2.7 NEXT YEAR WITH A 5.0 STICKER ON IT!!!

[ccomputertek]

Geez, temper temper lol, can you say L-O-V-E ........... lmao

I was thinking to myself while playing with NOD32 starting from version 2.7

" :o man, are all these release candidates called final release versions :o "

Don't know why you love 2.7, it looks like it never left the windows 3.1 age and it did in fact have many flaws, one of which you mentioned I.E. getting blow out easily and disabled by mediocre viruses.I have found the rest of the flaws while i was poking around with it.Then I found my true love, version 3.0.684.0 .... there is a slight problem with it I have experienced, but the rest of 3.0 is flawless IMO.Then i tinkered with 4.0, I did not have any issues with it, but for some reason I could not stand it, they got too happy and put a bunch of crap in it / on it, that IMHO was not necessary.I had 4.0 for one day and said screw this, I'm never leaving 3.0.I just wish / hope that their virus definitions stay unified, unlike other antivirus companies who force you to upgrade by making it so the latest definition models no longer work in older versions, like symantec for example.The last version of symantec I was able to tolerate honestly was 2003, before that it was norton antivirus 2000 for many years, till they made the new definitions incompatible with older versions.2003 is still supported and still works, but not for much longer i'm sure.Please do not do this ESET, I have no plans on leaving version 3.0 EVER !

stop getting happy with these GUI's and all the other stuff, you had it right with 3.0 ! just some minor fixes thats all.

I will now be submitting a resume to ESET, to work in the test / compatibility labs or as some type of PC tech / specialist.I wonder, I allways wanted to go to Cali, But perhaps they have an office in Romania or Slovakia, the girls there are freakin' HOT ! :o :wacko:

[edwin3333]

I'm currently removing Nod32 from over 600 PC's. Yes, I did remove Nod32 and rebooted twice before installing 4.0.437. The problems occur on new PC's installed from XP CD that never had any other AV. Yes, I've contacted support on many of these issues and they have acknowledged my issues are valid. Sometimes it took a few months of work to get that far. But none were resolved. My 2.7 PC's are stable but are the ones getting viruses all the time.

I've tried Kaspesky 2009, KIS, and KAV . We have had around 60 PC's with it. I don't recommend it either. It's an exception wh0re. WGET, Robocopy, HTTP streaming all get broken and need major exceptions to work. It's in their forums..

Symantec ESS 10 through 10.3 have had major issues too. File shares just quit working after a few days. But 10.4 MP4 seems to have fixed all the issues. You have to manually upgrade your server to get that version update though.

Didn't all the AV vendors have to re-write their products because Microsoft removed the way products such as 2.7 hooked into the OS in Microsofts newer OSes? Is that the reason why 3.0 and 4.0 are so different than 2.7 with no IMON but with the new proxy? I kind of think this change is the reason why I have so many problems. Cheyenne AV was like Nod2.7 in various regard. Then when CA modified it in 8.0 gold, I went through many very similar issues I am facing with Nod32 from 2.7 to 3/4.0. That's what made me switch to Nod in the first place.

Anyway, not ranting. I'm a lost customer and that's the reason why. In 3 years I will re-evaluate. Nod will be on the re-evaluate list..

[jeremyf]

-{ Quote: "Hello edwin3333,

what order may I ask are you installing after putting a fresh copy of XP on these new machines.And how many drivers does microsoft provide on it's own that are native ? sound, video, network card ? are they all installed allready with " microsoft " versions of those drivers ? or do you have to install most of the hardware ?

Try this:

Install a fresh copy of the OS on a newly formatted partition, and the first thing you do is all the automatic updates and security patches from microsoft.

Then before you install any other driver's if microsoft did not provide a driver allready for most of them, then make NOD32 the first thing you install after the OS updates, then follow driver installation after that.

I have found that this will put ESET driver at a higher priority before other drivers start that may be conflicting.

Try that on at least one PC and reboot at least 10 times and let me know if that helped or your having the same issues.

we will figure this out as a team." }-


lol, wut?

[Cosmo32]

I do not know whether I even belong in this conversation, but, I am now considering an upgrade to ESET V4.0BE.
I have now lived behind the V2.7BE code since 2006. I have been infection-free. At this date I rate this ~100%; and, I do NOT use the XP firewall and such.
For my money I only expect ESET to sell me a product that works. So far it has in spades! I am impressed.
I still have some fear of V4, but, I am still listening to the voices here.;D

[ethos]

Upgraded 90ish clients to 4.0.437.0 from 2.7, was a bit of a pain as it meant uninstalling 2.7 before updating. My method was:

* Uninstall Nod32 2.7, reboot later
* Install Nod32 4.0.437.0 and import config file
* Reboot Machine

I've had 0 problems so far, the startup scan seems a little longer but I'd imagine it's just searching for more / a more thorough scan.

[tsherr]

I've been installing v4 since May with zero problems. These installs have been on: XP Home, XP Pro, Vista Home (32 and 64), Business, Ultimate (32 and 64.) Not sure where you guys are finding the problems, and I don't doubt you are having them, but I've actually seen fewer problems with v4 installs than with 2.7 installs (and have fixed several machines that refused to run 2.7 by installing v4 installed.

T

[ioniancat21]

It's sad to see others in my boat although I am happy there have been some success stories here with the 4.0 client.

Like other users have said, v2.7 isn't as powerful against some of the newer virus and spyware types as compared to 3.0 and 4.0 but it's stability is unmatched, which to me is the more important feature.

Just to add, I've been working in I.T. for almost 20 years and I'm also doing consulting work as well. For most of the antivirus deployments I do, in most cases customers want Symantec's Endpoint Protection 11 MR4. In my experience, deployment of this product has been easy and Symantec has improved the client drastically since the Antivirus Corporate 10 version which was much more of a pain to deploy and had one of the biggest footprints I've seen in an AV client. While I know this is the ESET FORUM, I thought I'd share my experiences with others who are on the fence.

My experiences with NOD32 server-based deployment are few as many of my business partners are in the financial sector and Antivirus reporting is high on their list of needed features. Symantec Reporting is one of the most robust of the group as Sophos, McAfee, Kapersky, NOD32 and others either don't offer these options or don't do it as well. When I have deployed NOD32, it's usually been in smaller business settings as I feel that client fits best in that environment. The point is, the competition in this genre is fierce, if Eset doesn't get it together, they could lose their customer base very easily in this market. Stability, rather than features should be on Eset's list of goals, instead they continue to frustrate users of their product with unreliability. I hope the Eset support team understand that our goal here is the same, to have a happy, event-free experience running, deploying and administering the Eset 4.0 Client. I don't enjoy railing a product I've loved for years and am saddened by the diminshed reliability of their latest client. We all want this product to work as we remember. I can imagine most of us here were sold on this product initially in the v2.0 days. Years later, we're all still here wanting what we had, a lightweight client offering good protection from virus that's not too problematic to install. What we are currently getting is an unreliable, unstable product instead and this is why users in the forum seem frustrated. Most NOD32 users are not about seeing new versions every year and can live with all as it is provided that Eset in return gives them a client they can depend on. Eset has set their bar high with the 2.7 client, the question is; can Eset manage to get their stuff together finally and produce a stable product so we can all come here to the forum in praise of your product, rather than to complain about it.

[ioniancat21]

Also..........
Edwin3333 - Symantec ESS 10 and the whole damn series is absolutely wacked and I don't suggest that damaged fossil to anyone. If NOD32's deployment is giving you issues and you can't deploy it, check out Symantec's Endpoint Protection 11 MR4 as I can tell you from experience that this is the best antivirus product to come from Symantec since 2000 when Norton Systemworks 2001 was still good and not the bloatware they sell today along with their Norton 360 product, which is also junk I hope to never see again. Also, stay clear away from anything McAfee as machines slow to a crawl with that bloated, unstable horror story of a client.

Good Luck, CAT

[jeremyf]

-{ Quote: "? whats so confusing about that ? I explained in strict detail .... lmao :argh:" }-


-what is an "ESET driver"?

-how does order of install determine priority for loading "drivers" in Windows at startup? (please include reputable source)

-even if the procedure you outline: installing Windows on a freshly formatted partition, painstakingly installing all MS updates, then "reboot at least 10 times" (lol, what is 10th reboot for?). Even if this solved his problem on one machine, did you read he had 600 PC's? How would this help? Who has time for this?

-you did read his post was a conclusive statement that he was finished with eset right? not a request for "help"?

this is why I lol, wut?

[ccomputertek]

-{ Quote: "-what is an "ESET driver"?

-how does order of install determine priority for loading "drivers" in Windows at startup? (please include reputable source)

-even if the procedure you outline: installing Windows on a freshly formatted partition, painstakingly installing all MS updates, then "reboot at least 10 times" (lol, what is 10th reboot for?). Even if this solved his problem on one machine, did you read he had 600 PC's? How would this help? Who has time for this?

-you did read his post was a conclusive statement that he was finished with eset right? not a request for "help"?

this is why I lol, wut?" }-

1. An eset driver is someone who gets behind the wheel of a motor vehicle and just happens to use eset NOD32 antivirus.

2. If you install other software services that use drivers, like a firewalls ETC. first, then the eset drivers that are set to go into a load order group will get a TAG of say 18, 38 or 42, whereas if you installed NOD32 first before them, it would get a TAG of say 8 which would make it start before the others in the same load order group.... and I am the reputable source.

3. I retract my previous statement and deleted my 2 previous posts.

4. I retract my previous statement and deleted my 2 previous posts.

I made an interesting discovery while doing another fresh install of windows XP SP3 with only the video and network card installed by windows and no other software yet, including the windows firewall being turned off.I will post up what I have found in the original problem threads later sometime.


**************************************************************************************
-even if the procedure you outline: installing Windows on a freshly formatted partition, painstakingly installing all MS updates, then "reboot at least 10 times" (lol, what is 10th reboot for?). Even if this solved his problem on one machine, did you read he had 600 PC's? How would this help? Who has time for this?
**************************************************************************************

I was being sarcastic about the 10 reboots, a problem i have encountered started happening after exactly 4 reboots and I have traced the problem to 2 things, driver load order and what I just discovered, windows XP prefetch seems to be the culprit, I disabled it and the problem went away.will update that discussion later like I said.

As you may or may not know, most companies " the smart ones " try to stick with about the same config for all 600 of their pc's, so testing a method to get around a problem on 1 out of 600 will most likely work for the other 599 pc's in your deployment.

[volvic]

-{ Quote: "I'm currently removing Nod32 from over 600 PC's.

" }-

Really ...... let us know when you are done........

[cloneman]

NOD32 2.7 reaks awesomeness for older machines. I couldn't care less if it only blocked 1 virus in the world, the fact that it uses so little system resources is what made it popular. High detection rates are just a bonus :)

Some "fixing" was needed by the ESET team though since a modern rootkit can kill v2.7.