Fatal Exception w. Find function

[rrayl]

I have a SJ20. I just discovered that whenever I use the Find function, after my SJ20 goes through all my apps for the search term and gets to I think the end of the search, I get a Fatal Alert saying I have a Fatal Exception. At that point, the only thing I can do is hit the reset button and do a soft reset. This happens everytime I so a search. Has anyone else experienced this or have an idea what is wrong?

[exppcguy]

Might not solve your problem, but try FindHack (with X-master) to limit your search to current application only. That way you won't get to the end.

[rrayl]

Thanks for your suggestion. I downloaded trial FindHack and I do not get fatal exception when I search built in apps, which is all I am interested in anyway. Just starting to trial FindHack and so far it seems much better than default Find that I think I will buy it eventually. Still when I search "all apps" I get same fatal error. I still wonder what may be causing it. Don't know if its causing it, but when I did an "all apps" search, my clie bombed out when it seemed to try and search MobileDB. Wonder if that is the problem?
Thanks for the help. At least I know what I can do to avoid the problem as long as I don't have to search all apps.

[exppcguy]

No problem there. I use Findhack because I can't stand waiting while it searches through all tha apps - I am always searching in Memo anyway - which it doesn't reach till the end.

Worth the money I think.

[notmuch]

Most likely you've got a poorly programmed app or corrupt db that doesn't like Palm's global find command. You can open each app and use Findhack to search "current app". You should isolate the problem. Then either delete the app or make sure to exclude that app from any FindHack sets.

[Magicster]

Originally posted by rrayl
I have a SJ20. I just discovered that whenever I use the Find function, after my SJ20 goes through all my apps for the search term and gets to I think the end of the search, I get a Fatal Alert saying I have a Fatal Exception. At that point, the only thing I can do is hit the reset button and do a soft reset. This happens everytime I so a search. Has anyone else experienced this or have an idea what is wrong?

I've also had the same exact problem, question: are you using any launchers besides the original one?

This fatal reset seems to only happen to me when i have silver screen activated.

[rrayl]

I use ZLauncher but I think the problem may relate to MobileDB. After installing FindHack, and searching only the built in apps, which is really all I want, I have not had anymore problems. I think the problem relates to one of my many apps that I use. When I have the time, I may try and isolate the problem app. You may want to try FindHack. I think it will help.

[rrayl]

Just so I don't malign MobileDB unfarily, after my last post, I searched via FindHack, MobileDB and my Clie did not crash so that app is not the problem. One of these days I will find out which app is causing the problem, but not now.

[halosal]

I have the same problem with my SL10. I do not use a launcher (other than the original one), so that can't be the problem.

[Jake K]

Do you have any overclocking programs running? I used to have the same problem whenever I searched while I had Fastcpu going.

[halosal]

Do you have any overclocking programs running? I used to have the same problem whenever I searched while I had Fastcpu going.

Fastcpu does not give the problem; I just discovered that removal of Epocrates and all its drugs databases was the proper medicine for my PDA's illness.

[Unregistered]

Originally posted by halosal


Fastcpu does not give the problem; I just discovered that removal of Epocrates and all its drugs databases was the proper medicine for my PDA's illness.

How ironic...

[dasaunders]

My workbench will cause the find button to cause a fatal exception.

[Unregistered]

I had the same problem with my SL10/U. After reading the idea of a db causing the problem, I started deleting any unneeded aps. After deleting "ChemTable" (a periodic table) the Find function began to work properly without Fatal Errors.