It showed up during one of my periodic screwups playing with Win2000. It's
the same name and function as another system folder, and I only need one of
them. Honest. Really.

"Not to worry," I said, "I'll rename it (no problem) and then delete it
(hah)." No way. "<turdylittlefolder> is a Windows system folder and is
required for Windows to operate. It cannot be deleted."

"Not to worry," I said, "I'll delete it in DOS." (This dual boot Win 2K
system uses FAT32 just for such contingencies.) I rebooted to a Windows ME
DOS diskette. No way. DOS wouldn't touch it. "You are mean, evil, and nasty
for even *thinking* such a dastardly thing," it tch-tched.

"Not to worry," I said, "I'll use GiPo@MoveOnBoot and set the little $%$##!!
to self destruct at the next reboot. *Nothing* can survive GiPo." I
rebooted. Success! Gone! I lit a candle to the system folders god. Human is
still superior to machine!

But it was only gone for a while. Occasionally it shows up again. I zap it.
It's gone for a day or two (just until I forget about it), then it's back.

"Not to worry," I said, "I will ask the gurus of the Win2K newsgroup.
*They'll* know what to do."

*Do* you gurus know what to do? Please?

Thanks. :-)

"Walter Donavan" <(E-Mail Removed)> wrote in message
news:%23%(E-Mail Removed)...
> It showed up during one of my periodic screwups playing with Win2000. It's
> the same name and function as another system folder, and I only need one
of
> them. Honest. Really.
>
> "Not to worry," I said, "I'll rename it (no problem) and then delete it
> (hah)." No way. "<turdylittlefolder> is a Windows system folder and is
> required for Windows to operate. It cannot be deleted."
>
> "Not to worry," I said, "I'll delete it in DOS." (This dual boot Win 2K
> system uses FAT32 just for such contingencies.) I rebooted to a Windows ME
> DOS diskette. No way. DOS wouldn't touch it. "You are mean, evil, and
nasty
> for even *thinking* such a dastardly thing," it tch-tched.
>
> "Not to worry," I said, "I'll use GiPo@MoveOnBoot and set the little
$%$##!!
> to self destruct at the next reboot. *Nothing* can survive GiPo." I
> rebooted. Success! Gone! I lit a candle to the system folders god. Human
is
> still superior to machine!
>
> But it was only gone for a while. Occasionally it shows up again. I zap
it.
> It's gone for a day or two (just until I forget about it), then it's back.
>
> "Not to worry," I said, "I will ask the gurus of the Win2K newsgroup.
> *They'll* know what to do."
>
> *Do* you gurus know what to do? Please?
>
> Thanks. :-)
>

Sounds like some spyware stuff. Download & install AdAware to
clean your machine. You can also create a file of the same name
as the rogue folder and give it a read-only attribute. This will prevent
a folder of the same name from being created.

Hi Pegasus,

As sometimes happens, posting to a newsgroup gives me the answer before I
get a reply, and I then wish I hadn't posted to the newsgroup, but I
wouldn't have gotten the answer if I hadn't posted, etc. :-(

It was simple. I moved the little booger from my W2K system to my WME
system. DELTREE took care of it from there. Adios, baby.

Rename same as rogue folder. That's great! We tend to
make things more complicated than they need to be. I'm
filing this one away in my 'hints' file. Thanks Pegasus!
>-----Original Message-----
>
>"Walter Donavan" <(E-Mail Removed)> wrote in message
>news:%23%(E-Mail Removed)...
>> It showed up during one of my periodic screwups playing
with Win2000. It's
>> the same name and function as another system folder,
and I only need one
>of
>> them. Honest. Really.
>>
>> "Not to worry," I said, "I'll rename it (no problem)
and then delete it
>> (hah)." No way. "<turdylittlefolder> is a Windows
system folder and is
>> required for Windows to operate. It cannot be deleted."
>>
>> "Not to worry," I said, "I'll delete it in DOS." (This
dual boot Win 2K
>> system uses FAT32 just for such contingencies.) I
rebooted to a Windows ME
>> DOS diskette. No way. DOS wouldn't touch it. "You are
mean, evil, and
>nasty
>> for even *thinking* such a dastardly thing," it tch-
tched.
>>
>> "Not to worry," I said, "I'll use GiPo@MoveOnBoot and
set the little
>$%$##!!
>> to self destruct at the next reboot. *Nothing* can
survive GiPo." I
>> rebooted. Success! Gone! I lit a candle to the system
folders god. Human
>is
>> still superior to machine!
>>
>> But it was only gone for a while. Occasionally it shows
up again. I zap
>it.
>> It's gone for a day or two (just until I forget about
it), then it's back.
>>
>> "Not to worry," I said, "I will ask the gurus of the
Win2K newsgroup.
>> *They'll* know what to do."
>>
>> *Do* you gurus know what to do? Please?
>>
>> Thanks. :-)
>>
>
>Sounds like some spyware stuff. Download & install
AdAware to
>clean your machine. You can also create a file of the
same name
>as the rogue folder and give it a read-only attribute.
This will prevent
>a folder of the same name from being created.
>
>
>.
>