escript on Windows XP DLL load failed

escriptcpp.pyd tries to load libescript.dll.
Do you have your paths set correctly?

I believe I set paths correctly. I don't have libescript.dll (such file is not in the escript zip archive), perhaps you mean escript.dll? If so, than it is on the path, and you can see from the dependence walker output, that it was found and loaded successfully.

Hi,

I have experienced the same problems on a PC with Windows 7. However, on my home computer I had python xy 2.6 intalled and no problems with the escript installation. So I also reverted to python xy 2.6 at work PC and had this solved the problem.

Hi John,
Did you manage to get escript working in the end? I've got a virtual machine set up with Windows XP and Python 2.7 (which is my test machine before making a release) and I don't experience this problem. I was on leave for the last few weeks and couldn't answer your question, but I'm happy to help you sort things out now.

Hi guys,
I get the same errors when trying to install and use escript-3.2.1-win32-py2.7 under windows XP with a preexisting installation of python(x,y) 2.7.3.1.
I haven't tried to debug, but what I get is exactly:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "escript\py_src\__init__.py", line 22, in <module>
  File "escript\py_src\escript.py", line 28, in <module>
ImportError: DLL load failed: The specified procedure could not be found.

The path to esys_dlls is set and well verified, no question about it.

I also tried other python versions, such as 2.6 with the same results on Windows XP and Win 7.
I would really appreciate it if someone figured it out.
Thanks!
Lucian

This is weird since you're describing the exact configuration (winXP +py2.6 or 2.7) I used for the test machines on which the installers were tested before being uploaded on launchpad... As a guess, I would be tempted to advise you to check in your path for incompatibilities. A user previously reported that problem and the issue was a visualisation package (Visit, I think) which had put itself at the beginning of the path. Note that this was a few years ago, but it's worth checking if moving "esys_dlls" earlier in your path fixes the problem. If so, by dichotomy you can figure out the conflicting package.
Cheers,
Thomas.

Also, could you confirm the version you are using?
There is a more recent windows release [3.3] is it possible to test with that?

Thanks guys,
for a very prompt reply. Yes, I tried escript-3.2.1-win32-py2.7 under win XP with preexisting installation of python(x,y) 2.7.3.1.

There might be something about the path, indeed, though I'm not sure what.
It's also true that I have multiple version of python (2.5, 2.6, 2.7 ) installed in a portable manner on my computers. So they also appear in the path. An older version of escript runs very well with my portable 2.5 python version. I'll try to clean the path....

Maybe I'm not running the new escript version correctly. Do I have to use "run-escript"? How do I do that with a portable installation of python?
Many thanks,
Lucian

The run-escript launcher is only for the linux and mac distributions.

Hi,
I think I solved the problem. It was indeed related to the user path, in which I already had a path to an esys-dlls directory for an older version of escript working within python 2.5.
When I replaced that with the new path for the python 2.7 distribution all problems disappeared!
Thanks again for your prompt reply,
cheers,
Lucian