Software Page

Computer Nausium.  Will it ever end... probably not!

This page is dedicated to jokes of a more technical nature.

Like other pages of this site, most of what you're about to read (or not as the case may be)

[is crap!  Ed. sorry.] was donated by various devotees to the Church's cause.

i.e.  For having a good laugh.  We enjoyed them and hope you do too.

Pope P 1st (again...)

"May your palm be rough enough to do the job..."


Wife 1.0 - A Software Report From Within The Church

Last year, a user friend of mine upgraded GirlFriend 1.0 to Wife 1.0  (Papal Note: "Why?")
Finding that it was a real memory hogger and it left 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 phenomena was included in the product brochure or accompanying documentation.  Other users have informed him however, that this is to be expected, due to the nature of the application.  Not only that, Wife 1.0 installs itself in such a way that it is always launched at boot-up where it can monitor all other system activity.

The user in question also found out that some applications such as:-  PubNite 7.0, BeerBash 2.5 and PokerNite 10.3 are no longer able to run.  Crashing the system when selected (even though they all worked fine before).

At installation, Wife 1.0 provides no option as to the installation of undesired plugins.  For example MotherInLaw 55.8 and BrotherInLaw 0.98 (Beta Version).  Finally, system performance seems to diminish with each passing day.

Some feature the user would like to see in the release of Wife 2.0 are:-

1.)  A "Don't remind me again" button.
2.)  An "InstallShield" feature that allows Wife 2.0 to be installed with the option to uninstall at any time without the loss of cache or other system resources.
3.)  An option to run the network driver in "promiscuous mode" which would allow the systems "hardware probe" feature to be more useful.  And finally,
4.)  A "Minimize" button.

I myself decided to avoid all the associated headaches 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 uninstall GirlFriend 1.0 first.  Other users say this is a long standing bug of which I should have been aware.  Apparently all the versions of GirlFriend have conflicts over shared use of the I/O port.  You think they would have fixed such an obvious 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.  Another infuriating feature is that all versions of Girlfriend continually popup little annoying dialog boxes 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 deletes all MSMoney files before performing the uninstall itself.  Then Mistress 1.1 refuses to install claiming insufficient resources.
 
******************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 know to carry viruses that may affect Wife 1.0.  Another solution would be to run Mistress 1.1 via  a UseNet group under an anonymous name.  Here again, beware of the viruses which can accidentally be downloaded from the UseNet.


If operating systems were beer...

DOS Beer:
Requires you to use your own can opener, and requires you to read the directions carefully before opening the can.  Originally only came in an 8-oz.  can, but now comes in a 16-oz. can.  However, the can is divided into 8 compartments of 2 oz. each, which have to be accessed separately.  Soon to be discontinued, although a lot of people are going to keep drinking it after it's no longer available.

Mac Beer:
At first, came only a 16-oz. can, but now comes in a 32-oz. can.  Considered by many to be a "light" beer.  All the cans look identical.  When you take one from the fridge, it opens itself.  The ingredients list
is not on the can.  If you call to ask about the ingredients, you are told that "you don't need to know."
A notice on the side reminds you to drag your empties to the trash can.

Windows 3.1 Beer:
The world's most popular.  Comes in a 16-oz. can that looks a lot like Mac Beer's.  Requires that you already own a DOS Beer.  Claims that it allows you to drink several DOS Beers simultaneously, but in reality you can only drink a few of them, very slowly, especially slowly if you are drinking the Windows Beer at the same time.  Sometimes, for apparently no reason, a can of Windows Beer will explode when you open it.

OS/2 Beer:
Comes in a 32-oz can.  Does allow you to drink several DOS beers simultaneously.  Allows you to drink Windows 3.1 Beer simultaneously too, but somewhat slower.  Advertises that its cans won't explode when you open them, even if you shake them up.  You never really see anyone drinking OS/2 Beer, but the manufacturer (International Beer Manufacturing) claims that 9 million six-packs have been sold.

Windows 95 Beer:
The can looks a lot like Mac Beer's can, but tastes more like Windows 3.1 Beer.  It comes in 32-oz. cans, but when you look inside, the cans only have 16 oz. of beer in them.  Most people will probably keep
drinking Windows 3.1 Beer until their friends try Windows 95 Beer and say they like it.  The ingredients list, when you look at the small print, has some of the same ingredients that come in DOS beer, even
though the manufacturer claims that this is an entirely new brew.

Windows NT Beer:
Comes in 32-oz. cans, but you can only buy it by the truckload.  This causes most people to have to go out and buy bigger refrigerators.  The can looks just like Windows 3.1 Beer's, but the company promises to change the can to look just like Windows 95 Beer's - after Windows 95 beer starts shipping.  Touted as an "industrial strength" beer, and suggested only for use in bars.

