The poster ONLY posted this tidbit...
"I keep getting the IEXPLORE.exe is not working. I cannot
get into "My Computer" or "Search" for my files. I
recently cleaned a virus out of my computer. Can anyone
help? Thanks"
If she cleaned the virus, then she has a virus product installed. Knowing the AV product
and knowing the name of the virus are important because AV companies have removal
information on their respective web sites. Knowing both the virus and the AV vendor can
also lead to a possible utility that can fix the problems the virus caused. For example,
Symantec posts MANY removal tools that will remove and fix the damage performed on a PC and
is located at
http://securityresponse.symantec.com/avcenter/tools.list.html
I did not make up the term Safe Hex. This is industry wide terminology.
I did not call the poster dumb, I stated "Posting; "Problems after virus", and stating
"...recently cleaned a virus..."
and asking for help is really, really, dumb!" Based upon that little information in
severely insufficient to cure the three problems noted by the poster.
OK I'm rude -- now what have YOU done to help Jenny ?
"adcb"
| People get infected all the time by new viruses that have not been
| fixed by the various av companies. it happens nothing to do with being
| dumb, just unlucky
Luck has nothing to do with being infected. Receiving yes, being infected means that good
computing practices were not adhered to, thus thae actions of the PC user was the fault, and
not a matter of luck.
| >She posted "Problems after virus", and stated "...recently cleaned a virus..."
| >without stating what was supposedly cleaned - dumb !
| >
| You clean a virus, your AV software does it all, some people do not
| bother to look what it is, unlike like analy retentive people like
| you.
I am a Computer Analyst, doesn't that itself infer anal retentiveness ? I have been curing,
removing and dealing with computer viruses since I wiped out the "Jerusalem.B" on a Netware
v2.11 LAN in 1988.
| >She did not sate what was used to "clean" the virus - dumb !
|
| does not really matter though, she wants to know if the iexplore.exe
| files can be repaired. they are knackered, does not really matter why,
| she is looking for a solution
Yes -- It does. The product needs to be known in addition as to what was done to "clean"
the virus. What was the cleaing process ? Delete ? Rename ? Quarantine ? What was "cleaned
" an EXE a DLL ? Again knowing the infector and the AV product is important.
| >She posts a virus question in a Win2K forum - dumb ! { That's what
| >'alt.comp.virus' and 'alt.comp.anti-virus' are for }
|
| Err let us see who is the dumb one here, the problem is with Iexplore
| which if i remember rightly is part of Win2000, not a virus or
| antivirus software component. Again it is knackered, as to why is not
| a major concern, it is how to fix it from here that is.
Acttually, IExplore.exe is an Internet Explorer component and NOT part of Win2K. The same
program can be found on; Win9x/M, NT4, Win2K, WinXP and Win2003. The focal point of support
is the virus. Not the file. If the application FooBar is running on Win2K and it is
havinfg specxific problems, the first place to obtain help is from FooBar not a Win2K forum.
You can't fix something unless you know what the problem was. Once you know the infector,
you know what the infector did to the platform. For example, renname files, delete files,
modify the Registry, load trojans, etc.
| >I chose my words carefully and I stated the facts. Others must learn from her
| >mistakes. As the saying goes ...
| >"Be careful when you ask a question, you may not get the answer you are looking
| >for or expected."
| >
| >Rude ? It's a matter of opinion.
I actually asked very pertinent questions. What is really rude is when people post a query
and *NEVER* return to their post and provide additional information, ask questions of their
own, or even acknowledge the fact that somebody even tried to help. I can't tell you how
many posts I have read and or replied to where the OP *never* returned back to their post.
Mr. Lipman