[Riggs, David] Running Zope 2.5.1 on Win2k, installed as an NT service. On a fresh boot, I can start Zope with 'net start Zope', windows task manager shows both python.exe and PythonService.exe as running. If I try to stop Zope with 'net stop Zope', task manager shows that PythonService.exe dies but python.exe is still running. Task manager also won't let me manually kill python.exe since it belongs to a service. So I try to restart the service with 'net start Zope', task manager shows PythonService.exe start as well as a 2nd instance of python.exe. These two quickly die however, leaving the original python.exe still running and making windows think that the service is stopped. Has anyone else experienced this un-service-like NT service behavior, and if so, does anyone have a workaround? [Tom P] I just tried in on my Win2000 system, although I tried it with Zope 2.3.3, and it worked as expected. No funny business like you describe. Tom P