diff --git a/Contrib/MultiUser/Readme.html b/Contrib/MultiUser/Readme.html index 2c5cfc8e..fcfd7b9f 100644 --- a/Contrib/MultiUser/Readme.html +++ b/Contrib/MultiUser/Readme.html @@ -1,34 +1,39 @@ - - + + + + + Multi-User Header File (MultiUser.nsh) - - -

- Multi-User Header File (MultiUser.nsh)

-

- Installer configuration for multi-user Windows environments

-

- Table of Contents

+

Multi-User Header File (MultiUser.nsh)

+

Installer configuration for multi-user Windows environments

+

Table of Contents

-

- Introduction

+

Introduction

Modern Windows versions support multiple users accounts on a single computer, each with different privileges. For security reasons, the privileges of applications @@ -43,8 +48,7 @@

Note that all settings need to be set before including the MultiUser.nsh header file.

-

- Initialization and Execution Level 

+

Initialization and Execution Level 

Before the MultiUser.nsh file is included, the MULTIUSER_EXECUTIONLEVEL define should be set to one of the following values depending on the execution level that is required:

@@ -76,7 +80,7 @@ Power - Power User privileges are required
+ Power User privileges are required
(Power Users no longer exist in Windows Vista. For Vista this is equivalent to Admin) @@ -111,8 +115,7 @@ Insert the MULTIUSER_INIT and MULTIUSER_UNINT macros in the .onInit and un.onInit function to verify these privileges. If no uninstaller is created in the script, define MULTIUSER_NOUNINSTALL.

- - 
!define MULTIUSER_EXECUTIONLEVEL Highest
+        
!define MULTIUSER_EXECUTIONLEVEL Highest
 ;!define MULTIUSER_NOUNINSTALL ;Uncomment if no uninstaller is created
 !include MultiUser.nsh
 
@@ -124,8 +127,7 @@ FunctionEnd
 
 Function un.onInit
   !insertmacro MULTIUSER_UNINIT
-FunctionEnd

-    
+FunctionEnd

Whether the required privileges can be obtained depends on the user that starts the installer:

@@ -152,10 +154,8 @@ FunctionEnd The following additional settings are available to customize the initialization:

- + +
- Setting - Description - SettingDescription
@@ -193,7 +193,7 @@ FunctionEnd
- MULTIUSER_INIT_FUNCTIONQUIT
+ MULTIUSER_INIT_FUNCTIONQUIT
MULTIUSER_INIT_UNFUNCTIONQUIT 		@@ -202,8 +202,7 @@ FunctionEnd
-

- Installation Mode

+

Installation Mode

As mentioned before, applications can both be installed for a single users or for all users on a computer. Applications for all users are typically installed in the @@ -220,13 +219,8 @@ FunctionEnd The following settings are available to change the default installation mode: - - - + +
- Setting - - Description - SettingDescription
@@ -252,8 +246,7 @@ FunctionEnd After initialization, the variable $MultiUser.InstallMode will contain the current installation mode (AllUsers or CurrentUser).

-

- Mixed-Mode Installation

+

Mixed-Mode Installation

For the Admin and Power levels, both a per-machine as well as a per-user installation is possible. If the Highest level is set and the user is an Administrator or Power @@ -264,7 +257,7 @@ FunctionEnd installation mode. To use this page, define MULTIUSER_MUI before including User.nsh. Then, the MULTIUSER_PAGE_INSTALLMODE macro can be used just like a normal Modern UI page (this page will automatically be skipped when running Windows 95/98/Me):

- 
!define MULTIUSER_EXECUTIONLEVEL Highest
+        
!define MULTIUSER_EXECUTIONLEVEL Highest
 !define MULTIUSER_MUI
 !define MULTIUSER_INSTALLMODE_COMMANDLINE
 !include MultiUser.nsh
@@ -284,8 +277,7 @@ FunctionEnd
 
 Function un.onInit
   !insertmacro MULTIUSER_UNINIT
-FunctionEnd
-

+FunctionEnd

The MULTIUSER_INSTALLMODE_COMMANDLINE setting that also appears in this example enables the installation mode to be set using the /AllUsers or /CurrentUser command @@ -315,8 +307,7 @@ FunctionEnd

Append the username to the per-user radio button.
-

- Installation Mode Initalization

+

Installation Mode Initalization

The SetShellVarContext flag (which determines the folders for e.g. shortcuts, like $DESKTOP) is automatically set depending on the installation mode. In addition, @@ -324,18 +315,11 @@ FunctionEnd mode is initialized:

