PDA

View Full Version : UnInstallShield problem in Win95



NewsArchive
09-12-1996, 12:00 AM

NewsArchive
09-12-1996, 12:00 AM
The "problem" I was encountering turned out to be the result of an earlier
identically named 32-bit app whose registry entries were still intact. The
list of software in the Add/Remove Programs Properties window contained the
name of my old 32-bit version. Thus when I thought I was able to uninstall
a 16-bit app from that window, it was actually a vestige from a 32-bit app
that was not completely uninstalled.

Something I learned was that only 32-bit apps can appear in the list of
software in that Add/Remove Programs Properties window in Win95.
Uninstalling 16-bit apps in Win95 has to be accomplished in some way other
than using Add/Remove Programs from the Control Panel.

--
Jack Kulas
Radiation Measurements Div Email: Kulas_Jack@keithley.com
Keithley Instruments, Inc. Voice: (216) 498-2581
Cleveland, OH 44139 Fax: (216) 349-2307

NewsArchive
09-12-1996, 12:00 AM
The "problem" I was encountering turned out to be the result of an earlier
identically named 32-bit app whose registry entries were still intact. The
list of software in the Add/Remove Programs Properties window contained the
name of my old 32-bit version. Thus when I thought I was able to uninstall
a 16-bit app from that window, it was actually a vestige from a 32-bit app
that was not completely uninstalled.

Something I learned was that only 32-bit apps can appear in the list of
software in that Add/Remove Programs Properties window in Win95.
Uninstalling 16-bit apps in Win95 has to be accomplished in some way other
than using Add/Remove Programs from the Control Panel.

--
Jack Kulas
Radiation Measurements Div Email: Kulas_Jack@keithley.com
Keithley Instruments, Inc. Voice: (216) 498-2581
Cleveland, OH 44139 Fax: (216) 349-2307

NewsArchive
09-13-1996, 12:00 AM
>
> Something I learned was that only 32-bit apps can appear in the list of
> software in that Add/Remove Programs Properties window in Win95.
> Uninstalling 16-bit apps in Win95 has to be accomplished in some way
other
> than using Add/Remove Programs from the Control Panel.
>

This is not necessarily true. If you use a 32-bit version of InstallShield
to install the 16-bit application, you can register your application with
Add/Remove Programs. This will allow you to use the remove application
functionality in Windows 95/Windows NT 4.0 with a 16-bit application.

Leslie Easter
lesliee@OrangeBrain.com

NewsArchive
09-13-1996, 12:00 AM
>
> Something I learned was that only 32-bit apps can appear in the list of
> software in that Add/Remove Programs Properties window in Win95.
> Uninstalling 16-bit apps in Win95 has to be accomplished in some way
other
> than using Add/Remove Programs from the Control Panel.
>

This is not necessarily true. If you use a 32-bit version of InstallShield
to install the 16-bit application, you can register your application with
Add/Remove Programs. This will allow you to use the remove application
functionality in Windows 95/Windows NT 4.0 with a 16-bit application.

Leslie Easter
lesliee@OrangeBrain.com

NewsArchive
09-16-1996, 12:00 AM
> "Jack Kulas" <Kulas_Jack@keithley.com> wrote in article
<01bba0c8$5adc21e0$e29007ce@jk-rmd>...
> The "problem" I was encountering turned out to be the result of an
earlier
> identically named 32-bit app whose registry entries were still intact.
The
> list of software in the Add/Remove Programs Properties window contained
the
> name of my old 32-bit version. Thus when I thought I was able to
uninstall
> a 16-bit app from that window, it was actually a vestige from a 32-bit
app
> that was not completely uninstalled.
>
> Something I learned was that only 32-bit apps can appear in the list of
> software in that Add/Remove Programs Properties window in Win95.
> Uninstalling 16-bit apps in Win95 has to be accomplished in some way
other
> than using Add/Remove Programs from the Control Panel.
>
> --
//
>Jack,
Windows 95, NT 3.51, and 4.0 all have 32 bit registries. Therefore,
only
an InstallShield 32 bit installation can access the 32 bit registry to
make the
entry under the Uninstall key. The application entries placed under this
Uninstall
key will appear under the Add\Remove Programs applet. This is why most 16
bit
apps. use icons associated to an executable. However, you can use 32 bit
InstallShield to place an entry in the Add\Remove applet for a 16 bit
application
as long as the application does not reside in a long pathname.