Unix Beer:
Comes in several different brands, in cans ranging from 8 oz. to 64 oz.  Drinkers of Unix Beer display fierce brand loyalty, even though they claim that all the different brands taste almost identical.  Sometimes the pop-tops break off when you try to open them, so you have to have your own can opener around for those occasions, in which case you either need a complete set of instructions, or a friend who has been drinking Unix Beer for several years.

AmigaDOS Beer:
The company has gone out of business, but their recipe has been picked up by some weird German company, so now this beer will be an import.  This beer never really sold very well because the original
manufacturer didn't understand marketing.  Like Unix Beer, AmigaDOS Beer fans are an extremely loyal and loud group.  It originally came in a 16-oz. can, but now comes in 32-oz. cans too.  When this can was originally introduced, it appeared flashy and colourful, but the design hasn't changed much over the years, so it appears dated now.  Critics of this beer claim that it is only meant for watching TV anyway.

VMS Beer:
Requires minimal user interaction, except for popping the top and sipping.  However cans have been known on occasion to explode, or contain extremely un-beer-like contents.  Best drunk in high pressure
development environments.  When you call the manufacturer for the list of ingredients, you're told that it's proprietary and referred to an unknown listing in the manuals published by the FDA.  Rumours are that
this was once listed in the Physicians' Desk Reference as a tranquillizer, but no one can claim to have actually seen it.


If Microsoft Made Cars!

1. Every time they repainted the lines on the road, you'd have to buy a new car.

2. Occasionally your car would just die on the motorway for no reason, and you'd have to restart it.  For some strange reason, you'd just accept this, restart and drive on.

3. occasionally, executing a manoeuvre would cause your car to stop and fail to restart and you'd have to re-install the engine.  For some strange reason, you'd just accept this too.

4. You could only have one person in the car at a time, unless you bought a "Car 95" or a "Car NT".
But then you'd have to buy more seats.

5. Macintosh would make a car that was powered by the sun, was twice as reliable, five times as fast, twice as easy to drive - but it would only run on five percent of the roads.

6. The Macintosh car owners would get expensive Microsoft upgrades to their cars which would make their cars go much slower.

7. The oil, engine, gas and alternator warning lights would be replaced with a single "General Car Fault" warning light.

8. People would get excited about the "new" features in Microsoft cars, forgetting completely that they had been available in other cars for many years.

9. We'd all have to switch to Microsoft gas and all auto fluids but the packaging would be superb.

10. New seats would force everyone to have the same size
 butt.
11. The airbag system would say "Are you sure?" before going off.

12. If you were involved in a crash, you would have no idea what happened.

13. They wouldn't build their own engines, but form a cartel with their engine suppliers.  The latest engine would have 16 cylinders, multi-point fuel injection and 4 turbos, but it would be a side-valve design so you could use Model-T Ford parts on it.
 14. There would be an "Engium Pro,, with bigger turbos, but it would be slower on most existing roads.

15. Microsoft cars would have a special radio/cassette player which would only be able to listen to Microsoft FM, and play Microsoft Cassettes.  Unless of course, you buy the upgrade to use existing stuff.

16. Microsoft would do so well, because even though they don't own any roads, all of the road manufacturers would give away Microsoft cars free, including IBM!

17. If you still ran old versions of car (i.e.  CarDOS 6.22/CarWIN 3.11), then you would be called old fashioned, but you would be able to drive much faster, and on more roads!

18. If you couldn't afford to buy a new car, then you could just borrow your friends, and then copy it.

19. Whenever you bought a car, you would have to reorganize the ignition for a few days before it worked.

20. You would need to buy an upgrade to run cars on a motorway next to each other.
 


Some useful acronyms

* PCMCIA          People Can't Memorize Computer Industry Acronyms
*
* ISDN               It Still Does Nothing
*
* APPLE            Arrogance Produces Profit Losing Entity
*
* SCSI                System Can't See It
*
* DOS                Defective Operating System
*
* BASIC             Bill's Attempt to Seize Industry Control
*
* IBM                 I Blame Microsoft
*
* DEC                Do Expect Cuts
*
* CD-ROM         Consumer Device, Rendered Obsolete in Months
*
* OS/2                Obsolete Soon, Too.
*
* WWW              World Wide Wait
*
* MACINTOSH   Most Applications Crash; If Not, The Operating System Hangs
*
* PENTIUM        Produces Erroneous Numbers Through Incorrect Understanding of Mathematics
*
* COBOL            Completely Obsolete Business Oriented Language
*
* AMIGA             A Merely Insignificant Game Addiction
*
* LISP                 Lots of Infuriating & Silly Parenthesis
*
* MIPS                Meaningless Indication of Processor Speed
*
* WINDOWS       Will Install Needless Data On Whole System
*
* GIRO                Garbage In Rubbish Out
*
* MICROSOFT    Most Intelligent Customers Realize Our Software (is) Only (for) Fools (&) Teenagers.
(I added the brackets)

 
You must be desparate!Back to contents pageNo more (so far) thank God!