> Sorry, do you mean the box where the Zope 2.9.1 distro was built or the
> one where I was installing it?
> If the latter, how dowe fix Zope so it doesn't get tripped up by other
> pywin32 distros on the same box?
If this is the problem, it will probably only happen when using
runzope.bat - running as a service probably works fine.
In that case, the problem is the order that Windows uses to search for DLLs.
The short answer is that things should work if:
* the CWD of the process is the Python directory (ie, the directory with the
Python executables and the pywin32 system DLLs). This will be true when
starting as a service.
* that directory is on your PATH before the Windows SYSTEM32 directory
(which is where pywin32 sticks its copy of these files, for various reasons)
In the case of runzope.bat, this just means having the CWD of the shell be
the Python dir, and specifying the path to runzope.bat. A better solution
moving forward may be to have runzope.bat explicitly CD to that directory
before doing its thing...
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -