+joefrog Posted January 31, 2005 Share Posted January 31, 2005 I got a new Palm a month ago, and finally "upgraded" to Cachemate. Well, I thought it was an upgrade... When I try to search for "Nearest Caches" from a cache page via the "record" menu, 75% of the time (100% lately) it locks up the palm. Locks it up HARD. Sometimes it only locks it up so it has to be reset, others I have to do a hard reset and lose all the info on the palm until my next HotSync. It's a Palm Tungsten T3, running Cachemate 4.0.3. Synced from a Mac G4, running OS10.3 with twin 1.5gHz processors and 2 gigs of RAM. ANY ideas what could be causing the trouble? Quote Link to comment
+geobc Posted January 31, 2005 Share Posted January 31, 2005 I'm also running Cachemate 4.0.3 on my T3 w/o any problems. I use Cachemate Converter to generate the .pdb files and I don't use the SD card for db storage. I'm also running the PXA underclocker (to save batt. power) so Cachemate runs at 100mhz. I'm also running the patches to support landscape display, and have installed Graffiti 1 files. It's very likely one of your other apps installed on your Palm. Try to deactivate whatever you can. GeoBC Quote Link to comment
+clan_Barron Posted January 31, 2005 Share Posted January 31, 2005 I'm running Cachemate 4.0.3 on a Palm IIIxe with no issues. I agree that it sounds like maybe a conflict with another app. Also are you running and "hacks"? Quote Link to comment
+IVxIV Posted January 31, 2005 Share Posted January 31, 2005 Is the PDA pretty full of data/programs? Maybe you're running out of working space for it to do it's required sort... Quote Link to comment
+joefrog Posted January 31, 2005 Author Share Posted January 31, 2005 Nope, no hacks that I'm aware of... I also use the Cachemate Converter, but it's the Mac version, "CMConverter" or something like that. Quote Link to comment
+webscouter. Posted February 1, 2005 Share Posted February 1, 2005 Hi JoeFrog, Make sure you are not in the overview screen when you try to do the search for nearest caches. That will lock it up even if you have the search disabled. It is a known bug in the software. Quote Link to comment
+joefrog Posted February 1, 2005 Author Share Posted February 1, 2005 Hi JoeFrog, Make sure you are not in the overview screen when you try to do the search for nearest caches. That will lock it up even if you have the search disabled. It is a known bug in the software. "even if I have the search disabled?" Can you elaborate on that? Thanks for the help, folks! Quote Link to comment
+ICHTHYS Posted February 1, 2005 Share Posted February 1, 2005 (edited) I noticed I was having this problem. No hard lockups, just a reset of the PDA. I have an M125. I had over 500 caches in it, I reduced it to 200 and am not having problems anymore. Edited February 1, 2005 by TeamVanderTroll-BR Quote Link to comment
+JeremyA Posted February 1, 2005 Share Posted February 1, 2005 I think that the problems you are experiencing would be best addressed by the author of CacheMate. Although the he does frequent these forums I would suggest that you are more likely to get a timely and useful response if you report your problems through the Smittyware website. There you will find both a dedicated forum for CacheMate and a technical support email address that will allow you to contact the author directly. JeremyA Quote Link to comment
+webscouter. Posted February 1, 2005 Share Posted February 1, 2005 Yes even if you have the search disabled it will cause a lock up. Quote Link to comment
+Maeglin Posted February 3, 2005 Share Posted February 3, 2005 (edited) Yes even if you have the search disabled it will cause a lock up. Strange... just wish I could replicate this at home, and I'd at least be one step closer to fixing it. "even if I have the search disabled?" Can you elaborate on that? There's a "safety catch" that's supposed to keep you from doing a "nearest cache" search from the overview display, because of a documented known bug (at least in the CacheMate docs) that is either in the software or the OS (haven't been able to replicate it at home, so I have no idea where it lies). It's optional, because doing such a search from there seems to work for most people, but it's on by default. According to webscouter, though, sometimes even that doesn't keep it from doing weird things. If you're only doing nearest cache searches from the overview display, then that would be a correlation. Try doing one from either the list view or from one of the other record views, if that's the case. Edited February 3, 2005 by Maeglin Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.