Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Path messed up after uninstall

4 views
Skip to first unread message

Per Løvmo

unread,
May 22, 2000, 3:00:00 AM5/22/00
to
This is perhaps a very simple question, but here we go.

I'm reading up the "PATH" under HKEY_CURRENT_USER (environment) in
regristry. Adds some path to it and sets it to "NEW_PATH". When some one
then unistall, "NEW_PATH" is deleted totally and no 'old' "PATH" is set
in.
How can I do this ??

Best Regards
Per


Mark Manning

unread,
May 25, 2000, 3:00:00 AM5/25/00
to

Hmmmm....what OS are you doing this for? Not sure how to handle this under
Win95, but for Win NT (and 2000), all the environment variables, such as
path, is kept in the registry. So it would opnly involve copying reg key
values and creating/deleting keys.

However, I don't think that is the best idea, to be honest. Problem with
doing it that way is if the user installs or changes the PATH environment
variable after installing your app, he/she would be losing those updated
PATH values after your product was uninstalled. You probably want ot think
of a different way.

Mark Manning
VenturCom

"Per Lřvmo" <per....@epmtech.jotne.com> wrote in message
news:3928FBE0...@epmtech.jotne.com...

Jacob-InstallShield

unread,
Jun 20, 2000, 3:00:00 AM6/20/00
to
The issue here is that when you change the path variable, we only register
that you are replacing the value that is currently there.

What this means, is that in your uninstall log, this is registered as if you
created that value. Therefore, when you uninstall, it will wipe out that
value.

What you need to implement what you are looking for is to disable logging
when you make the modification to the path, and then create a custom
uninstall dll to go and take your path out of the environment variable at
uninstall time.

In InstallShield Professional 6.x this is a bit easier in that you can
script the uninstall. This would mean that you can take your path out of the
environment variable via the script, and not have to deal with creating a
custom dll.

--
Sincerely,

Jacob L.
Developer Support Engineer
InstallShield Technical Support
www.installshield.com
"Mark Manning" <mman...@vci.com> wrote in message
news:392d9...@208.30.171.38...


>
> Hmmmm....what OS are you doing this for? Not sure how to handle this
under
> Win95, but for Win NT (and 2000), all the environment variables, such as
> path, is kept in the registry. So it would opnly involve copying reg key
> values and creating/deleting keys.
>
> However, I don't think that is the best idea, to be honest. Problem with
> doing it that way is if the user installs or changes the PATH environment
> variable after installing your app, he/she would be losing those updated
> PATH values after your product was uninstalled. You probably want ot
think
> of a different way.
>
> Mark Manning
> VenturCom
>
>
>

> "Per Løvmo" <per....@epmtech.jotne.com> wrote in message

0 new messages