Latest (Version 3.3) Windows installer deletes the existing PATH environment variable in Vista

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run xuggle-xuggler.3.3.940-win32-setup.exe.
2. Check the value of the PATH variable. It will have just
   have "C:\Program Files (x86)\Xuggle\bin" and nothing else.

What is the expected output? What do you see instead?
The existing PATH variable value should be preserved and
"C:\Program Files (x86)\Xuggle\bin" should be just appended to it.

What operating system and JVM version are you using.
Windows Vista Business 64, Java JDK 1.5.0_19.

Attach relevant log/output files.
N/A.

Original issue reported on code.google.com by murat.ba...@gmail.com on 30 Oct 2009 at 4:12

[GoogleCodeExporter]

That sounds bad; can you ask on the list if others are seeing it though... 
because it
doesn't show up in our tests.

Original comment by art.cla...@gmail.com on 30 Oct 2009 at 4:41

[GoogleCodeExporter]

Have you tested it in Vista? In Vista 64? I took a look at your nsis script and 
seems
like you are using ${EnvVarUpdate} to update the Path variable and that
macro/function might be the problem. Which version of nsi are you using?
One other thing I should mention is that I chose the "Install for anyone using 
this
computer" option.

Original comment by murat.ba...@gmail.com on 30 Oct 2009 at 5:43

[GoogleCodeExporter]

Looks like this is a known issue with ${EnvVarUpdate}:

http://forums.winamp.com/showthread.php?postid=2483473

Some people say it can be because of the 1024 char limit on String length in the
regular nsis build and that you need to use the special large strings build that
supports longer strings:

http://nsis.sourceforge.net/Special_Builds

I have checked the current length of my PATH variable and it is over 1300 
chars, 
which is indeed longer than 1024. This might be one reason.

Other people with 64 bit os are saying that it is happening to them even after 
using
the long string build. This might be another reason since my OS is 64 bit.
I have not come across a definite solution for this one, yet.

Original comment by murat.ba...@gmail.com on 2 Nov 2009 at 11:51

[GoogleCodeExporter]

Hi 
I have the same problem. Installed Xuggler version: 
xuggle-xuggler.3.4.1012-win32-setup.exe. After install my PATH variable only 
included path to Xuggler. 

The PATH variable was very long. So I guess the problem could be related to 
String length. 

My OS are Windows 7 64 bit. 

Original comment by bjor...@gmail.com on 5 Jan 2011 at 4:48

[GoogleCodeExporter]

I'm just going to chime in with a "me too". Running Windows 7 64-bit Ultimate, 
with a long path.

Original comment by mike.mcc...@gmail.com on 17 Mar 2011 at 7:22

[GoogleCodeExporter]

Here is another "me too".  Windows 7 Professional 64-bit with 
xuggle-xuggler.3.4.1012-win32-setup.exe.  My path pre-xuggler install was ~1500 
characters.

Original comment by griffin....@gmail.com on 10 May 2011 at 6:17

[GoogleCodeExporter]

me too. also 263 is a duplicate of this issue:
http://code.google.com/p/xuggle/issues/detail?id=263

Original comment by ch...@turchin.net on 25 Jul 2011 at 10:34

[GoogleCodeExporter]

Original comment by art.cla...@gmail.com on 7 Apr 2012 at 5:46

• Changed state: Fixed