PTC MKS Toolkit Homepage v10.1 

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

PTC Inc.
140 Kendrick Street,
Needham, MA
02494 USA

  +1 781 370 5000

  +1 781 370 6000


PTC MKS Toolkit 10.1

PTC MKS Toolkit is the leader in UNIX to Window scripting, connectivity, and application migration.

Your attention please: The process for contacting Technical Support has changed. You may contact PTC Technical Support in the same way as all other PTC products and take advantage of all that the PTC eSupport Portal has to offer. Please visit for more information about contact phone numbers, web forms for problem submission and access to the knowledgebase.

POSIX 1003.1-2008 compliant runtime library.

Many new and reworked libc functions to achieve POSIX 1003.1-2008 compliance are included in PTC MKS Toolkit version 10.1.

The following libc functions have been added:

asprintf_l, aswprintf_l, atoll, bsd_strsignal, btowc_l, dprintf, dprintf_l, duplocale, fmemopen, fparseln, fprintf_l, freelocale, fscanf_l, fwide, fwscanf_l, getdelim, getline, getopt_long, imaxabs, imaxdiv, isalnum_l, isalpha_l, isblank_l, iscntrl_l, isdigit_l, isgraph_l, isleadbyte_l, islower_l, isprint_l, ispunct_l, isspace_l, isupper_l, iswalnum_l, iswalpha_l, iswblank, iswblank_l, iswcntrl_l, iswctype_l, iswdigit_l, iswgraph_l, iswlower_l, iswprint_l, iswpunct_l, iswspace_l, iswupper_l, iswxdigit_l, isxdigit_l, localeconv_l, mblen_l, mbrlen_l, mbrtowc_l, mbsinit_l, mbsnrtowcs, mbsnrtowcs_l, mbsrtowcs_l, mbstowcs_l, mbtowc_l, newlocale, nl_langinfo_l, offtime, offtime_r, open_memstream, open_wmemstream, printf_l, querylocale, scanf_l, sl_add, sl_delete, sl_find, sl_free, sl_init, snprintf_l, snprintf_ss, sprintf_l, sscanf_l, strcoll_l, strftime_l, strlcat, strlcpy, strndup, strptime_l, strsignal, strtod_l, strtof, strtof_l, strtoimax, strtoimax_l, strtold, strtold_l, strtoll_l, strtoull_l, strtoumax, strtoumax_l, strxfrm_l, swscanf_l, timelocal, tolower_l, toupper_l, towctrans_l, towlower_l, towupper_l, uselocale, vasprintf_l, vaswprintf_l, vdprintf, vdprintf_l, vfprintf_l, vfscanf, vfscanf_l, vfwprintf_l, vfwscanf, vfwscanf_l, vprintf_l, vscanf_l, vsnprintf_l, vsnprintf_ss, vsprintf_l, vsscanf_l, vswscanf_l, vwprintf, vwprintf_l, vwscanf, vwscanf_l, wcrtomb_l, wcscasecmp, wcscasecmp_l, wcscoll_l, wcsftime_l, wcslcat, wcslcpy, wcsncasecmp, wcsncasecmp_l, wcsnrtombs, wcsnrtombs_l, wcsrtombs_l, wcstod_l, wcstof, wcstof_l, wcstoimax, wcstoimax_l, wcstol_l, wcstold, wcstold_l, wcstoll_l, wcstombs_l, wcstoq_l, wcstoul_l, wcstoull_l, wcstoumax, wcstoumax_l, wcstouq_l, wcswidth, wcswidth_l, wcsxfrm_l, wctob_l, wctomb_l, wctrans_l, wctype_l, wcwidth, wcwidth_l, wprintf_l, wscanf_l,

The following libc functions have modified behavior:

querylocale setlocale, tzset

The following libm functions have been added:

exp2, exp2f, fdim, fdimf, fmax, fmaxf, fmin, fminf, log2, log2f, llrint, llrintf, llround, llroundf, lrint, lrintf, lround, lroundf, nan, nanf, round, roundf, tgamma, tgammaf

