NT/Win2000 "All Users" Install possible?

Heather B.

unread,

Sep 25, 2001, 6:41:09 PM9/25/01

to

Hi there,

Our installer generated by ISX 3.51, will only install under the profile of
the user logged into the computer. It won't work under any other user. Can
anyone tell me how to fix this so the app works under any user?

Thanks.

Heather

Jim Shawver

unread,

Sep 25, 2001, 6:28:36 PM9/25/01

to

If you are using the Customer Information dialog, set the "Show All
Users Option" property to No.

Another way to set the installation to All Users is to edit the
SETUP.INI file:

CmdLine= ALLUSERS=1

This does a per-machine (All Users) install, but it also requires an
Administrator to perform the installation. See the "ALLUSERS Property"
topic in the Windows Installer help file for more info.

Jim Shawver
BCC Software, Inc.

Heather B.

unread,

Sep 26, 2001, 8:20:36 PM9/26/01

to

Thanks for the response!

Follow-up question: Must I include this dialog in the project? Or can I
just set this setting on this dialog window to No, and still have it install
as an All User project even though this dialog is not shown?

Thanks again,
Heather

"Jim Shawver" <ji...@bccsoftware.com> wrote in message
news:3bb0ffd9...@news.installshield.com...

Jim Shawver

unread,

Sep 27, 2001, 3:53:50 PM9/27/01

to

I'm fairly certain that ISX ignores the property setting if you don't
include the dialog in your project. Someone from InstallShield please
correct me if I'm wrong.

If you don't want the dialog in your setup, you can set ALLUSERS=1 in
your SETUP.INI as I described previously. Of course, you have to
remember to edit the SETUP.INI after each build you do in ISX.

- Jim

On Wed, 26 Sep 2001 17:20:36 -0700, "Heather B."

Heather B.

unread,

Sep 27, 2001, 7:46:50 PM9/27/01

to

Well, I verified it, and yes, it seems to ignore it if the dialog box is not
included. Seems strange to me that there is no way within ISX to set this
setting without showing a dialog box with this particular option set to Do
Not Display. Crazy, huh?

Unfortunately for me we are building a setup.cab for web deployment, and it
is signed with a digital certificate. So to modify anything inside of the
.cab file after it is built means having to re-cab, as well as re-sign the
file - all steps that open us up to a mistake along the way, and all steps
that we were aiming to avoid with the purchase of ISX. Ugg.

Thanks for your help.

Heather

"Jim Shawver" <ji...@bccsoftware.com> wrote in message

news:3bb380f8...@news.installshield.com...

reply@installshield.com Chandima Rajakaruna

unread,

Sep 28, 2001, 9:21:33 AM9/28/01

to

This is a valid scenario that you have pointed out (Setup author being able
to set ALLUSERS without a dialog to verify). Work Order 1-6PMDS has been
submitted to address this issue. Thanks for bringing it up.

"Heather B." <heat...@NOSPAM.attglobal.net> wrote in message
news:3bb3...@news.installshield.com...

Heather B.

unread,

Sep 30, 2001, 10:56:55 PM9/30/01

to

So if I understand you correctly, this will make its way to production in
the future? Any idea when?

"Chandima Rajakaruna" <no re...@installshield.com> wrote in message
news:3bb47946$1...@news.installshield.com...

reply@installshield.com Chandima Rajakaruna

unread,

Oct 1, 2001, 11:59:39 AM10/1/01

to

Sorry but not sure when.

"Heather B." <heat...@NOSPAM.attglobal.net> wrote in message

news:3bb7...@news.installshield.com...