Re: Windows installer replaces the PATH variable

[Elliott S. <ell...@gm...>]

On Wed, Apr 20, 2011 at 4:53 PM, Anton Vodonosov <avo...@ya...>wrote:

>
>
> 16.04.2011, 11:06, "Elliott Slaughter" <ell...@gm...>:
> >
> > Anton,
> >
> > Could you please try the following test installers? Since I am unable to
> reproduce the bug, I can't meaningfully test this on my own.
> >
> > Installer (1) below is intended to fix the bug. Installer (2) is a sanity
> check to make sure the bug is still present when the fix is absent.
> >
> > (1) http://elliottslaughter.net/files/clisp-2.49+-win32-install-fix.exe
> >
> > (2) http://elliottslaughter.net/files/clisp-2.49+-win32-install-orig.exe
> >
> > *Please* back up your PATH (user and system) variables before trying
> either of the above.
> >
> > Note that the actually CLISP that gets installed is quite broken--there
> is a dll missing, among other things.
> >
> > Thanks.
> >
> > --
> > Elliott Slaughter
> >
> > "Don't worry about what anybody else is going to do. The best way to
> predict the future is to invent it." - Alan Kay
>
> Hello Elliott,
>
> Both installers replace my PATH.
>
> I did some investigations and found the reason. I have very long value of
> the PATH variable.
>
> If the PATH lenght >= 1024 characters, it is replaced by the installer.
>

Thank you for looking into this.

I'll try to confirm your results and see if I can find a fix.

-- 
Elliott Slaughter

"Don't worry about what anybody else is going to do. The best way to predict
the future is to invent it." - Alan Kay