FindimagePos failing to find search img on compiled scp

[AntoniusMomac]

I don't recall if this is normal behavior and I need to package up the search images. I don't recall having to ever do this but I would love to hear input from everyone.

So the env is Windows 7 pro 64bit. MS 14.0.18 and a compiled exe.

On the machine I developed the script on, I'm the admin so everything works. The script if fine and so is the compiled exe. On a separate workstation where I'm not the admin, I get the FindImagePos is missing the search image error from the same exe.

I guess it might be rights, or a missing path. Any ideas of where to look?

Many thanks in advance.

[Marcus Tettmar]

Gotta be a path issue. Could be admin issue but only if the images are in a folder that requires admin privs.

What path is specified in FindImagePos? Do they exist? If relative do they exist? If BMP_DIR does a folder same name as script/exe exist at same level as script? If SCRIPT_DIR do they exist in same folder as scriopt/exe?

[AntoniusMomac]

What path is specified in FindImagePos? Do they exist? If relative do they exist? If BMP_DIR does a folder same name as script/exe exist at same level as script? If SCRIPT_DIR do they exist in same folder as scriopt/exe?

Oh my Marcus... Mea culpa!

I can't believe that after 8 wonderful years and many MANY compiled scripts that i have somehow forgotten about this. I believe that I always used the SCRIPT_DIR variable as the path to all my images in the past and moved them accordingly. But I have been spoiled by the image capture wizard recently. What a brilliant design improvement. Max effect / Min effort for the user.

I didn't even notice that the compiled exe process puts the BMP_DIR into the compiled directory location...

I corrected that part. However, now I have a "Cannot find ircv.dll"

What path should I look for/in?

Cheers!

[Marcus Tettmar]

The compiler should also copy ircv.dll for you.

If not, copy it from the Macro Scheduler program folder to the .exe location.

[AntoniusMomac]

THANK YOU - All is fine and as intended. I advise the following to anyone the seems to have issues running exe's after compile:

For anyone that is having issues out there, I suggest making a clean directory to which you compile your scripts and take note of all the supporting files. You will want to copy this entire package to other machines.

ALSO, another method would be to simple compile to a network share and launch the exe from there.