Results 1 to 12 of 12
  1.    #1  
    It looks like the new PalmSource applications are on the Treo 650. The same buggy ones that the new T5 has. Here is a Datebk5 support forum post from the maker of Datebk5, a very respected person in the Palm community who is well aware of these problems, and they are causing me to think about just staying with the my 600.

    Wed Oct 27, 2004 6:17 pm
    Subject: Re: tungsten 5

    > Anyone having a problem with their T5.

    You and everyone who has bought one

    > I had to get the update for
    > the T5 because it would have Fatal Errors each time I would use
    > DateBk5. But after the update I still have a problem with it locking-
    > up after I put an appointment down in the calendar.

    That's because the update does nothing to fix any of the bugs in the PalmOne
    DataManager patch. Just hold on some 24 hours or so as I will be posting a
    maintenance release VERY SHORTLY that talks directly to the proprietary
    calendar and memo databases thereby sidestepping their DataManager patch
    (several people have been testing this for me and all of them indicate it
    eliminates all these problems on the T5 and also provides far better
    performance on the Tungsten T3, E, and Zire72/31).

    With the T5, the Datamanager patch has moved IMHO from a designation of
    "kludge" to "worthless kludge" - it's basically unusable - not only because
    the performance is so bad, but because it was inadequately tested and has
    too many bugs to be considered a usable piece of software.

    Among the very obvious problems when you try and use DateBk5 on a Tungsten
    T5 (or forthcoming Treo650) are:

    1) Slow exit out of DateBk5 (One time, I clocked it at over 35 seconds!!).
    2) Details dialog can take several seconds to appear
    3) strange clicking noises and delays when executing simple functions
    4) Unexpected crashes including ones with the message:

    VFSBCache.c,line:6761 DeleteRecord()called and invalid record

    The T5 is a nice looking device and has some nice features, but the testing
    was poor and this is by far the buggiest device that we've ever seen from a
    Palm licensee. I suspect there is a VERY good reason why PalmOne has
    announced the Treo650 (which uses the same architecture) but no carriers
    have started to make it available for sale(!).

    I have to say that in ten minutes of testing after I got this device, I
    noted FOUR very obvious bugs, which leaves me at a loss to explain how a
    device like this could be released with such obvious errors - it does make
    you wonder if anyone even looked at this device before it was put up for
    sale...

    Finally, while I may "Fix" DateBk5, this will not "fix" any other third
    party apps that use the built-in, standard Palmsource databases. So if you
    depend upon a third party addressbook app or memo app, or something like
    ToDO+, etc. you may well want to forgo the T5 (and the forthcoming Treo650)
    as your experience will no doubt leave a bad taste in your mouth.



    Cheers!
    CESD, Pimlico Software, Inc.
    Last edited by bremeski; 10/28/2004 at 10:41 AM.
  2. #2  
    Wow, very strong words from someone who knows what he is talking about and is rarely this critical. Hopefully more information on stability will be available before the DC Roadshow, when I had planned on making a purchase.
    Last edited by MarkY; 10/28/2004 at 11:55 AM.
  3. #3  
    If it helps at all... I ran DateBk5 OK on the simulator.
    Gabe Kangas
    Achievatron 2004 - ?
    Visor Deluxe -> Treo 300 -> TREO 600 -> Treo 650
  4. #4  
    Thanks for posting that, bremeski. I'm a long-time Datebk user. Hopefully problems will be resolved soon....
    tanster
    Treo 650 on Sprint, as of 11/18/04!
    To transfer data from your current Palm device to the Treo 650, click here.
    To see my Treo 650 pics, click here.
  5. #5  
    This is a little concerning to me as well even though I don't currently use DateBk5.

    I have to wonder how much of this is the new Palm version that's on the two devices. Maybe it just works differently? Admittedly, I'm not a Palm developer so I have no idea what I'm talking about :grin:

    Mike
  6. #6  
    My life relies on Datebk5 (OK...a little exaggeration, but not much). I'm sure hoping it will work with it! Kinda scarey to think of life without Treo 650 or without DateBk5!
  7. #7  
    Quote Originally Posted by dmax
    My life relies on Datebk5 (OK...a little exaggeration, but not much). I'm sure hoping it will work with it! Kinda scarey to think of life without Treo 650 or without DateBk5!
    In fact, it's already been fixed, and the comnpatible version will be available soon, I'm told.
  8. #8  
    Quote Originally Posted by elysian9
    In fact, it's already been fixed, and the comnpatible version will be available soon, I'm told.
    So, do you work for PalmOne or PalmSource?
  9. #9  
    Quote Originally Posted by elysian9
    In fact, it's already been fixed, and the comnpatible version will be available soon, I'm told.
    Now, in fact, if you're on the Yahoo support group.
  10. #10  
    DB5 has been fixed for the T5 (and presumably Treo 650). P1 doesn't seem to know or care about the crappy DMP
  11.    #11  
    The point of my original post was not that DateBk5 had the problem, but that any program relying on the basic PIM applications will probably have a problem. We who know DateBk5 know that CESD will fix it for his program, no matter what! But all of those other programs that reach out to the basic PIM data may not get fixed, which means to me that many programs may cause difficulty on the 650 (as they do on the T5 now). As much as I want a 650, no way I'm spending those hundreds of dollars until I know that these basic applications have been fixed to really work right.
  12. #12  
    Simulator may not full emulate effect of the flash memory file system- which could account for bugs not showing up until production. (what beta test- that's what users are for....)
    If that's the reason- then concern about T650 is justified.

Posting Permissions