I’ve been getting the following errors when I try to launch Delphi:
- “This program has performed an illegal operation and will be shut down.If the problem persists, contact the program vendor.” Then the followingappears: “Delphi32 caused an invalid page fault in module KERNEL32.DLL at0137:bff9a07c”.
- “Cannot open component library ProgramsFilesBorlandDelphi2.0BinCMPLIB32.DCL (error code 1114)”.
What causes these errors and what can I do about them?
What we’ve got here seems to be more of an OS issue than a problem withDelphi, 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 cancause a kernel page fault:
- You may have bad sectors on your hard disk. In that case you should use autility like Norton Utilities’ Disk Doctor to fix any errors. This isthe first thing to check. I’ve learned from experience that kernel page faults are usually due to drive errors. Also, I’vefound that particularly with IDE drives, when you start getting under a coupleof hundred megabytes of space, you start seeing some weird things happen.
- You have file corruption in your EXE. It could be due to condition 1above or to just a bad installation. But since you’vere-installed a few times, I’m thinking that it’s probably due to condition 1.
- You have registry entries that are invalid. This is pretty unlikely tocause a kernel page fault, but if you do a re-installation, make sure to goto the Control Panel, run the Add/Remove Programs property, and remove Delphientirely from the system. This will remove Registry references as well.Then you can do the re-installation. But run a disk diagnostic and anoptimizer prior to re-installation. That way, you know you’ll be installingto a new sector on disk.
- Your OS environment could be corrupt. This is the worst casescenario, but you have to consider it. If you tried all the stuff above,you probably have a bad Windows installation, which will requirea re-setup of your OS. It’s a bit daunting, especially if you have alot of stuff, but sometimes it’s the only way to get the results you require.
Regarding the second problem: This happens occasionally for areason(s) no one seems to know. The usual quick fix for this is todelete the the CMPLIB32.DCL file, then rename the backup file CMPLIB32.~DC toCMPLIB32.DCL. In most cases this will do the trick.