No announcement yet.

Wife V1.0

  • Filter
  • Time
  • Show
Clear All
new posts

  • Wife V1.0

    Just a warning, so people are aware of the problems with the application Wife 1.0, before they install it.

    Last year a friend of mine upgraded GirlFriend 2.0 to Wife 1.0 and found that it's a memory hog leaving very little system resources for other applications.

    He started out by running Casual GirlFriend 1.0, which is Freeware, but after getting the free upgrades, went from that to GirlFriend 2.0 and following that free upgrade seemed quite happy. Then one night he got very drunk and accidentally signed up for Fiance 1.0, which ultimately gives you the upgrade to Wife 1.0

    He is only now noticing that Wife 1.0 also is spawning Child-Processes which are further consuming valuable resources, Child 1.1 has installed before he realised it, it now looks like he will be getting Child 1.2 very shortly too.

    No mention of this particular phenomena was included in the product brochure or the documentation, though other users have informed him that this is to be expected due to the nature of the application.

    Not only that, 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.0 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 just fine before).

    Installation: Wife 1.0 provides no option as to the installation of undesired Plug-Ins such as MotherInLaw 55.8 and BrotherInLaw Beta release. Also, system performance seems to diminish with each passing day. Again, something to be expected?

    Features we'd like to see in the upcoming Wife 2.0.

    A "Don't remind me again" button

    Minimize button

    An install shield feature that allows Wife 2.0 be installed with the option to uninstall at anytime without the loss of cache and other system resources.

    An option to run the network driver in promiscuous mode which would allow the systems hardware probe feature to be much more useful.

    You may have decided to avoid all of the headaches associated with the upgrade of Girlfriend 2.0 to Wife 1.0 by sticking with Girlfriend 1.0

    Even here, however, there are many problems.

    Apparently you cannot install Girlfriend 2.0 on top of Girlfriend 1.0. You must uninstall Girlfriend 1.0 first. Other users say this is a long standing bug which everyone should have been aware of.

    Apparently the versions of Girlfriend have conflicts over shared use of the I/O port. You 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, which Girlfriend 2.0 may pick up on.

    One other thing that annoys... all versions of Girlfriend continually popup little annoying messages about the advantages of upgrading to Wife 1.0. Kinda like Microsoft registration and upgrade messages.

    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 most likely detect the presence of Mistress 1.1 and uninstall itself, taking a large proportion of your cache with it. Wife 1.0 will also cause issues with access to any Child 1.x installs, however the Child 1.x installs will still weigh heavily on your cache, despite the limited access.

    Bug work arounds

    To avoid the above bug, try installing Mistress 1.1 on a dual boot system and never run any file transfer applications such as Laplink 6.0. However, if Wife 1.0 detects any presence of Mistress 1.1, it has been known to uninstall without prior warning. Mistress 1.1 can also become unstable and attempt an upgrade to Wife 2.0, this will cause both Wife 1.0 and Mistress 1.1 to crash simultaneously.

    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 accidently be downloaded from the UseNet.

  • #2
    Thats very good


    • #3
      lol, i need an upgrade


      • #4


        • #5