MKS Homepage v9.0 Patch 4 

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

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



MKS Toolkit 9.0 Patch 4

MKS Toolkit 9.0 Patch 4 is a maintenance update for MKS Toolkit 9.0. It includes all fixes found in MKS Toolkit 9.0 Patches 1, 2, and 3 as well as those fixes listed in Fixed Problems below. In addition, it includes several new features.

New Utilities

The following new utilities have been added to MKS Toolkit:

  • bsdftp. The bsdftp utility provides an enhanced user interface to the Internet standard File Transfer Protocol.

  • bsdtelnet. The bsdtelnet utility provides an enhanced user interface for communication with another host using the TELNET protocol.

New Perl Modules

The following Perl modules have been added to MKS Toolkit:


Various Other Enhancements

The following new features have been added to existing utilities:

  • Support for Standards-Based Authentication Mechanisms. The imapmail, pop3mail, smtpmail, and web utilities have been enhanced to support standards-based authentication mechanisms. Among other benefits, this allows tighter integration with Microsoft IIS and Microsoft Exchange to turn off clear text authentication while maintaining compatibility with existing scripts using these utilities. For interactive use, new options have been added to allow the use of currently logged on users' credentials without further password prompting. Details on the options added and the authentication mechanisms supported can be found in the updated reference pages for these utilities.

  • Support for CTRL-D as End-of-File. The MKS KornShell (sh, ksh, bash, and resh), MKS C Shell (csh), the remote shell (rsh), and most utilities that accept input from the console now accept CTRL-D as the end-of-file (EOF) character when the TK_USE_CTRLD_AS_CONSOLE_EOF environment variable is set.

  • New Verbose Output Format for pending and gpending. The pending utility now features a -v option which displays information about the pending operations in a more verbose format. This verbose format is also now used as the display format for the gpending utility.

  • New TK_ECHO_DEFAULT_NO_ESCAPE_SEQUENCES Environment Variable for echo. The echo utility now supports the TK_ECHO_DEFAULT_NO_ESCAPE_SEQUENCES environment variable. When this variable is set, echo treats escape sequences as normal text and ignores any special meanings such sequences may normally have.

  • Current Locale Support for Thousands Separator. The awk and printf utilities now display (for appropriate formats) the thousands separator specified in the current locale (as set by the Regional and Language Options control panel applet) when the TK_USE_CURRENT_LOCALE environment variable is set.

  • Improved viw Support for Character File Formats. The viw utility (the GUI version of vi) now supports the selection of character file format for files being opened or saved through a Character Set dropdown list on the file selector dialog.

Updated Reference Pages

New reference pages are now included for all utilities and APIs added since MKS Toolkit 9.0. In addition, other reference pages have been updated to reflect changes in those utilities or APIs.

MKS Toolkit 9.0 Patch 3

MKS Toolkit 9.0 Patch 3 is a maintenance update for MKS Toolkit 9.0. It includes all fixes found in MKS Toolkit 9.0 Patch 1 and Patch 2 as well as those fixes listed in Fixed Problems below. In addition, it includes several new features. Reference pages for these new features will be available on the MKS Web Site at

New Utilities

Two new utilities have been added to MKS Toolkit:

  • Expect. The Expect utility allows users to automate interaction with utilities like ftp, telnet, or rlogin, or in fact, with any utility that normally requires human responses.

  • script. The script utility records the console output (and optionally, input too) of one or more console commands in a file.

New APIs

MKS Toolkit for Professional Developers, MKS Toolkit for Enterprise Developers, and MKS Toolkit for Enterprise Developers 64-bit Edition feature a several new APIs.

  • posix_spawn() and Related APIs.
      posix_spawn(), posix_spawnp(), posix_spawn_file_actions_addclose(), posix_spawn_file_actions_adddup2(), posix_spawn_file_actions_addopen(), posix_spawn_file_actions_destroy(), posix_spawn_file_actions_init(), posix_spawnattr_destroy(), posix_spawnattr_getflags(), posix_spawnattr_getpgroup(), posix_spawnattr_getschedparam(), posix_spawnattr_getschedpolicy(), posix_spawnattr_getsigdefault(), posix_spawnattr_getsigmask(), posix_spawnattr_init(), posix_spawnattr_setflags(), posix_spawnattr_setpgroup(), posix_spawnattr_setschedparam(), posix_spawnattr_setschedpolicy(), posix_spawnattr_setsigdefault(), posix_spawnattr_setsigmask(),

MKS Toolkit 9.0 Patch 2

