Bug: System Requirements: Administrator Rights

[Saturday, January 22, 2005 4:31 PM]

Using 5.0.1022

I just tested System Requirements Administrator Rights on 2K and XP Pro SP2.
A non-admin user that is a member of the Power Users group is considered to
have admin rights. That is incorrect as the two have different privilege
levels.

I tested a normal user account on XP Pro SP2. The setup displayed a message
that admin rights were necessary, but did not terminate the install. The
result of this is that the install fails later when it can't write to Program
Files.

--
Best regards,

Mark

[Saturday, January 22, 2005 6:01 PM]

Mark,

I just experimented (2k SP4) and power user is indeed also able to run the
install.

As for your second point - Friedrich is being tricky. (I asked him about
this some months ago.) When you click the Administrator Rights box once and
get a green tick, the setup will say admin rights are required but not
enforce it. When you click the box a second time and get a red X, the box
is enforced (with the power users bug you've pointed out.)

Jane

[Saturday, January 22, 2005 6:12 PM]

>Mark,
>
>I just experimented (2k SP4) and power user is indeed also able to run the
>install.
>
>As for your second point - Friedrich is being tricky. (I asked him about
>this some months ago.) When you click the Administrator Rights box once and
>get a green tick, the setup will say admin rights are required but not
>enforce it. When you click the box a second time and get a red X, the box
>is enforced (with the power users bug you've pointed out.)

Jane,

Well there's a clue. I saw the checkbox state behavior and thought the red x
would mean disallow an admin user, which made no sense to me.

Thanks much. :}

[Saturday, January 22, 2005 6:56 PM]

For me, the option to say that admin rights are required but let the
installation proceed anyway is something the potential usefulness of which I
can't fathom. (And I'm sure that having exposed my lack of perception, I'll
be educated as to its merits forthwith <g>)

Jane

[Saturday, January 22, 2005 8:44 PM]

>For me, the option to say that admin rights are required but let the
>installation proceed anyway is something the potential usefulness of which I
>can't fathom. (And I'm sure that having exposed my lack of perception, I'll
>be educated as to its merits forthwith <g>)

Jane,

For my own work, I agree completely. If I require permissions it's a hard
requirement that I have to enforce. OTOH, I have little doubt that were
Friedrich to implement that, and only that, some folks would desire a simple
warning. Pesky users are well, pesky, but with a user base of developers, I
envy Friedrich his patience. :}

I have an idea for a suggestion that will address this, while adding some
funtionality to SB5. In the meantime, I'm going to take a stab at porting a
couple of hundred line of WISE script to SB5 that makes having it any way for
any group membership easy.

--
Best regards,

Mark

[Saturday, January 22, 2005 11:50 PM]

Mark,

I built a simple installer and used the dll from vuFileTools to check for
admin. It flags administrators correctly.

> Friedrich to implement that, and only that, some folks would desire a
simple
> warning.
That I could possibly see. But as it is, Friedrich's isn't a warning. It
says "you MUST be an administrator" but proceeds anyway.

Jane

[Sunday, January 23, 2005 1:29 AM]

>Mark,
>
>I built a simple installer and used the dll from vuFileTools to check for
>admin. It flags administrators correctly.

Thanks for the suggestion. I had look and, like SB5, it only deals with admin
rights. I'm interested in Power User and administrators, and occasionally
have a need for arbitrary group membership (in what groups is user a member).

>> Friedrich to implement that, and only that, some folks would desire a
>simple
>> warning.
>That I could possibly see. But as it is, Friedrich's isn't a warning. It
>says "you MUST be an administrator" but proceeds anyway.

Typical of me, I didn't even stop to read it. I just blew by and let it fail
in Program Files. That's something I'm sure Friedrich will fix.

--
Best regards,

Mark

[Monday, January 24, 2005 9:20 AM]

Mark,

Fixed in our latest internal source codes, thank you.

As a temporary workaround, you can use this in your script:

If %_SB_INSTALLERFLAG% Not Equals "1" on Position "$SB_ADMINISTRATORFLAG$"
And %WINVER% Greater Than or Equal "$WIN_NT$" Then
Message Box "#ERR_LAUNCH_CONDITION_ADMIN#" -- ""
End

Thanks,
Friedrich

--
Friedrich Linder
www.lindersoft.com
Fax: 1.954.252.3910

[Monday, January 24, 2005 1:56 PM]

Thank you, Friedrich.

--
Best regards,

Mark