I am not sure if this applies or not but here goes.

On a WIN NT server I wanted to get zope running with another program on the same server that also required python. Problem is it needed a different version of python that had been hacked and wouldn't work with Zope. It also set up some environment variables that zope couldn't live with.

So I installed zope as an app and used srvany (part of the windows NT resource kit) to serve cmd calling a cmd file that set the variables to values zope could live with and then called zopes start.bat

It is installed as an app and runs as a service in it's own virtual machine.

HTH,

Mike.

Message: 6
Date: Wed, 06 Mar 2002 16:50:44 +0100
From: "Cornelis J. de Brabander" <brabander@fsw.LeidenUniv.nl>
To: zope <zope@zope.org>
Subject: [Zope] zope as win32 service and stupid_log_file

Did anybody succeed in activating that STUPID_LOG_FILE when running zope as
a win nt service?
Creating a environment variable does not help. I can understand that because
this would result in a conflict when running two versions of zope on the
same machine. So there would have to be a environment variable that is bound
to a specific service.

zope 2.4.3. python 2.1.

Cornelis J. de Brabander
==========================================
Department of Education, Leiden University
P.O.Box 9555, NL-2300 RB Leiden
+31 71 527 3422/3401
brabander@fsw.leidenuniv.nl
==========================================