28-03-2009, 04:21pm
WIFE FOR WINDOWS Vsn 1.0
Last year a friend of mine upgraded Girlfriend 6.0 to Wife 1.0, and found that it is memory hungry, leaving very little system resources for other applications. He is only now noticing that wife 1.0 is also spawning Child Processes, which are further consuming valuable resources. No mention of this particular phenomena was included in the product specification, brochures or documentation, although other users have informed him that this is to be expected due to the nature of the application. To add to the dilemma, Wife 1.0 also installs itself in such a way that it is always launched when the system is initialized, where it can monitor ALL other system activity. In so doing he is finding that some applications such as Poker Night 10.3, Beer Bash 2.5, and Pub Night 7.0 are no longer able to run, crashing the system when selected (even though they always worked fine before). When installed, Wife 1.0 automatically attaches undesired plug-ins, such as Mother-in-Law 55.8 and Brother-in-Law Beta 1.5 release. As a consequence, system performance seems to deteriorate with each passing day. Some features he'd like to see in the release of Wife 2.0 are:
A "Don't remind me again" button
A mute facility minimize button
An install shield feature that allows wife 2.0 to be installed with the option to de-install at any time without the loss of cache and other system resources.
I myself decided to avoid all of the headaches associated with Wife 1.0 by sticking with Girlfriend 2.0. Even here however, I found many problems. Apparently you cannot install Girlfriend 2.0 on top of Girlfriend 1.0. You must de-install Girlfriend 1.0 first. Other users say this is a long standing bug which I should have been made aware of. This may be actionable misrepresentation. Apparently all the versions of Girlfriend have conflicts over shared use of the I/0 port. You think they would have fixed such a stupid bug by now. To make matters worse, The Uninstall Program for Girlfriend 1.0 does not work very well at all, leaving undesirable traces of the application in the system. Another annoying problem with all versions of Girlfriend is that they continually pop up annoying messages about the advantages of upgrading to Wife 1.0.
******* BUG WARNING *******
Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before de-installing Wife 1.0, Wife 1.0 will delete MS Money files before executing a self-deinstallation. Then Mistress 1.1 will refuse to install, claiming insufficient system resources.
******* BUG FIX *******
To avoid the above bug, try installing Mistress 1.1 on a different system, and never run any file transfer applications such as LapLink 6.0. Also beware of similar shareware applications that have been known to carry viruses that may affect Wife 1.0 Another solution would be to run Mistress 1.1 via a Use Net provider under an anonymous name. Here again, beware of the viruses which can accidentally be downloaded from the Use Net.
MCI Telecommunications Corp
Last year a friend of mine upgraded Girlfriend 6.0 to Wife 1.0, and found that it is memory hungry, leaving very little system resources for other applications. He is only now noticing that wife 1.0 is also spawning Child Processes, which are further consuming valuable resources. No mention of this particular phenomena was included in the product specification, brochures or documentation, although other users have informed him that this is to be expected due to the nature of the application. To add to the dilemma, Wife 1.0 also installs itself in such a way that it is always launched when the system is initialized, where it can monitor ALL other system activity. In so doing he is finding that some applications such as Poker Night 10.3, Beer Bash 2.5, and Pub Night 7.0 are no longer able to run, crashing the system when selected (even though they always worked fine before). When installed, Wife 1.0 automatically attaches undesired plug-ins, such as Mother-in-Law 55.8 and Brother-in-Law Beta 1.5 release. As a consequence, system performance seems to deteriorate with each passing day. Some features he'd like to see in the release of Wife 2.0 are:
A "Don't remind me again" button
A mute facility minimize button
An install shield feature that allows wife 2.0 to be installed with the option to de-install at any time without the loss of cache and other system resources.
I myself decided to avoid all of the headaches associated with Wife 1.0 by sticking with Girlfriend 2.0. Even here however, I found many problems. Apparently you cannot install Girlfriend 2.0 on top of Girlfriend 1.0. You must de-install Girlfriend 1.0 first. Other users say this is a long standing bug which I should have been made aware of. This may be actionable misrepresentation. Apparently all the versions of Girlfriend have conflicts over shared use of the I/0 port. You think they would have fixed such a stupid bug by now. To make matters worse, The Uninstall Program for Girlfriend 1.0 does not work very well at all, leaving undesirable traces of the application in the system. Another annoying problem with all versions of Girlfriend is that they continually pop up annoying messages about the advantages of upgrading to Wife 1.0.
******* BUG WARNING *******
Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before de-installing Wife 1.0, Wife 1.0 will delete MS Money files before executing a self-deinstallation. Then Mistress 1.1 will refuse to install, claiming insufficient system resources.
******* BUG FIX *******
To avoid the above bug, try installing Mistress 1.1 on a different system, and never run any file transfer applications such as LapLink 6.0. Also beware of similar shareware applications that have been known to carry viruses that may affect Wife 1.0 Another solution would be to run Mistress 1.1 via a Use Net provider under an anonymous name. Here again, beware of the viruses which can accidentally be downloaded from the Use Net.
MCI Telecommunications Corp