From: David Kaye on
~BD~ <BoaterDave(a)hotmail.co.uk> wrote:

>BD knows that, sadly, a lot of David's friends died some years ago.
>When such things happen, it somewhat alters how one perceives things.

You make me sound friendless. I'd rather that you NOT make comments about my
personal life, lest you say things that will get misinterpreted. Since you
brought it up I now have to explain what you just said.

Yes, I lost about 6 dozen friends and acquaintances to AIDS in the 1980s,
and two boyfriends due to traffic accidents. Both were hit by oncoming
traffic.

But that was then and this is now. I have spent the better part of my life
organizing social communities. I travel in several social circles today,
which include jazz and bluegrass musicians, people who participate in Burning
Man and the Cacophony Society (you may already be a member), and people who
play board games and card games. I spend time with some of the dearest people
anyone can ever have the pleasure to know. So, don't feel sorry for me or
anything. I'm extremely lucky to have some really good friends.

From: Beauregard T. Shagnasty on
The Fake Truth Not-An-MVP wrote:

> You LIAR you stupid idiot troll you just proved to everybody why I have you
> in my sig Slacker.

<lol>

Being listed in your sig is like earning an Eagle Scout Merit Badge.

--
The Real Truth: http://www.google.com/search?q=pcbutts1+software+thief
*WARNING* Do NOT follow any advice given by the people listed below.
They do NOT have the expertise or knowledge to fix your issue. Do not
waste your time.
PCButtface1, The Not-Real Truth Not-an-MVP, fake-ms-mvp.org
From: Char Jackson on
On Sun, 04 Apr 2010 22:03:28 GMT, Dustin Cook
<bughunter.dustin(a)gmail.com> wrote:

>"FromTheRafters" <erratic(a)nomail.afraid.org> wrote in news:hpb21k$ltm$1
>@news.eternal-september.org:
>
>> "ASCII" <me2(a)privacy.net> wrote in message
>> news:4bb9db39.5432187(a)EDCBIC...
>>
>>> Keep pecking for the truth Dave, as a former electronics
>>> troubleshooter I've
>>> learned not to be distracted by a puff of smoke from some subsequently
>>> affected component that's not the primary cause of the issue at hand.
>>
>> I once blew some cigarrette smoke into a co-worker's UHF transceiver
>> (bench technincians). You shoulda seen his face when he turned back and
>> saw that gently rising smoke coming from the fan housing. :oD
>>
>> Sorry, just back from a walk down memory lane...
>
>HEHEHE.. you should do that when someone is adjusting the finals in a
>linear. A friend of mine has a texas star sweet 16 (I'm sure you both know
>what it is) and I blew smoke near him once when he was servicing one of the
>finals. you should have seen the expression on his face.

The *look* of the smoke would be enough to raise an eyebrow, but the
*smell* of it ought to be enough to realize very quickly that it's a
prank. Still, not bad.

From: Mumia W. on
On 04/04/2010 04:01 PM, David Kaye wrote:
> [...]
> I noted the file date/time and have looked back on this. The exploit appears
> to have come from foxnews, officedepot, or officemax -- the time stamps are
> within a few seconds of each other and show up right before the time stamp
> that was written to the temp directory in my documents and settings tree.
> [...]

See this:
http://www.broadbandreports.com/forum/r22225362-foxnewscom-infected~time=1240194878


From: ~BD~ on
Mumia W. wrote:
> On 04/04/2010 04:01 PM, David Kaye wrote:
>> [...]
>> I noted the file date/time and have looked back on this. The exploit
>> appears to have come from foxnews, officedepot, or officemax -- the
>> time stamps are within a few seconds of each other and show up right
>> before the time stamp that was written to the temp directory in my
>> documents and settings tree.
>> [...]
>
> See this:
> http://www.broadbandreports.com/forum/r22225362-foxnewscom-infected~time=1240194878
>
>
>
The last post in that thread was most telling! Viz:

"Please note people - you may think you removed it, but really did not.
Malwarebytes and others do not detect Rootkits. You should run
ROOTKITREVEALER. I thought I had cleaned this, and I had really not.
There was a deep and nasty rootkit involved here. Only way to remove was
to boot off a Windows CD, and delete hidden drivers. I would be willing
to bet that half the people think they clean this stuff and its not
really clean."

--
Dave