#1 Nursing Community for Nurses: 302,390 Members

Log in   Sign up   Why join?   | Layout: Switch to narrow layout Color: gold style blue style rose style
Nursing Community for Nurses
Home Forums Articles Specialty Students Region Career Resources

Advanced Search Site Help Site Map

Upgrading to Wife 1.0



Currently Online
Members: 99
Guests: 858
957

Job Spotlight
Sales & Customer Service Rep
Broughton, Illinois
Forum Spotlight
Distance Learning for Nursing

Nursing Degrees

Nursing Articles

The Patient I Failed
Patients Who Have Changed My Life
Rocking Camille
"I'm Leaving You Here....."
The most beautiful curls I'd ever seen
Patients who have changed our lives
We are so lucky....
The Little Old Lady
John Doe
Remember the days before my death
Submit An Article

Nursing Jobs

Job Seeker: Employer:

Scrubs & Gear

Newsletter

Subscribe to the free allnurses.com email newsletter. We will keep you informed of nursing news, articles, discussions, and more.

Enter your email address:

Read current:
Nursing Newsletter

How-To allnurses

allnurses videos

Welcome to allnurses: A Nursing Community for Nurses

The largest most active online nursing community. Join 302,390 nurses from around the world to learn, communicate, and network. For full allnurses.com access, register today - it's free! Problems during registration? Please don't hesitate to contact support.

Would you like to comment?
Join or Login if already a member.
 
 
Thread Tools Search this Thread
  #1  
Old Feb 27, 2002, 04:24 PM
ShadowKnight
Join Date: Feb 2002
Upgrading to Wife 1.0

Upgrading to Wife 1.0

Last year a friend of mine upgraded from Girlfriend 4.0 to Wife 1.0 and found that it's a memory hog leaving few system resources for other applications. He is also now noticing the Wife 1.0 is also spawning Child-processes which are further consuming valuable resources. No mention of this particular phenomenon was included in the product documentation, though other users have informed me that this is to be expected due to the nature of the application.
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. Some applications such as PokerNite 10.3 , Bachelor Party 2.5, and Pubnite 7.0 are no longer able to run on the system at all, causing the system to lockup when launched (even though the apps worked fine before).

Wife 1.0 provides no installation options. Thus, the installation of undesired plug-ins such as Mother-in-law 55.8 and the Brother-in-law Beta is unavoidable. Also, system performance seems to diminish with each passing day.

Some features my friend would like to see in the upcoming Wife 2.0:

A "don't remind me again" button.
Minimize button.
Ability to delete the "headache" file
An install feature that provides an option to uninstall 2.0 version without loss loss of other system resources.
An option to run the network driver in "promiscuous mode" allowing the the system's Hardware Probe feature to be much more useful/effective.

I myself wish I had decided to avoid all of the headaches associated with Wife 1.0 by sticking with Girlfriend 3.0 Even here, however, I have found many problems. Apparently you cannot install Girlfriend 4.0 on top of girlfriend 3.0. You must uninstall Girlfriend 3.0 first, otherwise the two versions of Girlfriend will have conflicts over shared use of the I/O port. Other users have told me that this is a long-standing problem that I should have been aware of. Guess that explains what happened to versions 1 and 2.

To make matters worse, the uninstall program for Girlfriend 3.0 doesn't work very well, leaving undesirable traces of the application in the system. Another identified problem is that all versions of Girlfriend have annoying little messages about the advantages of upgrading to Wife 1.0!

VIRUS ALERT

All users should be aware that 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. Once that happens, Mistress 1.1 won't install and you will get an "insufficient resources" error message. To avoid the aforementioned bug, try installing Mistress 1.1 on a different system and " never" run any file transfer applications(such as Laplink) between the two systems.

FYI: Don't even think about a shared directory!!!!!!!!!


Just a little fun, please dont kill me ladies

Top
  #2  
Old Feb 27, 2002, 05:40 PM
Registered User
Join Date: Oct 2001

I'm a woman, but I'm familiar with the above programs. I'll submit my resume as programmer, systems analyst and systems manager if you wish, although that was a previous life.

The problem you might find if you attempt to install any of the mistress v.xx programs is that it causes the wife.1 to abort. As you mentioned above, this creates a major drain on ALL system resources. Wife.2 and later versions start out relatively smoothly, but soon spawn subprograms which often result in total system breakdown. Uninstalling wife.1 is not recommended.

Love

Dennie

Top
Sponsored Links
 
Would you like to comment?
Join or Login if already a member.



Currently Active Users Viewing: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search



New To Site?
Need Help?

All times are GMT -5. The time now is 04:50 AM.

Upgrading to Wife 1.0

Copyright © 1996-2008, allnurses.com. All rights reserved.  allnurses.com, Inc. Advertising Information