Locate32 is driving me Crazy!

  • Thread starter Thread starter Howard Schwartz
  • Start date Start date
H

Howard Schwartz

At first I liked the thing - almost instant list after requesting a file
find, handy context mention to do various things with what you find (sort
of wish there were buttons for some like view, goto its directory, etc.),
quickly updatable database for filenames. Beats ordinary Find by a mile.

Then it started to happen: I would try to close locate32 without having
done anything special. Up comes a windows error screen telling me locate32
did something illegal and would be ``closed down'' . True true but sneaky:
locate32 closes OK but not the window with the error message. Nothing
closes it, not the task monitor, not my favority process monitor and
killers. It just stays on the screen and annoys you.

Want to know details the error screen says? Sure, it tells you locate32
causes some error in the kernal within memory.

Then you try to close windows and suddenly nots of things are non
responsive. YOu can ot do it and are forced into a hardware shutdown,
requiring the auto running of scandisk when you reboot -- again and again
and again and again.

I wrote the author -- no response.

I googled on the problem - and found post after post after post of others
who had the same intermittent problem with locate 32. One gave up in
exasperation saying, ``It is just too unstable''. Perhaps one of its
releases are not as prone to this?

Meanwhile, maybe that Wulbur might be OK after all.

Any ideas?
 
Howard Schwartz a écrit :

<snip>

I have the same problem since a long time, but imho there is nothing to
do for fixing locate32's behaviour. I'm carefully using taskill to shut
it down every time, and if i forgot i must reboot the computer because
of this bug.; Hence there is no program only half so good, and for
example Wilbur is only for collecting text from all over the PC, so
it's not an alternative. For searching text, i suggest trying noteTab
lite.
Locate32 and Wilbur are not comparable. maybe you could use a mix of
noteTab lite for text search and FindAnd Run Robot for launching
apps...

laurent h
 
Howard Schwartz wrote:

I use this one.

Instant File Name Search
http://www.softpedia.com/get/System/File-Management/Instant-File-Name-Search.shtml
Instant File Name Search (IFNS) is a fast, free and easy to use search
tool. Instantly search files by name or wildcards on your computer or
local network.
IFNS offers support of Boolean operators (AND, OR, NOT), database
management (you can create several databases), hot keys and a
convenient, Explorer like interface. Save your time and money. Windows
All.
 
ORIGINAL MESSAGE:

Howard said:
Then it started to happen: I would try to close locate32 without
having done anything special. Up comes a windows error screen telling
me locate32 did something illegal and would be ``closed down'' .
Click to expand...



*********** REPLY SEPARATOR ***********

Very interesting. I have no solution for you except to say I've been
using Locate32 for almost a year with no problems, running WinXP Home
SP2 with all updates.

Have you tried uninstalling it and running a registry cleaner, then
reinstalling? There might be some flakey registry entry causing the
problem.

It works so well I wouldn't want to be without it.

Bill T.
 
ence there is no program only half so good, and for
example Wilbur is only for collecting text from all over the PC, so
it's not an alternative.
Click to expand...

Yes and no: Wilbur indexes lots of words when it updates its database,
which it does pretty fast. But one can specify a file mask and search
for any words in files like that, thus allowing you to do a locate32
type search.

I tried taskkiller and other precess killers, but they did not close
that darn error window. Sounds like the problem is that locate32 cause
trouble in the important kernal, making it hard to avoid trouble from
then on.
 
Have you tried uninstalling it and running a registry cleaner, then
reinstalling? There might be some flakey registry entry causing the
problem.

It works so well I wouldn't want to be without it.
Click to expand...

It is too bad and I have run various registry cleaners. The registry
does not seem to be the problem, but a bug in the executable's code.
If you google on the error you will find many other unhappy users who
encountered the same problem. The problem does not occur every time, but
intermittently for unknown reasons.

It is not unreasonable to suppose this problem may be confined to windows
9x, since I am running win 98. The code and functions called may be
different. For reasons I will not go into here, I will not run win 2K even
though I have it.
 
Howard Schwartz a écrit :
I tried taskkiller and other precess killers, but they did not close
that darn error window.
Click to expand...


No, but you should close locate32 itself with the dam taskill, that
works ok !
if you write a .bat, remember to write the complete name of the app to
kill,
with the .exe extension, otherways no joy.


laurent h
 
Locate32 generally works great on my XP Home SP2 system.

I've had some crashes, all right - especially when trying some right-click
option. But not enough to make me stop using Locate32.

I tried Instant File Name search. It looks good - BUT no right-click
options. To get the right-click options, you have to shell out $20 for the
Pro version. The free version of Ava Find would be better than the free
version of IFNS.

The key thing about Locate32 - it doesn't bog down my system, unlike all the
"Desktop Search" programs like MSN Desktop Search, Yahoo, Copernic, etc.
 
if you write a .bat, remember to write the complete name of the app to
kill,
with the .exe extension, otherways no joy.
Click to expand...

Not needed: The command line version of taskkiller has a ``-wname string''
option that kills any task whose window contains ``string'' (e.g., locate,
locate32, 32, etc.). In fact, the windows version appears to replace the
task manager nicely, and I may start it automatically and retain in as
a tray icon.
 
(e-mail address removed) wrote in
nstant File Name Search
http://www.softpedia.com/get/System/File-Management/Instant-File-Name-S
earch.shtml Instant File Name Search (IFNS) is a fast, free and easy
to use search tool. Instantly search files by name or wildcards on
your computer or local network.
IFNS offers support of Boolean operators (AND, OR, NOT), database
management (you can create several databases), hot keys and a
convenient, Explorer like interface. Save your time and money. Windows
Click to expand...

But it does not let you open a context menu for found files. In general, I
found the freeware alternatives to locate32, find things but do not provide
anything or much for doing things with files found. Often to get this, you
need to buy the payware version.
 
Back
Top