InstallShield Technical Support
Stephen
> Jack Kulas
> Radiation Measurements Div Email: Kulas_Jack@keithley.com
> Keithley Instruments, Inc. Voice: (216) 498-2581
> Cleveland, OH 44139 Fax: (216) 349-2307
>

NewsArchive
09-16-1996, 12:00 AM
> "Jack Kulas" <Kulas_Jack@keithley.com> wrote in article
<01bba0c8$5adc21e0$e29007ce@jk-rmd>...
> The "problem" I was encountering turned out to be the result of an
earlier
> identically named 32-bit app whose registry entries were still intact.
The
> list of software in the Add/Remove Programs Properties window contained
the
> name of my old 32-bit version. Thus when I thought I was able to
uninstall
> a 16-bit app from that window, it was actually a vestige from a 32-bit
app
> that was not completely uninstalled.
>
> Something I learned was that only 32-bit apps can appear in the list of
> software in that Add/Remove Programs Properties window in Win95.
> Uninstalling 16-bit apps in Win95 has to be accomplished in some way
other
> than using Add/Remove Programs from the Control Panel.
>
> --
//
>Jack,
Windows 95, NT 3.51, and 4.0 all have 32 bit registries. Therefore,
only
an InstallShield 32 bit installation can access the 32 bit registry to
make the
entry under the Uninstall key. The application entries placed under this
Uninstall
key will appear under the Add\Remove Programs applet. This is why most 16
bit
apps. use icons associated to an executable. However, you can use 32 bit
InstallShield to place an entry in the Add\Remove applet for a 16 bit
application
as long as the application does not reside in a long pathname.

InstallShield Technical Support
Stephen
> Jack Kulas
> Radiation Measurements Div Email: Kulas_Jack@keithley.com
> Keithley Instruments, Inc. Voice: (216) 498-2581
> Cleveland, OH 44139 Fax: (216) 349-2307
>

NewsArchive
09-17-1996, 12:00 AM
--
Jack Kulas
Radiation Measurements Div Email: Kulas_Jack@keithley.com
Keithley Instruments, Inc. Voice: (216) 498-2581
Cleveland, OH 44139 Fax: (216) 349-2307

Steve <support@installshield.com> wrote in article
<01bba40e.2734f4e0$3546b1cc@stephend.installshield.com>...
>
> Windows 95, NT 3.51, and 4.0 all have 32 bit registries. Therefore,
> only
> an InstallShield 32 bit installation can access the 32 bit registry to
> make the
> entry under the Uninstall key. The application entries placed under this
> Uninstall
> key will appear under the Add\Remove Programs applet. This is why most
16
> bit
> apps. use icons associated to an executable. However, you can use 32 bit

> InstallShield to place an entry in the Add\Remove applet for a 16 bit
> application
> as long as the application does not reside in a long pathname.
>
> InstallShield Technical Support
> Stephen


Does this mean that ISXPro can't do that (that is, place a 16-bit app with
OK pathname in the Add/Remove applet),but only 32-bit IS can?

-- Jack

--
Jack Kulas
Radiation Measurements Div Email: Kulas_Jack@keithley.com
Keithley Instruments, Inc. Voice: (216) 498-2581
Cleveland, OH 44139 Fax: (216) 349-2307

NewsArchive
09-17-1996, 12:00 AM
Jack Kulas <Kulas_Jack@keithley.com> wrote
> Does this mean that ISXPro can't do that (that is, place a 16-bit app
with
> OK pathname in the Add/Remove applet),but only 32-bit IS can?

If you create a 32-bit installation with ISX, you can have your application
name appear in the Add\Remove applet.

Ritesh

NewsArchive
09-17-1996, 12:00 AM
Ritesh <support@installshield.com> wrote in article
<01bba4ce$9fe31be0$3746b1cc@Ritesh.installshield.com>...
> Jack Kulas <Kulas_Jack@keithley.com> wrote
> > Does this mean that ISXPro can't do that (that is, place a 16-bit app
> with
> > OK pathname in the Add/Remove applet),but only 32-bit IS can?
>
> If you create a 32-bit installation with ISX, you can have your
application
> name appear in the Add\Remove applet.
>
> Ritesh
>

I think I have discovered a deep (but probably not the deepest?) reason why
ISXPro will not allow one to install a 16-bit app on a Win95 box and have
its name appear in the Add/Remove applet.
It's that
[1]for 16-bit apps, ISXPro will only allow modification of registry keys
rooted in the key HKEY_CLASSES_ROOT [this is because Win3.1's registry only
has that root key]
&
[2] for an app's name to appear in the Add/Remove applet, there must be the
two value pairs "DisplayName <App's Name>" and "UninstallString
<AppUninstaller>" for the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
\Windows\Current Version\Uninstall\<APP>.
So it's just not possible using ISXPro to write those value pairs to that
key for a 16-bit app.

