Re: Re: Find Crash
Ryan Waldon <[email protected]> Thu, 23 Nov 2006 21:26:07 -0800 (PST)
| Newsgroups | gmane.comp.handhelds.palm.iconmgr |
|---|---|
| Message-ID | <[email protected]> |
Have you given FindHack a try? http://www.florentpillet.com/findhack.html --ryan --- Chris Antos <[email protected]> wrote: > Again, due to how the Find function actually works > on Palm devices, it is probably misleading you to > think an innocent app is crashing. > > Here is an entry from the HandyShopper Frequently > Asked Questions, which applies to both HandyShopper > and Icon Manager. Also, sometimes people suggest to > use FindTester to see which application is crashing. > But actually FindTester does not work on OS5 > devices -- FindTester itself will crash and/or give > an erroneous report. The way that FindTester tries > to do stuff only works on OS4 and lower, and is > explicitly incompatible with OS5. > > 31. Why does HandyShopper crash when I use the > global Find command on my device? > > a.. The odds are a few thousand to one that > actually it is some other app that is crashing. Here > is a brief explanation of why that happens and what > to do about it. > b.. Why: Due to how the Palm OS works, it's a > common newbie Palm programming mistake to have > crashing bugs in an app when a global Find happens. > People usually assume that the last app name shown > is the one that crashed. But in fact what happens is > that improperly written apps crash immediately when > the Palm OS notifies them that the user is doing a > Find. Each app is responsible to draw its name, so > the fact that an app's name got drawn means it did > not crash immediately, and therefore most likely did > not crash at all -- instead it was whatever app came > next that actually crashed. > c.. What to do: If you installed other apps > recently, try removing them in groups. If the Find > starts working after you remove a particular group, > then you can reinstall the suspect apps one at a > time until Find starts crashing again, and then you > will have found which app is causing the crash. You > can also try backing up all your HandyShopper data > and then removing HandyShopper from the device, and > verify that the global Find still crashes even > without HandyShopper on the device, in which case > you can at least rule out HandyShopper as the cause. > > > > > > ----- Original Message ----- > From: puntoyaparteconsultores > To: [email protected] > Sent: Wednesday, November 22, 2006 8:10 PM > Subject: [IconMgr] Re: Find Crash > > > Thanks for answer but my device is a treo 650 and > i dont know its have the same > problems than a t5 > mac > > --- In [email protected], "Steve" > <kunkel321@...> wrote: > > > > --- In [email protected], "jeffmdehart" > <jmdehart@> wrote: > > > > > > Has anyone had a problem with the TX or T5 > crashing when using the > > > Find funtion? I have been trying to find the > problem for a while. It > > > went away when I removed icon manager. I > vaugly remember a message > > > when first syncing the new device that icon > manager would have > > > problems with the device. > > > > > > Is there a memory architecture issue? > > > > > > Is there a fix? > > > > > > Jeff > > > > > > > Have not seen this with my T5. If your's is an > older T5, make sure > > you've installed the free T5 Updater 1.1 from > the Palm website. tI > > hink it's very unlikely that this will be your > problem, but if you have > > a really large icon set that you're working on > in RAM, then you try to > > activate the find feature, the T5 may not be > able to transfer things > > back to the Flash (NV) memory fast enough before > accessing all the > > other stuff it wants to search. This can cause a > crash and is a > > problem inherent in the newer NVFS Palms... > Though I'm not enough of an > > expert to say for sure if this is likely to > happen when using > > IconMgr ... Maybe Chris or another member can > expand further... At any > > rate you can check to see if your Palm has the > update... google "T5 > > updater" or such. > > > > > > > > [Non-text portions of this message have been > removed] > >