Robin said:
Well Kurt, you may be right. However, I've got this from a reasonable
source.
be that as it may, the command you quoted will not *remove* anything
other than protections on a certain file...
Also, I'm told that the reason I can't get rid of the Mersting file
is that it has been modified so that the permissions don't work, or words to
that effect. The calcs routine will restore these permissions and the file
can then be deleted.
so i've now seen...
This makes sense to me, except that I cannot get the calcs routine to 'go'!
try spelling it's cacls, instead... as in Change ACLs (Access Control
Lists)... also, the command you posted specified an invalid directory
name... no such creature as c:\windows32, but there is a
c:\windows\system32...
I've had this Mersting B file on my computer for yonks, and although it
doesn't seem to cause any harm I just don't want it there. Do you have a
better cure?
usually the product that detects it can also remove it... failing that,
the company that makes the product that detects it will probably have a
dedicated removal tool (you should actually look for the dedicated
removal tool first since they do a better job of removal)...
well, having googled it, i now see that the command you mentioned was
only one small part of what you need to do... you'll also need to
remove the registry entry that gets it loaded automagically when you
logon - you certainly won't be able to delete it after it's been loaded
(it will be locked by windows)...
take a look at
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=TROJ_AGENT.AC