| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 30532 | 2003-02-22 07:46:00 | AdAware 6 and new.net - a warning!!! | Robin S_ (86) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 123149 | 2003-02-22 07:46:00 | There is some stuff around about AdAware 6 that people need to know about. If an AA 6 scan ever comes up with a find on new.net or new.dot.net or similar DON'T let AdAware fix it. Similarly, if you recommend the prog to anyone else pass on that warning to them. New*.net is stealthware that comes/came with things like Go!zilla, some of the Real* group and Kazaa + others. New.net has something to do with domain server redirecting because the people behind it have created some new domain names that regular DNSs don't recognise. The problem is the interaction of AdAware and new.net (which apparently interferes with Winsock2). New.net can only be safely uninstalled by using a specific non-standard procedure - it is apparently designed to be resistant to removal. When AdAware 6 attempts to remove it it does not use the special procedure as a result it completely nobbles Windows start-up. This condition is almost impervious to recovery except by reformatting the Windows partition and reinstalling. AdAware 5 did not have the problem but I don't know whether it dealt with new.net. Part of the problem is that the Adaware people and the new.net people each say that the fault, and therefore the responsibility for designing a fix, lies with the other side. If you want to know more go to the user forum on the Adaware site http://www.lavasoft.de and look at the (5-page!) thread entitled "Adaware 6 ruined my computer!". For info on a claimed fix look up the thread called "Windows XP - Winsock issues and fix". Spybot apparently does not have this problem but I don't know if it deals to new.net |
Robin S_ (86) | ||
| 123150 | 2003-02-22 11:14:00 | I had encountered the problem with NewDotNet. The spybot only remove some of them. You have to remove them manually from registry. Thank you.(_)(_) |
chinadoll (682) | ||
| 123151 | 2003-02-22 22:55:00 | Thanks Robin S, I read about 4 of the 5 pages on the thread"AdAware has ruined my computer"late last night,but today it looks as if the Lavasoft admin have removed it?(Odd goings-on!) Iwould also recommend that anyone who has NDN,have a read here; cexx.org before trying to delete it! Not sure what Lavasoft is doing about prob,but a lot of their users are getting agro and will be trashing the app! Cheers,Kiwitas,;-) |
Kiwitas (514) | ||
| 123152 | 2003-02-23 06:27:00 | Interesting, Kiwitas - I successfully logged on to the AdAware thread about midmorning today. It had been added to since last night - much slagging-off, unfortunately, but a sprinkling of useful stuff. Have you read this thread, though - pressf1.pcworld.co.nz Dataminers in Spybot! Where do we turn now? |
Robin S_ (86) | ||
| 123153 | 2003-02-24 07:41:00 | Hi again Robin S, Got back to the rest of that thread OK and also a few more on the same topic(NDN versus AdAware) It now appears that problem was only with AdAware 6.0 ver 160? version 162 solved it(A pity AdAware didn't tell anyone!) A lot of members of other Forums are using AdAware and SpyBot side by side but think I will just stay with AdAware as it is user friendly and seems as efficient as the old 5.83! Cheers,Kiwitas,;-) |
Kiwitas (514) | ||
| 123154 | 2003-02-25 10:30:00 | A bit of an update. There is a degree of inconsistency in the information given on various threads on the AdAware forum, but in one recent posting one of the Lavasoft top guns had this advice on using AA 6 - Because of the problems that can result from the improper removal of the new.net and similar files, the latest (from about 17/2/03, I think) ref files for AA 6 MUST NOT be used with build 160 - only with build 162. His recommendation is that before running AA 6 you should check with Lavasoft for the latest build number as well as the latest ref files to ensure compatibility between the ref files and the base prog. The reason for checking specifically with Lavasoft is that the mirror sites are not always up with the play, although there is no harm in downloading from them if they have the latest stuff. There don't seem to be any reports of system crashes with the 162/latest ref file combination. |
Robin S_ (86) | ||
| 1 | |||||