Problem: Using BoClean 3.11 with Nod32 v 1 or 2 causes my Win XP's power management to fail (will not go into standby at predetermined interval). History: I used Nod32 v. 1 and BoClean 3.10 together for almost a year with no problems. In trouble-shooting this problem with BoClean 3.11, I inquired through Nod32. I got little to nothing in the way of an enlightening answer. I also inquired through BoClean and, after getting some very specific answers, was advised to configure Nod32 v 2 to exclude the BoClean directory and one of its files. When I did that, the machine went into standby at the preset interval. When I rebooted, it didn't go into standby any longer at the preset interval. (NOTE: I configured Nod32 v2 to SAVE the directory and file exclusion info, but it didn't, which suggests a possible bug in the file exclusion program.) Without going into a "he said/she said" scenario, ESET offered no information whatsoever about this problem, and BoClean stated that the problem lay with Nod32, offering me some very specific programming issues that I am not free to disclose here. A couple of weeks ago, my ESET license ran out without this problem's ever getting resolved. I am now using McAfee 8.0 (power management works fine with BoClean). My Hope: I'd like to find a way to "come back" to Nod32 and continue to use BoClean (sans McAfee), but in order to do that, I need ESET to show some initiative and look into this matter. My earlier discussion with ESET was anything but helpful in this regard. Your thoughts?