|
|
This is the first user report.
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. GirlFriend 2.0 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. I tried running GirlFriend 2.0 with GirlFriend 1.0 still installed, but they tried using the same i/o port and conflicted. Then I tried to unistall 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. GirlFriend 3.0 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 a while. GirlFriend 4.0 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." GirlFriend 5.0 Some features I'd like to see in the Upcoming GirlFriend 5.0...
Another thing that is very irritating -- all versions of Girlfriend continually popup little annoying messages about the advantages of upgrading to Wife 1.0 GirlFriend Plus and Wife 1.0 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 FreeSexPlus. Wife 1.0 must be running before he can do anything. Although he did not ask for it, Wife 1.0 came with Plug-Ins such as MotherInLaw and BrotherInLaw. Well, 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.
MS-Wife 1.0 Testimonial Wife 1.0 is not only a memory hog that leaves 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 though they always worked fine before). Also, system performance seems to diminish with each passing day.. NEWSFLASH I came across more tech notes about this product on the Usenet News Groups. You should immediately add this to your README.TXT and update your WIFE.INI file as noted.
|
•••••••••••••••••••••• |
|
| |
|
|
|