Right?

[But why couldn't ISXPro determine that the target system is Win95 and
thereby allow writing to subkeys of HKEY_LOCAL_MACHINE? Just restrict
Win3.1 targets from attempting such registry editing?]

-- Jack

NewsArchive
09-17-1996, 12:00 AM
--
Jack Kulas
Radiation Measurements Div Email: Kulas_Jack@keithley.com
Keithley Instruments, Inc. Voice: (216) 498-2581
Cleveland, OH 44139 Fax: (216) 349-2307

Steve <support@installshield.com> wrote in article
<01bba40e.2734f4e0$3546b1cc@stephend.installshield.com>...
>
> Windows 95, NT 3.51, and 4.0 all have 32 bit registries. Therefore,
> only
> an InstallShield 32 bit installation can access the 32 bit registry to
> make the
> entry under the Uninstall key. The application entries placed under this
> Uninstall
> key will appear under the Add\Remove Programs applet. This is why most
16
> bit
> apps. use icons associated to an executable. However, you can use 32 bit

> InstallShield to place an entry in the Add\Remove applet for a 16 bit
> application
> as long as the application does not reside in a long pathname.
>
> InstallShield Technical Support
> Stephen


Does this mean that ISXPro can't do that (that is, place a 16-bit app with
OK pathname in the Add/Remove applet),but only 32-bit IS can?

-- Jack

--
Jack Kulas
Radiation Measurements Div Email: Kulas_Jack@keithley.com
Keithley Instruments, Inc. Voice: (216) 498-2581
Cleveland, OH 44139 Fax: (216) 349-2307

NewsArchive
09-17-1996, 12:00 AM
Jack Kulas <Kulas_Jack@keithley.com> wrote
> Does this mean that ISXPro can't do that (that is, place a 16-bit app
with
> OK pathname in the Add/Remove applet),but only 32-bit IS can?

If you create a 32-bit installation with ISX, you can have your application
name appear in the Add\Remove applet.

Ritesh

NewsArchive
09-17-1996, 12:00 AM
Ritesh <support@installshield.com> wrote in article
<01bba4ce$9fe31be0$3746b1cc@Ritesh.installshield.com>...
> Jack Kulas <Kulas_Jack@keithley.com> wrote
> > Does this mean that ISXPro can't do that (that is, place a 16-bit app
> with
> > OK pathname in the Add/Remove applet),but only 32-bit IS can?
>
> If you create a 32-bit installation with ISX, you can have your
application
> name appear in the Add\Remove applet.
>
> Ritesh
>

I think I have discovered a deep (but probably not the deepest?) reason why
ISXPro will not allow one to install a 16-bit app on a Win95 box and have
its name appear in the Add/Remove applet.
It's that
[1]for 16-bit apps, ISXPro will only allow modification of registry keys
rooted in the key HKEY_CLASSES_ROOT [this is because Win3.1's registry only
has that root key]
&
[2] for an app's name to appear in the Add/Remove applet, there must be the
two value pairs "DisplayName <App's Name>" and "UninstallString
<AppUninstaller>" for the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
\Windows\Current Version\Uninstall\<APP>.
So it's just not possible using ISXPro to write those value pairs to that
key for a 16-bit app.

Right?

[But why couldn't ISXPro determine that the target system is Win95 and
thereby allow writing to subkeys of HKEY_LOCAL_MACHINE? Just restrict
Win3.1 targets from attempting such registry editing?]

-- Jack

NewsArchive
09-18-1996, 12:00 AM
Jack Kulas <Kulas_Jack@keithley.com> wrote
> I think I have discovered a deep (but probably not the deepest?) reason
why
> ISXPro will not allow one to install a 16-bit app on a Win95 box and have
> its name appear in the Add/Remove applet.
> It's that
> [1]for 16-bit apps, ISXPro will only allow modification of registry keys
> rooted in the key HKEY_CLASSES_ROOT [this is because Win3.1's registry
only
> has that root key]

Correct!

> &
> [2] for an app's name to appear in the Add/Remove applet, there must be
the
> two value pairs "DisplayName <App's Name>" and "UninstallString
> <AppUninstaller>" for the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
> \Windows\Current Version\Uninstall\<APP>.
> So it's just not possible using ISXPro to write those value pairs to that
> key for a 16-bit app.