PTC NuTCRACKER prefers a UNIX style language string e.g. en_US.ISO8859-1 or ja_JP.UTF-8, but it will continue to accept the strings accepted by previous versions (e.g. en-us.CP1250). Please see the xlocale man page for more details. Every effort has been given to backward compatibility both at the source and binary levels. None the less PTC strongly recommends a recompile against PTC NuTCRACKER 10.1 headers out of an abundance of caution. PTC also recomends extra testing around language specifics as there is a lot of new code but also a lot of new automated tests were added. PTC continues to test against the POSIX.1 test suite and has the same results in PTC NuTCRACKER 10.1 as in PTC NuTCRACKER 10.0p1.

LLVM/Clang compiler is now included

The LLVM clang/clang++ compiler version 3.8 is included with PTC MKS Toolkit for Professional Developers and PTC MKS Toolkit for Enterprise Developers (both 32 and 64 bit editions) that replaces the GCC that used to be provided in the PTC MKS Toolkit Resource Kit. Features include:

  • Clang/clang++ supports many of the same GCC extensions that gcc also supported.
  • Clang/clang++ supports a much more modern version of the C++ language.
  • The clang/clang++ compiler will generate 64-bit code. (-m64)
  • Full CodeView debugging information is generated by the compiler, suitable for use with any recent Microsoft debugger.
For more details, please see the the UNIX to Windows Porting Guide.

Note: clang does not use the normal "ncenv" wrappers. It will compile for the PTC NuTCRACKER target i386-pc-mks-msvc with no specific environment. There is however a requirement to have a linker installed. Linkers ship with the Microsoft Compilers and not the Windows SDKs. Thus a fairly modern linker from Visual Studio 2017 or 2015 would be the best choice.

Visual Studio 2017

PTC MKS Toolkit 10.1 is compatible with Microsoft Visual Studio 2017.

New plugins for Visual Studio IDE have been written and are installed with PTC MKS Toolkit 10.1. These plugins replace the manual instructions in previous releases. PTC still recommends the use of UNIX makefiles to reduce porting time and maximize compatibility with UNIX. The UNIX to Windows Porting Guide has been updated with new instructions for using the Visual Studio 2017 and earlier IDEs with these new plugins, but the older instructions remain.

Visual C++ 2017 is closer to c++ 14 compatibility than previous versions; while it is not 100% compatible it is close enough to use a shared C++ headers and runtime with our own clang++ (described earler). The C++ runtime library benefits from the new POSIX.1 2008 C runtime library work and is thus fully thread aware and passes about 90% of the LLVM C++ runtime library tests using Microsoft C++ and about 96% when using clang++.

OpenSSL updated to version 1.0.2

OpenSSL in both The NuTCRACKER Platform and the utilities are updated to 1.0.2.

Windows Vista support dropped.

Due to the fact that Vista does not have support for SHA256 code signing certificates, and an inability to purchase SHA1 code signing certificates, support for Windows Vista has been dropped (both 32 and 64-bit editions).

Windows Server 2003 support dropped.

With this release, support for Windows Server 2003 has been dropped (both 32 and 64-bit editions).

New Features in Previous Releases

Hardware and Software Requirements

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

