Two Cents Plain will be an ongoing feature of The Official Jewish American Princess Home Page and will contain viewpoints, opinions, editorials, etc... All input will be considered and we will also post all sincere, well thought out responses to these features. |
Dear HelpLine: | |
I am currently running the latest version of GirlFriend and I've been having a few problems. 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 off the sound. I just run them separately and it seems to work 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 ran out of 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. I had to clean out my whole system and shut down for a 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 new feature that automatically senses the presence of any other version of GirlFriend and communicates with it in some unknown way resulting in the immediately shut down of both version. The version I'm using now works pretty well, but there are still some problems. Like all versions of GirlFriend, it is written in some obscure language that I can't understand much less reprogram. And, frankly, I think there is too much attention paid to the look and feel rather than the desired function. 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 GirlFriend Plus 1.0 expires within 360 days if you don't upgrade to Fiance 1.0. He did but soon after found that same expire conditions exist unless he upgraded to Wife 1.0, which he describes as a resource hog. It has taken up all his space so he can't load anything else. One of the primary reasons he upgraded to Wife 1.0 was because it came bundled with FreeSexPlus. But, it turns out the resource allocation module of Wife 1.0 sometimes prohibits access to FreeSexPlus, 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 an automatic pop-up feature called MotherInLaw that cannot be deactivated. 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 automatically uninstalling itself. Then Mistress 1.0 won't install anyway because of insufficient resources. Looking to your advice on how to sort this all out. |
Submitted by Steve S. of Minnesota, You Betcha!
Dear HelpLine: | |
Last year a friend of mine upgraded Girlfriend 6.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 PokerNite 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 Brother-In-Law 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:
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 uninstall Girlfriend 1.0 first. Other users say this is a long standing bug of which I should have been aware. 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.
As stated above, 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, again, as stated above.
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. |
Submitted by Bob G. of California
