MKS Homepage v9.5 

MKS Toolkit is the leader in UNIX to Windows user productivity, platform interoperability, and application portability.

MKS Inc.
12701 Fair Lakes Circle,
Suite 350
Fairfax VA



MKS Toolkit 9.5

MKS Toolkit is the leader in UNIX to Window scripting, connectivity, and application migration. Enhancements found in the 9.5 release include support for the release version of Microsoft Visual Studio 2012 and updated operating system compatibility.

Microsoft Visual Studio 2012 Support

MKS Toolkit 9.5 is compatible with the final release versions of Microsoft Visual Studio 2012 and Microsoft Visual C++ 2012 Express (also known as Visual C++ 11.0 Express).

An updated version of the UNIX to Windows Porting Guide with instructions on using the Visual Studio 2012 and Visual C++ 2012 Express IDEs has been included with MKS Toolkit 9.5.

Full Windows 8 and Windows Server 2012 Compatibility

MKS Toolkit 9.5 is the official MKS Toolkit release for compatibility with Microsoft Windows 8 and Microsoft Windows Server 2012.

Updated Secure Shell Utilities

The Secure Shell utilities (secsh, secshd, scp, secsh-add, secsh-keygen, secsh-keyscan, secsh-keysign) have been updated based on OpenSSH 6.0p1.

Updated openssh/openssl in NuTCRACKER Platform

The MKS Toolkit 9.5 version of the NuTCRACKER Platform now features updated versions of the openssh and openssl libraries. OpenSSH has been updated to version 6.0p1. OpenSSL has been updated to version 1.0.1c.

Updated MKS X/Server

MKS Toolkit for Interoperability and MKS Toolkit for Enterprise Developers now include MKS X/Server 8.6. See the MKS X/Server 8.6 Release Notes for more information.


MKS Toolkit for Developers and MKS Toolkit for Interoperability now include the former standalone MKS LEX & YACC product. MKS LEX & YACC has been updated to include compatibility with Microsoft Visual Studio 2008, 2010, and 2012. It has also been updated to include compatibility with all operating systems supported by MKS Toolkit.

MKS Toolkit for Professional Developers and MKS Toolkit for Enterprise Developers continue to include the same UNIX-compatible versions of lex and yacc that were included in previous releases.

New Features in Previous Releases

Hardware and Software Requirements

MKS Toolkit products do not have any particular hardware requirements. Any machine that is sufficient to run the underlying operating system is sufficient. All MKS Toolkit products run on Windows systems with Intel 32-bit, Itanium (IA64), or Extended Architecture 64-bit (x64) processors.

