Products

 Services

 Support

 Company

 Partners

 Contact

Ten Minute Tutor Support               

TMT Windows Platform FAQs:

• How is the Windows product licensed?
  

• My C: drive is full, so I tried to install in D: but I get an error about a missing license file.
  
  
• When I try to select the Supported Constructs topic in the VHDL tutorial, I get an error message Bad record type
  
  

TMT Unix Platform FAQs:

• What's the difference between the demo and full TMT products?
  
  
• How is the product licensed?
  
  
• Can I merge TMT license keys with other EDA vendor keys?
  
  
• Why do I need these 'app-default' files?
  
  
• Where can I get the 'gunzip' tool?

• I set all environment variables but TMT doesn't see them
  
  
• I start the FLEXlm server and get:
     license manager: can't initialize: No SERVER lines in license file"
  
  
• OK, my FLEXlm server is up, but all I see is "Unknown Feature TMT"
  
  
• TMT gives me an error " Unable to find Locale Database"
  
  
• There is no VHDL tool option under Preferences->Tool Location
  
  
• TMT gives me an error "$HOME/.tmt_vhdl: File does not exist."
  
  
• On my HP workstation TMT gives me an error
  "ERROR couldn't open /usr/lib/dld.sl errno:000000002"
  
  
• On Solaris 2.6 TMT crashes and logs me out of CDE.
  

TMT uses the FLEXlm licensing technology from Globetrotter Software, Inc. On Windows, we offer two types of licensing, node-locked and dongle-protected.

Node-locked TMT means that the software is licensed to the ethernet networking card in your PC. In order to receive a license file from us you will need to provide us with the number. Here's how to determine it.

Dongle-based licensing is a little more expensive and means that we ship you a hardware dongle which installs on the parallel port of your PC. This dongle has a unique serial number to which we lock the TMT binary. Many people prefer dongle-based protection because it allows them to use the software on any PC simply by moving the dongle.

TMT is expecting to find the license.dat file in C:\flexlm . If you wish to install the product on another drive the license file MUST still be located on on the C: drive. There is a workaround involving a change to your autoexec.bat file, but we don't recommend this.

This is a known bug. It can be corrected by downloading the latest version of TMT. Alternatively, you can contact us directly for instructions on how to obtain the exact update file you need.

When you download from our FTP site you get the entire product fileset. The license keys you receive initially, enable a demonstrational subset of TMT language topics. If you purchase the product you will receive full license keys, which automatically enable every topic.

TMT is licensed using the FLEXlm licensing technology from Globetrotter Software, Inc. Two levels of licensing are supported, demo and full.

To keep demonstration product installs as simple as possible, demo keys do NOT require a FLEXlm license server to be setup. The demonstration product licenses itself directly from the demo license file for a limited period of time.

Full license keys DO require that you run a FLEXlm license server. Complete instructions for doing this are included in the TMT Installation instructions.

In either case the licenses must be held in a file called license.dat in the TMT home directory (see README files) and pointed to by an environment variable called LM_LICENSE_FILE.

Here's an example of each type of license key:

First, a full license:

SERVER sylvan 80715a1b 7781 
DAEMON whdldmon /tools/tmt/bin/whdldmon 
FEATURE TMT whdldmon 1.100 30-mar-59 10 3BE8B091E585DOG9DC6E "" 
FEATURE vlog_intro whdldmon 1.100 30-mar-59 10 B24870F1D2D222ADADA5 ""

Notice that SERVER and DAEMON lines are specified (as well as FEATURE). These are required for a FLEXlm license server to be setup.

And now a demo license file:

FEATURE TMT whdldmon 1.200 01-oct-99 0 2BB8F071AFB52BFB4030 "" DEMO 
FEATURE tmt_demo whdldmon 1.200 01-oct-99 0 2B588761CC979859c295 "" DEMO

Notice here, only the FEATURE lines are specified and the word DEMO is specified at the end of each FEATURE line... Demo keys WON'T work with a FLEXlm license server.

Since many EDA vendors use the FLEXlm license technology you are free to merge your TMT full license keys into another EDA vendor's license file. Please follow normal FLEXlm guidelines for this.

Unix-based "X" windowing environments (OpenWindows or Motif in this case) are extremely flexible and configurable: colors, gadgets, window locations etc. etc. Proper programming guidelines for X-windows recommend hard-coding only the absolute essential resources and leaving the rest for end-user configuration. Default values for these are usually specified in an application defaults (or app-defaults) file. Again by recommendation this file is stored in a standard directory:

/usr/lib/X11/app-defaults/TMT <-- under Motif
/usr/openwin/lib/app-defaults/TMT <-- under OpenWindows

