cchecker
1.0.0
Component Checker - COM ActiveX Checker
Luis Leonardo Nuñez Ibarra. Year 2000 - 2003. email: [email protected].
Chilean, married, I have 2 children. Video game and table tennis fan. My first computer was a Talent MSX that my dad bought me back in 1985. On it I took my first steps playing games like Galaga and PacMan and then programming in MSX-BASIC.
Currently my area of knowledge is related to .NET technologies with more than 15 years of experience developing several web pages using ASP.NET with SQL Server and Oracle databases. Technology integrator, service development, desktop applications.
Component Checker is an application that is responsible for verifying which activex controls and libraries are correctly installed. For this, the TLBINF32.DLL library is used, which helps obtain information about the libraries from the Windows registry.
Give a man a fish and you will feed him for a day, teach him to fish and you will feed him for the rest of his life (Chinese Proverb)
After having developed several activex libraries and controls and using third parties, there was no shortage of that component that could not be installed on a particular computer. Given this scenario, I decided to build this utility which reads all the activex libraries in the windowssystem directory and verifies their status. The information is extracted using the TLBINF32.DLL library.
This project occupies 5 ActiveX components
The PVB_XMENU.DLL file is a custom component so that the menus can apply icons and help at the time of selection.
It must be done from the windows command line regsvr32.exe [component name] For Windows 10 you will need to install with administrator permissions.
If you get a component license error when executing the project, you may need to install the Visual Basic 5 runtime (MSCVBM50.DLL) and download the VB5CLI.EXE and VBUSC.EXE files, both available on the Internet for download. This will fix VB5 component licensing issues.
Given the ease with which visual basic allows you to build libraries and activex controls both for personal use and for the projects in which I was working at that time and you had to go to install the application on the end user's PC and the installer crashed because I was not able to resolve the installation of the library or it was installed incorrectly because an external component that it used was missing.
It was the time of the DLL HELL (https://en.wikipedia.org/wiki/DLL_Hell) and many developers of the time who used Visual Basic suffered with it. To help mitigate this problem a little and verify which component was correctly installed, I developed this utility to help get an idea of which components were correctly installed.
Solving the DLL HELL was not easy...
During those years my intention was to offer it for free to the Visual Basic community that was quite active in those years. For this I created a website where I had several other applications that had also been created out of necessity and that I distributed them for free.
I hope that this project that was born from a personal need will be used for study and motivation purposes. How you can copy good ideas and improve them.
