GirlFriend also seems to have a problem coexisting with my Beer 1.0 program, often trying to abort Beer 1.0 with some sort of timing incompatibility, which causes a major problem since Beer 1.0 normally follows Skydiving 1.0 in the operating sequences. 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, however, the Token Ring absorbed the resources needed to run Skydiving 1.0 and Beer 1.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, I ran it with Saftey Meeting 2.0 and Mile High Club 3.3. It gave me a virus which precluded me from running Mile High Club anyway. 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 with Safety Meeting 2.0 and Mile High Club 3.3 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 unlike BASE 1.2 which requires just the opposite in order to avoid a crash. 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." but refuses to recognise E.F.S. as an essential operating system component.
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. Despite the known system control losses he did it anyway and found that even more resourses allocated to Skydiving 1.0, Beer 1.0, Safety Meeting 2.0 were being used. To make matters worse, 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 Skydiving 1.0 or Beer 1.0.
One of the primary reasons he decided to go with Wife 1.0 was because it came bundled with FreeSexPlus, which unknown to him at the time, has severe conditional parameters. Well, it turns out the resource allocation module of Wife 1.0 sometimes prohibits access to FreeSexPlus, particularly the new Plug-lns 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 MotherlnLaw which has an automatic pop-up feature he can't turn off. I told him to try installing Skygoddess 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 Skygoddess 1.0 and most other recreational programs won't install anyway because of insufficient resources, leading to over use of Beer 1.0.
Another friend found out that after eleven years running WifeAndKids 1.0, the Wife program decided to link to Boyfriends 2.0. He now allows to run any version of Beer, Girlfriends and Skydiving. His only problem now is that when he uninstalled Wife 1.0 it automaticly degrade his version of Wallet 1.0 to Wallet 0.5.
Page best viewed with