CopyMinder Knowledge Base

Browse By Category:
Look Up Error Number:

Glossary   |   Contact Us

Running CMInstall twice kills my original .cm.ini file

Views: 1642
Rating: 40
Rate It:
I have created a .cm.ini file that contains some parameters that I want pre-set.  I ship this .cm.ini file with my product.
When CMInstall is run, it copies these .cm.ini file parameters into the correct directory.  However, if I re-run CMInstall, it loses my parameters.

If no /S option is specified on the CMInstall command line, CMInstall copies the .cm.ini file from the CMInstall directory into the user data area (e.g. C:\Documents and Settings\All Users\ABC\MyProduct\cm) and adds the ProductKey= line.  It then creates a simple .cm.ini file in the program directory.  If CMInstall is run again from the same directory as the program directory then it will copy this simple file into the user data area.

You can avoid the problem by using separate directories for CMInstall and the protected program.

If the protected program is to be installed into "C:\Program Files\MyProgram", you should put CMInstall.exe, the original .cm file and the original .cm.ini file into a "C:\Program Files\MyProgram\CMInstall" directory )for example) and run CMInstall from there using:
    C:\Program Files\MyProgram\CMInstall\CMInstall.exe  /K  /P C:\Program Files\MyProgram.

Alternatively, you could use the /S option in CMInstall to point to a directory containg the original .cm and .cm.ini files.
More Help

If this article did not help you to solve your problem, please use the menu at the top of the page to browse or search more articles, or to contact our support team.

Others in this Category
articleI don't seem to have a CD-ROM with the CopyMinder software on it
articleMy computer hangs when installing the CopyMinder SDK
articleHow do I create a Trial Only installation?
articleHow do I find the .cm and .cm.log files?
articleWhy is a Product Key not in a Report I have produced?

© 2024 Microcosm Ltd.

Valid XHTML 1.0 Valid CSS 2.0