Logged In: YES 
user_id=31435

I'm not clear on what problem you're trying to solve.  
Fiddling PATH is highly anti-social on Windows, so I'm 
opposed to it even if it were easy (embedded spaces are 
easy; there are many ways to screw up a Win9x box by 
failures in editing autoexec.bat, from line-length 
limitations to failing to handle multiple PATH lines 
correctly).

You can find the location of Python's install directory via 
the registry.  You can also use "start xxx.py" (or 
os.startfile() from within Python) to use the registered 
executable for .py and .pyw files.  That's how Windows is 
supposed to be used.

In any case, PythonLabs doesn't have the bandwidth to 
fiddle with this even if I <wink> wanted to; any change 
here would have to be implemented by a community volunteer; 
or if it's important enough to pay for it, ActiveState may 
be willing to implement it in their installer.

BTW, if I were distributing a serious Windows app using 
Python, I'd ship the version of Python I used and install 
it along with my app, into a subdirectory of my app's 
directory.  That's how, e.g., PythonWare distributes their 
apps.  Then you have total control over it.