wpkg-gp's default installation path causes problems under Windows XP SP3

[GoogleCodeExporter]

I'm using wpkg-gp 0.14 (x86) on Windows XP English version (SP3 with latest 
updates) 

What steps will reproduce the problem?

1. Install wpkg-gp into the default program location %PROGRAMFILES%  (which in 
an English XP resolves to "C:\Program Files")
2. Either reboot and wait for the service to start, or run `WpkgPipeClient.exe 
Execute`.

I would expect the service to run WPKG and apply settings. Instead, when 
starting the service, nothing happens and an error message is displayed in the 
log file: "%1 is not a valid Win32 application"

This at first confused me into thinking that I installed the wrong build. 
However, I installed the right one (x86). Some searching on the Intertubes led 
me to the following: http://support.microsoft.com/kb/812486

So I thought "Wow, it's da spaces in the path again" and reinstalled wpkg-gp to 
some directory without spaces in the path. Afterwards, it indeed worked 
flawlessly.

This led me to the following conclusions:
1) Either path information to WPKG-GP is entered incorrectly without quotes 
into the registry or some path information is handled incorrectly in the 
WPKG-gp scripts
2) Installing WPKG-GP silently will never ever work for me, because it will 
always install into %PROGRAMFILES%, which resolves to a path with spaces.

I'll try to deliver the full error log later on (sorry, I'm not on that machine 
right now and don't have access to it), so we can track down the exact error in 
the code.

Original issue reported on code.google.com by dam...@gmail.com on 12 Sep 2011 at 12:02

[GoogleCodeExporter]

Hi, I would be interested in full logs. (Install and wpkg-gp service.) My 
development environments are English Windows XP (32 bit) and English Windows 7 
(32 bit).

Original comment by clei...@gmail.com on 12 Sep 2011 at 3:48

[GoogleCodeExporter]

Could you please check if this issue persists in newly released version 0.15?

Original comment by clei...@gmail.com on 15 Sep 2011 at 2:06

[GoogleCodeExporter]

I haven't been able to reproduce this problem with 0.15, but neither with 0.14 
since I "fixed it" (with that particular error message, i.e. "%1 is not a valid 
win32 application"). Curse myself for not having written down the full python 
stacktrace when this first happened.

I cannot guarantee that the problem is fixed, but I will keep testing and 
provide you with any updates in this issue.

Original comment by dam...@gmail.com on 25 Sep 2011 at 11:49

[GoogleCodeExporter]

Thank you for the feedback.

Original comment by clei...@gmail.com on 26 Sep 2011 at 11:36

• Changed state: Done