Anyone have any ideas? We don’t want to use the bloated legacy install and then run it in compatibility mode, and we don’t want to get a current developer to rebuild either app so we can deploy the new PCs. OCX is not properly registered a missing or invalid file. The last ditch effort? Try compatibility mode to XP – The test box with the “bloated” installer can run it, but the clean box cannot. Chances are you are missing Mscomct2.ocx, Msdatlst.ocx and other required old microsoft 32 bit dlls and ocx files. If that is the case, you will have some trouble getting it to run on a new Windows 7 computer.
However in an attempt to fix the issue we ran it on a test box – it copied the OCX file and put entries in the registry – now starting the app says: “unknown error”. If you have an old home-grown vb6 application, you may not have an installer for it. Default Locations are: C:WINNTSystem32 (Windows NT/2000) C:WindowsSystem32 (Windows XP, Vista, 7) In case you are using a 64-bit version of Windows, you should also place it in C:WindowsSysWOW64 Make a backup copy of the original file. There is a legacy installer tool (it does a lot of weird stuff and was written by the same developer) that we don’t want to use because it does a lot of “not useful” stuff, and has out lived its usefulness. In case it doesnt work, you will have to extract tabctl32.ocx to your system directory. But none of the solutions seem to work with this app’s issue and Win7. Normally the error says “Component ‘TABCT元2.OCX’ or one of its dependencies not correctly registered: a file missing or invalid.” Now Googling this I get all kinds of solutions for this in Vista, and some XP, etc.
But when installing/using a home grown app (was developed in house by a programmer who left the company) that is essential to our users there is an error. We finally get a budget to get some new PCs, they come with Windows 7 - no problems yet.
0 kommentar(er)
