|
2004/03/28, 04:18 AM
I can't believe no-one has posted this before, but I couldn't find it on fit buddy so apologies if any repetition:
Problems with MS Girlfriend 1.0
I'm currently running the latest version of Girlfriend and having some problems. I've been running DrinkingBuddies 1.0 all along as my primary application, and all the Girlfriend releases have conflicted with it.I hear the DrinkingBuddies won't crash if you run Girlfriend in background mode with the sound switched off. But I'm embarrassed to say that I can't find the switch to turn it off. I just run them separately, and it works OK.
Girlfriend also seems to have a problem coexisting with my Golf program, often trying to abort it with some sort of timing incompatibility.
I probably should have stayed with Girlfriend 1.0, but I thought I might see better performance with Girlfriend 2.0. After months of conflicts and other problems, I consulted a friend who has had experience with Girlfriend 2.0. He said that I probably didn't have enough cache to run Girlfriend 2.0 and that 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.
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 virus protection. It worked OK for a while until I discovered Girlfriend 1.0 was still in my system! I tried to run Girlfriend 1.0 again with Girlfriend 4.0 still installed, but Girlfriend 4.0 has a feature that I didn't know about that automatically senses the presence of Girlfriend 1.0 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 that I can't understand, much less e-program
Frankly, I think that there is too much attention paid to the look and feel and not enough to 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 Girfriend to GirlfriendPlus 1.0, which is a Terminate and Stay Resident version of Girfriend. 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, you have 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 that he upgraded to Wife is that it came bundled with FreeSexPlus 1.0. Well, it turns out that the resource allocation module of Wife 1.0 sometimes prohibits access to FreeSexPlus, particularly the new Plug and Play items 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. And, although he did not ask for it, Wife 1.0 came with MotherInLaw 1.0 which has an automatic pop-up feature that he can't turn off. I told him to install Mistress 1.0, but he said that he heard that if you try to run it without first uninstalling Wife, that Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.0 won't install anyway due to insufficient resources.
Anybody out there able to offer technical advice.....
>> Date:Mon Jun 1 9:40:47 1998 GMT/BST
>> From:PW
>> If you run Wife1.0 for a while you may find you receive a free Baby1.0 (without manuals) after nine months. This uses even more Cache and often crashes at seemingly random intervals. Also, you can't run Sleep1.0 for a good twelve months. That said apparently running Baby1.0 has lots of features which you only discover given time.
>>
>> Date:Mon Jun 1 9:53:07 1998 GMT/BST
>> From:Box
>> Trader I had a similar problem; found the solution was to install Shopping.Windows 98 - All versions of Wife, Girlfriend and Fiancee run perfectly under this, with just one main drawback - a continual decline of resources for MsMoney .
>>
>> Date:Mon Jun 1 10:40:46 1998 GMT/BST
>> From:Nervous
>> Have you tried Baby 1.0 release 2 (this is not just a maintenance patch) ? It seems to co-exist quite well with Release 1 (you don't have to upgrade or de-install Release 1 before release 2) and, having had all the implementation and user experience with release 1, release 2 is a doddle.
>>
>> Date:Mon Jun 1 10:42:40 1998 GMT/BST
>> From:JJ2 hswt(nr)- PW:
>> I've sent off for my copy of Baby 1.0 - should be here in July sometime. Apparently I'll have to run a complete uninstall on Going-Out 3.1 and in particular Pub Raider 4.2. Someone told me that Baby 1.0 comes with a freeware copy of Mother-in-Law which installs itself automatically and is very difficult to remove unless you uninstall Wife 1.0 at the same time. But I'm extremely attached to Wife 1.0 and will only consider this as a last resort. Any tips....?
>>
>> Date:Mon Jun 1 10:54:25 1998 GMT/BST
>> From:ChilliPepper
>> The problem with all versions of Baby is that they frequent purge their internal caches as well as producing unexpected dumps filling and sometimes overflowing the repository supplied for this purpose. This, the continuous leaks of internal resources and the frequent rejections of input (sometime delayed) would suggest an immediate upgrade to the newest version of Toddler. This in itself is not without defects however and is only available after a qualifying period where you have owned Baby for some considerable time.
>>
>> Date:Mon Jun 1 15:14:46 1998 GMT/BST
>> From:Spodfather
>> If you ask me, the problem with the Baby suite is the lifetime cost of ownership. Once you buy the software, you're into a forced upgrade commitment, not only for the software, but all of the ancillaries and peripherals. The SchoolFees 3.2 plug-in for MSMoney, for instance. What really worries me is the number of users who fail to realise that well into the lifecycle you have to roll-out Teenager 1.x, with a sudden increase in resource utilisation, including the possible need to upgrade the platform to House 2.0, and the problems with bus bandwidth leading to the installation of Mini 0.8, which soon leads to localised crashing and massive resource use by Dr Watson.
>>
|
