DLLs are always a "pleasure" to work with. This is the simplified version of my usual troubleshooting of dlls:
1. check if it is present in your system. Under most common installations, this dll should be located in c:\windows\system32
2. also check if ctl3dv2.dll is present in the same folder too. The two kinda work together, so if one is corrupted or missing the other one may throw errors too.
If the above are found then:
3. since this dll cannot be registered (regsvr32 won't work on it) it may be statically linked within the application you are trying to use. The hardcoded path could be anybody's guess but if this is the case then the dll from path in #1 above could be copied to where your program's executable files are located. Then try to run the proggie.
4. one or both are corrupted (need to download the dll as suggested above) and placed into the path as described in #1.
One trick with a lot of dll files is the source where you download it from. I could send you that dll (I won't) but you'd never know what else it does in your system. Bottom line, get it from someone you trust, like a family member or a neighbor with the same operating system.
To understand recursion, one must first understand recursion
Originally Posted by Al Schatz
Reply With Quote
