Pat, Another thing to check is that all the dll’s
dependencies are present on the remote computer as well. Often times an error
message that a dll can not be found can be misleading. What it really means is
that the dll did not load correctly because it could not find all it’s
dependencies. Use Dependency Walker to generate a dependency list for your
application. You can get it here: http://www.dependencywalker.com/ - From:
condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Shaun J. O'Callaghan Pat, I had a similar problem and although there
are numerous workarounds I found that executing a batch file in your submit
script, e.g. executable = script.bat, and have the script set the variables you
need to set for the execution environment. This can be done via the
submit script too I think. Either way, I set the PATH variable
manually in the batch file and any associated parameters e.g. SET PATH=some_dir;%PATH% Executable.exe %1 %2 etc… From:
condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Moriarty, Patrick Hello, I’ve noticed in the manual that some Windows apps have
trouble linking to their dll’s. So, I’ve followed the advice of the
manual and passed the dll along with the executable in Condor and also put
“getenv = true” in the submit file to create a path. And, things
still fail because the dll cannot be loaded. If I copy the execute directory on
the machine and then run it myself, all is fine. New ideas? Should I set the
path to the execute directory? The null path should force it to look only in
the local directory, right? That doesn’t work either. Cheers, Pat Pat
Moriarty |