Huumorit

Kasutaja avatar

simp
Postitusi: 1787
Liitunud: 27 Aug 2006, 23:25
Tsikkel: sv1000n
Asukoht: Tallinn
Tänanud: 122 korda
Tänatud: 195 korda

Re: Huumorit

Lugemata postitus Postitas simp »

pikem(originaal?) versioon:

Last year a friend of mine upgraded from GirlFriend 6.0 to Wife 1.0, and found that it’s a memory hog leaving very little system resources available for other applications. He is now noticing that Wife 1.0 is also spawning Child Processes which are further consuming valuable resources. 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.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).

During installation, Wife 1.0 provides no option as to the installation of undesired Plug-Ins such as Mother-in-law 55.8 and Brother-in-law 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 uninstall Girlfriend 6.0 first. Other users say this is a long standing bug that I should have known about. Apparently the previous 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 6.0 doesn’t work very well leaving undesirable traces of the application in the system. Another thing — all versions of Girlfriend continually popup little annoying messages about the advantages of upgrading to Wife 1.0.

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.

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 atechinternet-users.gifnonymous name. Here again, beware of the viruses which can accidentally be downloaded from the UseNet.

Tech Support Suggestions

These are very common problem 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. You cannot go back to Girlfriend 6.0 because Wife 1.0 is not designed to do this.

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:\YESDEAR to alleviate software augmentation.

Having installed Wife 1.0 myself, I might also suggest you read the entire section regarding General Partnership Faults (GPFs). 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:\YESDEAR because ultimately you may have to give the C:\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 GPFs.

Wife 1.0 is a great program, but very high-maintenance. Consider buying additional software to improve the performance of Wife 1.0. I recommend Flowers 3.1 and Diamonds 2K. Do not, under any circumstances, install Secretary with Short Skirt 3.3. This is not a supported application for Wife 1.0 and is likely to cause irreversible damage to the operating system.

Best of Luck,
Tech Support

+

I'm currently running the latest version of GirlFriend and I have been having some problems lately. I have been running the same version of DrinkingBuddies 1.0 forever as my primary application, and all the Girlfriend releases I have tried have always conflicted with it. I hear that Drinking Buddies runs fine as long as Girlfriend is ran in background mode and the sound is turned off.

Unfortunately, I can't find the switch to turn the sound off. Therefore, I have to run both of them separately. Girlfriend also seems to have a problem coexisting with my Golf program, often trying to abort Golf with some form of timing incompatibilities.

I probably should have stayed with Girlfriend 1.0, but I thought I might see better performance from GirlFriend 2.0. After months of conflicts and other problems, I consulted a friend who has had experience with Girlfriend 2.0. He said I probably didn't have enough cache to run Girlfriend 2.0 and eventually it would require a Token Ring to run properly. He was right, as soon as I purged my cache, and realized that no one in their right mind is installing new token rings, Girlfriend 2.0 uninstalled itself.

Shortly after that, I installed Girlfriend 3.0 beta. Unfortunately, there was a bug in the program and the first time I used it, it gave me a virus. I had to clean out my whole system and shut down for a while. I very cautiously upgraded to Girlfriend 4.0. This time I used SCSI probe first and also installed a virus protection program. It worked okay for a while until I discovered that GirlFriend 1.0 was still in my system. I tried running Girlfriend 1.0 again with Girlfriend 4.0 still installed, but Girlfriend 4.0 has a feature I didn't know about that automatically senses the presence of any other version of Girlfriend and communicates with it in some way. This results in the immediate removal of both versions.

The version I have now works pretty well, but there are still some problems. Like all versions of GirlFriend, it is written in some obscure language I can't understand, much less reprogram. Frankly, I think there is too much attention paid to the look and feel rather than the desired functionality.

Also, to get the best connections with your hardware, you usually have to use gold-plated contacts and I have never liked how GirlFriend is “object-oriented.”

A year ago a friend of mine upgraded his version of Girlfriend to GirlFriendPlus 1.0, which is a Terminate and Stay Resident version of GirlFriend. He discovered that GirlFriendPlus 1.0 expires within a year if you don't upgrade to Fiance 1.0. So he did, but soon after that, he had to upgrade to Wife 1.0, which he describes as a huge resource hog. It has taken up all his space: He can't load anything else. One of the primary reasons he decided to go with Wife 1.0 was because it supposedly came bundled with a feature called FreeSex Plus.

Well, it turns out the resource requirements of Wife 1.0 sometimes prohibits access to FreeSexPlus, particularly the new Plug-ins he wanted to try. On top of that, Wife 1.0 must be running on a well warmed-up system before he can do anything. Although he did not ask for it, Wife 1.0 came with MotherInLaw which has an automatic pop-up feature he can't turn off. I told him to trying installing Mistress 1.0, but he said he heard if you try to run it without first uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before uninstalling itself. Then Mistress 1.0 won't install because of insufficient resources.

P.S. Watch out for the K-I-D-S virus because they have an insatiable appetite for memory and CPU time over and above everything else above.

+

"Kuramus! Ma ei suuda uskuda, et see juhtus JUST minuga !!!! Ja veel vastu jõule! Tulin just koju ja avastasin, et kõik aknad on lahti! KÕIK on tühjaks tehtud! Faking varganäod ja tõprad !!!! Missugune haige mõtlemisega olend teeks seda teisele inimesele, eriti jõulude ajal !!!?? Sa ei ole inimene!!!!! Oled tühine ajupervert!!!! See oli MINU advendikalender ja sul ei olnud mingit õigust selle aknaid avada ja KÕIK mu šokolaadid p***e pista!!!" Ilusaid pühi teile kõigile!

Liitu vestlusega

Vestluses osalemiseks pead sa olema motokommuuni liige

Avan konto

Pole veel liige? Pole probleemi, registreeru ja liitu.
Liikmena saad sa ise postitada ja vastata teisetel või tellida endale teavitusi vestluse edenemise kohta.
Kõik siin on tasuta ja võtab vaid minuti. Kohtusi sellega ei kaasne.

Registreeru

Logi sisse

Mine “Ajaviiteks...”