Husband 1.0

Last year a friend of mine upgraded from BoyFriend 1.0 to Husband 1.0 and found that it’s a memory hog, leaving very little system resources available for other applications.

She is now noticing that Husband 1.0 is also spawning Child Processors 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 her that this is to be expected due to the nature of the application.

Not only that, Husband 1.0 installs itself such, that it is always launched at system initialization, where it can monitor all other system activity. She’s finding that some applications such as SpendingSpree 2.4, GirlsNight 3.5 and CocktailNight 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, Husband 1.0 provides no option as to the installation of undesired Plug-ins such as MotherInLaw 5.8 and BrotherInLaw Beta release. Also, system performance seems to diminish with each passing day.

Some features she’d like to see in the upcoming Husband 2.0 include:

1. A “Yes I’ll cook, clean etc.” button.
2. An install shield feature that allows Husband 2.0 be installed with the option to uninstall at anytime without the loss of cache and other system resources.

I myself decided to avoid the headache associated with Husband 1.0 by sticking with BoyFriend 2.0. Even here, however, I found many problems.

Apparently you cannot install BoyFriend 2.0 on top of BoyFriend 1.0; each program begins damaging the other. You must uninstall BoyFriend 1.0 first. Other users say this is a long standing bug that I should have known about. You’d think they would have fixed such a stupid bug by now! To make matters worse, the uninstall program for BoyFriend 1.0 doesn’t work very well, leaving undesirable traces of the application in the system.

Another thing–all versions of BoyFriend 1.0 continually popup little annoying messages about the advantages of upgrading to Husband 1.0.

Bug Warning
Husband 1.0 has an undocumented bug. If you try to install Lover 1.1 before uninstalling Husband 1.0, Husband 1.0 will delete MS Clothing allowance files, before doing the uninstall himself.

More applications that won’t run with Husband 1.0 include Chippendale 2.0, Netballwatching 3.5, Suremoreshoes 6.0, and Cleanup 4.3.

Applications that run very well with Husband 1.0, however, include Bummingaround 1.0, Pubnight 2.3, Golfing 2.7, Pokernight 5.3, and Wanderingeyes 4.9.

The Apple explosion

OFFICE MEMO
Date: 1/18/96

SPINDLER CALLS IN AIR STRIKE, DESTROYS APPLE TO SAVE IT

Stock Price Increases 50%

“We’ll do it better,” Says Microsoft

CUPERTINO, Calif. JANUARY 18, 1996
The massive pile of smoking rubble near Interstate 280 here in Cupertino was not the result of an earthquake or natural gas explosion, as officials first believed.

It now appears that the terrific explosion and fire at Apple Computer headquarters was the result of the first corporate-initiated airstrike on U.S. or California soil in U.S. history.

Sources within Apple have told newspapers that, in an effort to save Apple from an internal coup that would result in the breakup and sale of the company, embattled Apple CEO Michael Spindler called in elements of the California Air National Guard, based at Moffet Federal Air Station in Mountain View, Calif. to bomb and strafe his own headquarters.

Spindler allegedly called the California Air National Guard late last night and ordered the airstrike, using an Apple Macintosh Quadra A/V with experimental sound cards to simulate the voice of California Governor Pete Wilson.

Within Apple, Spindler is seen as a hero. “Cool! He called in an airstrike on his own position to save his company,” said one internal Apple applications developer, who gave his name as “Scooter.”"It was like one of those cool movies about, like, you know, Viet Nam, that I read about it on the Web, dude.”

A memo to key staffers, reportedly written by Spindler himself, explained the need for the sir strike to counter moves by Apple managers and board members to oust him in a corporate coup and to simultaneously increase the company’s marginal revenue. “Existing Macintoshes, both those in use and those in warehouses, will instantly become collector’s items and therefore increase dramatically in value,” according to the memo, which went on to explain that “this action will therefore increase our margins on existing stock with no cost to our sales and manufacturing operations.” Spindler, said to be ailing, is in seclusion. Attempts to reach him by phone mail and fax were unsuccessful.

