MKS
Toolkit Release Notes
Version 7.5
MKS Software Inc.
12701 Fair Lakes Circle, Suite 350
Fairfax VA 22033-3831 USA
Support: +1-703-803-7660
+1-703-803-3343
http://www.mkssoftware.com
January 2001
Contents
MKS Toolkit 7.5
Known Issues
Hardware and Software Requirements
Installing MKS Toolkit
Uninstalling MKS Toolkit
Customer Support
Additional MKS Toolkit Resources
Problems Fixed
MKS Toolkit 7.5 is the latest version of the MKS Toolkit product family. New features in MKS Toolkit 7.5 include:
hd formatted hexadecimal dump passwd change user password shutdown shut down a local or remote system view read-only version of vi whoami display user name of current user
gman -i -M $ROOTDIR/samples/groff pagename
where pagename is the name of the page to display. Note that these original pages occasionally refer to paths beginning with C:/PROGRA~1/MKSTOO~1. This is the short name of the standard installation location for MKS Toolkit (C:/Program Files/MKS Toolkit). If you installed MKS Toolkit in a different directory, please substitute that directory when searching for the file or directory described.
New Features in Previous Releases
If you are upgrading from a pre-7.0 version of MKS Toolkit, or this is your first experience with MKS Toolkit, you may find the following links useful in understanding recent changes to the product:
viw file1.ksh viw file2.ksh viw file3.kshThis is due to operating system changes on Windows Millennium. On other versions of Windows, selecting multiple .ksh files and right-clicking Edit is the equivalent of
viw file1.ksh file2.ksh file3.ksh
Hardware and Software Requirements
MKS Toolkit products run only on Windows systems with Intel 32-bit processors.
All MKS Toolkit products will install on Windows 95, Windows 98, Windows Millennium, Windows NT 4.0 (Workstation, Server, or Terminal Server) with Service Pack 4+, and Windows 2000 (Professional, Server, or Advanced Server). Applications migrated from UNIX with either MKS Toolkit for Professional Developers or for Enterprise Developers will run on any of these platforms.
There are limitations for Windows 95, 98, and Millennium. Many MKS Toolkit utilities are Windows NT- or Windows 2000-specific. These are clearly documented on the reference pages (Start > Programs > MKS Toolkit > Documentation > MKS Toolkit Utilities Reference). Additionally, the SLnet Telnet Server (provided in MKS Toolkit for Interoperability and MKS Toolkit for Enterprise Developers) only runs on Windows NT/2000. In addition, because of the lack of certain OS features on Windows 95, 98, and Millennium, certain of the MKS Toolkit UNIX APIs run in degraded mode (or return without doing anything) on those platforms. These are discussed in the MKS Toolkit Cross-Platform Developer's Guide and in great detail in the reference page for each API (Start > Programs > MKS Toolkit > Documentation > MKS Toolkit UNIX APIs Reference).
The development products work with Microsoft Visual C/C++ versions 5.0 and 6.0. Both MKS Toolkit for Professional Developers and for Enterprise Developers support both versions of the Standard Template Library. In addition, they both support the Absoft Pro Fortran f90/f77 compiler, versions 5.0, 6.0, and 7.0 (http://www.absoft.com/).
The typical disk space requirements are:
Product Typical Size MKS Toolkit for System Administrators 67M MKS Toolkit for Developers 73M MKS Toolkit for Interoperability 100M MKS Toolkit for Professional Developers 115M MKS Toolkit for Enterprise Developers 210M
MKS Toolkit products do not have any particular hardware requirements. Any machine that is sufficient to run the underlying operating system is sufficient to run any MKS Toolkit product.
Before installing MKS Toolkit 7.5, we recommend that you uninstall any previous version of MKS Toolkit. If you have a previous version of MKS NuTCRACKER Professional, we recommend that you uninstall it, or install MKS Toolkit on another machine.
When installing MKS Toolkit for Professional Developers or MKS Toolkit for Enterprise Developers, the following additional requirements apply:
All MKS Toolkit products share a common installer. To install your product:
To uninstall 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:
MKS
Evaluation Guide
MKS Toolkit 7.x
MKS Platform Components 7.x
You must reboot your system before reinstalling MKS Toolkit.
To receive support for your MKS Software product, you must buy a Preferred Customer Support (PCS) contract for that product. Some MKS Software products come bundled with PCS. For others, PCS is optional. PCS is renewable annually for a small fee and entitles you to unlimited customer support, patches, bug fixes, and all product upgrades for the duration of the contract. In any given 12-month period, MKS Software typically releases one minor upgrade (maintenance), one major upgrade (new features), and several patches, none of which you will want to miss.
In addition, customers with PCS may elect to receive periodic mailings from our customer support organization. These mailingsgeared at end usersoutline new features, give tips for using features, discuss how to solve common problems, and provide other frequently requested information. Moreover, as MKS Software moves more of its internal support information onto the support web site, only those customers with PCS will be able to access this controlled information, that will include instant status about reported issues, a searchable database of frequently asked questions, and much more detailed self-help information.
If you are a new customer or you have never activated your PCS account, you must register with our customer support organization. Registrationmandatory before you can receive supportis simple. The easiest way to register is by filling out the registration form during product installation, or you may do so at any time over the web at http://www.mkssoftware.com/register. And please be assured that this information is used for no other purpose than to provide support to you. Your personal information will not be given to anyone else.
Without PCS, you will not be entitled to any support, patches, bug fixes, upgrades, mailings, or self-help information. If you do not have PCS, all of our sales channels offer MKS Software products with bundled PCS for your convenience. If you already have product, but need PCS, you may purchase a PCS contract by contacting MKS Software directly at 800-637-8034 or +1-703-803-3343.
With PCS, you can request customer support by contacting us using one of the means listed below and in your request, include the name and version number of the product that you are using, your serial number, and the operating system and version/patch level that you are using. Contact MKS Software customer support at:
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 a number of 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:
The table below documents issues that were fixed in the MKS Toolkit 7.5 release.
For convenience, the following abbreviations are used in this table
TKSA MKS Toolkit for System Administrators
TKDev MKS Toolkit for Developers
TKIO MKS Toolkit for Interoperability
TKPDev MKS Toolkit for Professional Developers
TKEDev MKS Toolkit for Enterprise Developers
Problem | Applies To | Description |
SR 9028 | All | viw does not handle 2nd file correctly if 1st file is encrypted. |
SR 11848 | All | in viw/vi/ex, tag file lists ignore next entry if file not found |
SR 12134 | All | viw/vi problems with tags with regular expressions in context addresses |
SR 12135 | All | viw problems with highlighted text and vi-mode commands |
SR 15149 | All | would like option to disable KornShell (sh) checking file type associations |
SR 15774 | All | Problem on status line when editing multiple files with viw |
SR 15791 | All | vpax crashes when passed a filename as an argument |
SR 17761 | All | Customer would like an option for tar, pax, and cpio to archive NT security info |
SR 17790 | All | date field descriptors specified after %r are ignored |
SR 17812 | All | incorrect time information used in the smtpmail date field |
SR 18298 | All | rsh password truncated at 8 characters |
SR 18306 | All | Using "userinfo.exe" utility, one can set the field "User must change the password at next logon" in User Manager to "Yes" but if he tries to set it to "No", it fails. |
SR 18355 | All | viw does not resize window correctly |
SR 18435 | All | viw job title when printing is truncated path name |
SR 18468 | All | Using French Windows 98, "Azerty" Keyboard arrow keys do not work in vi editor. |
SR 18632 | All | C Shell sometimes adds extra, unnecessary backslashes to echoed lines |
SR 18633 | All | who am i does not return any output when executed by rshd |
SR 18665 | TKDev, TKIO, TKPDev, TKEDev |
web should include the "Host" header by default |
SR 18673 | All | find exits after receiving an access denied error |
SR 18695 | All | would like rcp to have the ability to copy files >2GB |
SR 18703 | All | cannot access more than 10 tape devices using NT tape support |
SR 18738 | All | cpio does not support storing symbolic links |
SR 18740 | All | rcp fails if you specify a domain user with a backslash |
SR 18741 | All | rcp incorrectly interprets a domain user name with a forward slash as a local path |
SR 18749 | All | rshd dies in 7.0.1 demo |
SR 18772 | All | pax doesn't correctly store symbolic links in cpio archive |
SR 18774 | All | pax doesn't correctly extract symbolic links in cpio archive |
SR 18776 | All | cpio crashes when extracting symbolic links from an archive |
CFS 14542 | TKIO, TKEDev | XGetImage() fails under XVision X server |
CFS 15168 | TKPDev, TKEDev | hcreate, hsearch: not getting entire capacity. |
CFS 15423 | TKPDev, TKEDev | Hang in pthread_once() |
CFS 15460 | TKPDev, TKEDev | Many RPC calls to PDC. |
CFS 15491 | TKPDev, TKEDev | Sys V semaphore lock problem. |
CFS 15649 | TKPDev, TKEDev | stat() incorrectly returns st_mode == 0 on Win9x. |
CFS 15697 | TKPDev, TKEDev | login.csh clobbered when NuTCRACKER 4.2a installed |
CFS 15749 | TKPDev, TKEDev | O_TEMPORARY open() option fails. |
CFS 15762 | TKPDev, TKEDev | Unhandled exception in nutsys4.dll (pt_nutc.cpp) function |
CFS 16091 | TKPDev, TKEDev | system() handles quoting in a way that causes cmd.exe to fail. |
CFS 16248 | All | missing utility whoami |
CFS 16328 | TKPDev, TKEDev | If $SHELL contains spaces, system() does not work |
CFS 16532 | TKPDev, TKEDev | kill() fails on newly created child process. |
CFS 16537 | TKPDev, TKEDev | Getting an exception when a Java app loads a DLL built with MKS NuTCRACKER 4.2a patch 1. |
CFS 16565 | TKIO, TKEDev | SCO XVision and graphics cards |
CFS 16569 | TKIO, TKEDev | file name problems with Unix Neighborhood |
CFS 16571 | TKPDev, TKEDev | kill command is not able to stop a NuTCRACKER service. |
CFS 16660 | TKIO, TKEDev | Trying to autostart X-server from 2 simultaneous processes |
CFS 16734 | TKIO, TKEDev | cannot print to the local printer as:\\computer name\printer name |
CFS 16744 | TKIO, TKEDev | getsockopt returns WINSOCK errors rather than POSIX errors |
CFS 16775 | TKPDev, TKEDev | getting error: Failed to create directory "\:\NutTrash4" using ulink(). |
CFS 16810 | TKPDev, TKEDev | Signal information is lost by vfork() child process handler. |
CFS 16852 | TKPDev, TKEDev | output struct not initialized in strptime() |
CFS 16900 | TKPDev, TKEDev | Getting 'Out of memory attempting to allocate atexit() entry' with NuTCRACKER DLL. |
CFS 16937 | TKPDev, TKEDev | Format character %LF is not working properly in scanf() family. |
CFS 17096 | TKPDev, TKEDev | support Absoft Fortran version 7 |
CFS 17324 | TKPDev, TKEDev | wait logic in thread communication is incorrect |
CFS 17390 | All | TKUninstall does not remove all registry keys on Windows ME |
CFS 17391 | All | install path could not be changed on Windows ME when no previous install was present |
CFS 17392 | All | TKUninstall is not removing the correct set of items |
CFS 17394 | All | Install scripts were overwriting environment variables HOME, TMP, and TMPDIR |
CFS 17399 | All | Anomalous behavior of Windows ME when selecting multiple .ksh files and right-clicking Edit (Note: Difference in ME behavior in this situation is described in the Known Issues section of these release notes.) |
CFS 17400 | All | Wrong version of zip and unzip included |
CFS 17408 | All | MIB file syntax incorrect |
CFS 17409 | All | snmp_variables reference page contains spurious reference to /cmu-snmp-linux-3.7 |
CFS 17416 | All | relax requirement for psapi.dll to be present |
CFS 17420 | All | rshd security bug? (Note: rshd behavior was correct. The rhosts reference page has been corrected to reflect the proper behavior.) |
CFS 17435 | All | dosname incorrectly returning backslashes instead of forward slashes |
CFS 17436 | All | Winzip associations overwritten by Toolkit installer |
Problems Fixed in Previous Releases
If you are upgrading from a pre-7.0 version of MKS Toolkit, or this is your first experience with MKS Toolkit, you may find the following links useful in understanding recent changes to the product: