OCX and Test Case 31

When we just use tabctl32.ocx in a form, the software does not break into the debugger, and all of our other EXEs run fine; it's just with mscomctl.ocx.

And here's a dump of when another app is run with mscomctl.ocx (on load this time):

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.

*** wait with pending attach
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 00400000 0050b000 C:\Program Files\App\app2exe
ModLoad: 77780000 7789e000 C:\Windows\system32\ntdll.dll
ModLoad: 73640000 73671000 C:\Windows\system32\verifier.dll
ModLoad: 734b0000 734d0000 C:\Windows\system32\vrfcore.dll
ModLoad: 73470000 734ad000 C:\Windows\system32\vfbasics.dll
ModLoad: 766e0000 767b8000 C:\Windows\system32\kernel32.dll
ModLoad: 732a0000 733f3000 C:\Windows\system32\MSVBVM60.DLL
ModLoad: 76990000 76a2e000 C:\Windows\system32\USER32.dll
ModLoad: 77970000 779bb000 C:\Windows\system32\GDI32.dll
ModLoad: 76bf0000 76caf000 C:\Windows\system32\ADVAPI32.dll
ModLoad: 76590000 76653000 C:\Windows\system32\RPCRT4.dll
ModLoad: 76040000 76184000 C:\Windows\system32\ole32.dll
ModLoad: 76350000 763fa000 C:\Windows\system32\msvcrt.dll
ModLoad: 76a30000 76abc000 C:\Windows\system32\OLEAUT32.dll
ModLoad: 778d0000 778ee000 C:\Windows\system32\IMM32.DLL
ModLoad: 767c0000 76887000 C:\Windows\system32\MSCTF.dll
ModLoad: 778a0000 778a9000 C:\Windows\system32\LPK.DLL
ModLoad: 778f0000 7796d000 C:\Windows\system32\USP10.dll
ModLoad: 750e0000 7511f000 C:\Windows\system32\uxtheme.dll
ModLoad: 75db0000 75e0f000 C:\Windows\system32\SXS.DLL
ModLoad: 74de0000 74f74000 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6000.16386_none_5d07289e07e1d100\comctl32.DLL
ModLoad: 762f0000 76345000 C:\Windows\system32\SHLWAPI.dll
ModLoad: 76cb0000 7777e000 C:\Windows\system32\shell32.dll
ModLoad: 75ed0000 75ee4000 C:\Windows\system32\Secur32.dll
ModLoad: 75ef0000 75f0e000 C:\Windows\system32\USERENV.dll
ModLoad: 76400000 76588000 C:\Windows\system32\SETUPAPI.dll
ModLoad: 747d0000 74887000 C:\Windows\system32\PROPSYS.dll
ModLoad: 76260000 762e4000 C:\Windows\system32\CLBCatQ.DLL
ModLoad: 75430000 75468000 C:\Windows\system32\rsaenh.dll
ModLoad: 27580000 27685000 C:\Program Files\App\mscomctl.ocx
ModLoad: 76890000 76904000 C:\Windows\system32\comdlg32.dll
(dc4.f20): Break instruction exception - code 80000003 (!!! second chance !!!)
eax=000001ff ebx=734baff0 ecx=777a14cd edx=00000000 esi=00000000 edi=000001ff
eip=777c2ea9 esp=0012f3e8 ebp=0012f5e8 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\system32\ntdll.dll -
ntdll!DbgBreakPoint+0x1:
777c2ea9 c3 ret

mscomctl is a Microsoft OCX.

Now this is a show-stopper: other programs that are using the same OCX. If they are uninstalled, somehow the OCX registration unregisters itself and the app.exe program will not run, giving the error:

Run-time error '339':
Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid

Thanks, Bruce. SxS fixed this problem.

Hi Bruce,

I also have the same problem. Should I recompile the VB application with the new version of mscomtl and then test it on the vista machine.

Thanks,

Raji