MKS Toolkit 9.0 Patch 2 is a maintenance update for MKS Toolkit 9.0. It includes all fixes found in MKS Toolkit 9.0 Patch 1 as well as those fixes listed in Fixed Problems below. In addition, it includes the following new features:

Improved Compiler Support

MKS Toolkit 9.0 Patch 2 supports additional compilers that were not available when MKS Toolkit 9.0 was released. To use this additional compiler support, you must first install MKS Toolkit 9.0 Patch 2 and then run Add/Remove Programs from the control panel. Select MKS Toolkit 9.0 and click Change. The MKS Toolkit installer starts and you can use the Repair option to access the new compiler support. Alternatively, you can obtain a CD version of MKS Toolkit 9.0 with Patch 2 included from MKS. With this version, access to the new compiler support is available during installation; however, if you have MKS Toolkit 9.0 (with or without Patch 1) installed, you must first uninstall it before installing from the cd.

  • Microsoft Visual Studio 2005. MKS Toolkit 9.0 Patch 2 is now fully compatible with the release version of Microsoft Visual Studio 2005. Details on using the Visual Studio 2005 IDE to compile, link, and debug applications can be found in the "The Porting Process" and "Using the Visual C++ IDE" chapters of the online version of the MKS Toolkit UNIX to Windows Porting Guide.

    There are four different varieties of Microsoft Visual Studio 2005 that can be used with MKS Toolkit:

    • Visual C++ 2005 Express. This version features a C++ compiler (for the 32-bit x86 platform only) and a small IDE. It is a solid solution for users wanting a free optimizing compiler to use with the MKS Toolkit development products. When using this product, the Microsoft Platform SDK is required for MKS Toolkit for Professional Developers and MKS Toolkit for Enterprise Developers.

    • Visual Studio 2005 Standard. This version includes a full x86/x64 compiler suite and full IDE.

    • Visual Studio 2005 Professional. This version is similar to the Standard version but includes additional tools and servers.

    • Visual Studio 2005 Team System. This version adds an IA64 (Itanium) cross compiler. It does not install on an IA64 system, so all Itanium development must be done on an x64 or x86 system. The resulting executable can then be deployed to an IA64 system, where it can be debugged using the remote debugger.

    Versions of Visual Studio 2005 which include a 64-bit compiler for x64 include both a native x64 compiler (that is, a 64-bit x64 binary producing 64-bit x64 binaries) and a 64-bit cross compiler (that is, a 32-bit x86 binary producing 64-bit x64 binaries). When MKS Toolkit for Enterprise Developers 64-bit Edition is installed on an x64 system, the native compiler is selected as the compiler of choice; on x86 systems, the cross compiler is selected.

    The Hardware and Software Requirements section of these release notes (in particular, the Deployment paragraph) has been updated to reflect Visual Studio 2005 support.

    Note: MKS Toolkit 9.0 Patch 2 is not compatible with beta releases of Visual Studio 2005.

  • Intel C++ 9.0. Support has also been added for the Intel C++ 9.0 compiler. Included in this support is the addition of a new icl9 compiler specifier to the ncenv, ncenv64x, and ncenv64i utilities.

Digital Code Signing

All MKS Toolkit binary and installer files are now digitally signed. This feature assures users that the software comes from MKS Inc., that it is virus free, and that it has not been tampered with since it was originally built.

Enhancements to the pending Utility

  • New -l Options. When the new -l option is specified, pending lists all pending operations without prompting for deletions. No operations are deleted with this option.

  • New gpending Utility. The new gpending utility is a graphical version of pending. It displays a dialog showing the pending delete and rename operations. To refresh this display, click the Refresh button. To delete one or more operations, select those operations and click the Delete button. To delete all pending operations, click the Delete All button. When using Delete All, be careful to make sure that you actually want to prevent these operations from being performed.

Enhancements to the strings Utility

  • New TK_STRINGS_DEFAULT_SECTIONS Environment Variable. This environment variable specifies a comma-separated list of file sections to search for strings. When this variable is unset, strings only searches the DATA section.

    File sections that can specified include:

       TEXT      read only code and static strings (normal origin)
       DATA      initialized data (absolute origin)
       BSS       uninitialized data
       SYM       symbol table
       RELT      read only code static strings (run-time relocatable origin)
       RELD      initialized data (run-time relocatable origin)
       STACK     function call stack
       OTHER     any other type of section

  • New -s Option. This option, like the TK_STRINGS_DEFAULT_SECTIONS environment variable, specifies a comma-separated list of file sections to search for strings. When specified, this option overrides that environment variable.

