RockyTSquirrel
Mon Mar 10 07:17:49 PDT 2008
Heirloom,
I think your all getting you chain pulled..
just block the Nellie from your puter..
That should remove the problem for the moment.. :-)
RTS
"Heirloom" <nobodyhome@noplacelike.hom> wrote in message
news:ebwQGwlgIHA.5280@TK2MSFTNGP04.phx.gbl...
> Obviously, Nellie, you missed this from one of your previous threads. I
> shall resubmit it for your perusal:
>
> Nellie,
> Nobody here is trying or wanting to hurt you, in fact, many have
> made 'out-of-their-way' attempts to help you! I remind you that YOU did
> your share of false accusations and name calling, so, let's just drop that
> part.
> Your last post displays progress, good for you. Whole words are
> much easier to interpret. Now, release your CAPS lock and let's start
> working on some punctuation to go along with the wonderful whole words
that
> we now know you are capable of!
> If you truly want help, you must start by helping
yourself......and
> I am most serious about this! The first step for you will be to read and
> comply with the 'rules of posting' that I have copied from the aumha.org
> website, written by Mr. Jim Eshelman.
> Jim is one of the best in the business. This forum has a large
> number of very professional, knowledgeable, understanding, patient and
> helpful people you will ever find in one place! You want help....this is
> your help. Use it well, it is your key to all the help you will ever need
> regarding computers.
>
> Newgroup Rules:
> a.. Do some research first...
> a.. Consult the online Help and the manual.
> b.. Search the Internet, put key words about the problem into a Search
> Engine like DTS-L Fast Search.
> c.. If you still can't find the answer, post to Microsoft Product
> Support Newsgroups.
> d.. First use the "Find" function on the newsreader to locate other
> messages about the problem.
> e.. Or use this Advanced Group Search Utility designed to filter the
> vast amount of information found on the WWW.
> b..
> Decide where to post...
> a.. Post to one general group if you are not sure which group applies,
> ask where the best place is to ask your question.
> c.. How to compose your post...
> a.. Create a new message, don't post a question of your own in
response
> to another question.
> b.. Make the "Subject line" a short, relevant synopsis of your
problem.
> c.. Before going into detail, clearly summarize the problem.
> d.. Make a concise, clear description of the problem.
> e.. Unless multiple problems seem related, do not mix them together,
> make separate posts.
> f.. If you are getting error messages, include the exact text in the
> error message. If there is a "Details" button, click it and copy/paste the
> error message itself into the post. If you are using Windows Millennium
> Edition (Windows Me) press Atl+D to bring up the detailed error message.
For
> XP, if there is an Event ID and Source, include it as well.
> g.. Tell if an error occurs when doing some action or using some
> particular software.
> h.. What changed in your system shortly before the problem occurred?
> Knowing about a setting change or added software or hardware may be
helpful
> in solving the problem.
> i.. Briefly describe your machine, video card, CPU, amount of RAM,
hard
> drive size and amount of free space.
> j.. Identify clearly the steps and procedures you have already used to
> try to fix the problem.
> k.. Proof-read and spell-check the post before sending.
> d.. After you post...
> a.. Be patient waiting for a response, it may take a couple of days or
> more before the right person sees the question.
> b.. You should carefully assess any advice you get. If there is bad
> information in a posted response, someone will almost always correct it.
Ask
> for clarification if you aren't certain.
> c.. If you don't get a response, it is probably because either the
> answer is unknown, perhaps your question was not understood or the
> information originally provided was not clear enough. If this occurs,
> posting an amended question could produce a better result.
> d.. Once your problem is solved...
> a.. It is useful to post back to the group afterwards, saying
thanks
> and that a suggestion worked (or not). That tells the group if it is a
> useful solution.
> e.. Survival Camp: posting errors to avoid...
> a.. Don't ask for an email reply unless absolutely necessary, and
then
> follow up to the group with a summary.
> b.. Avoid cross-posting, unless your problem clearly fits the
category
> of more than one group.
> c.. Never post separate identical messages to several newsgroups.
This
> wastes respondents' time, and may result in you being ignored.
> d.. Don't attach screen shots or files. If you believe a screen shot
> or file is critical to understanding your problem, advise that it exists
and
> offer to send it.
> e.. Don't post in ALL CAPITALS, it's too hard to read
> f.. Remove unnecessary included text from replies.
> g.. Use punctuation.
> h.. Stick to plain text, use html format only if necessary to
explain
> your problem. The stationery groups are exceptions to this.
> i.. Avoid poor subject lines like these:
> a.. HEEEELLLLLLLPPPPPPPPP!!!!!!!!!!!!
> b.. any experts around here?
> c.. <Name of person> EMAIL ME!!!
> d.. need help please
> e.. Bill Gates is the Devil
> f.. idontknowwhattodomycomputerquit
> g.. Read the Microsoft Rules of Conduct
> Heirloom, old and more than willing to help without hurt
> "nellie" <nellie@______.com> wrote in message
> news:OAumvykgIHA.5280@TK2MSFTNGP04.phx.gbl...
> > thats the prg
> >
> > thnx 4 hlpn me
> >
> > my folks r poor
> > puter was given 2 me
> > i go to unlv
> >
> > tryin hrd 2 get by
> >
> > nellie
> >
> > "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
> > news:u3aOM3jgIHA.4396@TK2MSFTNGP04.phx.gbl...
> >> From: "webster72n" <webster72n@gmail.com>
> >>
> >> | "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
> >> | news:%2345ckLjgIHA.1212@TK2MSFTNGP05.phx.gbl...
> >> >> From: "nellie" <nellie@______.com>
> >> >>
> >> |>> eav antivirus 4 win me
> >> |>>
> >> |>> good or bad
> >> |>>
> >> >> Please define "eav antivirus".
> >> >>
> >> >> What is "eav" ?
> >> >> Do you have a link ?
> >> |
> >> |
> >
http://www.download.com/EAV-Antivirus-Suite-Free-Edition/3000-2239_4-10358025.html
> >> |
> >>
> >>
> >> Thank you but, we don't know if this is what Nellie is referring to.
> > Nellie needs to
> >> respond.
> >>
> >> I can say one thing, if it is what you posted, it is *Chinese malware*
!
> >>
> >>
http://www.virustotal.com/analisis/93a1991fac4c56ea0b167db8b158b620
> >>
> >> File Anti-Virus.exe received on 03.09.2008 23:45:43 (CET)
> >>
> >> Antivirus Version Last Update Result
> >> CAT-QuickHeal 9.50 2008.03.08 (Suspicious) - DNAScan
> >> eSafe 7.0.15.0 2008.03.09 Suspicious File
> >> Ikarus T3.1.1.20 2008.03.09 Backdoor.Pigeon.194
> >> Prevx1 V2 2008.03.09 Heuristic: Suspicious File With Anti-Security
> > Technology
> >> VBA32 3.12.6.2 2008.03.05 suspected of Trojan-PSW.Lmir.60 (paranoid
> > heuristics)
> >>
> >> Additional information
> >> File size: 178176 bytes
> >> MD5: 263e1285e21a89486ee1fc1ac0893040
> >> SHA1: 06a2b1c6412772e8d1815c2e9f56cbdde61206fe
> >> PEiD: PECompact 2.xx --> BitSum Technologies
> >> packers: PecBundle, PECompact
> >> packers: PE_Patch.PECompact, PecBundle, PECompact
> >> Prevx info:
> >
http://info.prevx.com/aboutprogramtext.asp?PX5=721D2CCF002EC148B8AA02037C7A360046EE5E72
> >>
> >>
http://www.virustotal.com/analisis/60c80cfe1c55583dfb2a3cc98b14fead
> >>
> >> File Contact.exe received on 03.10.2008 00:17:05 (CET)Antivirus Version
> > Last Update Result
> >>
> >> CAT-QuickHeal 9.50 2008.03.08 (Suspicious) - DNAScan
> >> eSafe 7.0.15.0 2008.03.09 Suspicious File
> >> F-Prot 4.4.2.54 2008.03.09 W32/Heuristic-162!Eldorado
> >> Ikarus T3.1.1.20 2008.03.09 Trojan.Win32.Agent.app
> >> Panda 9.0.0.4 2008.03.09 Suspicious file
> >> Prevx1 V2 2008.03.10 Heuristic: Suspicious Self Modifying EXE
> >> Sophos 4.27.0 2008.03.09 Sus/Dropper-A
> >> Webwasher-Gateway 6.6.2 2008.03.09 Win32.Malware.gen#PECompact!92
> > (suspicious)
> >>
> >> Additional information
> >> File size: 38912 bytes
> >> MD5: 1ba66f3e31b80d9e2804ea762ce92e32
> >> SHA1: ac2384c4adcfcee1c68569103a0c01d15b0bf3d9
> >> PEiD: PECompact 2.xx --> BitSum Technologies
> >> packers: PecBundle, PECompact
> >> packers: PE_Patch.PECompact, PecBundle, PECompact
> >> Prevx info:
> >
http://info.prevx.com/aboutprogramtext.asp?PX5=2A86A5A900F4BCF898B7003C9B7CF100AB625A34
> >>
> >> From their web site...
> >>
> >> Trojan Guarder Gold
> >>
> >>
http://www.virustotal.com/analisis/260d14bbac5594ef0dc592cca5315b1a
> >>
> >> File Trojan_Guarder.exe received on 03.10.2008 00:22:02 (CET)
> >>
> >> CAT-QuickHeal 9.50 2008.03.08 (Suspicious) - DNAScan
> >> eSafe 7.0.15.0 2008.03.09 Suspicious File
> >> Prevx1 V2 2008.03.10 Heuristic: Suspicious File With Code Injection
> > Technology
> >> VBA32 3.12.6.2 2008.03.05 suspected of Trojan-PSW.Lmir.60 (paranoid
> > heuristics)
> >>
> >>
> >> Additional information
> >> File size: 217088 bytes
> >> MD5: c11294fe0d95f5925af379eab8e8e361
> >> SHA1: dd6684b14454b331dd204b4f7f751bbe4356299f
> >> PEiD: PECompact 2.xx --> BitSum Technologies
> >> packers: PecBundle, PECompact
> >> packers: PE_Patch.PECompact, PecBundle, PECompact
> >> Prevx info:
> >
http://info.prevx.com/aboutprogramtext.asp?PX5=E59947B000783D8E503903C524A9DC00A7C23F1F
> >>
> >>
> >> --
> >> Dave
> >>
http://www.claymania.com/removal-trojan-adware.html
> >> Multi-AV -
http://www.pctipp.ch/downloads/dl/35905.asp
> >>
> >>
> >
> >
>
>