GIRLFRIEND UPDATE 1.0

Last year a friend of mine upgraded GirlFriend 1.0 to Wife 1.0 and found that it's a memory hog leaving very little system resources for other applications. He is only now noticing that Wife 1.0 also is spawning Child-Processes which are further consuming 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 initialization where it can monitor all other system activity. He's finding that some applications such as PokerNight 10.3, BeerBash 2.5 and PubNight 7.0 are no longer able to run in the system at all, crashing the system when selected (even thought they always worked before).

At installation, Wife 1.0 provides no option as to the installation of undesired Plug-Ins such as MotherInLaw 55.8 and BrotherInLaw Beta release. Also, system performance seems to diminish with each passing day.

The features he'd like to see in the upcoming Wife 2.0 include:

--- A "Don't remind me again" button

--- Minimize button

--- An install shield feature that allows Wife 2.0 to be installed with the option to uninstall at anytime without loss of cache and other system resources.

--- An option to run the network driver in promiscuous mode which would allow the systems hardware probe feature to be much more useful.

I myself decided to avoid all of the headaches associated with Wife 1.0 by sticking with Girlfriend 2.0. Even here, though, I found many problems. Apparently you cannot install Girlfriend 2.0 on top of Girlfriend 1.0. You must uninstall Girlfriend 1.0 first. Other users say this is a long standing bug which I should have been aware of. Apparently the versions of Girlfriend have conflicts over shared use of I/O ports. You think they would have fixed such a stupid bug by now. To make matters worse, the uninstall program for Girlfriend 1.0 doesn't work very well leaving undesirable traces of the application in the system.

Another thing that sucks - all versions of Girlfriend continually pop-up little 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 uninstalling Wife 1.0, Wife 1.0 will de3lete MS Money files before doing the uninstall itself. Then Mistress 1.1 will refuse to install, claiming insufficient resources.

BUG WORK - AROUNDS
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.0 via a UseNet provider under an anonymous name. Here again, beware of the viruses which can accidentally be downloaded from the UseNet.

*******************************************************************************

THE FOLLOWING IS ANOTHER VERSION OF THE ABOVE DOCUMENT

*******************************************************************************

Last year, my friend upgraded his GirlFriend 3.1 to GirlFriendPlus 1.0 (marketing name: Fiancee 1.0). Recently he upgraded Fiancee 1.0 to Wife 1.0 and it's a memory hogger, has taken all his space; and Wife 1.0 must be running before he can do anything. Although he didn't ask for them, Wife 1.0 came with Plug-Ins such as MotherInLaw and BrotherInLaw.

Some features I'd like to see in the upcoming GirlFriend 4.0...
- A "Don't remind me again" button
- Minimize button
- Shutdown feature
- An installshield feature so that Girlfriend 4.0 can be completely uninstalled if so desired (so you don't lose cache and other objects)

I tried running Girlfriend 2.0 with Girlfriend 1.0 still installed, they tried using the same I/O port and conflicted. Then I tried to uninstall Girlfriend 1.0 but it didn't have an uninstall program. I tried to uninstall it by hand, but it put files in my system directory. Another thing that sucks -- in all versions of Girlfriend that I've used is that it is totally "object orientated" and only supports hardware with gold plated contacts.

***** BUG WARNING ********

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

*******************************************************************************

YET ANOTHER VERSION

*******************************************************************************

After extensive research and field testing we have learned that quite a few people who have upgraded BoyFriend 1.0 to Husband 1.0 have found that it's a memory hog leaving very little system resources for other applications. Furthermore, though operation with DOS is fine, Husband 1.0 doesn't do some WINDOWS operations.

She is also noticing that excessive interfacing with Husband 1.0 can lead to unwilling install of Pregancy 0.9, leading to the creation of new sub-systems which can further consume valuable resources. No mention of this particular phenomena was included in the product brochure or the documentation, though other users have informed her that this is to be expected due to the nature of the application.

Not only that, Husband 1.0 installs itself such that it is always launched at system initialization where it can monitor all other system activity. She's finding that some applications such as LadiesNight 10.3, RomanticMovie 2.5, and Shopping 7.0 are no longer able to run at all as Husband 1.0 crashes the system when they're selected (even though they always worked before). At installation, Husband 1.0 provides no option as to the installation of undesired Plug-Ins such as MotherInLaw 55.8 and BrotherInLaw Beta release. Also, system performance seems to diminish with each passing day.

Some features she'd like to see in the upcoming Husband 2.0.
-- Minimize button
-- An install shield feature that allows Husband 2.0 be installed with the option to uninstall at anytime without the loss of cache and other system resources.

I myself decided to avoid all of the headaches associated with Husband 1.0 by sticking with Boyfriend 2.0. Even here, however, I found many problems. Apparently you cannot install Boyfriend 2.0 on top of Boyfriend 1.0. You must uninstall Boyfriend 1.0 first. Other users say this is a long standing bug which I should have been aware of. Apparently the versions of Boyfriend have conflicts over shared use of the I/O port. You think they would have fixed such a stupid bug by now. To make matters worse, the uninstall program for Boyfriend 1.0 doesn't work very well leaving undesirable traces of the application in the system. Another thing that sucks -- all versions of Boyfriend continually pop up little annoying messages about the advantages of upgrading to Husband 1.0

***** BUG WARNING *****

Husband 1.0 has an undocumented bug. If you try to install OtherLover 1.1 before uninstalling Husband 1.0, Husband 1.0 will delete MSMoney files before doing the uninstall itself. Then OtherLover 1.1 will refuse to install, claiming insufficient resources.

***** BUG WORK-AROUNDS *****

Try installing OtherLover 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 Husband 1.0. Another solution would be to run OtherLover 1.1 via a UseNet provider under an anonymous name. Here again, beware of the viruses which can accidentally be downloaded from the UseNet.