ocx problems

[Mishlai]

Thanks for the responses.

I tried renaming the oca file (to ocd, humorously enough). Same error.

I opened up depends and looked at the ocx. I'm a little unclear on what all of the field mean, and which ones need to match exactly.

I've included a dependancy walker file in case you want to take a look at it, but here's an example of what I'm seeing:

Threed32.ocx depends on the following:
ADVAPI32, GDI32, KERNEL32, MFC40, MSVCIRT, MSVCRT, MSVCRT40, NTDLL, OLE32, OLEAUT32, RPCPRT4, USER32

and of course itself.

The dependancy walker file I sent is for the 2005 version of threed32.ocx. This is what was on my machine when it stopped working. I also have a 98 version, which comes on the VB cd. Neither works. Both seem to provide the same dependancy walker information at a glance, but I didn't meticulously verify every field.

Under the load order column, all the dlls are listed as "not loaded"

MFC40.dll has the following information in these columns:
File Ver 4.1.0.6140
Product Ver 4.1.0.1
Image Ver 4.1
Linker Ver 3.1
OS Ver 4.0
Subsystem Ver 4.0

File Ver and Product Ver match for most of the dlls. There are discrepancies for MFC40 and Threed32.ocx itself.
Threed32 is File Version 1.0.41.0 and Product Ver 1.0.0.0

All of the Link and Real Checksums match.

File and Link Time stamps are different for many of them: KERNEL32, MFC40, MSVCIRT, MSVCRT, MSVCRT40, NTDL, THREED32.OCX It seems that maybe these are not even supposed to match?

The Image, Linker, OS, and Subsystem versions are generally all over the map. These values do not match each other, and also generally do not match themselves for another file. (i.e. Linker version is not the same for threed32 as it is for kernel32, etc.)

Am I barking up the right tree here? How do I resolve these version discrepancies? - I'm a little wary of fiddling with an MFC dll. It's probably used by almost every app...

I don't have any experience at all with dll hell, if that's even my problem. Any help will be much appreciated.