Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: Pascal
Expertise: Beginner
May 28, 1997

"Cannot Open Component Library" -- What to do

Question:
I've been getting the following errors when I try to launch Delphi:

  1. "This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor." Then the following appears: "Delphi32 caused an invalid page fault in module KERNEL32.DLL at 0137:bff9a07c".
  2. "Cannot open component library \ProgramsFiles Borland\Delphi2.0\Bin\CMPLIB32.DCL (error code 1114)".

What causes these errors and what can I do about them?

Answer:
What we've got here seems to be more of an OS issue than a problem with Delphi, but I've seen this stuff before and there are ways to deal with it.

With respect to the first problem, there are a number of things that can cause a kernel page fault:

  1. You may have bad sectors on your hard disk. In that case you should use a utility like Norton Utilities' Disk Doctor to fix any errors. This is the first thing to check. I've learned from experience that kernel page faults are usually due to drive errors. Also, I've found that particularly with IDE drives, when you start getting under a couple of hundred megabytes of space, you start seeing some weird things happen.
  2. You have file corruption in your EXE. It could be due to condition 1 above or to just a bad installation. But since you've re-installed a few times, I'm thinking that it's probably due to condition 1.
  3. You have registry entries that are invalid. This is pretty unlikely to cause a kernel page fault, but if you do a re-installation, make sure to go to the Control Panel, run the Add/Remove Programs property, and remove Delphi entirely from the system. This will remove Registry references as well. Then you can do the re-installation. But run a disk diagnostic and an optimizer prior to re-installation. That way, you know you'll be installing to a new sector on disk.
  4. Your OS environment could be corrupt. This is the worst case scenario, but you have to consider it. If you tried all the stuff above, you probably have a bad Windows installation, which will require a re-setup of your OS. It's a bit daunting, especially if you have a lot of stuff, but sometimes it's the only way to get the results you require.

Regarding the second problem: This happens occasionally for a reason(s) no one seems to know. The usual quick fix for this is to delete the the CMPLIB32.DCL file, then rename the backup file CMPLIB32.~DC to CMPLIB32.DCL. In most cases this will do the trick.

DevX Pro
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date