Dragon NaturallySpeaking 12 Administrator Guide - Nuance

Chapter 10: Working with Custom commands
Using the MyCommands Protection
Utility
In Dragon Professional and higher, when you export a set of custom Text-and-Graphics, Step-by-
Step, Custom Command, and/or Advanced Scripting commands into a .dat file, you can set
the permissions on that file so that after an end-user imports them, that end-user can dictate the
commands but cannot view their source code, edit their source code, or re-export the commands.
As a result, the integrity of the commands remains intact.
To set the permissions on the .dat file of commands to protect the commands in this way:
1. Make a backup copy of the unprotected .dat file and store it in a secure location. You later use
that file to edit the commands, because once you protect the .dat file that you are distributing,
you cannot make the file available for editing again.
2. Select Start > Run and enter cmd into the Run dialog box.
3. Change directories to (In Windows XP):\Documents and
Settings\\Application
Data\Nuance\NaturallySpeaking12\Custom\
See Dragon file structure for information on default location on Windows 7 and other operating
systems.
4. Enter the following on the command line:
protectcmds.exe []
5. Once you press return, after an end-user imports these commands, if that end-user attempts to
edit any of them, the following message indicates that the commands cannot be edited:
The command was protected by .
Please contact for more information.
In the Command Browser, the same message appears as the Preview Content in Script mode.
Once you have protected the file, you can put it into the Data Distribution directory for distribution
to multiple User Profiles. For more information about distributing saved commands,
refer to Creating the Data Distribution Directory, then refer to one of the following topics about
distributing commands to multiple User Profiles by either:
n Using the Data Distribution Tool (Data Distribution Tool: Adding and removing custom
commands)
n Using the nsadmin command line tool (nsadmin: Adding custom commands)
345