ImageMagickObject.dll use - (Moved)

[photoevents]

hello,

I am using commandline imagemagick for the moment and that works fine but I would like to use com+

I registered the dll and then tried running:

The error I get is

==> Variable must be of type "Object".:

What am I doing wrong ?
And any tips/links that discuss this would be nice to get.

(I did search the forum for answers without avail)

Thank you,

Christian

[Jos]

Moved to the appropriate forum.

Moderation Team

[Jos]

Add the Comm Error checking as shown in the Helpfile to get information about the generated error.

Jos

[photoevents]

Okay, I get the error that the dll is not registered.

But, i dit tick the box register when installing imagemagick.

Will try registering manually.

Christian

[photoevents]

using vbs it works

Set img = CreateObject("ImageMagickObject.MagickImage.1")

and after that I can use commandline-alike statements

Christian

[photoevents]

As I am looking for an alternative for oleview (not available anymore) I stumbled upon:

https://www.nirsoft.net/utils/dll_export_viewer.html

Could anyone advice whether this is a safe site ?

I think so, but just want to get some additional confirmation.

Thanks,

Christian

(did not solve my intitially stated problem yet 😞 )

[TheXman]

Nirosft's utilities are safe.  I have been using his suite of utilities for over 10 years.  Nirsoft's Dll Export Viewer will only show you what functions are exported.  You are trying to determine what DLLs are registered.  Nirsoft's RegDllView can show that information.  Note that there is a 32-bit version and a 64-bit version.  Each will show you what is registered for that particular bit level (32 or 64).  However, the information from RegDllView is not as extensive as OleView. 

OleView (both the 32-bit & 64-bit versions) are still available if you know where to look on Microsoft's site.  I don't remember whether mine are from an old Windows Resource Kit or one of the older Visual Studio installs.  The dates on the files are from 2014 if that helps you narrow it down.  And contrary to what you may see on random searches, OleView works fine on Windows 10.  The Microsoft signed version of OleView that I use, that works on both Windows 7 & 10, is 6.3.9600.17298.  It is a bit tricky to get them working at first because they have to be run as administrator and they require the iviewers.dll.

As for your "not registered issue", note that 32-bit processes require 32-bit registered DLLs and 64-bit processes need 64-bit DLLs.  So if you only installed the 32-bit version of ImageMagick, are are running your scripts using the 64-bit AutoIt stub, it will not find the DLL and vice versa.  You need to make sure you have the correct DLLs registered for the version of the script you are executing.

 

Edit:

My OleView (32-bit & 64-bit) files are under "C:\Program Files\Windows Kits\8.1".  So that means that they are in the Windows 8.1 SDK.  I think Windows Update updated them once or twice since then.  I think it also may have been a part of Visual Studio 2013.

Edited April 25, 2020 by TheXman

[photoevents]

Hello 'TheXman',

And thank you for your helpful post.

I installed the 64bit native version of AutoIt and also choose "ImageMagick-7.0.10-7-Q16-HDRI-x64-static" and ticked the box to register the DLL.
After failed testing I registered it manually just to make sure.

The vbs testscript works. The autoit script not.
I could of course launch a vbscript.

Anyways, it is not urgent, I continue to use Imagemagick commandline, but still want to upgrade my script to using 'com' with imagemagick
Also, I do not want to revert back to 32bit.

I'll check your link for the oleview software.

Have a nice day,

Christian

 

[photoevents]

Okay, good news.

I initially ran my testscript in ISN AutoItStudio which gave me the error message.
Then, I tried it from the scite editor and from there it runs without errors.
So, it has something to do with ISN. (running in 32bit ?)

Also, I found oleview in the windows 10 SDK, thanks for that.
It does complain about the viewer not being registered.

Thanks again,

Christian

 

 

[TheXman]

You're welcome. 

3 hours ago, photoevents said:

Also, I found oleview in the windows 10 SDK, thanks for that.
It does complain about the viewer not being registered.

As I mentioned earlier, oleview needs to be run as administrator, especially in Windows 10.  If the 32-bit and 64-bit iviewers.dll files have been registered, which you can verify with RegDllView, just make sure that you either right-click the oleview executable and run as administrator or change the executable's properties to always run as administrator.  That should get rid of the iviewers.dll not registered error.

[photoevents]

Great !
And indeed : "I should read better! 🙂

Christian