- Tungsten E2
1. It has very many bugs with NVFS. After reset sometimes some dbs are
disappeared or corrupted. It can be solved with DmSyncDatabase function
inserting after db changing. But perfomance became too little.
I do not want Palm to go back to the old memory they had before. Sure,
you have to invest some effort to get the NVFS running properly with
your existing apps. But I dont wanna miss it anymore. Our service-calls
dropped by 75%, because customers don't lose their data anymore.
We are very satisfied with NVFS. Its a marketing-advantage towards
PocketPC, especially for business-applications.
> But perfomance became too little.
I'm running 35K-records database with 9MB of data on a TX. After
optimizing for NVFS there is no difference in speed anymore. Maybe you
should not call DmSyncDatabase after every change!? Its a cache! If you
flush EVERY operation they would not have to integrate it!
I haven't big expereance with devices Tungsten TX and Treo 650. And I don't
sure that this devices haven't big problems.
I'm having my Treo 650 for 4 months now. I think the number of resets I
had to perform is still between 10 and 20(in 4 months!). Ask some
PocketPC-users, they have that in 4 weeks.
Regarding the TX, I would be happy if they did not change little stupid
things with every model. The missing Home-Button in the Graffity-Bar
confuses my customers a lot!
Our company have written many Palm OS applications.
But it seems that we go to develop with Pocket PC in future.
Do whats right for you! We also do both if the customer really demands
it; otherwise we prefer Palm!
Thomas
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
