September 28, 2007

applications conflicts: girlfriend 6.0 - 7.0, wife 1.0 - 2.0, mistress 1.x, etc

hmm .. it seems people didn't finish complaining about different versions of girlfriend, wife 1.0 & even the newest wife 2.0.

to get what I mean, few time ago I posted a mail from a troubled user who upgraded from girlfriend 7.0 to wife 1.0 & was surprised with the radical differences between the two systems. the mail was sent to technical support which replied explaining those difficulties were common to the majority of the men who went through the same process.

if you don't get what I mean, it's about my entry titled: for fun review: girlfriend 7.0 v.s. wife 1.0

a hilarious review for me and many men I guess, but for women, I'm not sure ...

anyways, today I came across new complaints & queries from girlfriend or wife users. the one below is from a girlfriend 7.0 user this time, he saw the consequences of his friend's change to wife 1.0 & learned his lesson, however, we'll see that to stick with less resources consuming systems like girlfriend, has also its disadvantages.

dear tech support,

I have a friend who upgraded last year upgraded from girlfriend 6.0 to wife 1.0 and found that it's insatiable of memory leaving very little system resources available for other applications. worse, he is now noticing that wife 1.0 is also generating child processes which are further consuming valuable resources. this particular phenomena wasn't mentioned at all in the brochure or documentation of the product, though other users have informed him that due to the nature of the application, this is to be expected.

not only that, wife 1.0 installs itself so that it is always launched at system initialization, where it can monitor all other system activity. my friend's finding that he's no longer able to run some applications in the system at all, reputable applications such as pokernight 10.3, beerbash 2.5, and publate 7.0, drive the system to crash the system when selected, even though they always worked fine before.

during installation, wife 1.0 provides no option as to the installation of undesired plug-ins such asmotherinlaw 55.8 and brotherinlaw beta release. Also, system performance seems to diminish with each passing day.

some features he'd like to see in the upcoming wife 2.0.
  • a "don't remind me again" button
  • a minimize button
  • an install shield feature that allows wife 2.0 be installed with the option to uninstall at any time without the loss of cache and other system resources
  • an option to run the network driver in promiscuous mode which would allow the system's hardware probe feature to be much more useful.

I myself decided to avoid the headaches associated with wife 1.0 by sticking with girlfriend 7.0. even here, however, I found many problems. apparently you cannot install girlfriend 7.0 on top of girlfriend 6.0. you must first uninstall girlfriend 6.0. other users say this is a long standing bug that I should have known about. apparently the different versions of girlfriend have conflicts over shared use of the i/o port. I hope they've fixed such a stupid bug by now.

to make matters worse, The uninstall program for girlfriend 6.0 doesn't work very well as it leaves undesirable traces of the application in the system. another thing, all versions of girlfriend especially the latest, continually popup little annoying messages about the advantages of upgrading to wife 1.0.

troubled user

technical support suggestions

dear user,

these are very common problems men complain about, but is mostly due to a primary misconception. many people upgrade from girlfriend 6.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 6.0. hidden operating files within your system would cause girlfriend 6.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. wife 1.0 is not designed to not allow you go back to girlfriend 6.0.

some have tried to install girlfriend 7.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 (gpf's). 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 normal. the system will run smoothly as long as you take the blame for all the gpf's.

wife 1.0 stays however a great program, but it's very high-maintenance. I usually advise users to buy additional software to improve its performance & especially recommend flowers 3.1 and diamonds 2k. do not, under any circumstances, install secretary 3.3 with shortskirt 2.5. this is not a supported application for wife 1.0 and is likely to cause irreversible damage to the operating system.

bug warning:

wife 1.0 has an undocumented bug. if you try to install mistress 1.1 before uninstalling wife 1.0, wife 1.0 will delete msmoney files before doing the uninstall itself. what will have as a result, mistress 1.1 refuses to install, claiming insufficient resources.

bug work-around:

to avoid this bug, try installing mistress 1.1 on a different system and never run any file transfer applications such as laplink 6.0. also, beware of similar shareware applications that have been known to carry viruses that may affect wife 1.0. another solution would be to run mistress 1.1 via a usenet provider under an anonymous name. here again, beware of the viruses which can accidentally be downloaded from the usenet.

Best of Luck,
Tech Support