Well, maybe it would be overkill, but adding an option like "Add to PATH,
but make a backup first" which creates a .reg backup of the environment
variables on the desktop could be a nice option. There seems to be a way to
backup deleted environment variables as well, check the 3rd post on this
site
Thanks. Then, it seems that it is a bug in NSIS.
Now I know that this problem does not happen so often, but still is it possible
to
warn people to backup their PATH before running it? I was fortunate
because I
happened to have a backup so I could recover easily. But some one may have worse
luck.
On 08/07/2010 05:11 AM, notna wrote:
could maybe still be http://d.puremagic.com/issues/show_bug.cgi?id=3319
Am 06.08.2010 05:17, schrieb Wei Cheng:
Dear all:
I've found that D 2.0 windows installer (one key installer) will clear
the
original PATH and set it as the D path. Is it a bug in the in
could maybe still be http://d.puremagic.com/issues/show_bug.cgi?id=3319
Am 06.08.2010 05:17, schrieb Wei Cheng:
Dear all:
I've found that D 2.0 windows installer (one key installer) will clear the
original PATH and set it as the D path. Is it a bug in the installer? Should
it keep the original v
I'm not seeing that behavior here (XP SP3), and I've just tested it. PATH
gets appended with directories of DMD|DMD2|DM /bin. Btw., Rapid Environment
Editor is a nice freeware app for manipulating environment variables. You
can make backups with it as well.
I will say the download in the setup is
Dear all:
I've found that D 2.0 windows installer (one key installer) will clear the
original PATH and set it as the D path. Is it a bug in the installer? Should
it keep the original value and put the D paths in front of them? Thanks