Error 50003 Info

File Name            Size (7/98)  Ver 1.0c   Ver 1.4a  Ver 1.4d  Ver 1.5  Ver 1.5b 1.5c 1.5d  In DLL_UP.ZIP (4/12/04)
=====================================================================================================================
ASYCFILT.DLL        75,818        01-15-97  *          05-19-97  *         *        *     *    *   
COMCAT.DLL          10,146        10-31-96  *          *         *         *        *     *
COMCTL32.OCX        315,585       05-11-98  *          06-24-98  *         *        *     *    05-22-00 
COMDLG32.OCX        66,924        07-19-97  *          11-27-98  *         *        *     *    05-07-99   
CSCLOK32.OCX        35,303        06-17-97  *          11-19-98  *         *        *     *    *   
CSCMD32.OCX         50,957        11-17-97  *          12-01-98  *         *        *     *    *   
CSPLST32.OCX        53,100        06-17-97  *          11-19-98  *         *        *     *    *
CSSPIN32.OCX        41,759        06-17-97  *          11-19-98  *         *        *     *    *   
CSTEXT32.OCX        197,837       07-24-97  *          12-01-98  *         *        *     *    *   
CTL3D32.DLL         15,600        08-21-96  *          *         *         *        *     *
GTLIST32.OCX        167,847       02-05-97  *          *         *         *        *     *
HAMCAL32.DLL        11,775        10-20-95  *          *         *         *        *     *
MCI32.OCX           95,939        01-16-97  *          02-26-99  *         *        *     *    07-19-97
MFC42.DLL           555,434       06-28-98  *          05-11-98  *         09-26-98 *     *    06-19-03   
MSCHART.OCX         523,348       01-16-97  *          *         *         *        *     *
MSVBVM50.DLL        865,317       05-11-98  *          07-19-97  *         *        *     *    07-23-02   
MSVCIRT.DLL         31,630        06-28-98  *          *         *         *        *     *
MSVCRT.DLL          165,924       06-28-98  08-18-98  02-06-99  02-26-99 01-05-99   *     *    06-19-03   
OLEAUT32.DLL        323,508       01-15-97  *          05-18-97  *         *        *     *    *   
OLEPRO32.DLL        15,904        01-15-97  *          05-18-97  *         *        *     *    *   
QPRO32.DLL          73,740        07-24-96  *          11-19-98  *         *        *     *    *   
QRZ32.DLL           40,025        03-12-97  *          *         *         *        *     *
RACCD32A.DLL        26,500        11-15-97  *          *         *         *        *     *
RESIZE32.OCX        26,786        04-28-97  *          *         *         *        *     *
STDOLE2.TLB         7,136         01-15-97  *          05-19-97  *         *        *     *    *   
TABCTL32.OCX        118,781       07-19-97  *          *         *         06-24-98 *     *    05-22-00   
TABCTL32.1          118,781       07-19-97  *          *         *         *        *     *
VB5STKIT.DLL        16,457        01-16-97  *          *         *         *        *     * 

All Windows programs use DLL, OCX and other supporting files.  When an EXE file is compiled in the Visual Basic programming language it uses the existing supporting files on that computer.   Normally a complete Setup package is made which allows the user to install the needed support files. The Visual Basic Setup Program will not overwrite an existing support file if it is the same file or a newer one — it only replaces an older file.   After the Win1010 program is installed, to update the program only takes a new Win1010.EXE file, since the supporting files are already in place on the user's computer. If you attempt to run a program and get the "Unexpected Error 50003" then one or more of your supporting files are older than the ones that were used to compile the Win1010.EXE update. 

The 50003 problem arises many times when you install another new program and its Setup program blindly overwrites existing support files without checking the date of the file. An example can be seen above in the chart of the supporting files used to compile the various Win1010 updates. Note the boldfaced MSVCRT.DLL file above. I installed a new program between Win1010 Versions 1.5 and 1.5b and a new program installation overwrote my file dated 02-26-99 with an older one dated 01-05-99. It also replaced my MFC42.DLL and TABCTL32.OCX files.  There are many different Setup packages in use, and at least one does not check the date before overwriting an existing file as indicated above.  When trying to run my version 1.5, I got the 50003 error, but as you can see from the above chart, my version 1.5b and later versions run OK because they were compiled with the 01-05-99 version of MSVCRT.DLL.

Just before Version 1.4d was compiled, I updated my Visual Basic with MIcrosoft's Y2K Service Pack 3 Update. As you can see on the above chart, quite a few supporting files were updated.

The cause of this 50003 Error problem is that Microsoft does not make their supporting files forward compatible, only backward compatible. This has long been a popular discussion item on the programming newsgroups. Microsoft has promised relief from this problem in future versions of Windows — But what can be done about the problem at the present time?  I have compiled a group of DLL and OCX files that have been updated into a Setup package. The files included are marked in the right hand column above. This package does not have any Win1010 program or data files, only the supporting files.  Choose your original Win1010 destination path, although no new files will be written there and also answer NO to the option to install the FCC files.

The DLL Update Program is a self-extracting file which will be uncompressed into the c:\windows\temp\dll_up folder. These file will not be removed when the setup if finished so that they can be installed again by clicking on the SETUP icon.

If you ever get the 50003 error then you can run the DLL_UP Setup package and it will update any supporting files that need updating. To keep the download as small as possible, only the files included are those that have been updated since the original release of Win1010. If you install the DLL Update package and still have the 50003 error, then you probably installed a real old program written during the Window 95 days and its setup installed some really old support files. If this is the case, see the next paragraph.

Another solution to the 50003 problem is to check the dates of the supporting files listed above in the C:\windows\system folder.  Normally you can find a newer DLL or OCX file on another computer which can be copied to your computer. The file must be the date shown in the chart above or newer. If you manually copy a new supporting file, it must be manually registered. To register you must be at the DOS prompt or at the START - RUN box and enter   regsvr32.exe  msvcrt.dll  or what ever the supporting file name is.  When you hit ENTER or OK, you should get a popup message saying that the file was successfully registered.   If you cannot find a newer supporting file, then email me and I will send you an updated file via email attachment.

If the only 50003 error you get is when you try to go to the Options Menu, then only the TABCTL32.OCX file needs updating. Email me and I will send you this small file and you won't need the complete DLL/OCX download. This file is also on the main Win1010 download web page.

Another sure method to lick the 50003 problem is a complete re-install of Win1010. However, before re-installing, you should run the Remove Existing Programs option in the Control Panel.  This uninstall will only remove the files installed by the Setup program. No data files will be removed.