Re: Search and Destroy.



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.

<Pennywise@xxxxxxxxxxxxxx> wrote in message
news:uu3la2p4vvfd5s9if6v9bcuj29v31i59u1@xxxxxxxxxx
"Wiley Coyote - N2K" <mits_mvp@xxxxxxxx> wrote:

|>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.
|><Pennywise@xxxxxxxxxxxxxx> wrote in message
|>news:633la25fco1s8muc6pu85cva4kk3gkfm28@xxxxxxxxxx
|>> "Wiley Coyote - N2K" <mits_mvp@xxxxxxxx> wrote:
|>>
|>> |>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/
|>


--
http://absurdlycool.com/


.



Relevant Pages

  • Re: Search and Destroy.
    ... went back to the First Instance, deleted one file and the Second Instance ... "Group Deletes" still report the same error. ... |>Windows XP Pro, ...
    (microsoft.public.windowsxp.general)
  • Re: Title on taskbar changes to .exe name with multiple instances
    ... >When I start the first instance of my program, the taskbar shows the first N ... >But when I start a second instance of the program on Windows XP with the ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Search and Destroy.
    ... A temp file, one in use or non existent file is the most common reason ... |>went back to the First Instance, deleted one file and the Second Instance ... "Group Deletes" still report the same error. ...
    (microsoft.public.windowsxp.general)
  • Re: Passing arguments to a running application
    ... The second instance of your program is finding the first instance, ... WM_ACTIVATE to the first instance) and then exits. ... the first instance running, with whatever parameters it was initially ... Don't have it switch to ...
    (microsoft.public.pocketpc.developer)
  • Re: How kill process with Windows mobile 5 ?
    ... It is always better to keep first instance, than to kill it and create new ... I retrieve the PID enumerating processes with a Windev instruction too. ... Windows message to the first instance that ask it to close itself. ...
    (microsoft.public.pocketpc.developer)