6. Dezember 2010
 |  Keine Kommentare

nBinder LIMITED

Version: 5.5.1

Price and licensing: 89 USD single developer license or 199 USD company license

Release date: 14 May 2008

Copyright: NKProds SRL 2007

Website: www.NKProds.com (EN)

Support Forum: www.NKProds.com/forum

Contact: [email protected], [email protected]

Update: Update NOW!

Purcahse nBinder PRO Unlimited: PURCHASE NOW

This is the new nBinder generation modified according to users requests to offer more control and functionality.

For a more detailed description on what’s new in version 5.5.1 look here.

  • Can now add an unlimited number of files to a project. The 200 files limitations has been removed.

  • Added drag and drop support both for files and folders and for moving project items.
  • Supports conditional run. Can now implement repetitive and conditional sequences using Controls and Conditions.
  • New license for nBinder oriented to company development (single developer license and company license)
  • New Files and Registry related Commands. (9 new commands)
  • New Windows and File Commands (6 new commands).
  • Added Progress Window option for unpacker.
  • Changed the way commands are added into the project.
  • Command order now relative to file order in project.
  • Redesigned user interface.
  • Can now edit commands.
  • Improved icon handling. It now extracts all icons in a selected icon group and adds them to the output file.
  • Add new option to set command line arguments for each file in the project. Also supports special values.
  • Improved unpack folderfiles protection.
  • Improved Check for Updates feature.
  • Better security for the unpacker (for the output file)
  • Reviewed code and improved speed, security and error handling, also increasing stability and reliability.
  • Reviewed and improved the user interface.
  • Fixed reported bugs. (working dir and some interface issues and a problem regarding multiple builds).

nBinder has become easier to use, more secure, faster and more stable. The most important update is now the removal of the 200 files limit. This allows users to create larger projects not being forced create multiple projects in order to add more files.

With version 5.5 a new milestone has been reached in nBinder’s development by adding Controls and with them support for Conditional Run for files and commands inside the project. This allows users to create repetitive and conditional sequences based on a series of predefined conditions. This feature also provides more control over projects.

IMPORTANT CHANGE: From version 5.5 files added into the project are unpacked when they are encountered during the linear execution of the project and then executed if it should. In earlier version all files in the project were unpacked before anything else, all at once and then the unpacker executed the project in order. Now files are unpacked only when encountered.

This change means that if you have a project that contains more files, including an executable file (an application) and some dll files or other resource files that the .exe needs to run, then you should add all the .dll files and the resource files before the associated executable file in the project list so that the resource files are unpacked before the executable that needs them.

Also we have tried to make this version more stable and reliable, reviewing most of the code making fixes to improve speed, security and remove bugs. We also improved the error handling for both nBinder and the unpacker to catch and handle errors that in the past might have just crashed nBinder or the unpacker.

This version is compatible with projects created with nBinder 5.1.x and 5.5 but not vice-versa.

nBinder is a file binder, compressor and icon changer. Use nBinder to:

  • Compress your executables (and/or any other files) so they occupy less space and are more difficult to reverse engineer (hack)
  • Create complex projects using Controls to define conditional behaviors, repetitive structures and scheduled events.
  • Enhance your executables with complex commands.
  • Password Protect any file(s) at same time compressing them.
  • Bind and compress executables along with their resource ( DLLs and other) files into a single stand alone executable (.exe).
  • Replace your application’s icon and version information with data from another executable, dll file or icon file.
  • Keep your application updated by using URL files to automatically download files from the Internet.
  • Silently installation for your products.
  • Restrict your application to only one run by making it self delete itself after one use.

With nBinder you can:

  • Compress executables (or any other file type) without affecting their direct functionality, so you don’t have to unpack them before run

  • Password protect any kind of file without the file losing its direct functionality.
  • Use Controls to define conditional behaviors based on Conditions, tests of different kinds.
  • Create repetitive, conditional sequences and scheduled events.
  • Define scheduled events using the Wait for Control and Conditions.
  • Add more functionality to your application by biding it and adding complex commands to it both before and after execution
  • Compact applications by packing the executable files along with their dlls and other resource files

  • Bind dlls and other resource files to your executable so you can distribute your application as a single (smaller, protected) executable.

  • Protect your application by binding it and selecting the self delete option so that a user can use your application (output) only once, the file deleting itself after one run.

  • Make an silent installer for your application that will be able to install your application and its needed files to a certain directory and run your application when the install process is complete

  • Keep your applications updated by automatically downloading new files from the Internet.

  • Protect your applications against reverse-engineering and other hacks.

  • Transform any format in an executable without affecting its direct functionality

  • Convert an entire web site (along with pictures and other resources) into a single executable

  • Password protect your executables or any other file

  • Password protect your images, pictures, documents, projects,

    music …etc.

    and at the same time compress them

  • Compress and you picture gallery or your music gallery and transform it into a single executable file so you can carry it with you everywhere

  • Hide files inside an application and have them silently extracted to a certain directory

  • Change executables icons

  • Compress any file without losing its direct functionality

The primary disadvantage of common archives (.zip .rar .ace etc.) is that once files have been archived they loose their direct functionality, meaning they first have to be unpacked and the run. nBinder comes to fix this problem combining the advantages of archives with the direct functionality of the uncompressed files and many more other options like password protection and anti hacking protection for executables, complex commands that enhance functionality or URL files. Files compressed with nBinder are transformed into standalone executable files (.exe) that, when executed they act the same as the packed files would if run uncompressed, maintaining their full direct functionality. For example a packed movie when run will open the movie into its default application, without the user having to decompress it first. You can use the files compressed (blinded, protected) by nBinder without having nBinder or other application installed on the computer.  You can later extract the packed files from the output file either by using nBinder or by running the output file with the /unpack command line.