Enhancements to the vi/viw Utility

  • IME Support. Both vi and viw now accept Chinese, Japanese, and Korean characters entered using IME (Input Method Editor).

  • Visual Studio Debugging Features. When using viw as your Visual Studio editor, you now have access to Visual Studio's debugging features.

Various Other Enhancements

In addition to those listed above, enhancements have been made to several other MKS Toolkit utilities:

  • New -i and -u Options for chacl. The chacl utility features two new options dealing with the inheritance of ACEs on Windows 2000 and later operating systems. The -i option adds inherited ACEs from the parent where they would normally not be present. The -u option disables parental inheritance.

  • New -h Option for df, du, and ls. The df, du, and ls utilities now each feature a -h that, when specified, displays each file size using the most appropriate unit for that size. For example, large files may have their sizes displayed in megabytes (MB), terabytes (TB), petabytes (PB), or exabytes (EB) instead of the traditional options of bytes (B) or kilobytes (KB).

  • New -i Option for join. When the new -i option is specified, join ignores case differences when comparing fields.

  • New -E, -M, -N, and -U Option for filebox. The filebox utility now accepts several additional options that change how the displayed dialog looks and behaved. -E adds an edit box, letting users directly enter the items they are seeking. -M does not include a New Folder button on the dialog. -N displays a newer, enhanced version of the dialog. And finally, -U allows the dialog to accept URLs.

  • New Digital Certificate Handling for strip. As of MKS Toolkit 9.0 Patch 2, strip now reports an error when you attempt to strip an executable that contains a digital certificate. The new -f option forces strip to strip the digital certificate; however, this is not generally recommended.

  • New expandstr: Format for registry -V. The -V option of registry now accepts specifying values with a format of expandstr: (expanded string). Such values are stored in the registry as REG_EXPAND_STR instead of REG_STR.

  • New MAILHOST Environment Variable for smtpmail. This new environment variables specifies the mail relay host to be used if the -h option does not explicitly specify one. When this variable is not set and there is no -h option, smtpmail attempts to connect with the Domain host identified by the TCP/IP settings.

  • New TK_EVENTLOG_USE_FULL_EVENTID Environment Variable for eventlog. This new environment variable determines whether or not eventlog uses the full double word value of the specified event ID as the filter when searching for matching event IDs in the log. When this variable is set, the full double word value is used; when it is unset (the default condition), only the lower 16-bit word is used as the filter.

  • New ll, I32, and I64 Conversion Specifiers for printf() and scanf(). The printf() and scanf() APIs (and their related functions) now accept ll, I32, and I64 conversion specifiers in format strings. The ll and I64 are equivalent to the existing q specifier and represent 64-bit integers (whether quad_t, long long, or __int64). The I32 specifier is equivalent to the existing l specifier.

MKS Toolkit 9.0 Patch 1

MKS Toolkit 9.0 Patch 1 is a maintenance update for MKS Toolkit 9.0. The fixes included in this update are listed in Fixed Problems below. In addition, it includes the following new features.

New Utility Options

Some MKS Toolkit utilities now feature additional options:

  • -q for cp, ln, and rm. The cp, ln, and rm utilities now feature a -q option. When specified, this option suppresses warning messages. Error messages are still displayed.

  • -U for vi. The vi utility now features a -U option. This option is similar to the -U option for the cat and more option and lets you specify the character format to be used for input and output.

MKS Toolkit 9.0

MKS Toolkit is the leader in UNIX to Window scripting, connectivity, and application migration. Enhancements found in the 9.0 release include multibyte and wide character support, vi/viw enhancements, as well as new utilities and APIs.

The Fixed Problems section discusses the problems resolved in this release. The following section discusses the specific enhancements in much greater detail.

Multibyte and Wide Character Support

MKS Toolkit utilities now support multibyte (UTF-8) and wide (Unicode) characters as well as extended ASCII characters within file content, file and directory names, pipes, environment variables, console displays, and other areas. MKS Toolkit UNIX APIs continue to support the Double Byte Character Set (DBCS).

Vi/Viw Enhancements

The vi and viw editors have been enhanced with several new features.

  • Visual Studio Plug-In. viw can be now used as the editor for Microsoft Visual Studio. Details can be found in the viw_vs reference page in the online MKS Toolkit Utilities Reference.

  • Syntax Highlighting. vi and viw can now highlight commands, reserved words, comments, and so forth using customizable rules.

  • Large File Support. vi and viw can now support files larger than 2 GB in size.

