Number 217 - June 2001
Modem Non-Driver
by Joe Sherry - NOCCC , flaginfo@bigfoot.com - Dec 2000
    Have you installed a modem using the driver supplied by the manufacturer, and get this message when you try to go on-line The driver does not support your hardware? Don't worry.

    It seems that some of the modems sold by Frys with a 100% rebate (i.e., free) have this problem. Here is the solution I use.

    When that message comes up, first press Enter for OK, and then try to go on line again. If it disconnects again, try a third and fourth time.

    On my machine, it usually connects after the third try. So, don't give up. This is also a solution (trying a few times) to use with other such problems. It has served me well. Often the solution is a simple try it again a few times.

    A while back my daughter, then an executive assistant to the Regional VP of a major corp., invited me to lunch. While sitting in her office waiting for her to be ready to leave, a call (yell) came from the Conference Room; "Suzanne, our Regional meeting is stopped because this darn piece of equipment isn't working right. You're a great fix-it person. See if you can fix this while we go to lunch."

    She responded, "Okay," and the executive meeting attendees all left. Then she went into the conference room and returned in about two minutes. "Lets go to lunch now," she said.

    "Did you fix it?" I asked. "Of course!" she said. "What did you do?" I inquired. She replied, "I turned it off and then back on."
TOGGLE Editor's Note:
    This non-thinking man's story is an illustration of how to solve many problems that occur in other areas of computing. Although we much prefer to know why something has failed to perform as it should, so we can take some rational action to solve or correct it, often the reason for failure is not obvious and the solution elusive. Troubleshooting the problem seems to lead nowhere. As has been mentioned in previous articles, we have just given up in frustration, turned off the machine and gone away for a while. When we turned the machine back on, everything was working as it should. Often, it is as simple as a reallocation of system resources, which occurs when a machine, especially a Windows-based machine, is re-booted. We are reminded of the following allegorical tale heard many years ago. Somehow it seems apropos...

    One summer afternoon a bee was happily buzzing around a meadow. While it was collecting pollen from a flower, a grazing horse ate the flower -- bee and all. The bee was very upset by this event. Suddenly it was transported from a blissful, trouble-free environment to the dark and unfamiliar confines of the horse's stomach. How was the bee to get out of this predicament? -- But the atmosphere in the horse's stomach was so warm and comfortable that the bee relaxed and eventually fell asleep. When it woke up the horse was gone.

    Or ... "Don't sweat the small stuff."

    In the words of George Carlin's "hippy dippy weatherman" who, after reporting a series of line squalls and heavy thunder storms heading for the region, announced late-breaking news that intercontinental ballistic missiles have been detected heading for the continent: "... so don't sweat those thunderstorms!"
  Number 217 - June 2001