Announcement

Collapse
No announcement yet.

WindowsNT Permissions

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • WindowsNT Permissions

    When I tried to install on 2 other, different NT4 machines with restricted privileges, I got some odd results

    Windows NT4 has a concept of Program groups (icons), which can either be 'common' or 'personal'.

    'Common' refers to program groups/icons that can be used by any user, with administrator access or not.

    'Personal' refers to program groups that only a specific user or any administrator can access. A different user without admin privileges cannot access/see these program
    groups.

    To cope with this an installer needs to be able to identify an NT4 OS and to know if it has admin privileges or not.

    With admin privilege in NT4 the installer should set the Program Group type
    to 'common' and install the program groups/icons to there.

    If it does not have admin privilage then in NT4 the installer should set the Program Group type to 'personal' and install the program
    groups/icons to that location.

    Without this action if installer tries (by default) to install to the common
    group when it does not have admin privilage then in such a case it would fail to
    install the icons (what we see with you current installer).

    When we use SUF 5 to create an installer it works on all platforms, except NT. Without admin privileges, the installer does not install the program group icons in the menu, With admin privileges, it works fine.

    How can I get the installer to check and make adjustments for the Windows NT admin privileges?

    Please help. no one answered my email request.

  • #2
    Re: WindowsNT Permissions

    There are a few built-in variables available such as the following:

    *********************************************
    %DeskTop%
    The user's Desktop directory. On Windows NT, this is from the per user profile.

    %DeskTopNT%
    The user's Desktop directory. On Windows NT, this is from the All Users profile.

    %IsWin95%
    %IsWin98%
    %IsWinME%
    %IsWinNT3%
    %IsWinNT4%
    %IsWin2000%
    %IsWinXP%
    These variables have a value of "True" or "False" depending on whether the install is running on the respective operating system.

    %IsUserNTAdmin%
    Whether or not the user of your setup is currently logged into Windows NT with Administrator permission. Returns "True" or "False". On non-Windows NT systems, this will always return "False".

    %StartMenu%
    The user's Start menu directory. On Windows NT, this is from the per user profile.

    %StartMenuNT%
    The user's Start menu directory. On Windows NT, this is from the All Users profile.

    %StartMenuPrograms%
    The user's Start menu programs directory. On Windows NT, this is from the per user profile.

    %StartMenuProgramsNT%
    The user's Start menu programs directory. On Windows NT, this is from the All Users profile.


    %Startup%
    The user's Startup folder. On Windows NT, this is from the per user profile.

    %StartupNT%
    The user's Startup folder. On Windows NT, this is from the All Users profile.

    **********************************************

    These are just to name a few. You can find the full list in the "Built-in Variables" section of the Command Reference.

    You can create shortcuts using two methods, on the SHORTCUT tab of the file's properties and through the SHORTCUT ICONS tab in SYSTEM EDITORS. If you would like full control of your shortcut creations, how and where they are created, you may want to create your shortcuts in SYSTEM EDITORS with the addition of some conditions to control which ones are created. If you do this, remember that any shortcut you create using an action, must be removed with an action in Uninstall.

    This seems to be the core of your problem.


    ------------------
    Sincerely,

    Darryl Hnatiuk
    Indigo Rose Corporation

    Comment

    Working...
    X