gregmarsh
11-01-2004, 04:56 PM
Hi,
I've recently started using my XDA II, but I'm having a very frustrating problem which I suspect may be a 'feature' of PocketPC 2003 memory management.
When I open up applications and then switch focus away from them (e.g., by using a task switcher like Go, Smallmenu, MagicButton, etc.) they then 'close' themselves in the background.
This is annoying enough when it's just e.g., viewing a file and then have to reopen it and find your place again, but it's seriously irritating when you're in the middle of a task, swap out for a few seconds, and then try to return only to find that PocketExcel has closed, having 'saved' your file with a silly name, meaning you have to open it again. In some apps it even seems to lead to data loss (e.g., if you're half way through entering a new contact, and then do something else, you lose your half-completed entry).
I've got stacks of memory free, so if it's a memory management 'feature' it's being far, far too zealous in reclaiming what it thinks are "unused" resources.
Does anyone else have this problem -- and if so, is there a way to solve it? (please say yes!)
thanks!
Greg.
I've recently started using my XDA II, but I'm having a very frustrating problem which I suspect may be a 'feature' of PocketPC 2003 memory management.
When I open up applications and then switch focus away from them (e.g., by using a task switcher like Go, Smallmenu, MagicButton, etc.) they then 'close' themselves in the background.
This is annoying enough when it's just e.g., viewing a file and then have to reopen it and find your place again, but it's seriously irritating when you're in the middle of a task, swap out for a few seconds, and then try to return only to find that PocketExcel has closed, having 'saved' your file with a silly name, meaning you have to open it again. In some apps it even seems to lead to data loss (e.g., if you're half way through entering a new contact, and then do something else, you lose your half-completed entry).
I've got stacks of memory free, so if it's a memory management 'feature' it's being far, far too zealous in reclaiming what it thinks are "unused" resources.
Does anyone else have this problem -- and if so, is there a way to solve it? (please say yes!)
thanks!
Greg.