It did that because you don't know what you are doing. The only it copies
from backup locations is wininet.dll and it is checked before it copies it.
If it copied a bad file then you modified it wrong because you don't know
what you are doing. Leave it alone.

--

Newsgroup Trolls. Read about mine here http://www.pcbutts1.com/downloads
The list grows. Leythos the stalker http://www.leythosthestalker.com, David
H. Lipman, Max M Wachtell III aka What's in a Name?, Fitz,
Rhonda Lea Kirk, Meat Plow, F Kwatu F, George Orwell



"Dustin Cook" <spamfilterineffect.see.sig@nowhere.com> wrote in message
news:Xns98B1F018CAFDBHHI2948AJD832@69.28.186.121.. .
> "pcbutts1" <pcbutts1@leythosthestalker.com> wrote in
> news:kICdnVt50vivJzzYnZ2dnUVZ_vShnZ2d@giganews.com :
>
>> Look I'm not going to sit here and argue assembly language with you or
>> anybody. It won't do any good your mind is already made up. You are
>
> I wasn't attempting to start an Argument, I simply wanted an idea of your
> .. ehh, programming skillset. Since you wouldn't even take a guess, nor
> do you apparently know how to cheat and just look up the routines, you
> want to play word games instead; It makes me really suspect you are,
> generally speaking, full of ****, AND, a code thief.
>
>> starting to sound like Nick. If you want to argue with someone then
>> argue with Leythos the stalker he claims to be a programmer he
>> probably modified your code. It was not me. Ask leythos the stalker
>> what happened to his Newsfeed account.
>
> That's the thing, the code itself isn't modified, only a couple of my
> text strings, and only partially. Btw, the person whom did the hex
> editing disabled one of the logging commands...Another reason you should
> only download programs from the author. They tend to work as designed
> that way.
>
> Your spyerase program is a garbled together patch job of other people's
> work. It doesn't do everything you've said, either. No backups, no
> renaming, just deletion and possibly replace if you can find what you
> call a clean backup. I've done a silly test with your program. I made it
> look for a file it thought was bad, due to your stupid method of
> detection (filenames only) and guess what? It replaced the "bad" file
> with a byte for byte duplicate it thinks is clean, simply because of the
> folder in which it found the copy!
>
> BugHunter is by no means perfect, It can/does/has suffered from false
> alarms, but that's certainly NOT due to some silly "if file says
> britneystits.exe" it MUST be bad.
>
>
> --
> Dustin Cook
> Author of BugHunter - MalWare Removal Tool -V2.0
> web: http://bughunter.it-mate.co.uk
> email: bughunter.dustin@gmail.com.removethis
> Last updated: January 4th, 2007