GotJokes.net arrow Marriage Jokes arrow Upgrade Problems

Main Menu

GotJokes.net
Joke of the Day
Accountant Jokes
Animal Jokes
Applications
Bar Jokes
Blonde Jokes
Cannibal Jokes
Celebrity Jokes
College Jokes
Computer Jokes
Corny Jokes
Cowboy Jokes
Doctor Jokes
Elderly Jokes
Engineering Jokes
Farmer Jokes
Funny Pictures
Funny Videos
Gender Jokes
Genie Jokes
Golf Jokes
Holiday Jokes
Kid Jokes
Knock Knock Jokes
Languages
Lawyer Jokes
Lists
Little Johnny Jokes
Marriage Jokes
Military Jokes
Misc. Funny Jokes 1
Misc. Funny Jokes 2
Misc. Funny Jokes 3
Misc. Funny Jokes 4
Misc. Funny Jokes 5
Misc. Funny Jokes 6
Morals
Musician Jokes
One-Liners
Pickup Lines & Returns
Politician Jokes
Pollock Jokes
Redneck Jokes
Religious Jokes
State Jokes
Tests and Quizzes
Viagra Jokes
Yo Mama Jokes
You Might Be
HelpMyCredit.com

Upgrade Problems

E-mail this Joke
Discretion advised when upgrading.

Last year, a friend of mine upgraded Girlfriend 1.0 to Wife 1.0 and found that it's a memory hog leaving very little system resources for other applications. He is only now noticing that Wife 1.0 is also spawning Child-Processes which are further consuming valuable resources. No mention of this particular aspect was included in the product brochure or documentation, though other users have informed him that this is to be expected due to the nature of the application.

In addition, Wife 1.0 installs itself such that it is always launched at system initialization where it can monitor all other system activity. He's finding that some applications such as PokerNight 10.3, BeerBash 2.5, and PubNight 7.0 are no longer able to run in the system at all, crashing the system when selected (even though they always worked fine before). At installation, Wife 1.0 provides no option as to installation of undesired Plug-Ins such as MotherInLaw 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 up 1. A "Don't Remind M 2. A "M 3. An install shield feature that allows Wife 2.0 to be installed with the option to uninstall at anytime without the loss of cache and other s 4. An option to run the network driver in promiscuous mode which would allow the system's hardware probe feature to be more useful.

I myself decided to avoid all of the headaches associated with Wife 1.0 by sticking with Girlfriend 2.0. Even here, however, I found many problems. Apparently, you cannot install Girlfriend 2.0 on top of Girlfriend 1.0. You must first uninstall Girlfriend 1.0. Other users say this is a long standing bug which I should have been aware of.

Apparently, the versions of Girlfriend have conflicts over shared use of the I/O port. You would think they would have fixed such a stupid bug by now. To make matters worse, the uninstall program for Girlfriend 1.0 doesn't work very well, leaving undesirable traces of the application in the system.

In addition, all versions of Girlfriend continually pop up little annoying messages about the advantages of upgrading to Wife 1.0. ********** 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. Then Mistress 1.1 will refuse to install, claiming insufficient resources.

********** BUG WORKAROUNDS ********** To avoid the above bug, try installing Mistress 1.1 on a different system, and never run any file transfer applications such as Laplink. 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.

 


Bookmark and Share

User Rating:  / 1 Votes
BooooKnee Slapper 
< Prev   Next >