Apple stock shot up 50% on the news, as Wall Street apparently agreed with Spindler’s strategy. “Blowing up his own headquarters was a stroke of genius,” said one Wall Street analyst. “This is the kind of pure creative, self-destructive genius we used to see when Steve Jobs was at Apple. It’s like the old days. Mac is back!” Overall, computer stock stocks rose 75% as a result of the Apple news, then plunged 80% later in the day on rumors that Dan Dorfman had been seen having lunch with Jim Clark and Marc Andreeson.

The Spindler airstrike memo, obtained via Internet e-mail by this reporter, was fragmented and missing key information. Apparently, the strike was planned for January 1, but key aides to Spindler did not receive the e-mail until yesterday due to routing table buffer problems and addressing errors.

Cupertino city officials issued a statement at 10:00 PST this morning calling the air strike “an unfortunate incident that, while we hope we will all gain something from it, we hope it did not offend anyone of any race, creed, color, religion, thought process or emotional state, and we must emphasize that the City of Cupertino had no role in this incident if it did.” Class-action lawsuits against Apple and the city, alleging emotional trauma resulting in a lost train of thought, loss of computing resources and interrupted Internet access have already been filed in California State Court.

Later, when told by federal officials that the city will qualify for both federal disaster relief funds and labor department funds for unemployment and job training programs as a result of the destruction, Mayor Bob Mellow said, “Cool. We applaud Apple and Mike Spindler for having the vision and courage to take this decisive action, and hope that our earlier statement was taken in the spirit in which it was meant.”

In Redmond, Wash., Microsoft announced plans to build and detonate several networked low-yield nuclear devices at its own headquarters some time in 1997. “This is a project we already had underway,” said a spokeswoman for Microsoft chairman Bill Gates. “We just decided that the marketplace won’t be ready for it until 1997. Or 1998, if we decide that’s when we really want to do it. Or maybe later. Right now, we’re hiring additional staff, developing new technology and getting ready to copy Apple’s idea, strategy and execution. Oops, I meant to say that we’re evaluating previously extant competitive actions.” The project, dubbed Curtains `97, is expected by analysts to be complete some time in 1999.

Apple announced it will sue Microsoft in federal court over the “look and feel” of the use of explosive devices in business and home computing product strategies.

Floppy disk care

Never leave diskettes in the disk drive, as data can leak out of the disk and corrode the inner mechanics of the drive. Diskettes should be rolled up and stored in pencil holders.

Diskettes should be cleaned and waxed once a week. Microscopic metal particles can be removed by waving a powerful magnet over the surface of the disk. Any stubborn metallic shavings can be removed with scouring powder and soap. When waxing the diskettes, make sure the surface is even. This will allow the diskette to spin faster, resulting in better access time.

Do not fold diskettes unless they do not fit into the drive. “Big” diskettes may be folded and used in “little” disk drives.

Never insert a diskette into the drive upside down. The data can fall off the surface of the disk and jam the intricate mechanics of the drive.

Diskettes cannot be backed up by running them through the xerox machine. If your data is going to need to be backed up, simply insert two diskettes into the drive. Whenever you update a document, the data will be written on both diskettes.

Diskettes should not be inserted or removed from the drive while the red light is flashing. Doing so could result in smeared or possibly unreadable text. Occasionally the red light remains flashing in what is known as a “hung” or “hooked” state. If your system is “hooking” you will probably need to insert a few coins before being allowed access to the slot.

If your diskette is full and you need more storage space, remove the disk from the drive and shake vigorously for 2 minutes. This will pack the data enough (Data Compression) to allow for more storage. Be sure to cover all the openings with scotch tape to prevent loss data.

Access time can be greatly improved by cutting more holes in the diskette jacket. This will provide more simultaneous access points to the disk.

Diskettes may be used as coasters for beverage glasses, provided that they are properly waxed beforehand. Be sure to wipe the diskettes dry before using. (see item 2 above)

Never use scissors and glue to manually edit documents. The data is stored much too small for the naked eye, and you may end up with data from some other document stuck in the middle of your document. Razor blades and scotch tape may be used, however, provided the user is equipped with an electron microscope.

Periodically spray diskettes with insecticide to prevent system bugs from spreading.