Skip navigation
All Places > Licensing and Installation > Blog > 2013 > June

The information you get with the default settings for Windows Task Manager only scratch the surface of the information available. In this weeks Tip of the Week, I'll show you how to get more.


You may not be aware, but when you select the Processes tab in Windows Task Manager you get access to an additional option under the View pull down menu called 'Select Columns'. When you select that option, you get a dialog box that allows you to pick and chose from a number of additional items that will appear under a new column in Task Manager.



Ever wish you could tell where the executable was for a program you see running under Image Name? Select the Command Line column. This will allow you to see the full path name to the program. (Click on image to make it larger).




Once selected, the column will remain visible until you de-select it, so it's already set for the next time. Experiment with this and other values until you find a configuration you like.


That's all for now. Tune in next week for another useful tip!


Ken Foster

Mentor Graphics Customer Support

I need to have Oracle v11. installed in order to install MSS 11.3. How can I tell what version I currently have installed?



One way of determining the version of Oracle installed is to open the SQL Plus window. The version is displayed at the top of the window. There is no need launch SQL Plus to see the version.



Go to:

Start > Programs > Oracle > Application Development > SQL Plus

I have always found the Windows %PATH% variable difficult to read.  There are normally multiple lines and the ";" separator is difficult to see.


It turns out I am not alone; yesterday a colleague sent me the following command to report the contents of that variable (or any other) from a DOS window in a simple to read format.


     echo %PATH:;=&echo.%


I predict this command will be appearing on a post-it-note near your screen very soon!

Mentor Standard Licensing v2013_2 is now available for download on SupportNet. This release contains a number of important benefits and key changes detailed below.



Reasons to update your license server:


  • Update from FlexNet v11.10.0.3 to v11.11.1.1. As applications that build with Mentor Standard Licensing (MSL) v2013_2 ship, they will require license servers running or newer. It's advisable to update your license servers in advance of these product releases. You do not need to update anything if you are using Mobile Compute (uncounted) licenses.
  • Support added for AIX v6.1, Windows 8 and Windows Server 2012. Note: This applies to the licensing software only. For support information regarding specific product releases, please refer to the System Requirements on SupportNet. 
  • Support added for Consistent Network Device Naming (em0, em1, p1s3, etc...) on Linux
  • Stability improvements
  • Numerous defect fixes





Key Changes:


  • Red Hat EL 4 and SuSe SLES 9 are no longer supported. MSL v2013_2 will not run on these platforms.
  • Support for some hardware keys (dongles) has been  discontinued. If you are using a hardware key as your  license server's hostid, you may need to request a replacement key.  Please refer to for more information. As of MSL v2013_2, only the Aladdin USB FLEXid 9- key is supported. This is the teal-colored USB key.



Information about downloading MSL v2013_2 can be found in TechNote MG66951.*


*Requires SupportNet login.

You may have run into cases where the User Account Control (UAC) prompts multiple times during the execution of a batch (.bat) script. With executables (.exe) and non-batch (.bat) file types you can right-click and select "Run as Administrator", to force the UAC to elevate the execution of the program. However, this approach doesn't work with batch scripts.


See below for a simple VBScript which can serve as a "wrapper" script, to force the UAC to prompt before running the intended batch script. This results in the entire script running with elevated permissions, which means no more additional UAC prompts. Just update the value of the filePath variable on the second line to point to the full path of the script, and save the file with a .vbs extension (VBScript). The script is now ready to run (just double-click it).



Dim filePath

filePath = "F:\installs\myScript.bat"


Set objShell = CreateObject("Shell.Application")

objShell.ShellExecute "cmd.exe", "/c " & filePath, "", "runas", 1