Correct again!!

> [But why couldn't ISXPro determine that the target system is Win95 and
> thereby allow writing to subkeys of HKEY_LOCAL_MACHINE? Just restrict
> Win3.1 targets from attempting such registry editing?]

If you select a 16-bit install, the 16-bit engine is included in the setup.
This engine can only access HKEY_CLASSES_ROOT. If you select a 32-bit
install, then you will not be able to install on Win3.x (16-bit systems)
unless Win32s is installed.

Ritesh

NewsArchive
09-18-1996, 12:00 AM
Jack Kulas <Kulas_Jack@keithley.com> wrote
> I think I have discovered a deep (but probably not the deepest?) reason
why
> ISXPro will not allow one to install a 16-bit app on a Win95 box and have
> its name appear in the Add/Remove applet.
> It's that
> [1]for 16-bit apps, ISXPro will only allow modification of registry keys
> rooted in the key HKEY_CLASSES_ROOT [this is because Win3.1's registry
only
> has that root key]

Correct!

> &
> [2] for an app's name to appear in the Add/Remove applet, there must be
the
> two value pairs "DisplayName <App's Name>" and "UninstallString
> <AppUninstaller>" for the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
> \Windows\Current Version\Uninstall\<APP>.
> So it's just not possible using ISXPro to write those value pairs to that
> key for a 16-bit app.

Correct again!!

> [But why couldn't ISXPro determine that the target system is Win95 and
> thereby allow writing to subkeys of HKEY_LOCAL_MACHINE? Just restrict
> Win3.1 targets from attempting such registry editing?]

If you select a 16-bit install, the 16-bit engine is included in the setup.
This engine can only access HKEY_CLASSES_ROOT. If you select a 32-bit
install, then you will not be able to install on Win3.x (16-bit systems)
unless Win32s is installed.

Ritesh

NewsArchive
10-16-1996, 12:00 AM
Ritesh wrote:
>
> If you select a 16-bit install, the 16-bit engine is included in the >setup.
> This engine can only access HKEY_CLASSES_ROOT. If you select a >32-bit
> install, then you will not be able to install on Win3.x (16-bit >systems)
> unless Win32s is installed.
>
> Ritesh

But you said in an earlier thread that InstallShield Express and any
products created with InstallShield Express will *not* support Win32s.

Please explain.

Thanks,
Brian Cooper
System Manager
Lightstone Group
bc@lightstone.com

NewsArchive
10-16-1996, 12:00 AM
B Cooper <bc@lightstone.com> wrote
> Ritesh wrote:
> >
> > If you select a 16-bit install, the 16-bit engine is included in the
>setup.
> > This engine can only access HKEY_CLASSES_ROOT. If you select a
>32-bit
> > install, then you will not be able to install on Win3.x (16-bit
>systems)
> > unless Win32s is installed.
> >
> > Ritesh
>
> But you said in an earlier thread that InstallShield Express and any
> products created with InstallShield Express will *not* support Win32s.


When I wrote the above, I was mistaken. I had thought that ISX supported
Win32s like IS3, but ISX does not.

More clearly,

InstallShield Express or any installations created by InstallShield Express
does not support Win32s.

Ritesh

NewsArchive
10-16-1996, 12:00 AM
Ritesh wrote:
>
> If you select a 16-bit install, the 16-bit engine is included in the >setup.
> This engine can only access HKEY_CLASSES_ROOT. If you select a >32-bit
> install, then you will not be able to install on Win3.x (16-bit >systems)
> unless Win32s is installed.
>
> Ritesh

But you said in an earlier thread that InstallShield Express and any
products created with InstallShield Express will *not* support Win32s.

Please explain.

Thanks,
Brian Cooper
System Manager
Lightstone Group
bc@lightstone.com

NewsArchive
10-16-1996, 12:00 AM
B Cooper <bc@lightstone.com> wrote
> Ritesh wrote:
> >
> > If you select a 16-bit install, the 16-bit engine is included in the
>setup.
> > This engine can only access HKEY_CLASSES_ROOT. If you select a
>32-bit
> > install, then you will not be able to install on Win3.x (16-bit
>systems)
> > unless Win32s is installed.
> >
> > Ritesh
>
> But you said in an earlier thread that InstallShield Express and any
> products created with InstallShield Express will *not* support Win32s.


When I wrote the above, I was mistaken. I had thought that ISX supported
Win32s like IS3, but ISX does not.

More clearly,

InstallShield Express or any installations created by InstallShield Express
does not support Win32s.

Ritesh