MKS Toolkit products have the following software requirements:

  • Platforms. You can install all MKS Toolkit products on:
    • Windows 2000
    • Windows XP
    • Windows Server 2003
    • Windows Server 2003 R2
    • Windows Vista
    • Windows XP x64 Edition
    • Windows Server 2003 for Itanium-based Systems
    • Windows Server 2003 x64 Edition
    • Windows Server 2003 R2 x64 Edition
    • Windows Vista x64
    • Windows Server 2008 (32-bit and x64)
    • Windows Server 2008 for Itanium-based Systems
    • Windows 7
    • Windows 7 x64
    • Windows Server 2008 R2 (32-bit and x64)
    • Windows Server 2008 R2 for Itanium-based Systems
    • Windows 8
    • Windows 8 x64
    • Windows Server 2012 x64

  • FAT File Systems. It is not currently possible to adequately secure an MKS Toolkit installation on a FAT file system. Therefore, on Windows 2000/XP/2003/Vista/7/8 systems, we recommend installing MKS Toolkit on an NTFS file system.

  • Compilers. The MKS Toolkit development products work with various compilers and compilation environments. The "Using Languages" chapter of the MKS Toolkit UNIX to Windows Porting Guide describes how to use these MKS Toolkit products with C, C++, and Fortran.

    MKS Toolkit for Developers supports the following x86 compilers:
    • Microsoft Visual C++ 6.0, 7.0, 7.1, 8.0, 9.0, 10.0, or 11.0 (as a separate product or as part of Microsoft Visual Studio or the Windows SDK)
    • Windows SDK
    • Visual C++ 2012 Express (also known as Visual C++ 11.0 Express)
    • Visual C++ 2010 Express (also known as Visual C++ 10.0 Express)
    • Visual C++ 2008 Express (also known as Visual C++ 9.0 Express)
    • Visual C++ 2005 Express (requires Microsoft Platform SDK or Windows SDK)
    • Microsoft C++ 2003 Toolkit (requires Microsoft Platform SDK or Windows SDK)
    • Intel C++ 8.x or 9.x (requires Microsoft Platform SDK or Windows SDK)
    • GCC 3.3.1, as provided in the MKS Toolkit Resource Kit

    In addition, MKS Toolkit for Professional Developers and MKS Toolkit for Enterprise Developers also support the following compilation environments:
    • both versions of the Standard Template Library
    • the Absoft Pro Fortran f90/f77 compiler, versions 5.0, 6.0, 7.0, 8.0, 9.0, and 10.0. (

    MKS Toolkit for Enterprise Developers 64-bit Edition supports the following additional 64-bit compilers:
    • Visual C++ from Microsoft Visual Studio 2012
    • Visual C++ from Microsoft Visual Studio 2010 (Note: Ultimate edition or Windows SDK is required for IA64 compiler)
    • Visual C++ from Microsoft Visual Studio 2008 (Note: Team edition or Windows SDK is required for IA64 compiler)
    • Visual C++ from Microsoft Visual Studio 2005 (Note: Team edition or Windows SDK is required for IA64 compiler)
    • Microsoft Platform SDK or Windows SDK Compiler
    • Intel C++ 8.x or 9.x (requires Microsoft Platform SDK or Windows SDK)

    Note: As of Windows Vista, the Microsoft Platform SDK was renamed to the Windows SDK. References to the Microsoft Platform SDK also refer to the Windows SDK.

    For those 64-bit compilers that require the Microsoft Platform SDK or Windows SDK (that is, the Intel C++ 8.x or 9.x compilers), the version of the SDK required depends upon your system's processor. For those processors with IA64 architecture, you can use any version of the SDK from February 2003 or later, such as the one available for download at For Extended Architecture processors, you must use Build 1289 or later of the SDK.

    When installing MKS Toolkit, you are asked to specify the default compiler to be used with the development utilities provided. Should you decide to change your default compiler from your original choice, you should do the following:

    1. Close all MKS Toolkit shells and utilities.

    2. Select Add or Remove Programs from the Windows control panel applet.

    3. Select MKS Toolkit from the list of programs and click the Change button. The MKS Toolkit installer begins.

    4. When the Program Maintenance dialog appears, check the Modify option and click the Next > button.

    5. As the installer continues with the process of modifying your MKS Toolkit configuration, you are given the opportunity to select a new default compiler as well as to change other installer options.

  • Deployment. When deploying NuTCRACKER Platform applications built with Visual Studio 2005, Windows Installer 3.1 (or higher) must be installed on each target machine to ensure that all parts of the NuTCRACKER Platform are installed correctly.

  • Windows Task Scheduler. The MKS Toolkit Scheduler, the command-line scheduling utilities (at, batch, crontab, and wts) require Internet Explorer 4 (or later) and the Windows Task Scheduler. On most Windows operating systems, these are already installed.

    Alternatively, you can download Internet Explorer and its add-ons from

Installing MKS Toolkit

If you have MKS Toolkit 7.5 or earlier, or if you have a previous version of MKS NuTCRACKER Professional, we recommend that you uninstall it, or install MKS Toolkit 9.5 on another machine.

When installing on a machine with SCO XVision Eclipse installed, you should uninstall it before installing MKS Toolkit 9.5.

Note: If you have MKS Toolkit for Interoperability or MKS Toolkit for Enterprise Developers installed on a Japanese machine and uninstall XVision Eclipse, MKS X/Server is not installed with a standard English license for these products. Contact Customer Support to request the proper license.

When installing MKS Toolkit on a 64-bit machine, you must first uninstall any previously installed MKS Toolkit releases (version 8.6 and earlier).

When installing MKS Toolkit for Enterprise Developers 64-bit Edition on any platform, you must first uninstall any existing MKS Toolkit installation.

When installing MKS Toolkit, you must install from an account with local or domain administrator privileges. You do not need to be an Administrator, but your login ID must be a member of the local or domain Windows Administrators group before you can install.

All MKS Toolkit products share a common installer. If you are installing from a CD, insert the MKS Toolkit distribution CD; the installer should start automatically. If you are installing from an electronic distribution, run the self-extracting installer.

To install MKS Toolkit, click the Install Toolkit button and follow the instructions on the dialogs that appear.

Note: You should turn off all virus protection software before installing MKS Toolkit. Such software can sometimes cause the installation to be interrupted and rolled back. Once you have installed MKS Toolkit, you can turn virus protection back on.

For step-by-step installation instructions and an installation FAQ, see

Silent and Administrative Installations

For step-by-step installation instructions and information on administrative and silent installations for MKS Toolkit see

Additional Components on the MKS Toolkit CD

The MKS Toolkit CD also includes several items that are not installed as part of the normal installation procedure. These are:

  • The samples directory. This directory contains a collection of sample source code for use with MKS Toolkit for Professional Developers and MKS Toolkit for Enterprise Developers. Though they can be modified and compiled for 64-bit Windows systems, these samples were designed and tested on 32-bit Windows platforms using the MKS Toolkit porting and migration products.

    These samples include binaries for cpp, gawk, gmake, install, and the groff suite of utilities.

  • The redist directory. This directory contains a collection of utilities and drivers that may be needed to get full use out of MKS products. This includes the recent versions of the Jet Database driver, Microsoft Data Access Components (MDAC), Microsoft Management Console (MMC) and Adobe® Acrobat® Reader.

Uninstalling MKS Toolkit

Uninstalling MKS Toolkit 8.x or 9.x

To uninstall MKS Toolkit, use the following procedure:

  1. From the Control Panel run Add/Remove Programs.

  2. Remove MKS Toolkit 8.x or MKS Toolkit 9.x, as appropriate.

  3. Remove SCO XVision Eclipse (or MKS X/Server). (This is only necessary if one of the two X Server packages was installed. This X Server is normally only installed with MKS Toolkit for Interoperability, MKS Toolkit for Enterprise Developers, and MKS Toolkit for Enterprise Developers 64-bit Edition.)

You must reboot your system before reinstalling MKS Toolkit.

Uninstalling Previous Versions of MKS Toolkit

To uninstall a 7.x version of MKS Toolkit, run the TKUninstall utility found in your system directory (you can find your system directory with the windir -s command).

Alternatively, you can uninstall the components manually with the following procedure:

  1. From the Control Panel, run Add/Remove Programs.

  2. Remove, in order, each of the following (if present):
      MKS Evaluation Guide
      MKS Toolkit 7.x
      MKS Platform Components 7.x

You must reboot your system before reinstalling MKS Toolkit.

Activating MKS Toolkit

MKS Toolkit version 9.5 is copy protected and requires activation against the MKS Activation Server (located at to operate. The software is node fixed (that is, it is attached to a single computer system) and user counted (the Named Authenticated Users must be specified and are enforced). This activation takes place after installation, so you need to plan your product rollout so you do not find yourself with unactivated software on users' machines.

  • If your site has many different serial numbers and, in the past, have used only one of them on many machines, you will either need to contact MKS Sales to have these serial numbers bundled under one serial number or use each of these serial numbers as they were purchased (that is, install a single license on no more than one machine; install a five user license installed on no more than five machines with one user each, and so forth).

  • If you have used a single serial number to download the new version of MKS Toolkit during the update process and rolled out to many machines, you will need to specify all serial numbers that need to be updated as each serial number has a notion of the version number requested and will not activate unless it has been updated.

  • If you have some serial numbers under a valid PCS Support contract and some that are not, and they have not been retired, you will be unable to update any of your serial numbers until you bring all licenses in use under a valid PCS, or retire unused licenses permanently, or submit to MKS Personnel in writing, you will not update said serial numbers to any later version, unless you purchase an update license at a later date.

Further information about MKS Toolkit 9.5 activation and the information which is sent to and stored on MKS computers can be found here:

You can view the MKS Product Activation FAQ at

For questions related to sales issues, please e-mail:

For questions related to support issues, please email:

We at MKS sincerely value and appreciate your business and want to do everything we can to ensure a successful implementation of our MKS products.

Known Issues

The following known issues exist in MKS Toolkit 9.5:

  • Last Access Timestamps. On Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2, the default file system behavior for NTFS is to not update the "last access" timestamp on files when you access them, and this will be seen in NuTCRACKER applications where the st_atime field in the stat structure appears to be not be updated as you access files. While many applications will not have an issue with this behavior, some may have problems. You can restore the old behavior with the Windows command:
    	fsutil behavior set disablelastaccess 0
    A reboot will be required after making this change. The current setting of this flag can be queried with the command:
    	fsutil behavior query disablelastaccess
  • NuTCRACKER Platform Applications and MKS X/Server. Currently, there are some issues with NuTCRACKER Platform applications which use OpenGL to access MKS X/Server features such as Direct Rendering and Overlay Planes on systems using an NVIDIA video card. For details, see the MKS X/Server 8.5 Patch 1 release notes.

  • Short Path Names with Visual Studio 2008. The Microsoft Visual Studio 2008 IDE sometimes crashes when building a Win32 console application with the Additional Library Directories value set to a short path (for example, C:\PROGRA~1\MKSTOO~1\lib). We recommend always using long path names (C:\Program Files\MKS Toolkit\lib in this situation. Microsoft is aware of this issue and has it registered as C++ case number SRX071206601300. A fix is expected in Visual Studio 2008 Patch 1 from Microsoft, scheduled for April or May 2008.

  • Installing MKS X/Server. When installing MKS Toolkit for Interoperability or MKS Toolkit for Enterprise Developers, you may receive a message asking you to uninstall XVision and reboot before you install MKS X/Server. You can install MKS X/Server from the CD autoplay screen. It cannot be installed by performing a Modify or Repair operation on MKS Toolkit.

  • MIT Kerberos for Windows 3.0.0. When MIT Kerberos for Windows 3.0.0 is installed on a system, it appears to break SSPI, causing credential passing errors. We recommend uninstalling this software on systems running MKS Toolkit and rebooting.

  • Security ID Warning. When the TK_NTSECURITYINFO_OFF environment variable is set, it turns off all security related features. This includes the ability to look up user and group IDs. As a result, utilities such as id, chown, and chgrp that depend upon user and group IDs will not work properly when this variable is set.

  • _NutConf(). MKS Toolkit 8.6 added large file support and as a result inadvertently broke backward binary compatibility for applications linked against previous import libraries. With 8.6p2 and 8.7 we added an environment variable to supplement the _NuTConf() to revert the behavior of the runtime to pre-8.6 form such that read beyond a 2G boundary without large file support enabled will not result in an error. set NUT_DISABLE_FULL_LFS_SEMANTICS=1 to do the equivalent of _NutConf(_NC_SET_FULL_LFS_SEMANTICS, FALSE) without the need to recompile or relink your application.

  • Path Name Issue. If you install the Microsoft Platform SDK or Windows SDK on a 64-bit machine, and your PATH environment variable contains elements that begin with C:\Program files (x86), the script for setting up the 64-bit build environment included with that SDK does not work. There are two possible solutions:

    • Modify the PATH environment variable in the system environment to substitute the short path variant of the folder name Program Files (x86). The short path variant is normally C:\progra~2. You can use dir /x from a command window to be sure.

    • Modify the file setenv.bat in the root directory of the SDK tree. Find the section that looks like this:
              REM ---------------------------------------------
              REM Patch path to put Bin\WinNT\NT4 in path ahead
              REM of NT5 tools that don't run on NT4
              REM ---------------------------------------------
              For /F "delims=;" %%i IN ('Cmd /c Ver') DO (
                IF "%%i"=="Windows NT Version 4.0" (
                  Set Path=%MSSdk%\Bin\WinNT\NT4;%Path%
                  Goto Finish
              Goto Finish
      and remove or comment out the line that begins Set Path=.

  • The uil Compiler. The uil compiler used with some Motif applications can generate uid files that are compatible with either 32 or 64-bit platforms. A single uid file cannot be used for both situations. This is consistent with the documented behavior of the uil compiler. The uil compiler normally will try to figure out whether to build the 32-bit or 64-bit version based on your build environment. If the TARGET_CPU environment variable is set to either "AMD64" or "IA64", the uil compiler builds a 64-bit compatible uid file; otherwise, it builds a 32-bit compatible uid file. The TARGET_CPU environment variable is set as appropriate for all 64-bit NuTCRACKER build environments launched from the Start menu.

    The uid file that is generated by the uil compiler in this release is not guaranteed to be portable to other 64-bit UNIX platforms.

Customer Support

When reporting a problem, you will need certain information about your product, which you can find on the Support Information tab of the MKS Toolkit Control Panel Applet.

Contact MKS Toolkit customer support at:

Web Site:
Online Request Form:
Telephone: +1-703-803-7660
Fax: +1-703-803-3344

Additional MKS Toolkit Resources

There are several other sources for additional information about our MKS Toolkit products.

We have general product information, including technical specifications, detailed utility listings, and datasheets at:

We offer a resource kit including example scripts, additional utilities, more tutorials, and a wide variety of other useful information at:

We have several additional articles, tutorials, and white papers about using features of the MKS Toolkit at:

Through the years, we have accumulated a lot of technical details about the MKS Toolkit products and have put this information in a searchable database at:

Our customers commonly ask certain questions. These questions and their answers are in our Frequently Asked Questions pages at:

Known installation issues are listed at:

Fixed Problems

Several problems were fixed in MKS Toolkit 9.5. These are listed at:

Fixed Problems in Previous Releases