So this file of course exists, in a different path. Inno expected \build \bin\lib\site-packages\win32\PythonService.exe and it is in \build\bin \lib\site-packages\PythonService.exe
Should I change Inno's reference (have to do that for the b2 release) or should it go into a different path in future?
Additionally, it then asked for PyWinTypes23.dll which is in ./build/bin/Lib/site-packages/PyWinTypes23.dll instead of ./build/bin/Lib/site-packages/pywin32_system32/PyWinTypes23.dll.
Looks like a couple of things are ending up in the wrong places ...
This sounds alot like a "win32all" package, not a pywin32 one. Looking inside the pywin32 one: % unzip -l pywin32-204.win32-py2.3.exe | grep pythonservice warning [pywin32-204.win32-py2.3.exe]: extra 63975 bytes at beginning or within zipfile (attempting to process anyway) 20480 04-12-05 18:11 PLATLIB/win32/pythonservice.exe % unzip -l pywin32-204.win32-py2.3.exe | grep 23.dll warning [pywin32-204.win32-py2.3.exe]: extra 63975 bytes at beginning or within zipfile (attempting to process anyway) 311296 04-12-05 18:09 PLATLIB/pywin32_system32/pythoncom23.dll 98304 04-12-05 18:08 PLATLIB/pywin32_system32/pywintypes23.dll ie, exactly where you say Inno wants them. Are you sure you are using pywin32-204.win32-py2.3.exe from sourceforge? Mark