Skip to main content
If Operating Systems were вееr..
DOS Вееr:
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 Вееr:
At first, came only a 16-oz. can, but now comes in a 32-oz. can. Considered by many to be a "light" вееr. 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 trashcan.
Windows 95 Вееr:
You can't buy it yet, but a lot of people have taste-tested it and claim it's wonderful. The can looks a lot like Mac Вееr's can, but tastes more like Windows 3.1 Вееr. It comes in 32-oz. cans, but when you look inside, the cans only have 16 oz. of вееr in them. Most people will probably keep drinking Windows 3.1 Вееr until their friends try Windows 95 Вееr 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 вееr, even though the manufacturer claims that this is an entirely new brew.
Once you start playing with software you quickly become aware that each
Software package has a revision code attached to it. It is obvious that
This revision code gives the sequence of changes to the product, but in
Reality there's substantially more information available through the rev
Code than that. This is a guide for interpreting the meaning of the
Revision codes and what they actually signify.
1.0: Also known as "one point uh-oh", or "barely out of beta". We had
To release because the lab guys had reached a point of exhaustion and
The marketing guys were in a cold sweat of terror. We're praying that
You'll find it more functional than, say, a computer virus and that its
Operation has some resemblance to that specified in the marketing copy.
1.1: We fixed all the killer bugs...
1.2: Uh, we introduced a few new bugs fixing the killer bugs and so we
Had to fix them, too.
2.0: We did the product we really wanted to do to begin with. Mind you,
It's really not what the customer needs yet, but we're working on it.
2.1: Well, not surprisingly, we broke some things in making major
Changes so we had to fix them. But we did a really good job of testing
This time, so we don't think we introduced any new bugs while we were
Fixing these bugs.
2.2: Uh, sorry, one slipped through. One lousy typo error and you won't
Believe how much trouble it caused!
2.3: Some jеrк found a deep-seated bug that's been there since 1.0 and
Wouldn't stop nagging until we fixed it!!
3.0: Hey, we finally think we've got it right! Most of the customers
Are really happy with this.
3.1: Of course, we did break a few little things.
4.0: More features. It's doubled in size now, by the way, and you'll
Need to get more memory and a faster processor ...
4.1: Just one or two bugs this time ... Honest!
5.0: We really need to go on to a new product, but we have an installed
Base out there to protect. We're cutting the staffing after this.
6.0: We had to fix a few things we broke in 5.0. Not very many, but
It's been so long since we looked at this thing we might as well call it
A major upgrade. Oh, yeah, we added a few flashy cosmetic features so we
Could justify the major upgrade number.
6.1: Since I'm leaving the company and I'm the last guy left in the lab
Who works on the product, I wanted to make sure that all the changes
I've made are incorporated before I go. I added some cute demos, too,
Since I was getting pretty bored back here in my dark little corner (I
Kept complaining about the lighting but they wouldn't do anything).
They're talking about obsolescence planning but they'll try to keep
Selling it for as long as there's a buck or two to be made. I'm leaving
The bits in as good a shape as I can in case somebody has to tweak them,
But it'll be sheer luck if no one loses them.
DIRECTIONS for MICROSOFT TV DINNER
1. You must first remove the plastic cover. By doing so you agree to accept and honor Microsoft rights to all TV dinners.
2. You may not give anyone else a bite of your dinner (which would constitute an infringement of Microsoft's rights). You may, however, let others smell and look at your dinner and are encouraged to tell them how good it is.
3. If you have a PC microwave oven, insert the dinner into the oven. Set the oven using these keystrokes: mstv. Dinn.//08.5min@50%heat// Then enter:
4. If you have a Mac oven, insert the dinner and press start. The oven will set itself and cook the dinner. Be forewarned that Microsoft dinners may crash, in which case your oven must be restarted.
5. Remove the dinner from the oven and enter to be repeated. Try unplugging the microwave and then doing a cold reboot. If this doesn't work, contact your hardware vendor.
6. Many users have reported that the dinner tray is far too big, larger than the dinner itself, having many useless compartments, most of which are empty. These are for future menu items. 7. If the tray is too large to fit in your oven you will need to upgrade your equipment.
7. If you want another variety, call Microsoft Help and they will explain that you really don't want another variety. Microsoft Chicken is all you really need.
8. Microsoft has disclosed plans to discontinue all smaller versions of their chicken dinners. Future releases will only be in the larger family size.
9. Microsoft promises a dessert with every dinner after '98. However, that version has yet to be released. Users have permission to get thrilled in advance.
10. Microsoft dinners may be incompatible with other dinners in the freezer, causing your freezer to self-defrost. This is a feature, not a bug. Your freezer probably should have been defrosted anyway.