Thread: A Laugh A Day
View Single Post
Old 2009-01-17, 01:36   Link #3452
TinyRedLeaf
Moving in circles
 
 
Join Date: Apr 2006
Location: Singapore
Age: 49
Who cares about Husband 1.0? Wife 1.0 comes with a lot more bugs!

Last year a friend of mine upgraded from GirlFriend 6.0 to Wife 1.0 and found that it's a memory hog leaving very little system resources available for other applications.

He also noticed that Wife 1.0 spawns child processes which consume further valuable resources. No mention of this particular phenomena was included in the product brochure or the documentation, though other users have informed him that this is to be expected due to the nature of the application.

Not only that, Wife 1.0 installs itself such that it is always launched at system initialisation, where it can monitor all other system activity. He discovered that some applications — such as PokerNight 10.3, BeerBash 2.5, and PubNight 7.0 — are no longer able to run on his system at all, crashing the system whenever selected (even though they always worked fine before).

Also, Wife 1.0 installed some undesired plug-ins by default, such as MotherInLaw 55.8 and BrotherInLaw Beta release. These plug-ins have diminished his system performance with each passing day.

Unlike my friend, I decided to avoid the headaches associated with Wife 1.0 by sticking with Girlfriend 7.0. Nonetheless, I still encountered many problems. Apparently you cannot install Girlfriend 7.0 on top of Girlfriend 6.0. You must uninstall Girlfriend 6.0 first. Other users say this is a long standing bug that I should have known about. Apparently the previous versions of Girlfriend have conficts over shared use of the I/O port. You'd think they would have fixed such a stupid bug by now.

To make matters worse, the uninstall program for Girlfriend 6.0 doesn't work very well leaving undesirable traces of the application in the system. Another thing: all versions of Girlfriend continually pop up annoying messages about the advantages of upgrading to Wife 1.0.

What Tech Support advised me to do

Many people upgrade from Girlfriend 6.0 to Wife 1.0 with the idea that Wife 1.0 is merely a Utilities & Entertainment program. Wife 1.0 is indeed an operating system and designed by its creator to run everything.

Bear in mind that it is unlikely you would be able to purge Wife 1.0 and still convert back to Girlfriend 6.0. Hidden operating files within your system would cause Girlfriend 6.0 to emulate Wife 1.0 so nothing is gained. It is impossible to uninstall, delete, or purge the program files from the system once installed. You cannot go back to Girlfriend 6.0 because Wife 1.0 is not designed to do this.

To avoid this problem, 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 UseNet provider under an anonymous name. Here again, beware of the viruses which can accidently be downloaded from the UseNet.

Beware though: 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 Mistress 1.1 will refuse to install, claiming insufficient resources.

To avoid such unnecessary hassle, we suggest installing background application program C:\YES DEAR to alleviate software augmentation. Other useful programs include C:\APOLOGIZE. Avoid excessive use of C:\YES DEAR because ultimately you may have to give the APOLOGIZE command before the operating system will return to normal.

Wife 1.0 is a great program, but very high-maintenance. Consider buying additional software to improve the performance of Wife 1.0. We recommend Flowers 3.1 and Diamonds 24K. Do not, under any circumstances, install Secretary with Short Skirt 3.3. This is not a supported application for Wife 1.0 and is likely to cause irreversible damage to the operating system.


Best of luck,
Tech Support
TinyRedLeaf is offline   Reply With Quote