the imperial gatekeeper finished version 175 patched Archived Forum Post

Index of archived forum posts

Question:

The Imperial Gatekeeper Finished Version 175 Patched -

Dec 16 '15 at 12:28

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.


Answer

See the online reference documentation for the correct strings to pass to sp_OACreate. See http://www.chilkatsoft.com/refdoc/xChilkatCrypt2Ref.html

The Imperial Gatekeeper Finished Version 175 Patched -

The translation patch brings this subtext to life. In Japanese, the nuances of the dialogue were lost on Western players. Now, with the 1.75 patch, the humor and political intrigue land perfectly. You aren't just a robot stamping papers; you are a cog in an imperial machine, forced to choose between blind loyalty and moral compassion when refugees or desperate merchants arrive at your gate.

: As you successfully perform your duties, you can rise through the ranks of the "Deadguard" or city gatekeepers. the imperial gatekeeper finished version 175 patched

: Players have noted that "v1.75" may appear in different builds (e.g., Steam vs. non-Steam versions), sometimes featuring different character designs or assets due to various updates and localization changes. The "Patched" Content The translation patch brings this subtext to life

Master the Border: The Imperial Gatekeeper Finished Version 1.75 Patched Guide You aren't just a robot stamping papers; you

“Imperfection is costly,” the Threshold replied. “So is holding on.”

Years later, when the Empire's maps grew thick with new names and the High Vault released Version 176 with polite marginalia, he was there to watch again. He had learned enough about patches to be wary, and enough about thresholds to be compassionate. When the technicians argued about sealing the Threshold’s heart more tightly, he put his palm on the basalt and told them a story—one sentence, but true: “Finishings are not ends; they are agreements we make to be less cruel to ourselves.”


Answer

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.


Answer

What about 9.4.x? Did it use the Chilkat.Crypt2 naming? If so, is there a download for it?