Jump to content
jayzar

Installing HUSBAND 101

 Share

15 posts in this topic

Recommended Posts

Dear TechSupport,

Last year I upgraded from Boyfriend 5.0 to Husband 1.0 and noticed a distinct slow down in overall system performance - particularly, in the flower and jewelry applications, which operated flawlessly under Boyfriend 5.0.

In addition, Husband 1.0 uninstalled many other valuable programs, such as Romance 9.5 and Personal Attention 6.5 and then installed undesirable programs such as NHL 5.0, CFL 3.0, and Golf 4.1.

Conversation 8.0 no longer runs, and Housecleaning 4.6 simply crashes the system. I've tried running Nagging 5.3 to fix these problems, but to no avail.

What can I do?

Signed,

Desperate

-------

Dear Desperate:

First keep in mind, Boyfriend 5.0 is an Entertainment Package, while Husband 1.0 is an Operating System.

Please enter the command: "http: I Thought You Loved Me.HTML" and try to download Tears 6.2, and don't forget to install the Guilt 3.0 update. If that application works as designed, Husband 1.0 should then automatically run the applications Jewelry 2.0 and Flowers 3.5.

But remember, overuse of the above application can cause Husband 1.0 to default to Grumpy Silence 2.5, Happy Hour 7.0, or Beer 6.1. Beer 6.1 is a very bad program that will download the Snoring Loudly Beta.

Whatever you do, DO NOT install Mother-in-Law 1.0. (It runs a virus in the background that will eventually seize control of all your system resources.) Also, do not attempt to reinstall the Boyfriend 5.0 program. These are unsupported applications and will crash Husband 1.0.

In summary, Husband 1.0 is a great program ,but it does have limited memory and cannot learn new applications quickly. You might consider buying additional software to improve memory and performance. We recommend Food 3.0 and Lingerie 7.7.

Good Luck,

Tech

:);)

Link to comment
Share on other sites

Haha, soooo true!

Timeline

AOS

Mailed AOS, EAD and AP Sept 11 '07

Recieved NOA1's for all Sept 23 or 24 '07

Bio appt. Oct. 24 '07

EAD/AP approved Nov 26 '07

Got the AP Dec. 3 '07

