Unfortunately I am using Zope with IIS, not ZopeHTTPServer. My real goal here though is to get COM working with Zope. I have existing python scripts, when run with my own (not Zope's) python installation, which execute properly. Set up as external methods these scripts don't work. I thought about installing the COMObject product, but the instructions suggested the best approach to getting COM to work was to use a "real" python installation. From what I can tell there are three possible solutions: a) Setting up Zope to use my standard Python installation and IIS; b) using ZopeHTTPServer; c) modifying Zope's python installation to contain the correct COM modules. IMO: (a) is best, I could certainly live with (c), but (b) seems unacceptable for a future production environment. Any suggestions?
Just adjust the path to python in the start.bat. This will ensure that ZopeHTTPServer runs with your python.
I do not know how (if at all possible) the NT Service version of Zope can be made to run with a different python.