The LangaList

So You Think *You* Have Computer Problems?

I found this item in the current issue of "Science News;" it affects hundreds of millions of us, yet I saw absolutely nothing about it elsewhere on line or in any of the conventional media.

On Sept 27th, a power supply in the National Weather Service's primary supercomputer, a Cray C90, started smoking. Local firefighters put out the small fire promptly, but instead of using the carbon dioxide extinguishers provided by the lab, they used calcium carbonate ("dry chemical") extinguishers.

The calcium carbonate put out the fire all right, but it's highly corrosive, and---get this---actually did more damage than the original fire! In fact, the calcium carbonate *destroyed* the Cray's circuitry and the computer was pronounced "irreparable."

Since then, two smaller backup computers have been trying to keep up, but they're not capable of the speed or accuracy of the Cray. A spokesman for the Weather Service allowed that perhaps "there's more uncertainty" in weather forecasts now.

Fortunately, the Cray was old (a 1994 model), and was already scheduled for replacement by a new IBM model that's almost 50 times faster. But it'll probably be the end of the year before the new computer can be installed, tested, and brought fully up to speed. 

Meanwhile, the two backup computers are limping along, trying to provide the backbone of National Weather Service predictions. Amazing!

(And you know, after seeing this, I realized that all my home's fire extinguishers are the dry chemical type. I guess I'll be buying a carbon dioxide or Halon extinguisher for my computer room soon....)

return to top of page

-------------( Please Visit This LangaList Sponsor!) ------------

--------------( the above is an advertisement )--------------

More On The "Billion Monkey" Rule

A number of readers wrote about the adage: "If a billion monkeys banged on a billion keyboards for a billion years, one of them will eventually produce the complete works of Shakespeare."

They say the Internet proves this not to be true. 8-)

More seriously, the column and discussion at Byte.Com about how large numbers of instances can cause low-probability events to surface have brought up interesting points. For example, it's more likely that you *will* encounter a seemingly random hardware error now than some time ago or some time in the future due to---of all things---the solar sunspot cycle, which is reaching its peak about now.

Other possible effects include power line disruptions, satellite failures, and more.

Check out the Byte column at http://www.byte.com/column/BYT19991019S0002 and then join in the discussion--- it's bound to be interesting!

return to top of page

When AntiVirus Apps Err

Sometimes, Antivirus apps don't go far enough. For example, my current InformationWeek column is about how "SHS" and other little-known or seemingly-benign file types (often completely ignored by antivirus apps) can disguise malicious executables and macro viruses! The column gives specific info on how to beef up your antivirus sweeps to catch these dangerous file types. (See http://www.informationweek.com/langaletter )

But AV apps can sometimes go too far the other way: For example, a number of readers using Norton AV 2000 who also tried to download Microsoft's new Java VM ( http://www.langa.com/newsletters/oct-25-99.htm#java ) got a surprise when their AV software claimed to have found a virus in the Microsoft download!

As it turns out, other versions of Norton AV don't give the false alarm, and in fact there is no virus. Norton is simply being hypersensitive: It seems the new heuristics in AV2K somehow mistake the Microsoft software for a virus.

Now is that a perfect straight line for a joke, or what? 8-)

return to top of page

Time For This Month's Winner!

It's almost time for me to select another winner of a copy of "Poor Richard's E-Mail Publishing: Creating Newsletters, Bulletins, Discussion Groups and Other Powerful Communications Tools." This book has been described as "An excellent, straightforward manual on email publishing, banner ads, driving traffic and especially ethics."  

To enter,  just use the following link to recommend the LangaList to a friend. Your friend just may find a new source of useful information; I just may gain a new subscriber; and you just may win a book! (Full details also available via this link):

http://www.langa.com/recommend.htm#2 

Or, if you'd like to try to win a Palm III organizer, try this link (full details also available here):

http://www.langa.com/recommend.htm#1

Either way, thank you, and good luck!

return to top of page

Backing Up/Restoring The Registry

Dixie Ann Scott writes:

Fred, I sure have learned a lot from your newsletter. I have pretty much discovered that if Fred Langa says its so, its so. I can't tell you how much I have learned from it and how much I look forward to the next one....

I liked your piece from the fellow that downloaded a program to check out the Registry but of course he encourages you to make a back up copy of it. Well Fred...could you discuss how to do the rudimentary function of backing up your registry. I realize that's pretty kindergarten for you but myself and many many others just don't have your expertise yet.

However, if you keep putting out those great newsletters, we are hoping to catch up. Thanks for all your help. Dianne Scott

My pleasure:

Win98 actually automatically makes a backup of the registry each time you restart, but you can do so manually as well:

The key is two executable files, Scanreg.exe and Scanregw.exe, which are normally found in the \Windows\Command and \Windows folders. Microsoft says:

The Registry Checker utility is actually two executable files: Scanreg.exe (ScanReg) is a real-mode, MS-DOS executable file and Scanregw.exe (ScanRegW) is a protected-mode, Windows executable file. They store copies of the entire registry, both User.dat and System.dat, as well as Win.ini and System.ini, into a compressed file (filename.cab).

Once per day at startup a new CAB file containing a backup of the registry is created by Registry Checker. The file name is Rbxxx.cab (where xxx is a unique number assigned when the file is created). The new file replaces the oldest file. These files are located in the \Windows\Sysbckup folder (a hidden folder). Registry Checker always maintains at least the last configuration from which the system was successfully booted.

To force a manual backup:

1. Click Start/Run
2. Type scanregw.exe into the Run dialog box, and click OK

To Restore a backed-up Registry:

1. Click Start/Shut Down/Restart in MS-DOS mode and click OK
2. At the C:\ prompt, type scanreg /restore
3. Select the latest known good backup

If you're still using Win95, see: http://content.techweb.com/winmag//library/1997/1102/95tip5.htm for some registry backup tips.

return to top of page

-------------( Time Is Running Out!) ------------

--------------( the above is an advertisement )--------------