PTC MKS Toolkit products have the following software requirements:

  • Platforms. You can install all PTC MKS Toolkit products on:
    • Windows 7
    • Windows 7 x64
    • Windows Server 2008 R2 (32-bit and x64)
    • Windows 8
    • Windows 8 x64
    • Windows Server 2012 x64
    • Windows 10
    • Windows 10 x64
    • Windows Server 2016 x64

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

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

    PTC MKS Toolkit for Developers supports the following x86 compilers:
    • Microsoft Visual C++ 6.0, 7.0, 7.1, 8.0, 9.0, 10.0, 11.0, 12.0, 14.0 or 14.1 (as a separate product or as part of Microsoft Visual Studio or the Windows SDK or Microsoft Build Tools 2017)
    • Windows SDK
    • Visual C++ 2013 Express (also known as Visual C++ 12.0 Express)
    • 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)
    • Intel C++ 8.x, 9.x, 10.x, 2011, 2013, or 2013 SP1 (requires Microsoft Platform SDK or Windows SDK)
    • LLVM 3.8.0, as provided by the PTC MKS Toolkit installer

    In addition, PTC MKS Toolkit for Professional Developers and PTC 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, 10, and 13.0. (

    PTC MKS Toolkit for Enterprise Developers 64-bit Edition supports the following additional 64-bit compilers:
    • Visual C++ from Microsoft Visual Studio 2017 (Microsoft compiler only)
    • Visual C++ from Microsoft Visual Studio 2015
    • Visual C++ from Microsoft Visual Studio 2013
    • Visual C++ from Microsoft Visual Studio 2012
    • Visual C++ from Microsoft Visual Studio 2010
    • Visual C++ from Microsoft Visual Studio 2008
    • Visual C++ from Microsoft Visual Studio 2005
    • Microsoft Platform SDK or Windows SDK Compiler
    • Intel C++ 8.x or 9.x (requires Microsoft Platform SDK or Windows SDK), 2015, 2016
    • LLVM 3.8.0, as provided by the PTC MKS Toolkit installer

    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.

    Note: Support for Microsoft Visual C++ 6.0, 7.0, and 7.1 are deprecated in this release. For PTC MKS Toolkit for Professional Developers and PTC MKS Toolkit for Enterprise Developers, the VC6 linker is no longer able to link executables that include debug information when the executable is linked against many the static libraries that are included with the product.

    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 Extended Architecture processors, you must use Build 1289 or later of the SDK.

    When installing PTC 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, or if you install new compilers or new instances of compilers, or if a compiler instance upgrade leaves you unable to use that compiler, you should do the following:

    1. Close all PTC MKS Toolkit shells and utilities.

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

    3. Select PTC MKS Toolkit from the list of programs and click the Change button. The PTC 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 PTC 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 PTC 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 PTC 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 PTC MKS Toolkit 10.1 on another machine.

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

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

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

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

When installing PTC 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 PTC MKS Toolkit products share a common installer. If you are installing from a CD, insert the PTC MKS Toolkit distribution CD; the installer should start automatically. If you are installing from an electronic distribution, run the self-extracting installer.

To install PTC 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 PTC MKS Toolkit. Such software can sometimes cause the installation to be interrupted and rolled back. Once you have installed PTC 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 PTC MKS Toolkit see

Patch Installation

If you are installing a patch for PTC X/Server and PTC MKS Toolkit on the same machine, PTC recommends applying the PTC MKS Toolkit patch to update the shared components before applying the PTC X/Server patch. It is not an error to install the PTC XServer patch first, but you may be asked to reboot after patch install is complete. Installing PTC MKS Toolkit first will reduce the risk that a reboot will be needed.

For step-by-step patch installation instruction for PTC X/Server see

Additional Components on the PTC MKS Toolkit CD

The PTC 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 PTC MKS Toolkit for Professional Developers and PTC 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 PTC MKS Toolkit porting and migration products.

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

Uninstalling PTC MKS Toolkit

Uninstalling PTC MKS Toolkit 8.x, 9.x or 10.x

To uninstall PTC MKS Toolkit, use the following procedure:

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

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

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

You must reboot your system before reinstalling PTC MKS Toolkit.

Uninstalling Previous Versions of PTC 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 PTC MKS Toolkit.

Activating PTC MKS Toolkit

PTC MKS Toolkit version 10.1 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 PTC 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 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 PTC MKS Toolkit 10.1 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 log in to the PTC eSupport Portal:

We, the PTC MKS Toolkit Product Team, sincerely value and appreciate your business and want to do everything we can to ensure a successful implementation of our products.

Known Issues

The following known issues exist in PTC MKS Toolkit 10.1:

  • Windows 10 console windows Windows 10 console windows have been revamped. Please see the developer blob posting. As a consequence the default settings enable control characters such as ^F for a find window. These can interfere with PTC MKS Toolkit programs. The current implementation of these console windows does not provide an API to disable this capability on a temporary basis. Thus, for example, ^F in vi will not cause the next screenful of text, but bring up the console window find dialog. Fortunately this new capability can be disabled using the console window properties dialog.

  • OpenSSL cert.pem no longer delivered OpenSSL stopped delivering a root certificates file some releases ago. PTC MKS Toolkit has followed suit and no longer delivers a $ROOTDIR/etc/openssl/cert.pem as of verion 10. As a consequence OpenSSL tools will complain about the missing file until one is created. Please read the comments in $ROOTDIR/etc/openssl/ This script is offered to provide an up to date root certificates file derived from the Mozilla Root Certificate store which is a trusted source of root certifictaes for many. Alternatively your orginization may have a set of trusted root certificates that you can convert and store as $ROOTDIR/etc/openssl/cert.pem. If the cert.pem file is missing, certain features of web.exe, smtpmail.exe, openssl.exe and snetnews.exe will not work as expected.

  • [SPR 6696607] The C++ header <atomic> is missing from this release although plans exist to include it in a future release.

  • [SPR 6696609] The C++ runtime library for Visual Studio 2017 and clang++ is a static link library in this release Plans exist to ship a dynamic library in a future release.

  • [SPR 6696611] std::rethrow_exception() will result in unresolved externals in both clang++ and Visual Studio 2017. This will be investigated and considered to resolve the external in a future release.

  • CONHOST.exe dies and the console vanishes While running the PTCS automated regression test suites on the NuTCRACKER Platform on a Windows 7 x64 machine we discovered numerous errors we had not seen before. During debugging, we discovered that the console window was vanishing and we had messages in the event log about CONHOST.exe dying with a 0xC0000005 exception. PCTS uses a NutCRACKER ported PDKSH and we had just the right combination of events to trigger a well known bug in Windows. Applying a fix found here: The conhost.exe process crashes when an application exits on Windows 7 or Windows Server 2008 R2 cured the problem and PCTS again ran properly to conclusion.

  • Perl CPAN support. Some Perl CPAN modules include source code for which must be built into a dll for the module to function. Building such modules is only possible if you have PTC MKS Toolkit for Professional Developers or PTC MKS Toolkit for Enterprise Developers. In such cases, perl should be launched from a development window (on 64-bit machines, use a 64-bit development window). Not all such Perl CPAN modules will compile out of the box - some may require porting to the NuTCRACKER environment.

  • Problems with constructors for global objects when using deprecated compilers. If you have PTC MKS Toolkit for Professional Developers or PTC MKS Toolkit for Enterprise Developers, and you are compiling and linking applications with one of the deprecated compilers (Microsoft Visual C++ 6.0, 7.0 or 7.1), you may have issues whereby constructors and destructors for C++ global objects are not called. This is most likely to happen when you directly use the link command to link your application, but it could also happen if you are using a Visual Studio project to link your application. The fix is to include old_initcode.obj on the command line when you invoke the linker, and this needs to be specified on the command line before c.lib.

    A warning sign that you may encounter this issue is if you encounter this warning message when linking your application:
    c.lib(initcode.obj) : warning LNK4078: multiple ".CRT" sections found with different attributes (40300040)

    If you are using the ld command to link your application, then no changes to your makefiles or build scripts should be required.

  • Last Access Timestamps. On Windows 7 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 PTC X/Server. Currently, there are some issues with NuTCRACKER Platform applications which use OpenGL to access PTC X/Server features such as Direct Rendering and Overlay Planes on systems using an NVIDIA video card. For details, see the PTC X/Server 8.7 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 was expected in Visual Studio 2008 Patch 1 from Microsoft, but there seems to be no evidence in the list of fixed problems that it was included.

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

Technical Support

To contact Technical Support regarding an existing or new case, you will need to log on to the PTC eSupport Portal, You will need a PTC SCN to access PTC online tools and to ensure exclusive access for active Maintenance Support customers. Technical Support contact phone numbers by region and support hours are listed within the eSupport Portal.

Additional PTC MKS Toolkit Resources

There are several other sources for additional information about our PTC 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 PTC MKS Toolkit at:

Through the years, we have accumulated a lot of technical details about the PTC 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 PTC MKS Toolkit 10.1. These are listed at:

Fixed Problems in Previous Releases