Fatal Alert- Help

[pat43]

I can no longer use the "find" function (looking glass) because every time I do I get the following Fatal Alert message: Emul68KMain.c.Line:108, divide by zero at address 203E9EEC. How can I know which app is causing the crash? I made a search for fatal alert on the forum but wasn't able to find a solution to my problem. Any clues as to what may be causing this? Any assistance will be much appreciated.

[jwm]

Do you have SplashID - did this once for me and it was this little blighter. An upgraded version of SplashID fixed the problem.

[pat43]

Thank you for your posting. No I don't have Splash ID. So, I guess I have to keep on looking.

[jwm]

Guess you'll have to do a bit of trial & error to trace the problem. Some food for thought:

- Does it crash as soon as you hit the "Find" icon in the Graffiti area, or when actually doing the search?

- Does "Find" actually go through any databases on the screen before the crash?

- Another thing that may help you trace the problem is that "Find" will start with the application is was invoked from, so if you're in Datebook, that'll be the first database it'll search.

Good luck.

[pat43]

Find doesn't crash immediately but after it has gone through some databases. I suspect the problem may be related to the Contacts5 program I recently downloaded. When I am in Conctacts and invoke the global find I doesn't crash. If I invoke "Find" from another application it does crash. Could it be due to the fact that it can't access the Address database because I have allocated that button to Contacts?
Thanks for your help anyway.

[jwm]

Doubt it - I can't see how re-assigning a hard button's function would effect the "Find".

If the last database is (starts to) search through before it crashes is Contacts 5, then I'll bet its that that's causing the problem.