• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

"in desperate need of tech support"

webekyle

Banned
I'm currently running the latest version of Girlfriend 5.0 and having some problems. I've been running the same version of DrinkingBuddies 1.0 for years as my primary application, and all the Girlfriend releases have always conflicted with it. I hear that DrinkingBuddies won't crash if you minimize Girlfriend with the sound off, but since 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 Golfware, often trying to abort my Golf program 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, I consulted a friend who has 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 upgrade to run properly. He was right. As soon as I purged my cache, Girlfriend 2.0 uninstalled itself.

Shortly after that, I installed a Girlfriend 3.0 beta. All the bugs were supposed to be gone, but the first time I used it, it gave me a virus. After a hard drive clean up and thorough virus scan I very cautiously upgraded to Girlfriend 4.0. This time using a SCSI probe and virus protection. It worked OK for a while until I discovered Girlfriend 1.0 wasn't completely uninstalled!

I tried to run Girlfriend 1.0 again with Girlfriend 4.0 still installed, but Girlfriend 4.0 has an unadvertised feature that automatically senses the presence of Girlfriend 1.0 and communicates with it in some way, resulting in the immediate removal of both versions!

The version I have now works pretty well, but, like all versions, there are still some problems. The Girlfriend package is written in some obscure language that I can't understand, much less reprogram. And I've never liked how Girlfriend is totally 'object-oriented.'

A year ago, a friend upgraded his version to GirlfriendPlus 1.0, which is a Terminate-and-Stay resident version. He discovered GirlfriendPlus 1.0 expires within a year if you don't upgrade to Fiance9e 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 because it came bundled with FreeSex 1.0. Well, it turns out that the resource allocation module of Wife 1.0 sometimes prohibits access to FreeSex (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 popup feature 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 uninstalling itself. Then Mistress 1.0 won't install anyway, due to insufficient resources. If anybody out there is able to offer technical advice...


**********************************************************************************************


OTHER ISSUES......


---------------------------------------------------------------



Dear (IT) Technical Support:


I am desperate for some help. I recently upgraded from Girlfriend 7.0 to Wife 1.0 and found that the new program began unexpected child processing and also took up a lot of space and valuable resources. This wasn't mentioned in the product brochure.


In addition Wife 1.0 installs itself into all other programs and launches during system initialization where it monitors all other system activity. Applications such as Boys Night Out 2.5, and Golf 5.3 no longer run and crash the system whenever selected. Attempting to operate Saturday Softball 6.3 always fails but Saturday Shopping 7.1 runs instead. I cannot seem to keep Wife 1.0 in the background while attempting to run any of my favorite applications. I am thinking about going back to Girlfriend 7.0 but uninstall doesn't work on this program. Can you please help?

-Joe


---------------------
Answer From Technical:


Dear Joe,


This is a very common problem resulting from a basic misunderstanding.

Many men upgrade from Girlfriend 7.0 to Wife 1.0 thinking that Wife1.0 is merely a UTILITIES & ENTERTAINMENT program. Wife 1.0 is an OPERATING SYSTEM designed by its creator to run everything. You are unlikely to be able to purge Wife 1.0 and still convert back to Girlfriend 7.0 as Wife 1.0 is not designed to do this and it is impossible to uninstall, delete or purge the program files from the system once installed. Some people have tried to install Girlfriend 8.0 or Wife 2.0 but have ended up with even more problems. (See in manual under Alimony/Child Support and Attorney's Fees).


Having Wife 1.0 installed myself, I recommend you keep it installed and deal with the difficulties as best you can. When any faults or problems occur, whatever you think has caused them, you must run the C:\I APOLOGIZE program and avoid attempting to use the *Esc-key. It may be necessary to run C:> \I APOLOGIZE a number of times but hopefully the operating system will return to normal. Wife 1.0, although a very high maintenance program can be very rewarding.

To get the most out of it consider buying additional software such as Flowers 2.0 and Chocolates 5.0. Do not under any circumstances install Secretary (Short Skirt version) as this is not a supported application for Wife 1.0 and the system will almost certainly crash.

Regards,
Technical support
 
The trick to this is to keep Wife 1.0 behind a firewall so it can't get to Mistress 1.0 If Wife 1.0 find the install of Mistress, more than Mmoney will disappear. It's best to keep Wife 1.0 and Mistress 1.0 installed on seperate systems...
 
Back
Top