Updated Perl

Perl has been updated to version 5.8 and with this update, a variety of new features are now available to MKS Toolkit Perl users:

  • fork() Now Available. Unlike pervious versions, Perl 5.8 for MKS Toolkit supports the fork() function.

  • 32-bit and 64-bit Executables. Perl 5.8 includes executables for both 32-bit and 64-bit Windows platforms. The MKS Toolkit installer automatically installs the correct executable for your system.

  • Multithreaded. Perl 5.8 features "interpreter threads" ("ithreads", for short). This is a new multithreading implementation of threads intended to replace earlier implementations, such as "5.005 threads".

  • Standard HTML-Based Perl Reference Pages. The MKS Toolkit version of Perl 5.8 includes the standard HTML-based Perl reference pages. These pages can be viewed from the MKS Toolkit Perl Reference available on the MKS Toolkit Start menu or via the man -H command. Specifically:
       man -H mksperl
    is the equivalent of using the Start menu item.

Visual SFTP Enhancements

Several enhancements have been made to the Visual SFTP tool:

  • Drag and Drop Directories. Visual SFTP now lets you drag and drop directories in the same manner as regular files.

  • Editable Permissions. You can now edit the permissions for the appropriate files using Visual SFTP.

  • Large File Support. Visual SFTP can now handle files of any size.

  • Performance Enhancements. Various small enhancements have been made to Visual SFTP to improve its performance and stability.

IPv6 Support

MKS Toolkit utilities and APIs now support IPv6 addresses in addition to traditional IPv4 addresses.

  • Secure Utilities. The secsh utility and other related utilities have been updated to allow IPv6 addresses. To turn on support for IPv6 addresses, launch the MKS Toolkit control panel applet, select the Secure Shell Service tab and click Advanced.... Then, from the Secure Shell Server Configuration dialog that appears, select the TCP/IP tab and add a listening address of ::0.

  • New APIs. The following new APIs have been added to MKS Toolkit to help support IPv6 address:
  • Enhanced APIs. In addition to the new APIs listed above, many APIs have been enhanced to allow the use of IPv6 addresses as well as IPv4 addresses.

New Utilities

Several new utilities have been added to MKS Toolkit:

  • dgstsum and Related Utilities. The new dgstsum utility calculates and compares message digests (checksums) for specified files using a variety of digest formats.

    The following additional utilities are similar to dgstsum but use the digest format indicated by the utility name:
  • mksrv. The new mksrv utility lets you set up any standard script or program to run as a Windows service.

  • mktemp. The new mktemp utility creates a temporary file with a named based upon a provided template.

  • pwrmgr. The new pwrmgr utility allows you to display defined power schemes and to switch between them.

  • shexec. The new shexec utility lets you automatically execute any arbitrary application or file.

New Porting APIs

New APIs for clocks, timers and other SUSv3 functions have been added. For more information on these functions, please refer to the appropriate reference pages in the MKS Toolkit UNIX API Reference available from the MKS Toolkit Start menu or from the MKS web site at

      clock_getcpuclockid(), clock_getres(), clock_gettime(), clock_nanosleep(), clock_settime(), pthread_getcpuclockid()

      timer_create(), timer_delete(), timer_getoverrun(), timer_gettime(), timer_settime()

    Temporary Files
      mkdtemp(), mkstemps(), mkstemps64(), mkstemp64()

    File I/O
      pread(), pread64(), pwrite(), pwrite64(),

Miscellaneous Enhancements

A variety of minor enhancements have been made to several utilities and APIs:

  • Tab Completion of Environment Variables. The MKS KornShell now allows you to use tab completion with environment variables.

  • Expanded API PATH_MAX. The size of PATH_MAX used by the MKS Toolkit UNIX APIs has been increased to 4096 bytes on Windows NT/2000/XP/2003 systems.

  • man Now Supports HTML Reference Pages. The man utility can now display HTML reference pages using the -H option.

Operating System and Compiler Support

  • Support for Visual Studio 2005. MKS Toolkit for Developers and all higher products have been tested with Beta 2 of Microsoft Visual Studio 2005. Full support for Visual Studio will be available shortly after its formal release.

  • Support for 64-bit Windows. MKS Toolkit for Enterprise Developers 64-bit Edition now supports Windows XP x64 Edition and Windows Server 2003 x64 Edition as well as Windows Server 2003 for Itanium processors.

  • Support for Windows Server 2003 Service Pack 1. MKS Toolkit is now fully compatible with the latest beta release or release candidate for Microsoft Windows Server 2003 Service Pack 1.

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, IA64, or Extended Architecture 64-bit (such as AMD64) processors.

