WE Search Problem

Search using Companion

Win XP Pro is up to date.

Keep getting a message that stops searching.

something about a Volume missing.
I get several during a search on a HDD.

(SYSTEM IS ABOUT TO CRASH SO I AM SENDING THIS MESSAGE NOW)

What causes this and how to avoid?

And when I click STOP it does not stop so I have to hit the close box. Why?

Running it again finds nothing it found before. What is going on?

Also when I hit the close button (upper right corner) it wants to crash
WE and that mean crashing Windows. RATS !!!

On 12 Aug 2016, Searcher wrote in
microsoft.public.windowsxp.general:

Search using Companion

Win XP Pro is up to date.

Keep getting a message that stops searching.

something about a Volume missing.
I get several during a search on a HDD.

(SYSTEM IS ABOUT TO CRASH SO I AM SENDING THIS MESSAGE NOW)

What causes this and how to avoid?

And when I click STOP it does not stop so I have to hit the close
box. Why?

Running it again finds nothing it found before. What is going on?

Also when I hit the close button (upper right corner) it wants to
crash WE and that mean crashing Windows. RATS !!!

Sorry - I don't know what either "WE Search" or "Companion" are. Third-
party search utilities perhaps? Do they have their own support forums?

Maybe you have hard disc or file system corruption. Have you run
CHKDSK?

Nil wrote:
On 12 Aug 2016, Searcher wrote in
microsoft.public.windowsxp.general:

Search using Companion

Win XP Pro is up to date.

Keep getting a message that stops searching.

something about a Volume missing.
I get several during a search on a HDD.

(SYSTEM IS ABOUT TO CRASH SO I AM SENDING THIS MESSAGE NOW)

What causes this and how to avoid?

And when I click STOP it does not stop so I have to hit the close
box. Why?

Running it again finds nothing it found before. What is going on?

Also when I hit the close button (upper right corner) it wants to
crash WE and that mean crashing Windows. RATS !!!

Sorry - I don't know what either "WE Search" or "Companion" are. Third-
party search utilities perhaps? Do they have their own support forums?

Maybe you have hard disc or file system corruption. Have you run
CHKDSK?

This is the same poster as the previous thread,
only using a different news server. The poster in
the previous thread, did not respond to the answers given.

*******

WE = File Explorer

Search Companion text string can be seen here.

https://s9.postimg.org/vab4wyahb/search.gif

"Crashing" File Explorer does not cause Windows to crash.
A new copy of File Explorer will open if the previous
instance crashes. If Dr.Watson dialogs are seen on
the screen, do your best to dismiss them. If File Explorer
doesn't return, do control-alt-delete and bring up
the Task Manager.

In Task Manager, you may see two instances of DRWATSON, one
which uses very little memory. Using Task Manager, kill the
little one, and both instances of DRWATSON should disappear.
Seconds later, a new File Explorer appears (now, you can
use the computer again). Dr.Watson should disappear on its own,
but it doesn't in these cases, and needs to be
"eased off the stage" with Task Manager.

File Explorer can *hang*, resulting in a lost
session. But only if you lose the ability to use
Task Manager, have you completely lost control. So
if the HID (human interface, keyboard input) path
dies, are you completely screwed. To test this, press
the shift-lock key - if the keyboard LED continues to
light up and un-light, as you press the shift-lock,
that proves the machine still parses keyboard input.
Then, a control-alt-delete should work.

*******

The OP has a mapped drive which is not responding
or something similar. A file search may search in
more places than are seen in Disk Management. Clearing
out any defunct mounts would be important to making
the search work faster.

And Windows does have some weird corner cases. I have
File Explorer crashing on me right now, in shell32.dll
Ordinal 65. As near as I can tell, it's having trouble
with some volume on my machine. A machine that includes
a DataRAM RAMDisk. RAMDisks normally do not carefully
emulate all the characteristics of normal volumes,
so just about any critical data field could be
missing from some descriptor. But the path to setting
up the crash is a long one, a kind of latent fault,
and it can take all day before File Explorer
decides to take a tumble. Since Task Manager works
to manage the problem, this is mainly a nuisance.

Paul

On 12 Aug 2016, Paul wrote in
microsoft.public.windowsxp.general:

This is the same poster as the previous thread,
only using a different news server. The poster in
the previous thread, did not respond to the answers given.

I predict he won't respond to these, either.

*******

WE = File Explorer

Search Companion text string can be seen here.

https://s9.postimg.org/vab4wyahb/search.gif

Ah, so. I've never seen or used that acronym. Or used Windows search,
for that matter, especially with XP.