ad info




CNN.com
 MAIN PAGE
 WORLD
 ASIANOW
 U.S.
 LOCAL
 POLITICS
 WEATHER
 BUSINESS
 SPORTS
 TECHNOLOGY
   computing
   personal technology
   space
 NATURE
 ENTERTAINMENT
 BOOKS
 TRAVEL
 FOOD
 HEALTH
 STYLE
 IN-DEPTH

 custom news
 Headline News brief
 daily almanac
 CNN networks
 CNN programs
 on-air transcripts
 news quiz

  CNN WEB SITES:
CNN Websites
 TIME INC. SITES:
 MORE SERVICES:
 video on demand
 video archive
 audio on demand
 news email services
 free email accounts
 desktop headlines
 pointcast
 pagenet

 DISCUSSION:
 message boards
 chat
 feedback

 SITE GUIDES:
 help
 contents
 search

 FASTER ACCESS:
 europe
 japan

 WEB SERVICES:
COMPUTING

From...
PC World

Say good-bye to Windows crashes

August 2, 1999
Web posted at: 12:45 p.m. EDT (1645 GMT)

by Steve Bass
INTERACTIVE

Does Windows crash often for you?

Yes No
View Results

(IDG) -- It was like an episode of Outrageous Police Chase Videos. Under my PC's hood, deep in a Windows folder, dozens of DLL files were wildly pursuing one another, careening out of control and smashing into my hard drive. After each collision, my system would shudder and crash. And I'd end up staring at a lovely blue screen with an ugly Windows error message.

I'll bet you've had the same problem. Unexpected crashes are a sure sign something's wrong under the hood--something far worse than a bad gasket on your search engine. The culprit is almost always a faulty DLL. Don't sweat it. I have a way to get you out of a DLL traffic jam.

Trial By File

First, a few basics. Dynamic link libraries (aka DLLs) are small programs used by Windows applications. Some DLLs are needed by specific programs and rarely cause problems. Others--the usual DLL troublemakers--are part of Windows itself and are shared by many programs. For instance, commdlg.dll, a "common dialog" DLL, enables other programs to create dialog boxes.
MORE COMPUTING INTELLIGENCE
IDG.net   IDG.net home page
  PC World home page
  FileWorld find free software fast
  Make your PC work harder with these tips
 Reviews & in-depth info at IDG.net
 *   IDG.net's desktop PC page
  IDG.net's portable PC page
  IDG.net's Windows software page
  IDG.net's personal news page
  Year 2000 World
  Questions about computers? Let IDG.net's editors help you
  Subscribe to IDG.net's free daily newsletter for computer geniuses (& newbies)
  Search IDG.net in 12 languages
 News Radio
 * Fusion audio primers
 * Computerworld Minute
   

The problem? Some programs dump their own versions of these DLLs--usually outdated, crotchety ones--onto your system. When you launch the program, it loads the old DLL. Even when you quit the app, that DLL hangs around in memory. Later that day, you load another program that uses the same DLL--only a more recent version of it--then wham! The new app gets rear-ended by the old DLL, road rage ensues, and the bits hit the fan.

Windows 98 is supposed to sort out these conflicts whenever you install a new program, comparing DLLs and throwing out the older ones. Trouble is, this does not always happen.

Fortunately, you can get rid of old DLLs yourself. It's a relatively safe task, but even so, back up your system first.

The trick is to search for all the DLLs on your hard disk, find the duplicates, and nuke the prior versions. You can do this by going to the Windows Desktop, hitting F3 to bring up the Find: All Files box, and searching My Computer for all files ending in .dll. (Be sure to search your entire drive, including subfolders.) In the results window, select View, Details and click the Name column heading to sort the files. If your PC is like mine, your drive is filled with duplicate DLLs. Depressing, no?

Now right-click each duplicate file, select Properties, and click the Version tab. The file with the higher version number should be in the \Windows\System folder. If the DLL with the lower version number is in the app's program folder, change its file extension to .d_l. That way, the old version won't load, which will force the program to look in the System folder for the right DLL. (The one place you should see many duplicate DLLs is in your \Windows\Sysbckup folder. Leave those alone.)

Last step: Reboot your PC and load the program that used the older DLL. If it runs, it's probably okay, and you can repeat the process with the next pair of duplicates. If it doesn't run, then restore the original name of the old DLL.

Never a DLL Moment

If all that sounds too complicated, consider getting an application like DLLChecker that'll do the job for you. The program, written by my user group buddy David Jung, scans your PC for DLLs, VBXs, OCXs, and VXDs (say that three times, fast). Then it lists their location and identifies them by size, date, and version. That helps you see the duplicates, compare the versions, and decide which ones to dump. The utility can also archive old DLLs.


RELATED STORIES:
Early code shipped for friendlier, family Windows
July 26, 1999
You can tell a lot about an OS from its games
July 1, 1999
You can prevent 'Windows arthritis'
June 30, 1999

RELATED IDG.net STORIES:
Can Windows 98 provide some sort of solution to DLL hell?
(InfoWorld)
Top Ten Windows Power Tools
(PC World Online)
What's the big DLL? A fix would be appreciated
(InfoWorld)
DLLaGator sinks its teeth into DLL admin problems
(InfoWorld)
Year 2000 World
Note: Pages will open in a new browser window
External sites are not endorsed by CNN Interactive.
 LATEST HEADLINES:
SEARCH CNN.com
Enter keyword(s)   go    help

Back to the top   © 2001 Cable News Network. All Rights Reserved.
Terms under which this service is provided to you.
Read our privacy guidelines.