Archived Forum Post
Index of archived forum posts
Question:
Archived Forum PostQuestion:
I have been unsuccessful at getting past sp_OACreate under SqlServer 2012. The same sproc works on a SqlServer 2008 box.
EXEC @hr = sp_OACreate 'Chilkat.Crypt2', @crypt OUT results in -2147221005 for @hr.
Callig get error: EXEC @HR = sp_OAGetErrorInfo @crypt, @Source OUT, @Description OUT;
results in @Description being "Invalid class string".
I have checked the registry, the clsids are there. I even edited permission on crypt2 and crypt2.1 adding full control to everyone. I also verified the DLL's folder has everyone read/exec permissions.
I am at a loss here.
See the online reference documentation for the correct strings to pass to sp_OACreate. See http://www.chilkatsoft.com/refdoc/xChilkatCrypt2Ref.html
Many legacy games mistakenly install the binkw32.dll file into a \System or \Bin subfolder instead of the main directory where the game's executable ( .exe ) resides.
By following these steps, you should be able to get your game working immediately. If your game still isn't launching, let me know: are you trying to play?
The most effective way to resolve this is to ensure the correct version of the Bink Video codec is available to the game. Reinstall the Application/Game
The game relies on older audio codecs (like Indeo or older DirectSound features) that are not enabled by default in modern Windows. How to Fix the "BinkSetVolume12" Error binksetvolume12 fixed work
Here are the most reliable methods to fix the binksetvolume12 issue, ranging from simple file management to system-level repairs. 1. Copy Binkw32.dll to the Root Folder (Most Successful)
Because Bink uses fixed-point math:
The error binksetvolume12 is not a permanent hardware failure. It is a historical artifact—a miscommunication between a legacy audio middleware and modern operating system architecture. But as you have learned, it is entirely fixable. Many legacy games mistakenly install the binkw32
For very old games (like Homeworld Cataclysm ), a DirectX wrapper tool called is an effective "fixed work". This tool translates the game's old DirectX calls into something modern Windows can understand, which can bypass Bink-related issues.
Locate binkw32.dll inside that folder, right-click it, and select .
Whether you replaced the Bink DLL, enforced a single audio stream, leveraged WineD3D, or cleaned the registry’s audio endpoints, you now possess the knowledge to resolve this issue permanently. The phrase is no longer a desperate search query—it is a solved problem. The most effective way to resolve this is
If you own the game on a platform like Steam:
Once you have a "binksetvolume12 fixed work," you can take steps to prevent the error from recurring:
: This error is notoriously common in illegally downloaded games where the "crack" file conflicts with the original Bink video files. Proven Fixes
BinkSetVolume12 sometimes triggers when an application attempts to modify volume on a stream that hasn’t been fully opened. This is common in games that pre-load cutscenes but fail audio initialization.
This approach is much faster on older CPUs (since integer math is simpler than floating-point) and requires no specialized hardware.
It is so that a future version of the ActiveX can co-exist with older versions. You've heard of DLL hell, right? The current naming of "Chilkat_9_5_0." has not changed for several YEARS. Eventually, Chilkat will do a major update to rid itself of all deprecated methods and make long-needed changes which break backward compatibility. When doing so, the name will change -- this will make it so that new programs can use the new version WITHOUT breaking existing older applications.
What about 9.4.x? Did it use the Chilkat.Crypt2 naming? If so, is there a download for it?