Some More Light Relief
Anonymously by email
Last Year a friend of mine upgraded from Girl-friend 4.0 to Wife 1.0 and found that it's a memory hog leaving few system resources for other applications. He is also now noticing that Wife 1.0 is also spawning Child- Processes which are further consuming valuable resources. No mention of this particular phenomenon was included in the product document, though other users have informed me that this is to be expected due to the nature of the application. Not only that, Wife 1.0 installs itself so that it is always launched at system initialization where it can monitor all other system activity. Some applications such as FootballNite 10.3, Allnite Party 2.5 and Pubnite 7.0 are no longer able to run in the system at all, causing the system to lockup when launched (even though these apps worked before). Wife 1.0 provides no installation options. Thus, the installation of undesired plug-ins such as Mother-in-Law 55.6 and the Brother-in-Law beta is unavoidable. Also, system performance seems to diminish with each passing day.
Some features my friend would like to see in the upcoming Wife 2.0:
I myself wish I had decided to avoid all the headaches associated with Wife 1.0 by sticking with Girlfriend 3.0. Even here, however, I had found many problems. Apparently you cannot install Girlfriend 4.0 on top of Girlfriend 3.0. You must uninstall Girlfriend 3.0 first, otherwise the two versions of Girlfriend will have conflicts over shared use of the I/O port. Other users have told me that this is a long-standing problem that I should have been aware of. To make matters worse, the uninstall program for Girlfriend 3.0 doesn't work very well, leaving undesirable traces of the application in the system. Another identified problem is that all versions of Girlfriend continually pop up annoying little messages about the advantages of upgrading to Wife 1.0. All users should be aware the Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then for some reason Mistress 1.1 won't install at all, claiming insufficient resources. To avoid the aforementioned bug, try installing Mistress 1.1 on a different system and never run any file transfer applications (such as Laplink) between the two systems.
