That CDSDK.dll is a Canon dll as you're probably aware and you can download
it by just doing a Google search if you need it.
Now here's a straight off-the-hip guess. You loaded some other program
(maybe some Canon camera utilities or other image software) that also uses
this same dll and when you loaded it - it may have broke the link to the dll
for the updater or wrote a different version to the directory.
Since you have communicated with the author, I would assume he had you do a
search of your system and locate the dll - right? If not, where (which
directory) should it be located in Vista and is his update software looking
in the correct directory for that particular version ?
You didn't mention if you tried uninstalling and reinstalling but I'll
assume you did so it would then appear to be a version conflict. Meaning it
could be in the correct directory but his software expects a specific
version. If it's in the correct directory, then replace it with the correct
version that his software requires and that also rules out a possibility
that the file is corrupted. If it now works, I'd bet something else just
got broken if you just replaced it with an older version.
Did he write the updater or just include someone else's code and he's not
really sure what it's doing. You can do some snooping and check the
properties on the main .exe file for the updater and see what company it
came from (most of the time), what version it is, internal name, original
file name, Product name and version. You may get enough info to track down
that software (updater) and check their site or call them.
Just an idea to try,
"Imageman" <Images@Clean.New> wrote in message
> Vista PC
> I hope this isn't too off topic. I'm using IMatch digital asset management
> software, Vista version. Runs fine, but when I tried to run the latest
> updater, it fails for lack of the "CDSDK.dll". The error box title says;
> "IMatch4.exe-Unable to locate the component" The error message says; This
> application failed to start because CDSDK.dll was not found. Re-installing
> the application may fix this problem".
> The very knowledgeable software author doesn't have a solution for this.
> And I thought maybe one of you do - Help appreciated, IM