AOS interview Feb 7th (5 days after the 1 year anniversary of our K1 NOA1!

Stuck in FBI name checks...

Got the GC July '08

Link to comment
Share on other sites

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!

Bug warning!!!

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.

BUG WORK-AROUNDS

To avoid the above 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.0 via a UseNet provider under an anonymous name. Here again, beware of the viruses which can accidentally be downloaded from the UseNet.

For all you who were considering upgrading Girlfriend 3.0 to Wife 1.0 here goes a story :

Dear Wife Help desk,

I have had a bizarre experience beginning with Girlfriend 3.0. I was playing with the registry one day and found that the only difference between Girlfriend 3.0 and Wife 1.0 was one registry value.

Wife 1.0 was pretty cool at first since it didn't have the curfew setting and came with some extra resources I could only demo in Girlfriend 3.0. After a while though some of my favorite features from Girlfriend 3.0 began to run into problems. The headache feature kept pushing the fun feature out of memory and the graphics started to fade. Try as I might, I couldn't get Wife 1.0 to revert to Girlfriend 3.0. Thinking I had nothing to loose I kept twiddling with Wife 1.0 and it spawned RUGRAT 1.0 and RUGRAT 2.0 sub programs. Those have kept me so busy with stack overflows, memory leaks, and sound problems that I haven't had much time to fiddle with Wife 1.0 much anymore. Every time I try, RUGRAT 2.0 seems to make itself memory resident which tends to cause Wife 1.0 to crash. Restarting Wife 1.0 takes so long after that, that I usually pack it in for the night and go to bed.

I've been thinking about the Mistress 1.0 program but I'm worried about the compatibility problems like everyone else. My main concern is that trying to un-install Wife 1.0 will leave me with so few system resources that Mistress 1.0 won't work anymore. Does anyone know if there is a patched version for Wife 1.0 that has the ice graphical features of Girlfriend 3.0 and the utilities I've come to expect with Wife 1.0??

Thanks...

Dave

*Reply from Wife Help Desk*

Dear sir, there currently is no patched version of Wife 1.0 with the specs you define in above last paragraph. However, I do have some useful info re: RUGRAT programs. RUGRATs are metered software apps; that is, after 18 years the applications no longer occupy resident memory and are instead archived to your hard drive. The RUGRATs may be temporarily restored as you like, like on Christmas, Easter, birthdays, etc. We have been told by users that Wife 1.0 quickly regains much of the original optimum performance levels as before compilation of the RUGRAT subprograms.

One word of caution: we have had a few reports of the metering function malfunctioning, resulting in the RUGRAT occupying resident memory beyond 18 years; in some cases well into 30 or more years.

There is a patch available on our FTP site: UPAYRENT.EXE, which seems to solve the problem.

- Good Luck,

Wife Help Desk

Link to comment
Share on other sites

Filed: Other Country: Morocco
Timeline
:lol: You guys are all crazy :lol: Thanks for the much needed laugh.

Maggie

08-07-06 I129 NOA1

02-05-07 Visa in Hand

02-13-07 POE JFK w/temp EAD

02-23-07 Civil Marriage

06-17-07 Wedding

08-13-07 Card received in mail

04-14-09 Trip to Maui for Anniversary

06-04-09 Filed to lift conditions

08-13-09 Perm Card received

Link to comment
Share on other sites

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!

Bug warning!!!

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.

BUG WORK-AROUNDS

To avoid the above 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.0 via a UseNet provider under an anonymous name. Here again, beware of the viruses which can accidentally be downloaded from the UseNet.

For all you who were considering upgrading Girlfriend 3.0 to Wife 1.0 here goes a story :

Dear Wife Help desk,

I have had a bizarre experience beginning with Girlfriend 3.0. I was playing with the registry one day and found that the only difference between Girlfriend 3.0 and Wife 1.0 was one registry value.

Wife 1.0 was pretty cool at first since it didn't have the curfew setting and came with some extra resources I could only demo in Girlfriend 3.0. After a while though some of my favorite features from Girlfriend 3.0 began to run into problems. The headache feature kept pushing the fun feature out of memory and the graphics started to fade. Try as I might, I couldn't get Wife 1.0 to revert to Girlfriend 3.0. Thinking I had nothing to loose I kept twiddling with Wife 1.0 and it spawned RUGRAT 1.0 and RUGRAT 2.0 sub programs. Those have kept me so busy with stack overflows, memory leaks, and sound problems that I haven't had much time to fiddle with Wife 1.0 much anymore. Every time I try, RUGRAT 2.0 seems to make itself memory resident which tends to cause Wife 1.0 to crash. Restarting Wife 1.0 takes so long after that, that I usually pack it in for the night and go to bed.

I've been thinking about the Mistress 1.0 program but I'm worried about the compatibility problems like everyone else. My main concern is that trying to un-install Wife 1.0 will leave me with so few system resources that Mistress 1.0 won't work anymore. Does anyone know if there is a patched version for Wife 1.0 that has the ice graphical features of Girlfriend 3.0 and the utilities I've come to expect with Wife 1.0??

Thanks...

Dave

*Reply from Wife Help Desk*

Dear sir, there currently is no patched version of Wife 1.0 with the specs you define in above last paragraph. However, I do have some useful info re: RUGRAT programs. RUGRATs are metered software apps; that is, after 18 years the applications no longer occupy resident memory and are instead archived to your hard drive. The RUGRATs may be temporarily restored as you like, like on Christmas, Easter, birthdays, etc. We have been told by users that Wife 1.0 quickly regains much of the original optimum performance levels as before compilation of the RUGRAT subprograms.

One word of caution: we have had a few reports of the metering function malfunctioning, resulting in the RUGRAT occupying resident memory beyond 18 years; in some cases well into 30 or more years.

There is a patch available on our FTP site: UPAYRENT.EXE, which seems to solve the problem.

- Good Luck,

Wife Help Desk

:dance: good one brother gary

Peace to All creatures great and small............................................

But when we turn to the Hebrew literature, we do not find such jokes about the donkey. Rather the animal is known for its strength and its loyalty to its master (Genesis 49:14; Numbers 22:30).

Peppi_drinking_beer.jpg

my burro, bosco ..enjoying a beer in almaty

http://www.visajourney.com/forums/index.ph...st&id=10835

Link to comment
Share on other sites

Filed: Country: England
Timeline

heh....good stuff! :P

Co-Founder of VJ Fluffy Kitty Posse -
avatar.jpg

31 Dec 2003 MARRIED
26 Jan 2004 Filed I130; 23 May 2005 Received Visa
30 Jun 2005 Arrived at Chicago POE
02 Apr 2007 Filed I751; 22 May 2008 Received 10-yr green card
14 Jul 2012 Citizenship Oath Ceremony

Link to comment
Share on other sites

Filed: Citizen (apr) Country: Brazil
Timeline
:lol: at husband 101



* K1 Timeline *
* 04/07/06: I-129F Sent to NSC
* 10/02/06: Interview date - APPROVED!
* 10/10/06: POE Houston
* 11/25/06: Wedding day!!!

* AOS/EAD/AP Timeline *
*01/05/07: AOS/EAD/AP sent
*02/19/08: AOS approved
*02/27/08: Permanent Resident Card received

* LOC Timeline *
*12/31/09: Applied Lifting of Condition
*01/04/10: NOA
*02/12/10: Biometrics
*03/03/10: LOC approved
*03/11/10: 10 years green card received

* Naturalization Timeline *
*12/17/10: package sent
*12/29/10: NOA date
*01/19/11: biometrics
*04/12/11: interview
*04/15/11: approval letter
*05/13/11: Oath Ceremony - Officially done with Immigration.

Complete Timeline

Link to comment
Share on other sites

Filed: IR-1/CR-1 Visa Country: Ghana
Timeline

that's great! I have yet to run husband 1.0 he hasn't made it to the States yet.

I-130

07/29/2007---began process

01/24/2008---I-130 APPROVED (email)

I-129F

11/2007-------sent I-129F - VSC

02/17/2008---touched (at Vermont)

...I'm CR1 now--IV bill shows CR1--oh well

NVC

02/12/2007---at NVC

02/25/2008---received DS-3032 and AOS bill

03/10/2008---received IV Bill ($400!!)

03/24/2008---mailed DS2032

10/10/2008---approved at NVC

11/06/2008---interview (more evidence)

02/17/2009---2nd interview- PASSED!!!!!

04/01/2009---He finally landed on US soil. (no joke)

4309082_bodyshot_175x233.gif

Link to comment
Share on other sites

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
- Back to Top -

Important Disclaimer: Please read carefully the Visajourney.com Terms of Service. If you do not agree to the Terms of Service you should not access or view any page (including this page) on VisaJourney.com. Answers and comments provided on Visajourney.com Forums are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or other professional advice. Visajourney.com does not endorse, and expressly disclaims liability for any product, manufacturer, distributor, service or service provider mentioned or any opinion expressed in answers or comments. VisaJourney.com does not condone immigration fraud in any way, shape or manner. VisaJourney.com recommends that if any member or user knows directly of someone involved in fraudulent or illegal activity, that they report such activity directly to the Department of Homeland Security, Immigration and Customs Enforcement. You can contact ICE via email at Immigration.Reply@dhs.gov or you can telephone ICE at 1-866-347-2423. All reported threads/posts containing reference to immigration fraud or illegal activities will be removed from this board. If you feel that you have found inappropriate content, please let us know by contacting us here with a url link to that content. Thank you.
×
×
  • Create New...