Dear Sir, Last year I upgraded my system from Girlfriend 7.0 to Wife 1.0 and noticed that the new program began creating problems within the system processing and that took up a lot of space and valuable resources.
Wife 1.0 installs itself into all other programs and launches during system initialization, where it monitors all other system activity.
Applications such as Poker Night 2.3, Girlfriend 3.2 and Saturday Football 5.0 no longer run, crashing the entire system whenever selected :(
I cannot seem to keep Wife 1.0 in the background while running my other favorite applications. Whichever module or software I enter, only Wife 1.0 seems to run and nothing else.
I am thinking about going back to Girlfriend 7.0, but the uninstall from Wife 1.0 to Girlfriend 7.0 does not work on this program. Can you help me, please!!!
RE:RE:Problems when using WIFE 1.0
by geo on Sep 08, 2007 11:00 AM Permalink
These are very common problem men complain about, but is mostly due to a primary misconception. Many people upgrade from Girlfriend 7.0 to Wife 1.0 with the idea that Wife 1.0 is merely a Utilities & Entertainment program. Wife 1.0 is indeed an operating system and designed by its creator to run everything.
It is unlikely you would be able to purge Wife 1.0 and still convert back to Girlfriend 7.0. Hidden operating files within your system would cause Girlfriend 7.0 to emulate Wife 1.0 so nothing is gained. It is impossible to uninstall, delete, or purge the program files from the system once installed. You cannot go back to Girlfriend 7.0 because Wife 1.0 is not designed to do this.
Some have tried to install Girlfriend 8.0 or Wife 2.0 but end up with more problems than the original system. Look in your manual under "Warnings - Alimony/Child support". I recommend you keep Wife 1.0 and deal with the situation.
I suggest installing background application program C:YES DEAR to alleviate software augmentation. Having installed Wife 1.0 myself, I might also suggest you read the entire section regarding General Partnership Faults (GPFs). You must assume all responsibility for faults and problems that might occur, regardless of their cause. The best course of action will be to enter the command C:APOLOGIZE. In any case avoid excessive use of C:YES DEAR because ultimately you may have to give the APOLOGIZE command before the operating system will return to no
