NLMs

Included are two NLMs per NetWare platform, IS_SRVx0.NLM (x=3 for NW3x; x=4 for NW4x; x=5 for NW5x/6x) and CVMONE.NLM.

Together, these NLMs provide the following services:

• NCP Packet Trails, i.e. File Open/Close Requests
• NLM Inter-Dependencies, i.e. of NLMs that are loaded
• Amount of RAM each NLM is using
• Zero Privilege Helpdesk functions where the CVMONE.NLM enables non-administrator accounts to change NDS information

If you require these services, the NLMs must be loaded.

You need only load CVMONE.NLM as it will auto-load IS_SRVx0.NLM.

If you are using SofTrack (software metering product) you will notice it uses the same IS_SRVx0.NLM. The latest version of IS_SRVx0.NLM is included in the product download of DSRAZOR.

TRIAL MODE

When the product is used without a valid token (i.e. license) the result is each list is limited to the first 3 items. Indication of this truncation is provided in the list as well as the name of the unlicensed server.

DESIGNER

The Designer Module (DSRDES.EXE) requires a Windows-based workstation. The Designer will operate with or without a network present.

The Designer includes some wizards (assistants) that help in selections (such as choosing an NDS object class) that do require a network connection to operate.

RUNTIME

The Runtime Module (DSRRUN.EXE) requires a Windows-based workstation with Novell’s Client32 (3.21 or higher for Win9x and 4.71 or higher for NT/2000). To operate fully, the Runtime requires a valid token.

To view the Runtime’s Build, simply run any solution (i.e. "DSRRUN SolutionName") and click on the main window’s caption bar icon (top left corner) and click on "About this Application".

If the Runtime does not find a valid token, it will DEFAULT to TRIAL MODE.

If the Runtime is used with any command line parameters the CONSOLE will be presented.

TOKEN

Token files (*.TKN) are date coded. The date code indicates which "builds" (versions) of the Runtime will use that token. For instance, if a token is date coded for January 10, 2003, then any Runtime built before that date will accept that token.

When you receive a token file, it will be date coded ahead one year. Because of this, you will receive the next year’s worth of enhancements with no further purchase!

Site license tokens include the number of servers they will authorize, this number must match or exceed the total number of servers in your network. Tree license tokens are also available and include the number of servers they will authorize, this number must match or exceed the total number of servers in your NDS tree.  

Token files are installed by merely copying them to the directory you installed the product to or where the Runtime is kept.

Tokens do not require the NLMs and the NLMs do not require a token.