Search and Destroy.

[Wiley Coyote - N2K]

Windows XP Pro, all the latest updates/sp etc. I do a Windows Search for
let's say README.*. Windows Seach finds all the files, I then try to "MASS
DELETE" and Windows responds with "Unable to read from source disk".

I can delete them one at a time (or even a few at a time).

Sometimes, Windows responds with "Nothing to do", then the file(s) are
deleted.

These files are located (for example) in Docs & Setting, Desktop, Temp etc.

I installed FileLocatorPro and do the same thing and all is well. I would
imagine that this is a Windows Search Thingy???

This is not a life and death issue, just more curosity than anything else.

Anyone know why?

Thanks.

 

[Pennywise]

|>Windows XP Pro, all the latest updates/sp etc. I do a Windows Search for
|>let's say README.*. Windows Seach finds all the files, I then try to "MASS
|>DELETE" and Windows responds with "Unable to read from source disk".
|>
|>I can delete them one at a time (or even a few at a time).
|>
|>Sometimes, Windows responds with "Nothing to do", then the file(s) are
|>deleted.
|>
|>These files are located (for example) in Docs & Setting, Desktop, Temp etc.
|>
|>I installed FileLocatorPro and do the same thing and all is well. I would
|>imagine that this is a Windows Search Thingy???
|>
|>This is not a life and death issue, just more curosity than anything else.
|>
|>Anyone know why?

Your trying to delete from the temp directory - if you can' the file
is in use or has been deleted since the search was perform'd, and it
stops the whole process

 

[Wiley Coyote - N2K]

Okay good. So how come I can delete them One at a Timte or in Smaller
Groups? This is what I'm confused about.

BTW: Before replying to this, I ran a second instance of Search (for the
same files as the First Instance). Obviously they would be the same. I then
went back to the First Instance, deleted one file and the Second Instance
dynamically upates itself (which is what I would expect). However, Group
Deletions (in Either Instancees) reported the same message. So, being a
diligent as possible, I went to the Second Instance of Search, re-ran it and
the file list was identical to the First Instance.

In the First Instance, I deleted a file - the Second Instance updated
Dynamically. BUT, "Group Deletes" still report the same error.

Hmmm - you see my delima?

Thanks,

Wiley.

 

[Pennywise]

|>Okay good. So how come I can delete them One at a Timte or in Smaller
|>Groups? This is what I'm confused about.

A temp file, one in use or non existent file is the most common reason
for your complaint.

Reading below you might be screwing with the auto update so badly it's
can't handle it :}

I read an earlier post of someone making a thousand folders just
because they could, then having problems because of it...

No help from here otherwise...

|>BTW: Before replying to this, I ran a second instance of Search (for the
|>same files as the First Instance). Obviously they would be the same. I then
|>went back to the First Instance, deleted one file and the Second Instance
|>dynamically upates itself (which is what I would expect). However, Group
|>Deletions (in Either Instancees) reported the same message. So, being a
|>diligent as possible, I went to the Second Instance of Search, re-ran it and
|>the file list was identical to the First Instance.
|>
|>In the First Instance, I deleted a file - the Second Instance updated
|>Dynamically. BUT, "Group Deletes" still report the same error.
|>
|>Hmmm - you see my delima?
|>
|>Thanks,
|>
|>Wiley.
|>|>>
|>> |>Windows XP Pro, all the latest updates/sp etc. I do a Windows Search for
|>> |>let's say README.*. Windows Seach finds all the files, I then try to
|>> "MASS
|>> |>DELETE" and Windows responds with "Unable to read from source disk".
|>> |>
|>> |>I can delete them one at a time (or even a few at a time).
|>> |>
|>> |>Sometimes, Windows responds with "Nothing to do", then the file(s) are
|>> |>deleted.
|>> |>
|>> |>These files are located (for example) in Docs & Setting, Desktop, Temp
|>> etc.
|>> |>
|>> |>I installed FileLocatorPro and do the same thing and all is well. I
|>> would
|>> |>imagine that this is a Windows Search Thingy???
|>> |>
|>> |>This is not a life and death issue, just more curosity than anything
|>> else.
|>> |>
|>> |>Anyone know why?
|>>
|>> Your trying to delete from the temp directory - if you can' the file
|>> is in use or has been deleted since the search was perform'd, and it
|>> stops the whole process
|>>
|>> --
|>> http://absurdlycool.com/
|>

 

[Wiley Coyote - N2K]

Thanks. I'm convinced it's a Windows thing, primaril because FileLocatorPro
works just fine. I'm going to dig a little more (just cause I "Need to
Know".

Cheers.

ps: I'll post anything relavent that I find.

 

[Wiley Coyote - N2K]

By Gawd. It looks like a Windows Indexing issue. I truned off Windows
Indexing for the entire hard drive, did a search (slow...) and then nuked
all the files found in the Search Window. All worked well.

Here are the steps I then took to try to duplicate:

1) I then turned on Indexing, re-ran Search and all was well!!!
2) Turned off Indexing,
3) I created 200 copies of Readme.Txt (just cause). I then distrubuted them
across the hard disk,
3) Shutdown,
4) Restarted and turned on Indexing. Waited some time,
5) Ran Search again and tried to nuke multiple files - the error message
resurfaced,
6) Turned off Indexing, and all was well,
7) Turned it back on and the same messages appeared again.

So then, a colleque suggested that I stop MS SQL 2K and try again. All was
well and after repeating the above steps 5 times, I have to assume it's an
MS SQL and Indexing issue.

Reapplied SQL SP 4 and now all is well.

WIley.

 

[NoStop]

Thanks. I'm convinced it's a Windows thing, primaril because
FileLocatorPro works just fine. I'm going to dig a little more (just cause
I "Need to Know".

Cheers.

ps: I'll post anything relavent that I find.

When you do finally find out why this toy operating is so brain-dead in so
many ways, do let us know. We'd all like to find out why MickeyMouse
unleashed this on the buying public and why most Windoze users haven't yet
figured out that they've been had.

--
The ULTIMATE Windoze Fanboy:

http://video.google.com/videoplay?docid=-2370205018226686613

A 3D Linux Desktop (video) ...

View Some Common Linux Desktops ...
http://shots.osdir.com/