On Thu, Jan 15, 2009 at 8:48 AM, Brian van den Broek <br...@cc.umanitoba.ca>wrote:
> > The (recognized by me as) relevant bits of output are: > Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program > Files\texlive\2008\bin\win32;C:\Python26 > PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH > > There is no subsequent Path line that might be stomping on the line shown > above. > New thought: could this be some sort of long-filename/short-filename weirdness? What happens if you have your friend do the following: > C:\>dir /x py* > Volume in drive C has no label. > Volume Serial Number is E400-17CA > > Directory of C:\ > > 2008-09-22 10:24 PM <DIR> Python26 > 0 File(s) 0 bytes > 1 Dir(s) 9,809,756,160 bytes free > See that long empty space between "<DIR>" and "Python26"? That means that there's no fake short filename associated with "Python26", which is what we expect - "Python26" is less than eight characters and has no spaces. However, funky things can happen during installation, and I have seen cases where filenames that _look_ normal STILL get fake short filenames associated with them. If you see anything between "<DIR>" and "Python26" on your friend's machine (it would probably look like PYTHON~1.0, or something similar), then try putting (whatever it is) into the Path instead... -- www.fsrtechnologies.com p.s. - Full disclosure - I actually still have Python 2.5.1, so my directory is actually "Python25". Shouldn't matter, but wanted to disclose that.
_______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
