Registered: May 2001
Location:
Posts: 70

Date Book 5

Is anyone testing Datebook 5 on their Prism? I am having to reset everytime I go into preferences. I love 4 and the features on 5 look great but this is wacky. I have diabled hacks,hard reset, taken everything off and still this wacky message. anyway if you have any thoughts please let know!

Registered: Mar 2000
Location: Richmond, VA, USA
Posts: 151

remove

Did you remove Datebk4 (just the prc) before installing Datebk5? I think that can cause this issue.

Registered: May 2001
Location:
Posts: 70

Yep

Yes I did remove it, a side note it is amazing to me how many files can lurk on a visor. I use Filez to remove files and I am all ways amazed at how many orphaned and left over files are left behind when you deleate a program. I guess I am doing a spring cleaning now, at least I know I can go back to 4. Thanks

Registered: Mar 2001
Location: Moncton, New Brunswick, Canada
Posts: 29

I know this won't solve your problem, but just to let you know, I'm running DateBook 5 on my Prism with launcher III and I haven't experienced any problems (knock on wood) yet. I seem to be able to go in and out of preferences with no reset. Good luck!

Registered: May 2001
Location:
Posts: 70

Maybe

The good folks at Dtb pointed out that I did not have OS patch needed to run 5 so I give it a try.

Registered: May 2001
Location:
Posts: 70

A fix

Well I learned something important, the following work. One of the many reason I recomend these folks is there speeding response
===============================
Note: There is a serious bug in Handspring's OS 1.4 update. If DateBk5
detects you have this old update it will turn off several video
optimizations that would otherwise crash your device. If you are using this
1.4 update, we strongly urge you download the OS 1.5 update that fixes this
bug:.HS Updater 3.5.2v1.5
===============================
I am looking into this because DateBk5 has a specific check for this buggy
release and should tell you about it, but for some reason it is not
identifying it properly. I think the problem is that I don't have the right
sub-version (i.e. it's actually something like 1.401, etc.). I do have a
copy of the 1.4 update for testing, so the final release version of DateBk5
should properly complain about it and provide the above link to Handspring's
fixed version.