Last year, my friend upgraded his GirlFriend3.1 to GirlFriendPlus1.0 (marketing name: Fiancee1.0). Recently he upgraded Fiancee1.0 to Wife1.0 and it's a memory hogger, it has taken all his space; and Wife1.0 must be running before he can do anything. Although he did not ask for it, Wife1.0 came with Plug-Ins such as MotherInLaw and BrotherInLaw.
Some features I'd like to see in the Upcoming GirlFriend4.0...
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 supported hardware with gold plated contacts.
***** BUG WARNING ********
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
Last year a friend of mine upgraded from Girlfriend 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 the 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 documentation, 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 PokerNite 10.3 , Bachelor Party 2.5, and Pubnite 7.0 are no longer able to run on the system at all, causing the system to lockup when launched (even though the apps worked fine before).
Wife 1.0 provides no installation options. Thus, the installation of undesired plug-ins such as Mother-in-law 55.8 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 of the headaches associated with Wife 1.0 by sticking with Girlfriend 3.0 Even here, however, I have 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. Guess that explains what happened to versions 1 and 2.
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 have annoying little messages about the advantages of upgrading to Wife 1.0!
All users should be aware that 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. Once that happens, Mistress 1.1 won't install and you will get an "insufficient resources" error message. 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.
Don't even think about a shared directory!!!!!!!!!
I'm currently running the latest version of GirlFriend and I've been having some problems lately. I've been running the same version of DrinkingBuddies 1.0 forever as my primary application, and all the GirlFriend releases I've tried have always conflicted with it. I hear that DrinkingBuddies won't crash if GirlFriend is run in background mode and the sound is turned off. But I'm embarrassed to say I can't find the switch to turn the sound off. I just run them separately, and it works okay. Girlfriend also seems to have a problem co-existing with my Golf program, often trying to abort Golf with some sort of timing incompatibility. I probably should have stayed with GirlFriend 1.0, but I thought I might see better performance from GirlFriend 2.0. After months of conflicts and other problems, I consulted a friend who has had experience with GirlFriend 2.0. He said I probably didn't have enough cache to run GirlFriend 2.0, and eventually it would require a Token Ring to run properly. He was right - as soon as I purged my cache, it uninstalled itself. Shortly after that, I installed GirlFriend 3.0 beta. All the bugs were supposed to be gone, but the first time I used it, it gave me a virus anyway. I had to clean out my whole system and shut down for while.
I very cautiously upgraded to GirlFriend 4.0. This time I used a SCSI probe first and also installed a virus protection program. It worked okay for a while until I discovered that GirlFriend 1.0 was still in my system. I tried running GirlFriend 1.0 again with GirlFriend 4.0 still installed, but GirlFriend 4.0 has a feature I didn't know about that automatically senses the presence of any other version of GirlFriend and communicates with it in some way, which results in the immediate removal of both versions.
The version I have now works pretty well, but there are still some problems. Like all versions of GirlFriend, it is written in some obscure language I can't understand, much less reprogram. Frankly I think there is too much attention paid to the look and feel rather than the desired functionality. Also, to get the best connections with your hardware, you usually have to use gold-plated contacts. And I've never liked how GirlFriend is totally "object-oriented."
A year ago, a friend
of mine upgraded his version of GirlFriend to GirlFriendPlus 1.0, which
is a Terminate and Stay Resident version of GirlFriend. He discovered
that GirlFriendPlus 1.0 expires within a year if you don't upgrade to
Fiancee 1.0. So he did, but soon after that, he had to upgrade to Wife
1.0, which he describes as a huge resource hog. It has taken up all his
space, so he can't load anything else. One of the primary reasons he decided
to go with Wife 1.0 was because it came bundled with PleasurePlus. Well,
it turns out the resource allocation module of Wife 1.0 sometimes prohibits
access to PleasurePlus, particularly the new Plug-Ins he wanted to try.
On top of that, Wife 1.0 must be running on a well warmed-up system before
he can do anything. Although he did not ask for it, Wife 1.0 came with
MotherInLaw which has an automatic pop-up feature he can't turn off. I
told him to try installing Mistress 1.0, but he said he heard if you try
to run it without first uninstalling Wife 1.0, Wife 1.0 will delete MSMoney
files before doing the uninstall itself. Then Mistress 1.0 won't install
anyway because of insufficient resources.
PRODUCT RELEASE INFORMATION
Last year a friend of mine upgraded GirlFriend 6.0 to Wife 1.0 and found that it is 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, crashing the system when selected (even though they always worked fine before). At installation, Wife 1.0 automatically installs undesired Plug-Ins such as MotherInLaw 55.8 and BrotherInLaw Beta release. As a consequence, system performance seems to diminish with each passing day.
Some features he'd like to see in the upcoming wife 2.0:
o Minimize Button
o A "Don't remind me again" button
o An option to run the network driver in promiscuous mode which would allow the system hardware probe feature to have greater use.
o An install shield feature that allows Wife 2.0 to 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 Wife 1.0 by sticking with Girlfriend 2.0. Even here however, I have 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 a long standing bug which I should have been aware of.
Apparently the versions of Girlfriend 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 Girlfriend 1.0 doesn't work very well leaving undesirable traces of the application in the system.
Another annoying problem - all versions of Girlfriend continually popup annoying messages about the advantages of upgrading to Wife 1.0.
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 executing a self-uninstallation. Then Mistress 1.1 will refuse to install, claiming insufficient system resources.
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.
Last year I upgraded from Boyfriend 5.0 to Husband 1.0 and noticed that the new program began making unexpected changes to the accounting software, severely limiting access to wardrobe, flower, and jewelry applications that operated flawlessly under Boyfriend 5.0.
No mention of this phenomenon was included in the product brochure. In addition, Husband 1.0 uninstalls many other valuable programs such as DinnerDancing 7.5, CruiseShip 2.3, and OperaNight 6.1 and installs new, undesirable programs such as PokerNight 1.3, SaturdayFootball 5.0, Golf 2.4 and ClutterEverywhere 4.5.
Conversation 8.0 no longer runs, and invariably crashes the system. Under no circumstances will it run DiaperChanging 14.1 or HouseCleaning 2.6. I've tried running Nagging 5.3 to fix Husband 1.0, but this all purpose utility is of limited effectiveness. Can you help please!
This is a very common problem women complain about, but is mostly due to a primary misconception. Many people upgrade from Boyfriend 5.0 to Husband 1.0 with no idea that Boyfriend 5.0 is merely an ENTERTAINMENT package. However, Husband 1.0 is an OPERATING SYSTEM and was designed by its creator to run as few applications as possible.
Further, you cannot purge Husband 1.0 and return to Boyfriend 5.0, because Husband 1.0 is not designed to do this. Hidden operating files within your system would cause Boyfriend 5.0 to emulate Husband 1.0, so nothing is gained. It is impossible to uninstall, delete, or purge the program files from the system, once installed.
Any new program files can only be installed once per year, as Husband 1.0 has severely limited memory. Error messages re common, and a normal part of Husband 1.0. In desperation to play some of their "old time" favorite applications, or to get new applications to work, some women have tried to install Boyfriend 6.0, or Husband 2.0. However, these women end up with more problems than encountered with Husband 1.0. Look in your manual under "Warnings: Divorce/Child Support". You will notice that this program runs very poorly, and comes bundled with HeartBreak 1.3. I recommend you keep Husband 1.0, and just learn the quirks of this strange and illogical system.
Having Husband 1.0 installed myself, I might also suggest you read the entire section regarding General Partnership Faults (GPFs). This a wonderful feature of Husband 1.0, secretly installed by the parent company as an integral part of the operating system. Husband 1.0 must assume ALL responsibility for ALL faults and problems, regardless of root cause.
To activate this great feature enter the command "C:\ I THOUGHT YOU LOVED ME" Sometimes Tears 6.2 must be run simultaneously while entering the command. Husband 1.0 should then run the applications Apologize 12.3 and Flowers/Chocolates 7.8.
Avoid excessive use of this feature. Overuse can create additional and more serious GPFs, and ultimately YOU may have to give a C:\ APOLOGIZE command before the system will return to normal operations.
Overuse can also cause Husband 1.0 to default to GrumpySilence 2.5, or worse yet, Beer 6.0 Beer 6.0 is a very bad program that causes Husband 1.0 to create FatBelly files and SnoringLoudly wave files that are very hard to delete. Save yourself some trouble by following this tech tip. Just remember! The system will run smoothly, and take the blame for all GPFs, but because of this fine feature it can only intermittently run all the applications Boyfriend 5.0 ran.
Husband 1.0 is a great program, but it does have limited memory and cannot learn new applications quickly. Consider buying additional software to improve performance. I personally recommend HotFood 3.0, Lingerie 5.3 and Patience 10.1. Used in conjunction, these utilities can really help keep Husband 1.0 running smoothly. After several years of use, Husband 1.0 will become familiar and you will find many
valuable embedded features such as FixesBrokenThings 2.1, Snuggling 4.2 and BestFriend 7.6.
A final word of caution! Do NOT, under any circumstances, install MotherInLaw 1.0. This is not a supported application, and will cause selective shut down of the operating system. Husband 1.0 will run only Fishing 9.4 and Hunting 5.2 until MotherInLaw 1.0 is uninstalled.
I hope these notes have helped. Thank you for choosing to install Husband 1.0 and we here at Tech Support wish you the best of luck in coming years. We trust you will learn to fully enjoy this product!"
Dear Tech Support,
Last year I upgraded from Boyfriend 5.0 to Husband 1.0 and noticed a distinct slow down in overall system performance - particularly in the flower and jewelry applications, which operated flawlessly under Boyfriend 5.0.
In addition, Husband 1.0 uninstalled many other valuable programs, such as Romance 9.5 and Personal Attention 6.5, and then installed undesirable programs such as NFL 5.0, NBA 3.0. and Golf Clubs 4.1. Conversation 8.0 no longer runs, and Housecleaning 2.6 simply crashes the system. I've tried running Nagging 5.3 to fix these problems, but to no avail.
First keep in mind, Boyfriend 5.0 is an Entertainment Package, while Husband 1.0 is an Operating System.
Please enter the command: "http: I Thought You Loved Me.htm" and try to download Tears 6.2 and don't forget to install the Guilt 3.0 update.
If that application works as designed, Husband 1.0 should then automatically run the applications Jewelry 2.0 and Flowers 3.5. But remember, over use of the above application can cause Husband 1.0 to default to Grumpy Silence 2.5, Happy Hour 7.0, or Beer 6.1. Beer 6.1 is a very bad program that will download the Snoring Loudly Beta.
Whatever you do, DO NOT install Mother-in-law 1.0 (it runs a virus in the background, that will eventually seize control of all your system resources).
Also, do not attempt to reinstall the Boyfriend 5.0 program. These are unsupported applications and will crash Husband 1.0.
In summary, Husband 1.0 is a great program, but it does have limited memory and cannot learn new applications quickly.
You might consider buying additional software to improve memory and performance. We recommend Hot Food 3.0 and Lingerie 7.7.