We ship two sets of app-defaults, one for TMT and the other for HyperHelp, both of which are needed.

In order to reduce the time/size of a TMT download, we compress the product using 'gzip'. Most Unix sites have this high-performance utility already. If your site does not, you can download the source to both the 'gzip' and 'gunzip' tools from:  

ftp://prep.ai.mit.edu/pub/gnu/

This one's common... Typically, you set the environment variables in one shell but NOT in the shell where you invoke TMT. We recommend declaring all TMT environment variables in your .cshrc (or equiv.) file.

Our demo licenses DO NOT use a FLEXlm license server. They are tied to the license file directly. You have tried to run demo keys through a FLEXlm license server (see "How is the product licensed").

To remedy the situation try this:

1. Shut down the FLEXlm license server (if you started a unique one). Typically this means executing the lmdown command. See FLEXlm documentation or the TMT README file for specifics.

remove the demo licenses keys from the license file and do an lmreread (if you merged our keys into another EDA vendors FLEXlm server).

2. Make sure the demo keys are in a file called license.dat in the $TMTHOME directory. Be sure the file is formatted correctly. If you received the keys via email on a PC for example, make sure the file has no PC-style end-of-line characters etc.
The easiest way to do this on a Sun is by running the SunOS command dos2unix (On our Sparc workstations: /usr/bin/dos2unix) on the license file. The equivalent tool on HP: /usr/bin/dos2ux

3. Then, simply make sure all the environment variables are set correctly

setenv TMTHOME /tmt 
setenv HHHOME $TMTHOME 
setenv XLIBI18N_PATH $HHHOME/lib 
setenv LM_LICENSE_FILE $TMTHOME/license.dat set path=($path $TMTHOME/bin)

This process is fully described in the README.demo file included with the product. You probably followed the README.product instructions by mistake.

This is usually caused by a corrupted (incorrectly edited?) license file. Carefully check any changes or additions YOU have made to this file. Another common source of corruption is when people receive their email on a PC. We send out license key files via email and often, when users transfer their key-file to Unix it will still have PC-style end-of-line characters embedded within it. To avoid this make sure the PC file is correctly translated to Unix ASCII. Perhaps the easiest way to do this is by running the SunOS command /usr/bin/dos2unix or the HPUX equivalent: /usr/bin/dos2ux

This problem relates to the interface language specified (English, Japanese, Norwegian etc.) for your workstation. The error message usually looks like this:

Error: Unable to find Locale Database
Error: Try setting XNLSPATH environment variable

This error is triggered if there is no nls library installed for your workstation (typically found at /usr/lib/X11/nls). See your sysadmin for help on this one. We provide an nls lib if you need one. To use ours:

setenv XNLSPATH $TMTHOME/lib/X11/nls

Typically, this problem happens when a user switches from an older release of TMT to a newer one.

Another way it can manifest itself is via the following error message:

$HOME/.tmt_vhdl: File does not exist.

Fortunately, the fix is easy:

There are some files created in your $HOME directory that all begin with ".tmt". If you remove these files (exit TMT first, of course), and then re-invoke TMT, the VHDL selection and file should appear in the Preferences->Tool Location dialog.

If they do not you'll have to go one step deeper. The problem is that the $HOME/.tmtrc file does not have a vhdl entry. This file is automatically created when you first invoke TMT and is from then on updated whenever any of its' variables change. For example, a typical $HOME/.tmtrc file contains:

TMT.workDir: TMTWORKDIR 
TMT.notebook: /home/sylvan/joan 
TMT.resume: true 
TMT.sound: false 
TMT.template: true 
TMT.course: VHDL - Introduction 
TMT.topic: Bit string 
TMT.tools: "editor","verilog","vhdl" 
TMT.editorPath: /usr/ucb/vi 
TMT.verilogPath: verilog 
TMT.vhdlPath: /usr/local/bin/VHDL

If removing the .tmtrc file doesn't fix your problem you can edit the .tmtrc file and insert the vhdlPath line plus add vhdl to the tools variable, using the example above for the exact syntax.

We plan a permanent fix for this in our next release.

The TMT executable was built under HPUX10.20. It will not run on previous releases (specifically 9.X) because of non-backward compatible OS changes involving the dynamic linker. Unfortunately this has turned out to be a larger project than it initially looked. Right now we do not have a schedule to do the necessary full port to HP-UX 9.X due primarily to a lack of user interest in TMT on that platform.

We do support SunOS, Solaris, Win 200/NT/98, if you have access to any of those machines.

This problem has been fixed by a patch (T105633-38)from Sun Microsystems. You may download this patch (5MB) from here.