MKS Toolkit products have the following software requirements:

  • Platforms. You can install all MKS Toolkit products on:
    • Windows Me
    • Windows NT (Workstation, Server, or Terminal Server) with Service Pack 6+ (Service Pack 6a is recommended)
    • Windows 2000 (Professional, Server, or Advanced Server)
    • Windows XP (Home or Professional)
    • Windows Server 2003

    Note: MKS Toolkit 9.0 is the last planned release of MKS Toolkit for the Windows Me operating system.

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

  • Limitations for Windows Me. Many MKS Toolkit utilities are Windows NT/2000/XP/2003-specific. These are clearly documented in the reference pages in the MKS Toolkit Utilities Reference, available from the Start menu.

    In addition, because of the lack of certain operating features on Windows Me, some MKS Toolkit UNIX APIs run in degraded mode (or return without doing anything) on those platforms. These are discussed in the MKS Toolkit UNIX to Windows Porting Guide and in great detail in the reference page for each API in the online MKS Toolkit UNIX APIs Reference which you can access via the Start menu.

    Also, you cannot do 64-bit cross development on a Windows Me system. When you install MKS Toolkit for Enterprise Developers 64-bit Edition on Windows Me, the libraries required for 64-bit development are not installed. If you also have a license for the 32-bit libraries, those libraries will be installed instead, giving you the equivalent of MKS Toolkit for Enterprise Developers. If you do not have a license for the 32-bit libraries, no libraries are installed, giving you the equivalent of MKS Toolkit for Developers.

  • 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 compilers:
    • Microsoft Visual C++ 6.0, 7.0, 7.1, or 8.0 (either as a separate product or as part of Microsoft Visual Studio)
    • Visual C++ 2005 Express (requires Microsoft Platform SDK)
    • Microsoft C++ 2003 Toolkit (requires Microsoft Platform SDK)
    • Intel C++ 8.x or 9.x (requires Microsoft Platform 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, and 9.0 (

    MKS Toolkit for Enterprise Developers 64-bit Edition supports the following additional 64-bit compilers:
    • Visual C++ from Microsoft Visual Studio 2005
    • Microsoft Platform SDK Compiler
    • Intel C++ 8.x or 9.x (requires Microsoft Platform SDK)

    For those 64-bit compilers that require the Microsoft Platform 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.

    Note: Currently, Absoft does not provide a 64-bit Fortran compiler and associated libraries for the Windows 64-bit platforms. Once this support is available from Absoft, MKS Toolkit for Enterprise Developers 64-bit Edition will provide Fortran support.

  • 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 Windows Me, 2000, XP, and 2003 these are already installed. On Windows NT 4, you should follow these steps to install the Windows Task Scheduler:

    1. Select Add/Remove Programs from the Control Panel. The list of currently installed programs appears.

    2. Select Microsoft Internet Explorer and click Add/Remove. A dialog appears prompting you for action.

    3. Select Add a component to Internet Explorer. A list of additional Internet Explorer components appears.

    4. If you are running Internet Explorer 5+, select Offline Browsing Pack. If you are running Internet Explorer 4, select Additional Explorer Enhancements.

    Alternatively, you can download Internet Explorer 5 or 6 and their 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.0 on another machine.

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 for Professional Developers or MKS Toolkit for Enterprise Developers, 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. (This is only necessary if the XVision X server is installed. This X Server is normally only installed with MKS Toolkit for Interoperability and MKS Toolkit for Enterprise Developers.)

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.

Known Issues

The following known issues exist in MKS Toolkit 9.0:

  • 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_NTSERCURITYINFO_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 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 the platform 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 platform 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=.

  • X Server Support. The SCO X Vision X server (included in some MKS Toolkit products) is a 32-bit application that will run on the Extended Architecture 64-bit platforms in 32-bit emulation mode. If you require a 64-bit native X server, and not a 32-bit client display server, MKS recommends the Hummingbird Exceed product which is available directly from Hummingbird Ltd..

  • 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 of the MKS Toolkit Control Panel Applet.

Contact MKS customer support at:

Web Site:
Online Request Form:
Telephone: +1-703-803-7660
(9:00am to 7:00pm ET, Mon-Fri, except holidays)
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.0 Patch 4. These are listed at:

Fixed Problems in Previous Releases