Also using nBinder you can enhance or create applications by using Commands (for registry access, file access, windows management and more) and Controls (used for conditional run, repetitive and conditional sequences, scheduled events, error detection( and more. The Commands and Controls are aware of date, time, special folders, username, command arguments and more through the use of keywords that are replaced on runtime (for example you can use %DATE% for the date at runtime)

Unlike other executables packers with nBinder the files are unpacked to a safe, protected location and then ran from there so the unpacked executable will not fail any CRC checks it may contain because the files are extracted to their initial state, unmodified in any way before they are launched.

Please write bugs, problems, questions, ideas. Contact Us.or write to us on our Support Forum.

  • Can be used to pack (compress, encrypt and protect) dll’s and other resource files that might be needed by executables, for a more compact and fast distribution, into a single stand alone executable file. It doesn’t modify files in any way, it unpacks them to their initial state and then it launches them.

  • Handles an unlimited number of files.
  • Save and Load projects along with file options and commands for a faster work flow.
  • Supports Conditional run with repetitive, conditional sequences along with event schedule, all using Controls and Conditions.
  • Advanced compression algorithm offers a very good compression ration and at the same time a very fast decompression.
  • Can compress executables to make it harder to reverse engineer or hack.
  • Can encrypt files to make it almost impossible ot extract them using hack methods.
  • Complex system, file, and registry Commands that can be added to projects to increase the functionality of your files.
  • Can add and use URL files (addresses to files on the Internet that are downloaded when the output file is launched and are handled as normal files).
  • Extract icon and version information for the output file from other applications (EXEs), DLL files, and ICO files.
  • Can show the progress of the unpack process for each file and the total progress by using the Progress Window option from Global Options.
  • Password Protection for the output file to restrict access to the binded files. Strong password protection: the password is not stored in the output file, only a hash check is. You can add a password for RUN or/and Unpack.
  • Can set individual options for each file in the project along with Global options affecting all files in the project.
  • Supports directory structures for unpacking files.
  • Can send different command line arguments to each file in the project. It also supports special values. You can send the arguments from the output to any file in the project. (C:.exe ).
  • Can remove unpacked files either after all EXEs in the project close or at next boot. You can also leave the files on the hard disk.
  • Can handle multiple files or a single file per project.
  • Can create project only with commands and controls, with no files.
  • Unpack binded files either from within nBinder(Project->Unpack output file) or by command line with the output file (C:.exe /unpack /).
  • Start the password protected bound files by sending the password in the command line (C:.exe /pass /) when you launch the output.
  • Can add a protective measure to your application by selecting the self delete option so that the application (output) will delete itself right after it will run, preventing user to rerun application.
  • The folder in which the files are unpacked can be protected so that no other application can access the folder or the files inside.
  • Can use special keywords like %TEMP%, %DATE% and other to specify special folders and special system parameters fro commands, controls, unpack paths and command line arguments.
  • Other special keywords are used to get system information at runtime like the date, time, user name, the command arguments used when the output file was launched and more.
  • Select a level of compression for each file in the project when you compress files in the project, select to which folder should each file be unpacked to, the name of the file (should be kept the same for dlls), the order in which they should be executed, if they should be visible at start, and if the files should be removed after run or at the next boot.
  • User friendly interface includes hints and help that explain features and also explains how to use them.

Plans for the future:

  • Maybe nMacro 2 + nBinder. What do you say? Contact us.

nBinder can be used if, for example, you have an application that uses one or more dlls (or other resource files) and you want to bind the files into the executable file so you can distribute your application as a single file, and in the same time compress your application, making it smaller and harder to hack. To do so add the files of your application beginning with the executable by clicking the button „Add“ (at the bottom of the list), and then the button file from the menu that appears, and then using the same method add all the resource files or executables included in your project. If you bind the dlls to your application please make sure to check the „keep original file names“ check box found in the Advanced dialog (Global Options), in order to make sure that the dll files keep their name through the unpacking process, so that your executable can find and use them as it was designed to. After you make sure that all the settings are correct for each file add the output file in the text box in bottom part of the dialog. You can modify settings for each file either by double clicking on any file in the list or by selecting a file from the list and clicking on the button option situated in the lower right side of the main dialog. Also you can select the icon of the binded (output) application. If you select no icon, the icon of the first file (the host) is automatically used. This is it. all you have to do now is to click the Bind button. The compression feature in nBinder works much better on bigger files (>100 KB).

nBinder can be used if, for example, you have a movie that you want to password protect or compress it. To do this add the movie file to the list, write the password in the Advanced->Password Protection screen, check the compress check box if it isn’t so already and make sure the extension of the movie file is written in the Start file types edit box. (only insert the last 3 characters of the files name: avi, mpeg=peg, mp3 etc.) or double click the file after adding it in the list and select Execute. Then all you have to do is to select an output file and press on the Bind button. You can also add a mp3 file for example then and select the all hidden option. On run the mp3 will start playing in the default player (Ex. Winamp) but the window of the program will no be visible. This is true for all files types you add to the project.

nBinder can also be used to create new applications from scratch by working with Commands, Controls and Files. You have a large number of commands available for registry, files, system and windows management. These commands and any files can be combined inside the project with Controls. Control allow for conditional run of files and commands. You can use controls to create repetitive and conditional sequences and also to create scheduled events.

  • If you want for an file created with nBinder to run only on a given date or time you can add a wait for command by pressing the ‚add control‘ button and selecting the ‚wait for…‘ control. Next the Conditions dialog appears. Here you can specify how long this control should wait until letting the project continue (use 0 for infinite). To make sure the output file continues only at a certain date and time add the Date is… condition (specifying the date you want the file to run at) and the Time is… condition (specifying the time at which you want the file to run). Now the output file when encountering this control in the project will pause and wait until the set conditions are met, in our case until the system date and time are the same with the ones specified at creations.
  • If you want to create a repetitive sequence (a sequence of files, commands and controls in the project that are executed more than one time, depending on some set conditions) add the commands, files and controls that you want to be repeated then add a jump to line control by pressing the ‚add control‘ button and selecting the ‚Jump to line…‘ control. Next the Conditions dialog appears. Specify here the line to which this control should jump if the conditions that we will specify next will be accomplished (in this case if you have started a new project enter 0 to specify that it should jump to the first line of the project. Next specify the Conditions to let the project know when it should jump to the given line. You can leave the Conditions list empty if you want the output to jump to the specified line every time the control is encountered. In our case this will create a never ending repetitive sequence and is not indicated to do so unless you know what you are doing.

The unpacker (output file) after creation, when launched it will ask for a password if one has been set, then if set it will execute the before commands, then it will unpack the files to the selected folder for each of one (also protecting the folder is set to), decompress them and if selected it will open (launch them). If the selected start mode is In Order it will open files, waiting for each EXE file to close before unpacking the files after it. When it has unpacked and opened all files it will execute the after commands and then it will close. The Unpacker will protect the unpack folder(s) only as long as it is open. When the unpacker exists the folder(s) will no longer be protected.

  • If you decide to unpack the files included in bound (output) file run the file with the following command line: C:.exe /unpack /
  • It will ask for a password if the file is password protected on Run OR on Unpack

Example: D:Projectsbound.exe /unpack /C:Program FilesBound 

  • You can start a password protected output file by specifying the password as a command line argument: C:.exe /pass /

Example: D:Projectsbound.exe /pass /mypassword (where mypassword is the set password)

  • You can also pass command line arguments to the first .EXE file in the project or to any file in the project that has %OUTPUTCMD% set as it’s Command Line Argument (in file options):  C:.exe

Example: D:Projectsbound.exe -h -a

Remember: Projects are executed sequentially in order from the first line to the last if controls aren’t used.

To reset settings to default just click on the Reset to Default button in the Advanced dialog or close nBinder, delete the file options.dat in the program’s installation directory (by default: C:Program FilesNKProdsnBinder) and then re-start nBinder.

If you want to change options to multiple files and you don’t want to change them file by file by using individual file options you can change them all at one by using the Advanced Global options. Once an option is changed here it will affect all files in the project.

NOTE – KEYBOARD SHORTCUTS: You can use keyboard shortcuts like the DELETE key to remove a file or a command from the project, INSERT to add a new file to the project, SPACE to see a file’s options or to edit a command, CTRL+S to save the project, CTRL+O to load a project, CTRL+N to start a new project and F5 to Bind.

Terminology:

  • Output file – is the executable (.exe) file that will result after the bind operation completes. This is the file that will contain the files added to the list.
  • Commands – special project items that can be added to a project to enhance functionality and perform a series of predefined actions like registry access, file creation, removal, window management (hide/close/minimize/activate windows) and many more.
  • Controls – special project items that can influence the project flow, the order in which commands and files from the project are executed or if they are executed or not, based on some set conditions that have to be true for the control to work. Projects are executed sequentially in order from the first line to the last if controls aren’t used.
  • Conditions – are tests done to see whether to execute a control or not. Multiple conditions can be added for every control and they need to be true simultaneous in order for the control to be executed. If no conditions are added for a control then it will be executed every time it is reached in the project.
  • Unpacker – The unpacker is actually the part of the output program that unpacks the files added to the project (output) as temporary files in the specified temporary folder according to the options the user set and then runs the specified files. The unpacker is also responsible for protecting folders if this option was specified. The protected folders will only be kept protected while the unpacker is open (runs), once it closes the folder will be unprotected. The unpacker will be opened until the last executable file in the project has closed.
  • Take icon from – sets the icon of the output file. If no icon file, executable or dll is selected the icon of the first file (if .exe .dll or .ico) in the list will be used. If the project contains no exe file then no icon will be set and the default icon will be used.
  • Take version from – sets the version information (product name, company name, version number …) for the output, by copying this information from the specified .exe file
  • Unpack output file – select an packed file (output) created with nBinder to unpack the files that were added, to an selected path. If the packed files was protected you will have to insert the right password before unpacking. You can also unpack an output file by running it with the following command line: C:.exe /unpack / Example: D:Projectsbound.exe /unpack /C:Program FilesBound 
  • URL file – Refers to a file that resides on the Internet. When you add a URL file you actually add an address to a file from the internet (for example: http://www.NKProds.com/res/nk_title.gif) that will be downloaded at runtime each time the output file is launched. The URL file is handled by nBinder exactly as a normal file.

Add menu (add files, commands or controls to the project)

  • Add file(s) – This allows you to add files situated on your hard disk to the project list. You can add one or multiple files (using CTRL or SHIFT).

    To add a new file you can also press the INSERT key or CTRL + I while in the main list. When a new file is added it’s File Options are set after the Global Options.

  • URL file – This option allows you to add an address to a file located on the Internet. The file will be downloaded each time the output is launched. You can manage this file inside nBinder’s project the same as you would any other file.
  • Files and Sub Folders – This option allows you to add all files in a folder along with files in sub folders, maintaining the directory structure of the selected folder. This options is useful when binding multiple files with hard coded relative path dependencies.
  • Files from folder – This options adds all files from the specified folder but does not add files from sub folders, only files from the selected folder.
  • Add Command – This option presents you with a list of commands that you can add to the list. After you select a command from the list menu you will see a window in which you can insert the settings for the selected command. The command will be added to the list and executed in the project order.
  • Add Control – This option presents you with with a list of 4 Controls from which you can choose.

To Remove an item from the list you can either press the Remove button found bellow the Add button or you can use the DELETE key. You can select for removal one or multiple project items.

NOTE: To see and edit the File/Command/Control options or just double click the project item item and a new window will appear with the options for the selected item.

Keyboard Shortcuts

nBinder supports the following keyboard shortcuts:

  • F5 – Bind project
  • CTRL + B – Bind project
  • CTRL + N – New project
  • CTRL + O – Open project
  • CTRL + S – Save project
  • CTRL + P – Global options
  • CTRL + I – Insert a new file
  • INSERT – Insert a new file
  • SPACE – Edit selected project item
  • DELETE – Removes a project item
  • CTRL + Z – Undo last action. Supports adding, removing and moving project items. Does not support editing project items
  • CTRL + Y – Redo last undo-ed action. Does not support editing project items
  • CTRL + A – Select all project items

Command line arguments

Both nBinder and files created with nBinder (output files) support command line arguments. For example you can start nBinder using the /load= argument followed by the path to a project file (.nbp) to load the specified project.

For nBinder:

  • /load= – Followed by the path to a project file will open the specified project file and will start with the project open.
  • /build – Will build the opened project. Valid only when the /load= argument is also specified
  • /out= – Followed by the path where to save the output file (include the filename). Overwrites the output path specified in the project (if it exists)
  • /quiet – Will build the project without showing the interface. Valid only when the /build argument is also specified
  • /progress – When specified will display the progress dialog during a build even if /quiet has been specified
  • /test – Will open the newly binded file as soon as the bind process is completed succsesfully

Example: nBinder.exe /load=D:project.nbp /build /out=D:project.exe /quiet

For the unpacker (output):

  • /unpack – If you decide to unpack the files included in bound (output) file run the file with the following command line: C:.exe /unpack /. It will ask for a password if the file is password protected on Run OR on Unpack

Example: D:Projectsbound.exe /unpack /C:Program FilesBound 

  • /pass – You can start a password protected output file by specifying the password as a command line argument: C:.exe /pass /

Example: D:Projectsbound.exe /pass /mypassword (where mypassword is the set password)

  • You can also pass command line arguments to the first .EXE file in the project or to any file in the project that has %OUTPUTCMD% set as it’s Command Line Argument (in File Options):  C:.exe

Example: D:Projectsbound.exe -h -a

Special Keywords

Special keywords are text sequences that can be used any ware, in commands, in conditions, in unpack paths, command line argument list and so on, that will be replaced at runtime by the output file with the special value associated. Here is a description of all the keywords:

  • Runtime folder means the folder in which the output file is opened from. To extract the files in the same folder as the output use the %RUNTIME% keyword or leave the unpack path field empty.
  • %UNPACK% – Will be replace with the folder in which the last extracted project file has been unpacked into. If there was no file extracted until that point then it will be replaced with runtime folder.
  • %TEMP% – Will be replaced with System Temporary folder. Example: C:Documents and SettingsAdministratorLocal SettingsTemp
  • %WIN% – Will be replaced with Windows folder. Example: C:Windows
  • %SYSTEM% – Will be replaced with the systems folder Example: C:WindowsSystem32
  • %DESKTOP% – Will be replaced with the desktop folder for the current user. Example: C:Documents and SettingsAdministratorDesktop
  • %USER% – Will be replaced with the current user’s Documents and Settings folder. Example: C:Documents and SettingsAdministrator (if the user name is Administrator. Also you can get the user name by using the %USERNAME% keyword)
  • %PROGRAMFILES% – Will be replaced with current Program Files folder. Example: C:Program Files
  • %OUTPUTCMD% – Will be replaced with the command line arguments (if any) that have been sent to the output file when it was launched. Example: nBinderExample.exe -nnn (here the -nnn text is the command line argument)
  • %OUTPUTNAME% – Will be replaced with the name of the output file. Example: nBinderExample.exe (here the name of the output file created with nBinder is nBinderExample.exe)
  • %DATE% – This keyword will be replaced with the current date at runtime of the output file. The date format is HH/MM/YY.
  • %TIME% – This keyword will be replaced with the current time at the runtime of the output file. The time format is HH:MM (where HH is in 24h format)
  • %USERNAME% – Will be replaced with the current name of the current logged on user.
  • %ACTIVEWND% – Will be replaced with the name of the currently active window

For registry commands and registry related conditions only, you can use the following keyword too when specifying the registry path:

  • HKCU – Will be replaced with HKEY_CURRENT_USER
  • HKLM – Will be replaced with HKEY_LOCAL_MACHINE
  • HKCR – will be replaced with HKEY_CLASSES_ROOT

Commands

Commands can be added to the project in what ever order necessary relative to other commands or files. You can add commands in any order you want.

  • Message Box – This command will display a message box containing the message you selected, no icon and the caption will be the name of the output file.
  • Execute command – Here you can add commands like paths to files to be opened or internet addresses to opened in the default internet browser or names of Windows apps like notepad to open NotePad or mspaint to open Paint or msconfig. You can also write a command like mailto:[email protected] to begin composing an email (using the default email application) to send it to the specified email address.
  • Sleep – This command will make the unpacker (output) pause for the specified time. This is useful if for example you need the unpack folders to stay protected for a longer period of time and to do this you need to keep the unpacker open, by adding a delay after execution, a delay until it exits.
  • Create File – This command will create a new file on your hard disk having the specified path, name and contents. You can specify the path and name in the first edit box in the add command window and the contents of the new file in the second edit box. You can use special keywords like %DATE% and other in both edit boxes.
  • Register DLL/ActiveX/OLE – This command uses system’s regsvr32.exe to register the specified .dll file, ActiveX file or OLE file. The registration is silent and doesn’t display any information in case of success or failure
  • Delete File – This command simply deletes the specified file. You can use special keywords to specify relative paths, just as you can in the unpack path in the Temporary screen.
  • Block Input – This command blocks all keyboard and mouse input until the all executable files in the project exit and so the output exits or until the user presses CTRL+ALT+DEL or until the user adds another Block Input command to disable it. Until then the keyboard and the mouse will not function.
  • Shutdown/Restart – this command shuts down or restarts the system. NOTE: It forces applications to close.
  • Delete File – Deletes the specified file
  • Copy File – Copies the specified file from it’s location to the specified new location.
  • Create Folder – Creates a new folder (directory) having the specified name.
  • Delete Folder – Deletes the specified folder and all it contents (files and sub folders)
  • AddSet Registry Value – Create a new registry value having the specified value or change the value of an existing registry value.
  • Delete Registry Value – Removes the specified registry value.
  • Add Registry Key – Creates a new registry key or modifies an existing registry key, also setting it’s default value. This value can be „“.
  • Delete Registry Key – Removes an existing empty registry key.
  • Activate/Close/Hide Window – This command will modify the status of the window with the specified title. The specified title needs to be an exact match of the window title. You can Close the window (closes the app owning the window too), Minimize it to the task bar, Hide it so that it will still be opened in the background but will disappear from the desktop and task bar. Also you can choose Show Window which will show the window if it is hidden and reactivates it, bringing it to the desktop.
  • Terminate Process – This command will close the specified process (application). You should specify the process name (as it appears in Task Manager). Usually the process name is the same with the file name, for example mspaint.exe for Windows Paint.

For registry commands use:

HKCU for HKEY_CURRENT_USER

HKLM for HKEY_LOCAL_MACHINE

HKCR for HKEY_CLASSES_ROOT

NOTE: To edit a command just double click it or select it and press the SPACE key. You can also press F5 to Bind the project.

Controls and Conditions

Starting with version 5.5, nBinder supports controls, which allow for better project control and conditional run. Users can now add controls to create repetitive sequences, to schedule events, to conditional events and more.

Controls will be execute only if all set conditions are true. You can add a control without any conditions, so that the control will be executed each time it encountered in the project with no matter for conditions.

With controls you can create repetitive structure by adding a jump to line control that will jump backwards. You can create a scheduled event by adding an Wait for control with unlimited wait time and as condition you can add a Date is… or a Time is… condition that will keep the project idle in the background until the date andor time are the same as the ones you have specified, at which moment it will continue executing the project.

For demonstrations on how to use control and other nBinder features you can take a look at the examples found in the Examples folder in the installation folder.

Controls:

  • Jump to line – When this control is encountered in the project, the output file will jump back or forward to the specified project line (to the project item that has the specified priority). Please note that the counting begins from 0 so the first project line (item) has the number 0. In order for this command to work properly please specify a line value between 0 and the number of project item minus 1. This control will be executed only if all set conditions are true.
  • Pause for – This control makes the project stop at it’s line and wait for the specified number of seconds, only if the set conditions (for this control) are all true.
  • Wait for – This control can be used for schedule purposes as it makes the project stop at it’s line and wait for the specified conditions to be true, testing them every 2 seconds. You can also specify a maximum wait time, which can be set to 0 (zero) for an unlimited wait. So when all set conditions are true or after the maximum wait the project will continue past this control. When this control is encountered the output file (the project) will be blocked at the control’s line until all conditions are met or (if the maximum wait time is not 0) until the maximum wait time passes.
  • Abort if – This control will cause the project to end there, if all it’s set conditions are found to be true. When aborted the output file will just close and no line after the Abort control line will be executed.

Conditions:

Conditions are test that need to be true in order for the control associated with them to be executed. A control can contain one conditions, multiple conditions or no condition at all. If it contains no condition, the control will be executed every time it is encountered in the project with no test done.

Users have available for each control a set of 14 predefined Conditions from which they can choose.

  • Last exe returned – Test to see if the value returned by the last executable file (application) launched in the project is the same as the specified value. This value should be a number. If no executable file has been launched by the project or no value has been returned the default value will be 999999. If the specified value is not the same as the last returned value this condition is set to false and the control that owns it will not execute.
  • Folder exists – Tests to see if the specified folder (directory) exists. If the folder exists the condition is true.
  • Folder is empty – Tests to see if the specified folder (directory) contains no files or sub folders. If the folder is empty the condition is true.
  • File exists – Tests to see if the specified file exists at the specified path. If the file exists the condition is true.
  • File is empty – Tests to see if the specified file is empty, contains nothing. If the file is empty the condition is true.
  • File contains only – Test to see if the specified file contains only the specified text. If the file contains other text (other characters) than the specified ones the condition is false. The condition is true only if the specified file contains only the entered text. You can specify the offset from which to begin reading and the number of characters to read. To do this add : after the path to specify the offset from which to read. Add another : and specify how many characters to read from the file. For example D:text.txt:10:20 reads 20 characters from the 10th character in the file.
  • File contains also – Test to see if the specified file contains the entered text along other text, or if the file contains only the entered text. This condition is true if the file find the specified text in the contents of the file. You can specify the offset from which to begin reading and the number of characters to read. To do this add : after the path to specify the offset from which to read. Add another : and specify how many characters to read from the file. For example D:text.txt:10:20 reads 20 characters from the 10th character in the file.
  • Registry key exists – Test to see if the specified registry key exists in the Registry.
  • Registry entry exists – Test to see if the specified registry entry (value) exists in the Registry.
  • Registry KeyEntry contains – Test to see if the specified registry entry (value) contains the specified text only. This condition is true only if the entry contains only the entered text.
  • Window exists – Test to see if the specified window is opened. In order to find the window you must enter it’s exact title.
  • Window is active – Test to see if the specified window is opened and is active (has focus). In order to find the window you must enter it’s exact title.
  • Process exists – This condition tests to see if the specified process (application) is running. Yo should specify the process name (usually the file name, for example mspaint.exe for Windows Paint).
  • Date is – Test to see if the date at runtime is the same with the specified date. If the dates are the same then this condition is true. To select a date you can use the calendar by pressing the calendar button. The format for the date is DD/MM/YY where D is the day, M is the month and Y is the year.
  • Time is – Test to see if the time at runtime is the same with the specified time. If the times are the same then this condition is true. The format for the date is HH:MM where H is the hour in 24h format and M is the minute.

Starting with version 5.5.1 you can also specify when to execute the controls. You can specify if the controls should be executed when all the conditions are true or false, or when any condition is true or false. You can do this in the Add Control window by clicking on the all text at the bottom yo change it to any or by clicking on the true text at the bottom to change it to false.

When the first text is any instead of all then the control will be executed when any of the specified conditions in the list is true or false (as set next). When the text is set to all then all conditions must be true or false for the control to be executed.

When the second text is false the all (or any) conditions must be false for the control to be executed.

FILE OPTIONS

To access the file options just select the file from the list and press the Options button situated on the lower part of the screen, on the right. You can also press the Spacebar to see the File Options window.

NOTE: File options are influenced by the Global options. If you change a global option then that option will be change for all files in the list. The Global options and the file options don’t have to be the same. Global options are just a quick way to change and set all individual file options.

Unpack Options

Here you can specify where to unpack the selected file. The same rules as for the global unpack path apply here. You can also select if you want the unpack file to be protected. Again the same rules apply as for the global protect option.

This keywords, along with the other special keywords, can be used to specify special folders:

  • Runtime folder means the folder in which the output file is opened from. To extract the files in the same folder as the output use the %RUNTIME% keyword.
  • %UNPACK% – Will be replace with the folder in which the last extracted project file has been unpacked into. If there was no file extracted until that point then it will be replaced with runtime folder.
  • %TEMP% – Will be replaced with System Temporary folder. Example: C:Documents and SettingsAdministratorLocal SettingsTemp
  • %WIN% – Will be replaced with Windows folder. Example: C:Windows
  • %SYSTEM% – Will be replaced with the systems folder Example: C:WindowsSystem32
  • %USER% – Will be replaced with the current user’s Documents and Settings folder. Example: C:Documents and SettingsAdministrator (if the user name is Administrator. Also you can get the user name by using the %USERNAME% keyword)
  • %DESKTOP% – Will be replaced with the desktop folder for the current user. Example: C:Documents and SettingsAdministratorDesktop
  • %PROGRAMFILES% – Will be replaced with current Program Files folder. Example: C:Program Files
  • %USERNAME% – Will be replaced with the current name of the current logged on user.

File Compression

Specify if you want the selected file to be compressed and also select the compression level for this file only.

File Execution

Specify if you want this file to be opened (executed) after it has been unpacked. If not an EXE the file will be opened using it’s associated application.

Start priority allows you to modify the file’s position in the list. This will change the order in which the files will be unpacked and opened.

Also you can specify here if you want the file to be started visible or hidden. This refers to the window of the application or of the associated application.

Command Argument allows you to specify a command line argument to be used when launching the selected executable file. This can be a user custom value or a special value like %OUTPUTCMD% that send as command argument for the current file the command argument that the output file received.

%OUTPUTCMD% – will get replaced with the command argument that the output file received when it was opened. This value is automatically set for the first .EXE file in the project.

%RUNTIME% – will get replaced with the folder from which the output file has been opened

%OUTPUTNAME% – will be replaced with the name of the output file (including the extension)

%UNPACK% – will be replaced with the folder path to which the current file will be unpacked.

You can also use here the other special keywords.

The rest of the controls (options) present on this window are the same as their Global equivalents, except for the fact that they affect a single file.

NOTE – KEYBOARD SHORTCUTS: You can use keyboard shortcuts like the DELETE key to remove a file or a command from the project, INSERT to add a new file to the project, SPACE to see a file’s options or to edit a command, CTRL+S to save the project, CTRL+O to load a project, CTRL+N to start a new project and F5 to Bind.

GLOBAL OPTIONS

Compression

  • Compress – If checked the files are compressed before they are binded and decompressed after they are unpacked. This option may slow the binding process and the execution of the output but will decrease the size of the output.

  • Level of Compression – Specify how much do you want the files in the project to be compressed. Choosing a higher value results in smaller output and increased unpacking time, while choosing a smaller value results in increased speed while but a larger output file. This option will not directly modify project options but if modified it will change individual options for each file accordingly.

Cryptography

  • Encryption of files protects your files from unauthorized unpacking. It changes the data contained in added files (based on a key phrase) when they are added to the output file, so they do not resemble the original files.

    The files are decrypted to their original form when they are unpacked. This means that the files inside the output file are not the same as the original files, the size is the same but the content is different. NOTE: If you encrypt files, the unpacking process may take longer to unpack files in the project. This depends on the number of files and size of files.

  • Key Phrase – This string is a set of characters, that you can input yourself or you can press the Generate button to automatically generate random characters, used like a password to encrypt the files in the project and then decrypt them when they are unpacked. Try to use long, non-repetitive strings.

Unpack Files

Unpacked files are those files added in the project and then unpacked when the output is launched according to the options set.

  • Unpack temporary files in – select the folder in which the output file will first unpack the binded files, upon execution of the output file. You can use the following keywords to specify special folders:
    • Runtime folder means the folder in which the output file is opened from. To extract the files in the same folder as the output use the %RUNTIME% keyword.
    • %UNPACK% – Will be replace with the folder in which the last extracted project file has been unpacked into. If there was no file extracted until that point then it will be replaced with runtime folder.
    • %TEMP% – Will be replaced with System Temporary folder. Example: C:Documents and SettingsAdministratorLocal SettingsTemp
    • %WIN% – Will be replaced with Windows folder. Example: C:Windows
    • %SYSTEM% – Will be replaced with the systems folder Example: C:WindowsSystem32
    • %USER% – Will be replaced with the current user’s Documents and Settings folder. Example: C:Documents and SettingsAdministrator (if the user name is Administrator. Also you can get the user name by using the %USERNAME% keyword)
    • %DESKTOP% – Will be replaced with the desktop folder for the current user. Example: C:Documents and SettingsAdministratorDesktop
    • %PROGRAMFILES% – Will be replaced with current Program Files folder. Example: C:Program Files
    • %USERNAME% – Will be replaced with the current name of the current logged on user.
    • You can also use here any of the other special keywords.
  • Protect Unpack Folder – If selected this option enables the unpacker to protect the folder in which the files are extracted (unpacked). The folder is then protected against read and write meaning that it can’t be opened until all executables in the project have exit.
  • NOTE:

    If you activate the protection for the unpack folder, the contents (all files) of the unpack folder(s) will be deleted at runtime for each file which has this option turned on. Also if the contents of the unpack folder can’t be deleted the output file will exit without any warning or error. This is to ensure the protection of your files against hack attempts.

  • NOTE:

    With the Protection for the temporary folder active the non-executable files (music, video, docs etc.) added to the project will not be opened by their default application as it has no access to the protected folder. This does not apply to dlls needed by executables in the project or to executables.

  • Name of the unpacked files – specify the name of the unpacked files. If the name is „temp“, the files will be unpacked with the names „temp1“, „temp2″…. If you check keep originals file names the files will be unpacked and run bearing their original names.

  • NOTE:

    If you have dlls or other resource files in your project needed by an executables you should keep their original names otherwise they will not be recognized and used by file that needs them.

Output File

  • Use default icon – specifies to use the default icon even if a icon was specified or the first file in the list has an icon (is a exe a dll or a ico file).

  • Take version info – Tells the program to take the version information from project file with the specified priority number (starting from 0) in the list if it is an executable file(.exe) and add it to the output file so that the output resembles as much as possible on the surface with the selected executable, bearing the fact that the icon from that file can also be taken.
  • Do CRC32 check on output file – When activated, before unpacking files the output file will check to see if the file has been modified in any way. If the the output file has been modified suggesting a hack attempt the output will exit with any warning or error message before unpacking the files.
  • Self delete output – If this option is selected the output exe file will delete itself after it has been opened once. So once all executable files in the project close the output will close too and then delete itself.

Progress Window

Progress Window – If this option is enabled a progress window will be shown when the unpacker will be unpacking/decompressing the project files. This will show the progress for each file and also the total progress.

NOTE: The Progress Window will not show the download progress of URL Files, just the progress for unpacking of files packed into the output file.

You can set the title and a subtitle for the progress window and you can select whether you want the Abort button to be visible, thus allowing users to abort the unpacking.

Password Protection

Password protection – if password on RUN is selected the password will be requested when the output executable is launched and when you unpack (start the output with /unpack / command line or when files are extracted (unpacked) using nBinder), before unpacking the files. If password on UNPACK is selected the password will be requested only when the output is being unpacked either using command line /unpack or by using nBinder. The password is encrypted. If the inserted password is not right the output file will exit without any warning.

Start Mode

Start Mode – Specifies whether the dialogs of the binded files (exe’s) are visible or not or if the files are opened (started) or not. It works for both executables or other multimedia files as well. For example if all hidden is selected the default player for the added multimedia player will be started in hidden mode as will any executable in the project if through file option you haven’t selected otherwise. This option will not affect in direct mode the output, this will only change the individual execute and visible options for each file.

Start Options

  • Start Order – select the order in which the temporary files will be executed after they are unpacked: All at once or start in order, one at a time. This only applies to executable files (.exe). If start in Order is specified then the unpacker will wait for the EXEs to exist before it opens the next files.

  • Open this file types – Specify what file types (from the project list) should be opened using their default application when the output runs.You can also select which file should be opened by selecting the execute option from the individual file options.

Temporary Removal

  • Delete temp files after all EXEs close – If checked the temporary files will be deleted from the directory in which they were unpacked when the output file was executed, before the output file closes, after all executables in the project have closed. This options should be selected for executables and their resource files.

  • Delete temp files on next boot- If checked all temporary files will be deleted at the next boot. This option should be selected for other files than executables and their resources. For example if you have movies or sounds or documents, files that need to stay around for use and cannot be deleted after they have been unpacked.

  • NOTE:

    You can choose not to delete the unpacked files by not selecting any of the 2 options.

If you have any questions or troubles with the options in nBinder you can post questions or any suggestion or idea you may have to www.NKProds.com/forum or you can contact us.

v5.5.1 – 14 May 2008 (maintenance update)

  • Added drag and drop for files and folders. Files and folders can now be dragged onto the window to be added
  • Added drag and drop for project items. Items can now be move in the project by dragging them to the desired location
  • Added Undo(CTRL+Z) and Redo (CTRL + Y) capabilities (only for adding, removing and moving items)
  • Added argument commands for building projects (/build /load= /quiet /test)
  • Updated the interface. New buttons, rearranged controls, options dialog before binding
  • Added new options for Controls: Any/All, True/False
  • Added Terminate Process command
  • Added Process exists condition
  • Added new keyboard shortcuts
  • Improved the icon extraction algorithm
  • Can now specify the file from which to take version information without needing it to be part of the project
  • CRC32 check and self delete options are now stored in projects
  • Added a new keyword ( %ACTIVEWND% ) for the name of the active window
  • Added nKeys to distribution
  • Added new example projects
  • All keyboard shortcuts now work when the list is not selected too
  • Rename existing output file to .bak
  • Fixed problem with the Progress Window not displaying the progress for the first file
  • Improved the way the unpacker handles conditions and controls
  • Improved some of the existing commands and conditions
  • In the File Contains condition you can now specify the offset from where to read
  • Added option in installer to check for updates on each run
  • Various small fixes and improvements
  • Purchased NBINDER.COM domain

v5.5 – 18 Aug 2007 (feature update)

  • Added new project items, Controls: Jump to line, Wait for, Sleep if, Abort if…
  • nBinder now supports conditional run, repetitive sequences, scheduled events and more project control based on predefined conditions
  • IMPORTANT: Now files are unpacked when they are encountered in the project and not before as in previous versions
  • Added new keywords: %UNPACK% (for the last unpack folder), %DATE%, %TIME%, %USERNAME%, %USER%, %DESKTOP% (more…)
  • Added new commands: Create File, Register DLL/ActiveX/OLE, and Window Management (Activate/Close/Hide Window)
  • Added new keyboard shortcuts (F5 to bind, CTRL+S to save project, CTRL+O to open project, CTRL+N to create a new project)
  • Easier to move project items (files, commands, controls) in the project
  • Added Move Up and Move Down buttons in the right click menu of all project item
  • Now file priority in File Options is relative to all project items, not just to file
  • Improved unpacker’s performance, security, error and memory handling (consumption)
  • Improved nBinder’s performance and memory handling
  • Improved project management
  • The title and subtitle for the Progress Window can now contain more characters
  • Fixed a problem regarding registry commands
  • Fixed nBinder’s Reset To default button for Global Settings
  • Fixed the crash on multiple consecutive binds
  • Fixed a problem that affected unpack paths (which contained \)
  • Various other small fixes and improvements
  • This version is compatible with projects created with nBinder 5.1.x but not vice-versa.

v5.1.1 – 12 May 2007 (maintenance update)

  • Small interface fixes
  • Fixed the automatic updater
  • Improved stability

v5.1.0 – 24 March 2007 (feature update)

  • Added Progress window option for unpacker (Global options)
  • Can now add commands in relative order to files
  • Redesigned and improved the interface
  • Can add commands in the main list
  • Fixed some issues regarding the unpacker
  • Can now bind projects that only contain commands
  • nBinder now remembers saved projects

v5.0.2 – 28 February 2007 (maintenance update)

  • Commands can now be edited
  • Redesign Commands interface
  • Added Rename/Move command
  • Improved the way the unpacker handles commands
  • Fixed problem with option file size check
  • Improved nBinder’s stability and memory handling
  • Decreased unpacker size

v5.0.1 – 15 January 2007 (maintenance update)

  • Fixed icon extraction from .ico files
  • Removed default version information from PRO version unpacker
  • Small updater fix

v5.0 – 15 January 2007 (feature update)

  • Can now add an unlimited number of files to a project. The 200 files limitations has been removed.
  • New license for nBinder oriented to company development (single developer license and company license)
  • New Files and Registry related Commands. (9 new commands)
  • Added Encryption for files.
  • Improved icon handling. It now extracts all icons in a selected icon group and adds them to the output file.
  • Add new option to set command line arguments for each file in the project. Also supports special values.
  • Improved unpack folderfiles protection.
  • Improved Check for Updates feature.
  • Greatly improved security for the unpacker (the output file). Files are now more secure. Better encryption is available.
  • Greatly improved stability and the way nBinder handles files.
  • Reviewed code and improved speed, security and error handling, also increasing stability and reliability.
  • Reviewed and improved the user interface.
  • Fixed reported bugs. (working dir and some interface issues).

v4.0 – 15 March 2006

  • New design and interface.
  • Added possibility to add URL files
  • Can now set individual options for each files
  • Supports directory structures
  • Better protection for unpack folder
  • New Add option (Folder) to add files along with sub folders, maintaining directory structures
  • Can now enhance project by adding complex commands
  • Can now bind 200 files
  • Can now save and load complex projects along with individual file options and commands.
  • Can now take version info from any executable in the list.
  • Improved unpacker security and memory usage.
  • Bug fixed: It now opens files in their current unpack folder.

  • Many more bug fixes and improvements

nBinder 5.5 LIMITED

Copyright NK Prods SRL 2007 Web: http://www.nkprods.com (EN) http://nkprods.com/forum (EN)

Contact: [email protected] [email protected]

NK PRODS SRL will be referred to in this documents as NKProds and NKPRODS.
The software nBinder /nBinder PRO / nBinder limited will be referred to in this document as nBinder, „this software“ or „the software“.

Use this software on your own risk. The author is not responsible for any damage of any kind produced to users and to any computer. The author is not responsible for any damage of any kind produced by files or other data created with this software.

YOU ARE NOT ALLOWED TO USE NBINDER FOR ANY COMMERCIAL PURPOSE OF ANY WAY, UNLESS YOU OWN A COMPANY LICENSE PURCHASED BY YOURSELF OR YOUR COMPANY / BOSS / ASSOCIATE. YOU ARE NOT ALLOWED TO USE NBINDER IF YOU DON’T AGREE AND ACCEPT THIS DISCLAIMER / LICENSE.

NOTE: NBINDER MAY CONNECT FROM TIME TO TIME THROUGH THE INTERNET (ONLY ON USER REQUEST) TO WWW.NKPRODS.COM TO CHECK FOR UPDATES. DURING THIS PROCESS IT WILL DOWNLOAD A SMALL FILE THAT CONTAINS THE NUMBER OF THE LATEST VERSION AVAILABLE ON THE INTERNET TO CHECK IF THE VERSION AVAILABLE ON THE INTERNET IS NEWER THAN THE VERSION INSTALLED ON THE USER’S COMPUTER. nCLEANER WILL NOT SEND ANY DATA FROM THE USER’S COMPUTER.

NKPRODS IS WILLING TO LICENSE THE ENCLOSED SOFTWARE (AS WELL AS UPDATES NKPRODS MAY FURNISH YOU FROM TIME TO TIME) AND DOCUMENTATION (THE “ SOFTWARE „) TO YOU (“ YOU „) ONLY ON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS IN THIS SOFTWARE LICENSE AGREEMENT (THE “ AGREEMENT „). IF YOU ARE AN EMPLOYEE OR AGENT OF A COMPANY (THE “ COMPANY „) AND ARE ENTERING INTO THIS AGREEMENT TO OBTAIN THE SOFTWARE FOR USE BY THE COMPANY FOR ITS OWN BUSINESS PURPOSES, YOU HEREBY AGREE THAT YOU ENTER INTO THIS AGREEMENT ON BEHALF OF THE COMPANY AND THAT YOU HAVE THE AUTHORITY TO BIND THE COMPANY TO THE TERMS AND CONDITIONS OF THIS AGREEMENT.

USE THIS SOFTWARE ON YOUR OWN RISK. THE AUTHOR IS NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KIND PRODUCED TO THE USERS AND/OR THEIR COMPUTERS AND SYSTEM OR TO OTHER COMPUTERS AND SYSTEMS. THE AUTHOR IS NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KIND PRODUCED BY THIS SOFTWARE AND IT’S USE.

LICENSE . Subject to the terms and conditions of this Agreement, NKProds hereby grants You a limited, non-exclusive, personal license to install, perform and use the Software, in machine-readable form only, solely for Your own personal or internal business use on a single computer in accordance with the instructions, specifications and documentation provided with the Software. You may make one (1) copy of the Software only for backup and archival purposes (if you own a single user license from NKProds) or multiple copies for your employees (if you own a company license from NKPRODS) , provided that You reproduce all copyright and other proprietary notices that are on the original copy of the Software and agree and respect this license agreement and the license type that you have purchased from NKPRODS, as described here: www.nkprods.com/buy/ and below.

This software is not free. This software is not freeware, this software is shareware. In order to use this software in commercial purposes or in any other activity that implies profit of any kind you must first buy a company license from NKProds.
To buy a license for this software you must go to www.nkprods.com/buy/. Licenses bought from anywhere else are not valid and are illegal.

You are NOT allowed to install and use this software („nBinder“) unless you have bought a license from NKProds.

If you have a license make sure you have the license that is right for you. There are 2 types of licenses available. The single user license allows only one user, the user that has bought the license, to use nBinder PRO. Buy a single user license if you are the only person that will use the product (nBinder PRO). The second license available is the company license that allows more than one users to use the product (nBinder PRO) as long as they are all employees of the company that has bought the license for the product (nBinder PRO).

This software is meant only for educational and utility purposes like binding your resource files to your executable.
You are not allowed to use this software for any kind of illegal purposes like binding viruses or other mallwares like creating mallware and other illegal purposes. We are not responsible for any type of files or other data created using nBinder. We are not responsible for any damage of any kind produced or determined in any way by any type of files or other data created with nBinder.

You may not modify, rent, sell or transfer any part of the Software except as provided in this Agreement, and you agree to prevent unauthorized copying of the Software. You may not reverse engineer, disassemble, decompile, or translate the Software.

You may not sublicense or permit simultaneous use of the Software by more than one user unless you have bought a valid company license from NKPRODS.

YOU CAN USE THIS SOFTWARE TO CREATE COMERCIAL APPLICATIONS ONLY IF YOU HAVE BOUGHT A LICENSE OF THIS SOFTWARE AND YOU ARE NOT USING THIS SOFTWARE AS LIMITED AND HAVE BOUGHT THE PRO VERSION FROM NKPRODS. YOU CAN MAKE COPIES OF THIS SOFTWARE ONLY IF YOU HAVE BOUGHT AND YOU OWN A COMPANY LICENSE FROM NKPRODS. YOU CAN ONLY SHARE COPIES WITH EMPLOIEES OF THE COMPANY THAT YOU REPRESENTED WHEN YOU BOUGHT A COMPANY LICENSE FROM NKPRODS. YOU ARE NOT ALLOWED TO DISTRIBUTE THIS SOFTWARE THROUGH THE INTERNET. YOU CAN DISTRIBUTE THIS SOFTWARE ONLY BY INTRANET OR ANY OTHER TYPE OF LOCAL NETWORK.

OWNERSHIP OF SOFTWARE AND COPYRIGHTS.

Title to all copies of the Software remains with NKPRODS. The Software is copyrighted and protected by the laws of the Romanian country and other countries, and international treaty provisions. You may not remove any copyright notices from the Software. The author may make changes to the Software, or to items referenced therein, at any time without notice, but is not obligated to support or update the Software. Except as otherwise expressly provided, The author grants no express or implied right under The author’s patents, copyrights, trademarks, or other intellectual property rights.

EXCLUSION OF WARRANTIES. THE SOFTWARE IS PROVIDED „AS IS“ WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE.

LIMITATION OF LIABILITY. IN NO EVENT SHALL THE AUTHOR OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF THE AUTHOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION.

* LICENSE . Subject to the terms and conditions of this Agreement, NKProds hereby grants You a limited, non-exclusive, personal license to install, perform and use the Software, in machine-readable form only, solely for Your own personal or internal business use on a single computer in accordance with the instructions, specifications and documentation provided with the Software. You may make one (1) copy of the Software only for backup and archival purposes, provided that You reproduce all copyright and other proprietary notices that are on the original copy of the Software.

* RESTRICTIONS . You may not use or copy the Software, or any copy thereof, in whole or in part, except as expressly provided in this Agreement. You may not modify, reproduce, create derivative works of, distribute, sell, resell, lend, loan, lease, license, sublicense or transfer (except as expressly provided herein) the Software or any portion thereof. You may not reverse engineer, disassemble, decompile, or translate the Software, or otherwise attempt to derive the source code of the Software, or authorize any third party to do any of the foregoing, except to the extent allowed under any applicable law. The Software contains trade secrets, trademarks, patents, and copyrights owned by NKProds, and You shall maintain the Software in confidence. You shall not allow any access to or use of the Software by anyone other than You, or Your employees or agents, and any such use must be consistent with the terms, conditions and restrictions set forth in this Agreement. You may not transfer the limited license granted to anyone andor anything. You will allow accesss to Your employees or agents only if you have a company license bought from NKProds. It is forbidden to use nBinder PRO if you haven’t bought a license for nBinder PRO or if a representative of the company where you are employed hasn’t bought a company license for nBinder PRO from www.nkprods.com/buy/. It is forbidden to use nBinder PRO if nBinder PRO has been registered using a single user license that has been bought by someone else and not by you.

If you have bought a single user license it is forbidden to use nBinder PRO to gain any kind of profit for or from any organization, company or any other type of association, composed or represented by more that a single (1) person.

* LICENSE FEES . You are responsible for paying BNKProds or the authorized reseler from whom you purchased the Software, the specified fees, and applicable taxes, for the license of the Software.

* OWNERSHIP . The Software is licensed, not sold, to You for Your use only under the terms of this Agreement, and NKProds reserve all rights not expressly granted to You. You own the media, if any, on which the Software is recorded, but NKProds retains ownership of all copies of the Software („nBinder“) itself.

* UPDATES/SUPPORT . From time to time, NKProds may make new releases, revisions or enhancement to the Software (“ Updates „) available to You. Your purchase must be recorded with NKProds either through product registration or a direct purchase through www.nkprods.com for You to be notified of Updates.
NKProds may send YOU emails notifing you of offers, updates, new version and so on.

* TERM/TERMINATION . The Agreement becomes effective when You agree to the terms and conditions of this Agreement by opening, installing, using, accessing or manipulating the Software (the “ Effective Date „), and this Agreement will terminate immediately upon notice to You if You materially breach any term or condition of this Agreement. You agree upon termination to promptly destroy the Software and all copies thereof.

* LIMITED. If you are using the Software in LIMITED mode (if you are using the Limited version), and are authorized to do so, then You shall have a license under this Agreement to use the Software for the specified activities and purposes indicated in the materials accompany the Software („nBinder LIMITED“) and in the documents on www.nkprods.com , solely for the purpose of evaluating the Software to determine whether to purchase an ongoing license to the Software. While using nBinder LIMITED, the Software is provided to You „as is“ and Your use is entirely at Your own risk. Also during this time you are not allowed to use the LIMITED version in any commercial purposes.

* WARRANTY DISCLAIMER . THE SOFTWARE IS PROVIDED TO YOU „AS IS“ AND NKPRODS AND ITS SUPPLIERS AND LICENSORS EXPRESSLY DISCLAIM ANY AND ALL WARRANTIES AND REPRESENTATIONS OF ANY KIND WITH REGARD TO ANY SUBJECT MATTER OF THIS AGREEMENT, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF NON-INFRINGEMENT, TITLE, FITNESS FOR A PARTICULAR PURPOSE, FUNCTIONALITY OR MERCHANTILIABILITY, WHETHER EXPRESS, IMPLIED OR STATUTORY. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY NKPRODS, DISTRIBUTORS, DEALERS, OR AGENTS SHALL INCREASE THE SCOPE OF THE ABOVE WARRANTIES OR CREATE ANY NEW WARRANTIES .

* LIMITATION OF REMEDIES . REGARDLESS OF WHETHER ANY REMEDY SET FORTH HEREIN FAILS OF ITS ESSENTIAL PURPOSE OR OTHERWISE, IN NO EVENT WILL NKPRODS OR ITS SUPPLIERS AND ASSOCIATES BE LIABLE TO YOU OR TO ANY THIRD PARTY FOR ANY LOST PROFITS, LOST DATA, INTERRUPTION OF BUSINESS, OR OTHER SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE OR ANY DATA SUPPLIED THEREWITH, EVEN IF NKPRODS OR IT’S ASSOCIATES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGES AND WHETHER OR NOT SUCH LOSS OR DAMAGES ARE FORESEEABLE. IN NO EVENT SHALL THE LIABILITY OF NKPRODS EXCEED THE TOTAL AMOUNT RECEIVED BY NKPRODS FROM YOU UNDER THIS AGREEMENT .

* FOR nBinder ® SOFTWARE ONLY: YOUR ACKNOWLEDGMENTS. The nBinder Software includes features that enable users to create or hide software that can do damage on systems and users. The authors of nBinder’s are not responsible in any way for any data (files, code, software etc.) created using nBinder.

* HIGH RISK ACTIVITY . You acknowledge and agree that the Software is not intended for use with any high risk or strict liability activity, including, without limitation, air or space travel, technical building or structural design, power plant design or operation, life support or emergency medical operations or uses, and that NKProd makes no warranty and shall have no liability arising from any use of the Software in any high risk or strict liability activities.

NOTE: THE ICONS IN THIS SOFTWARE DO NOT BELONG TO NKPRODS. THEY BELONG TO THEIR CREATORS OR OWNERS.