- - - + + - + - +
- Setting - - Description - SettingDescription
- MULTIUSER_INSTALLMODE_INSTDIR - MULTIUSER_INSTALLMODE_INSTDIR Name of the folder in which to install the application, without a path. This folder will be located in Program Files for a per-machine installation and in the local @@ -343,9 +327,7 @@ FunctionEnd
- MULTIUSER_INSTALLMODE_INSTDIR_REGISTRY_KEY MULTIUSER_INSTALLMODE_INSTDIR_REGISTRY_VALUENAME - MULTIUSER_INSTALLMODE_INSTDIR_REGISTRY_KEY MULTIUSER_INSTALLMODE_INSTDIR_REGISTRY_VALUENAME Registry key from which to obtain a previously stored installation folder. It will be retrieved from HKCU for per-user and HKLM for per-machine. @@ -353,7 +335,7 @@ FunctionEnd
- MULTIUSER_INSTALLMODE_FUNCTION
+ MULTIUSER_INSTALLMODE_FUNCTION
MULTIUSER_INSTALLMODE_UNFUNCTION 		diff --git a/Contrib/System/System.html b/Contrib/System/System.html index 1ef8c1f3..e723ba64 100644 --- a/Contrib/System/System.html +++ b/Contrib/System/System.html @@ -7,7 +7,7 @@ System Plug-in (NSIS) diff --git a/Contrib/VPatch/Readme.html b/Contrib/VPatch/Readme.html index f6cb99be..26c89094 100644 --- a/Contrib/VPatch/Readme.html +++ b/Contrib/VPatch/Readme.html @@ -8,7 +8,7 @@ -

VPatch 3.1

-
+

VPatch 3.1

+

Introduction

VPatch allows to create a patch file to update previous versions - of your software. The GenPat utility generates the patch file. The - plug-in can use the patch to update a file. Using a patch, you can + of your software. The GenPat utility generates the patch file. + The plug-in can use the patch to update a file. Using a patch, you can reduce the download size of your updates because only the differences between the files are included in the patch file.

@@ -119,8 +119,9 @@ a, a:link, a:visited, a:active { color: #4be; } a:hover { color: #6df; }
  • Patch data is invalid or corrupt
  • No suitable patches were found
    • -

    Check example.nsi for an example. You - should check whether the stack string starts with "OK" +

    Check example.nsi for an example. + You +should check whether the stack string starts with "OK" because then the patch has succeeded and you can rename "temporary_newfile.txt" to "oldfile.txt" to replace the original, if you want.

    @@ -128,9 +129,11 @@ a, a:link, a:visited, a:active { color: #4be; } a:hover { color: #6df; }

    GenPat appends a patch to the file you specified. If there is already a patch for the same original file, with the same CRC/MD5, in the patch file, + the patch will be replaced. For example, if you want to be able to upgrade - version 1 and 2 to version 3, you can put a 1 > 3 and 2 > 3 patch in - one file.

    + version 1 and 2 to version 3, + you can put a 1 > 3 and 2 > 3 patch in +one file.

    You can also put patches for different files in one patch file, for example, a patch from file A version 1 to file A version 2 and a patch from file B version 1 to file B version 2. Just call the plug-in multiple @@ -175,6 +178,7 @@ a, a:link, a:visited, a:active { color: #4be; } a:hover { color: #6df; }

    Source code

    Source code is available in the original package and in the SVN repository of NSIS.

    +

    NSIS plug-in (C++)

    The source of the NSIS plug-in that applies patches can be found @@ -183,9 +187,10 @@ a, a:link, a:visited, a:active { color: #4be; } a:hover { color: #6df; }

    Patch Generator (C++)

    The most interesting part of VPatch, the actual patch generation - algorithm, can be found in Source\GenPat\PatchGenerator.cpp. The - header of that file contains a brief explanation of the algorithm - as well.

    + algorithm, can be found in Source\GenPat\PatchGenerator.cpp. + The +header of that file contains a brief explanation of the algorithm as well. +

    User interface (Delphi)

    diff --git a/Contrib/nsDialogs/Readme.html b/Contrib/nsDialogs/Readme.html index ca5f2817..1e7db6f0 100644 --- a/Contrib/nsDialogs/Readme.html +++ b/Contrib/nsDialogs/Readme.html @@ -7,7 +7,7 @@ nsDialogs