Tech Support Request

Last year I upgraded Girlfriend 1.0 to Wife 1.0 and noticed that the new program began unexpected child processing that took up a lot of space and valuable resources. No mention of this phenomenon was included in the product brochure. In addition, Wife 1.0 installs itself into all other programs and launches during system initialization where it monitors all other system activity. Applications such as Pokernight 10.3 and Beerbash 2.5 no longer run, crashing the system whenever selected. I can not seem to purge Wife 1.0 from my system. I am thinking about going back to Girlfriend 1.0 but un-install does not work on this program. Can you help me?

-- Reply 1 -------------
I found that if you install Mistress 1.0 on the same drive wife 1.0 , wife 1.0 will un-install automatically, but it will also delete you quicken money files in the process and possibly remove child 1 and child 2 forever.

--- Reply 2 -------------
Solution: Don't install Mistress at any time. If Mistress is a consideration, Remove Wife first. Will solve all problems.

A different perspective.

--- Reply 3 -------------
Similar to the problems with removing Internet Explorer 4, once installed, the removal of Wife 1.0 is often a difficult and painful process that can further damage portions of the OS. The user should always carefully consider the ramifications of installing any software before installation, noting any incompatibilities between the user's OS, Wife 1.0 and any related files

The hapless "upgrader" asked:

<<Last year I upgraded Girlfriend 1.0 to Wife 1.0 and noticed that the new program began unexpected child processing that took up a lot of space and valuable resources. No mention of this phenomenon was included in the product brochure. In addition, Wife 1.0 installs itself into all other programs and launches during system initialization where it monitors all other system activity. Applications such as Pokernight 10.3 and Beerbash 2.5 no longer run, crashing the system whenever selected. I cannot seem to purge Wife 1.0 from my system. I am thinking about going back to Girlfriend 1.0 but un-install does not work on this program.

Can you help me?>>

Answer:
I have recently experienced the suprising results of that "upgrade" myself and couldn't resist responding with some "tech support"... Unexpected child processing is one of the principle undocumented features of your upgrade. While the drain on valuable resources can be truly stunning, the long turn benefits can be awesome. This undocumented feature can be avoided in most cases through use of the P.I.L.L 1.0 patch.

Wife 1.0 does install itself into all other systems. Depending on how effectively you apply proper wife maintenance procedures (communication, love, affection, gifts, quality time, etc.), this profound intrusion will produce either substantial system wide improvements or substantial system wide degradation. (many users experience a mixed bag of results as maintenance procedures for this program require an unmatched level of user commitment.)

Wife 1.0 is completely incompatible with certain programs. Many of these programs are detrimental to system efficiency and health and this benefit is one of the incidental advantages to installation. Others will fail simply because the Wife 1.0's maintenance requirements and/or drain on system resources.

As you have noted, uninstall followed by a "downgrade" to Girlfriend will always fail. While it is theoretically possible to purge the system of Wife 1.0 and install a copy of girlfriend 2.0, this process is costly and filled with many unexpected and unpredictable problems. Many users find themselves upgrading girlfriend 2.0 to wife 2.0 only to find that Wife 1.0 was a better install than they originally appreciated.

Girlfriend users who are considering this upgrade are urged to evaluate the changes to their system carefully. The potential improvements in overall system productivity and stability are awesome but entail profound changes in overall system priorities and resource allocation.

Your "system" will never be the same.