This can be caused by several things:
Windows assigns drive letters to the mass storage devices like CmStick that are following directly to the fix drives (harddisk, CDROM). If the next drive letter is already occupied by a network drive, the mass storage device can not be listed.
To recognize the CmStick as drive you need to reassign your network drives to letters that do not conflict with the mass storage devices. Please choose drive letters at the end of the alphabet.
Possibly the access to mass storage devices is restricted on your system. To check this please run CmDust and contact our support team.
Please check, whether your browser is in "offline-mode". In the Internet Explorer this can be changed in the "File" menu.
To be able to reset your CmStick password you need the CmStick Master-Password. A detailed description can be found on the page CodeMeter and the passwords.
Please register your CmStick on my.codemeter.com and request the Master-Password for your CmStick (specify the serial number) via e-mail to email@example.com. You will receive the CmStick Master-Password after your data was checked via e-mail to your registered e-mail address. Please allow us some time, since the check is done manually.
The backup is done automatically in a given interval (24 hours for default). Additionally you can do an additional backup at any time. Open the WebAdmin, change to the page "Content" and select the "Backup/Restore" area. Select the CmStick you want to backup and click on "Backup now". The backup files can normally be found on "%Program Files%/CodeMeter/Backup". The file name contains the serial number of the CmStick and the date and time of the backup.
The automatic backup is done for every connected CmStick when the set time interval (24 hours for default) was reached. The check for doing a backup is done every hour. The first backup is done earliest one hour after the start of the CodeMeter Runtime Server.
This is only useful for CmSticks with memory (CmStick/M). To assign a fix drive letter
Using the right mouse button you can open the menu for changing the drive letter. This does not work on all operating systems and only with newer versions of CmStick hardware. If you specify your operating system and your CmStick hardware version (can be found in the WebAdmin) the support team can check this.
To uninstall CodeMeter from your computer, please do the following.
If you have registered your CmStick on
before it was lost, you can lock your CmStick within the my.codemeter portal.
If the CmStick is connecting to a CodeMeter Timeserver, it is automatically locked and can not be used anymore.
The licenses are bound to the CmStick and therefore they are also lost. But of course you can ask your software vendor, maybe he will give you a special price for a replacement.
Windows 95 and Windows NT do not support USB. Therefore it is not possible to use CmSticks on these operating systems. In general it is possible to use CodeMeter protected software on these operating systems if the software supports usage of CodeMeter in network. Please ask your software vendor whether this is supported.
The support of Windows NT was suspended with version 4.0. If you want to use CodeMeter on Windows NT please use an older version, e.g. version 3.30b
Microsoft has finished the extended support phase for Windows 98 and Windows ME. Therefore these operating systems are not supported for CodeMeter, too. The last CodeMeter version that supports Windows 98 and Windows ME was 3.10. If you want to use this old version please contact our CodeMeter Support Team.
The restore of previously backuped data should be done as follows:
On transfering licenses to your CmStick e.g. after shopping in the CodeMeter Onlineshop the last Certified Time in your CmStick must not be older than seven days for security reasons. If the last Certified Time is too old, CodeMeter automatically gets a time update from one of the CodeMeter timeservers. A detailed description of the time handling can be found at CodeMeter and the Time.
The only way to adjust the Box Time is to get a Certified Time Update from one of the CodeMeter Timeservers. This can be triggered manually in the WebAdmin on the page Content by pressing "Update". A detailed description of the time handling can be found at CodeMeter and the Time.
On SuSe 10.1 the hotplug mechanism is per default configured not to recognize mass storage devices automatically. You can change this default behaviour by changing the fstab to enable the automatic detection again. Please do the following:
The communication inbetween protected applications and the CodeMeter Runtime Server is done using TCP/IP. Per default port 22350 is used. You may need to allow communication on port 22350 for TCP and UDP if a firewall is running on your system. If your firewall filters the traffic using the application name you need to unblock CodeMeter.exe (%Programme%\CodeMeter\Runtime\bin). Please notice that some antivirus programs also contain firewall functionality.
If you want to allow other computers to use the licenses on your CmStick, you need to configure the machine that should host the licenses (server). The clients that want to use the licenses normally need not be configured.Configuration of the server:
Up from now the licenses stored in CmSticks at the server can be used also by other clients if the protected application is designed to support CodeMeter in network.
If updating the Certified Time or the CmStick firmware does not work, normally the connection to the server can not be established. In the network of companies often a network proxy is used. This also needs to be configured for CodeMeter. If you want to know, whether a proxy is used in your network, please ask your administrator. Alternatively you can try to read it out by yourself from your internet browser. In the Internet Explorer use the menu Tools - Internet Options - Connections - LAN Settings - Proxy server - Advanced. Please write down the configured proxy e.g. "proxy.mycompany.com" with "3128" or "192.168.146.200" with "8080".
Now updating the Certified Time and the CmStick firmware should work.
This is a warning message of your operating system that occurs for all disks which have less than 200MB free space. You can disable this message, but in this case you also get no message if your system drive runs out of space. To disable this message you may do the following: