Re: Windows installer replaces the PATH variable

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

On Sun, Apr 10, 2011 at 9:37 PM, Elliott Slaughter <
ell...@gm...> wrote:

> 2011/4/10 Anton Vodonosov <avo...@ya...>
>
>>
>> 10.04.2011, 23:33, "Elliott Slaughter" <ell...@gm...>:
>> >
>> > Anton: Did you install this "for everyone" or "just for me"? Have you
>> ever had any previous versions of CLISP installed via the installer on this
>> machine?
>> >
>> >> Elliott, could you please take a look at
>> clisp/win32msvc/nsis/add_to_path.nsh?
>>
>> "for everyone". Previously I had installed CLISP 2.48, which I uninstalled
>> manually from control panel before installing the new installer.
>>
>> I can not say what mode (everyone/just for me) was use in the old, 2.48,
>> installation.
>>
>
> I can't seem to reproduce the bug you observed. I also had CLISP 2.48
> installed ("just for me") before starting, uninstalled it, and then
> installed CLISP 2.49 ("for everyone"). At every step my user and system
> PATHs were still intact, and CLISP path got added and removed as expected. I
> am also using Windows 7 64-bit, so no difference there.
>
> I'm not exactly sure what to do from here if I can't reproduce the bug...
>

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