|
|
Read configuration data and license information |
|
|
|
|
||
Read configuration data and license information |
|
|
|
|
|
|
|
Read configuration data and license information |
|
|
|
|
||
Read configuration data and license information |
|
|
|
|
|
|
|
||
If the main application is an EXE file, the application should work without any modifications. Only if the EXE files writes configuration files, which should be available after the next program start, a modification could be necessary.
Test your application. If the application writes configuration files typically on the installation folder, this folder is not visible any more to the EXE file while it is running. The folder name can be retrieved reading a text or XML file. The name of the folder, where the EXE file is stored, can be found in the variable <Install-Path-Player>.
The configuration file also provides additional information like the registered customer name, time limitation or whether the product is activated or not.
The All-In-One Player provides a file mp-config.xml and mp-config.txt. This file is generated during runtime. If you application runs in the Virtual Zone the file is not visible. Both files have the same content. Just read the file with the format your application can handle. The files are created in the same folder, where the EXE file is located.
The files provide a lot of information. Some are for future use and are not explained in this documentation. You can download a sample of each file. Download Now!
It is an XML file and you need an XML parser to read it.
<Default> <Install-Path-MMF> - path where the mmf file (database) can be found
<LicenceInfo> <Customer> - license holder name. This is the name which was type in during the product activation
<Module1> <TotalLicences> - number of maximum network licenses define in the screen - License Information or in the Serial Number <RemainingLicences> - licenses available in a network installation <ExpiredOn> - Expiry date of the license - if expired on is 30.12.1899 then it is a version without any time limitation <RemainingDays> - Days left to evaluate the product or to run the full version. If the value is -1 then there is no time limitation <LicenceType> - S - license per Computer, U = license per User, R = license per concurrent user - defines in the screen - License Information <WebActivation> - 0 = status after program start. No Serial Number was applied, 1 = Serial Number was applied, 2 = product is activated, 3 = erroneous activation |
It is standard Windows INI file.
[Default] - Section Name you have to specify if you read an parameter Install-Path-MMF - path where the mmf file (database) can be found [LicenceInfo] Customer - license holder name. This is the name which was type in during the product activation
[Module1] TotalLicences - number of maximum network licenses define in the screen - License Information or in the Serial Number RemainingLicences - licenses available in a network installation ExpiredOn - Expiry date of the license - if expired on is 30.12.1899 then it is a version without any time limitation RemainingDays - Days left to evaluate the product or to run the full version. If the value is -1 then there is no time limitation LicenceType - S - license per Computer, U = license per User, R = license per concurrent user - defines in the screen - License Information WebActivation - 0 = status after program start. No Serial Number was applied, 1 = Serial Number was applied, 2 = product is activated, 3 = erroneous activation |
The variable Install-Path-Player provides you with the installation path of the application. This would be the folder where your application previously stored configuration files.
It is possible that the protected EXE file (variable Player-Name) has a different name like your original EXE file (variable StartExe.)
Use the name of the EXE file you want to protect in the field: Name of EXE file. Then the name of the protected EXE file has the same filename like your original application.
As a configuration file needs a read and write access, you cannot place it to c:\program files folder as there is no write access on this folder for Vista.
Although we found no recommended procedure from Microsoft how to share a file on one PC for all users, the following installation process will work.
Retrieve folder names
You can retrieve the folder name via the registry.
Windows Vista
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Shell Folders |
|
Common AppData |
C:\ProgramData\ |
Windows XP
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Shell Folders |
|
Common AppData |
C:\Documents and Settings\All Users\Application Data |
Create a folder
Save the configuration file to
•Windows Vista - C:\ProgramData\yourcompany name\appname\app.dat
•Windows XP - C:\Documents and Settings\All Users\Application Data\yourcompany name\appname\app.dat
By default, standard users on Vista have only Read access and the folder is not visible. See below how to set write access to this folder.
Some installers have built in options to change rights on folders. You cannot use the standard Windows tool cacls.exe or icacls (Vista) because you have to address the user / group name you want to change in the language of the operation system - e.g. 'users' or 'Benutzer'.
There is a tool SetAcl.exe which allows using SID to change the permission. The tool can be downloaded here: http://setacl.sourceforge.net/html/examples.html . Documentation for the SID can be found here (only German): http://www.grurili.de/index.html?/Grundlagen/WellKnown_SIDs.htm
Your installer could use the following sequence
•Copy setacl.exe to the installation directory •Execute Setacl.exe e.g. "maindir\SetAcl.exe" -on "maindir" -ot file -actn ace -ace "n:S-1-5-32-545;p:full;s:y" - This will set full rights to the group users. The SID S-1-5-32-545 is used instead of the name users •Delete setacl.exe
|
