Is it true Agendus Pro and Datebk5 shouldn't be run on the same T3?

[Shamrock]

Even if they are both the latest versions.

[CWolf]

Yup, it put my T3 into a continuous reset loop until I hard reset and restore using one from Backupman from before I added Datebk5...

I prefer Agendus so far...

[Shamrock]

WOW! I wonder what I am doing wrong. I haven't had a peep but I don't like skating on thin ice. Thanx.

[jreyes1]

I've been running them both on the same t3 in various incarnations and versions with not a problem yet.

i use them both really extensively

i think agendus is still buggy, but use it primarily for grouping function in addressbook so haven't used a lot of the calendar stuff on it -- use datebk for that.

[CWolf]

Hmmm, it can depend on the T3 it seems. I have problems others don't but don't seem to suffer the problems that some do!

[CWolf]

CORRECTION:

OK, I have found that if you install Datebk5 first then Agendus Pro then things will work fine. No idea why it doesn't work the other way!

I know that I could edit my previous post, however I feel this is important as I made a slight mistake and want this thread to appear on people's New Posts list...

[dgoeg]

Just tested the following on the T3 and the Simulator:

1. Install DateBK5 and Icons-DATEBK5.
You can change icons, everything is fine.

2. Install Agendus. Run it once.

3. Try to change Icons in DateBK5 --> results in fatal exeption on T3 or crash of the simulator.

Is this just an incompatibility or an act of sabotage?

[Vidge]

I have heard that Agendus does something to the icons which causes them to crash DB5

[orol]

Originally posted by Vidge
I have heard that Agendus does something to the icons which causes them to crash DB5

yes, that't true (yet another nasty iambic policy)
I prefere datebk5 since is superior to agendus

[dgoeg]

I'm still trying to test both. So that means, I have to test DateBK first and after that Agendus. Not optimal to compare them both side by side.

I don't think it is an DateBK5 bug. I used Icon Manager to look at the icon-database and found that Agendus creates an additional "dot" at the end, which is not an icon resource.

I had the idea to set the read-only bit for the icon-database, but Agendus still changes it. Is there another way to prevent Agendus from modifying the icon resources?

[scandalex]

Originally posted by Vidge
I have heard that Agendus does something to the icons which causes them to crash DB5
This is interesting considering that the icons for Agendus & Datebk are supposed to be compatible....go figure!