> > * that directory is on your PATH before the Windows SYSTEM32 directory
> > (which is where pywin32 sticks its copy of these files, for
> various reasons)
>
> Do both this and the above have to be true, or will things work if
> either of them are true?
Either one has the end result of locating
Mark Hammond wrote:
If this is the problem, it will probably only happen when using
runzope.bat - running as a service probably works fine.
Ah, okay, yeah, I only use runzope...
In that case, the problem is the order that Windows uses to search for DLLs.
The short answer is that things should
Hi Chris,
> Sorry, do you mean the box where the Zope 2.9.1 distro was built or the
> one where I was installing it?
The latter.
> 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
Hi Mark,
I see you replied, but I missed this first time round:
http://mail.zope.org/pipermail/zope-dev/2006-March/027166.html
> What version of pywin32 did you use for the build?
http://svn.zope.org/Zope/trunk/inst/WinBuilders/README.txt?rev=65838&view=auto
...shows the exact list of inst
