[Smhblackberry]

pocketday list?

[ShelW]

Originally Posted by fmeehan

donc36, I did not find anything about Spouse...

I have Spouse 2.0. VERY expensive to maintain.

Previously had Spouse 1.0, as previously mentioned, the nag screen couldn't be disabled... on and on and on. Finally had to get rid of Spouse 1.0, but what a hassle.... messed up not just my computer, but EVERYTHING! Removed numerous items from my system when I removed it to install upgrade.

Moved up to Spouse 2.0, much improved, but expect to have to maintain with expensive enhancements and add-ons for it to continue working without nag feature.

Also, you may find unexpected add-on's in the form of Offspring, which was NOT purchased nor requested of the original developer, but suddenly appeared on my OS.

I now have Offspring 1.0, 2.0 and 3.0, and these are NOT trial ware or demo ware... haven't figured out how to extract from my OS... I believe it may take years.....what's worse, Offspring 3.0 is NOT an upgrade, it must be used in congunction with Offspring 1.0 and 2.0, draining system resources at an alarming rate!

Stick with ShopMagic.

[vinmontRD]

Originally Posted by ShelW

I have Spouse 2.0. VERY expensive to maintain.

Good info!

I upgraded to Spouse 2.0 as well, several years back, and my experience is similar to yours. Definitely uses up a lot of resources. At least it's more stable than Spouse 1.0 was.

One thing I've never solved with the entire Spouse series, though, is that, despite pre-sale advertising up front, they're not as compatible with all of my gear as I had anticipated, and this problem doesn't seem to have improved with release 2.0, unfortunately. For example, when I devote time to dealing with important items such as blackberryforums, editing a theme or upgrading my OS on the BB, Spouse 2.0 raises a dialog indicating that I am expending too many cycles on my Blackberry, and prompts me to response to the question, "are you playing with your Blackberry AGAIN?". I've found it to be a bit finicky at this point, so it's good to be careful how I respond if I will need it again later that evening.

I keep hearing interesting things about a company called Stepford. Haven't had time yet to explore it yet...

[John Clark]

Excellent! Love it! Can't believe nobody noticed this! I only came back to see what was so popular about a Grocery Shopping list app!

And I am currently on OffSpring 4.0 (with plans to disable the Offspring feature altogheter.) Offspring 4.0 really adds spark to Offspring 1.0, 2.0, and 3.0 and especially Spouse 2.0. Fortunatly, OffSpring was still in Beta testing during Spouse 1.0, so no worries there.

[fmeehan]

Well only have Spouse 1.0, I am very conservationist and that one works flawlessly.

In order to get Ipod touch 1.0 and GoplaygolfwhenIwant 15.0 (for this year), I need to do grocery 1.0.1 to please Spouse 1.0.

As far as Offspring 1 and 2 are concerned, they are useless for grocery 1.0.1.

[rivviepop]

Wow, I love BBF. You guys have convinced me that I did the right thing to never upgrade from Cat 1.5 and Kitten 0.95-beta to these new Spouse and Offspring models. Like grandpappy said, if it ain't broke...

[Smhblackberry]

Originally Posted by ShelW

I have Spouse 2.0. VERY expensive to maintain.

Previously had Spouse 1.0, as previously mentioned, the nag screen couldn't be disabled... on and on and on. Finally had to get rid of Spouse 1.0, but what a hassle.... messed up not just my computer, but EVERYTHING! Removed numerous items from my system when I removed it to install upgrade.

Moved up to Spouse 2.0, much improved, but expect to have to maintain with expensive enhancements and add-ons for it to continue working without nag feature.

Also, you may find unexpected add-on's in the form of Offspring, which was NOT purchased nor requested of the original developer, but suddenly appeared on my OS.

I now have Offspring 1.0, 2.0 and 3.0, and these are NOT trial ware or demo ware... haven't figured out how to extract from my OS... I believe it may take years.....what's worse, Offspring 3.0 is NOT an upgrade, it must be used in congunction with Offspring 1.0 and 2.0, draining system resources at an alarming rate!

Stick with ShopMagic.

Try nanny 1.0 with spouse 2.0 very interesting.

[John Clark]

Make sure you are running nanny 1.0 on a different device than spouse 1.0 or 2.0 or you may be required to load spouse 3.0.

[Smhblackberry]

i found that nanny 2.0 works well when spouse 2.1 is inactive and offspring 4.0 is asleep

[JSanders]

whew, at least all of us have these automated processes, Manual 5.0 leaves a lot to be desired.

[John Clark]

HA HA HA HA HA HA HAH HA!!!!!!!!!!!!!!!!

[BBFreak]

Also you can use the extra protection addon when possible to keep from getting the Offspring virus.

[Stinsonddog]

Wirelessly posted (9900: BlackBerry8800/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/102)

I have this disease called Market Measles so I don't need this app.

[vinmontRD]

Originally Posted by JSanders

whew, at least all of us have these automated processes, Manual 5.0 leaves a lot to be desired.

Reminds me of the whole issue with kids using calculators instead of doing math themselves...manually. After using a calculator, you never want to go back to doing math, uh, long-hand...

There's also the consideration, discussed here already, about the dangers of booting up Spouse 2.0 on the same platform as Nanny 1.0. Although some apparently wind up using Spouse 3.0 when the inevitable incompatibilities destabilize the entire platform as described above, I've heard that it's just as common for people to wind up having to fall back to using one of the deprecated versions of Manual once again, despite its limitations.

I've been relying on Spouse 2.0 for several years now, after having lost significant resources to version 1.0. If this version doesn't hold up, it may be time to try a different series altogether. An associate of mine finally gave on the product line, became an associate professor and took advantage of the educational discount available on the Student 4.0 product to give it a whirl -- from what he told me, it involved some serious over-clocking, so you have to be careful not to burn things out.

[John Clark]

Roflmao!

[donc36]

Originally Posted by BBFreak

Also you can use the extra protection addon when possible to keep from getting the Offspring virus.

True, but like any hardware / software system, there are vunerablities. In my case, Spouse 2.0 had an outbreak of Offspring 4.0, inspite of these addon's which marketed to protect against such outbreaks. Offspring 4.0 is actually a good thing, as it often provides friendly greetings when I arrive home from work.

[vinmontRD]

Originally Posted by donc36

True, but like any hardware / software system, there are vunerablities. In my case, Spouse 2.0 had an outbreak of Offspring 4.0, inspite of these addon's which marketed to protect against such outbreaks. Offspring 4.0 is actually a good thing, as it often provides friendly greetings when I arrive home from work.

It's possible that the protection add-ons were actually working, but that the implementation of Spouse 2.0 actually disabled the add-ons after you applied them, and you simply weren't aware of this. I've found that Spouse 2.0 is far more complex than I ever anticipated. It's possible that this is part of the programmed behavior.

Glad to hear that Offspring is working out for you.

[JSanders]

Anybody have one of those Nanny 1.0s morph into a Spouse 2.0?

[BBFreak]

Heck no. I'm looking for the new anti-virus and anti-hacking software as the protection addon may not be as good as I thought.

[donc36]

Originally Posted by vinmontRD

.... I've found that Spouse 2.0 is far more complex than I ever anticipated.....

That has to be the understatement of this thread. I never realized the complexity during the trial period, but as soon as I ponied up for the license for Spouse 2.0 and formally upgraded..... lets just say there were some undocumented "features" of the program until well after the trial period had expired.

Of course, all my problems with spouse 1.0 and spouse 2.0 absolutely can't be user error, right ?