CPS (Client Profile Setup) Utility Obsolete
The Client Profile Setup utility, or CPS, was a solution developed forMicrosoft Windows NT 3.51. For the Microsoft Windows NT 4.0 ResourceKits, the CPS utility is no longer supported or developed.
The new tools for automating Microsoft Windows NT 4.0 setup aresetupmgr.exe and sysdiff.exe. For further information about these tools,please consult the Microsoft Windows NT 4.0 Resource Kit printeddocumentation or RKTOOLS.HLP.
Desktop Themes Crashes When JPEG Filter is Used
Desktop Themes might crash (and generate a Dr. Watson log) with any of thefollowing symptoms:
Exception number: c0000005 (access violation) Exception: access violation (Oxc0000005) error in themes.exe Desktop Themes closes without warning
The Microsoft Windows NT Resource Kit team has developed a patch to addressthis problem for all Windows NT platforms. This patch is available for freedownload at the following ftp site:
Note: You must have the original Windows NT 4.0 Desktop Themes programinstalled in order for the patch to work properly.Cause
Microsoft Office 97 (and possibly other programs) installs a JPEG filterthat is incompatible with the initial release of Desktop Themes included inthe Windows NT 4.0 Resource Kit. This incompatibility is not a problem withMicrosoft Office 97. The only complete resolution is to obtain the DesktopThemes patch file.Workaround:
To circumvent this issue without the patch, use the following steps:
- Open Desktop Themes
- Click the Save As button, then enter the theme named Original Settings.Theme, and then click OK to save your current settings as a theme
When you save or change the current theme settings, the Settings check boxes become available. You now also have a desktop theme with a .BMP wallpaper.
- Uncheck the desktop theme wallpaper option before changing desktop themes, and then set your theme as normal and click OK to save your change
- To change the desktop theme again, open the Desktop Themes program in the Control Panel and then select the "Original Settings" theme. This theme has a .BMP wallpaper and should not cause Desktop Themes to crash. After changing the theme selection, you can once again disable the Wallpaper checkbox before choosing a theme that has a JPEG wallpaper.
If you wish to use the wallpapers without the patch, use another program toconvert the appropriate .JPG file into a .BMP file, and then change thedisplay background setting to the new .BMP file.
Please e-mail RKINPUT@MICROSOFT.COM if you find additional informationregarding this issue such as:
- Other applications known to conflict with Desktop Themes
- Other symptoms resolved by installing the Desktop Themes patch
MAILSRV: Known issues, alternatives, and support policy
The Mail Server 1.1 utility (MailSrv) provided with the "Microsoft WindowsNT Server Resource Kit, Version 4.0" was designed as a basic SMTP and POP3mail server implementation. It was never designed or intended to be amission-critical, secure, or enterprise-scale solution. Microsoft hasdeveloped two full-featured mail servers to provide superior functionalityand reliability. Microsoft recommends implementing a more secure andreliable mail service than can be managed by the MailSrv utility, and forthis reason MailSrv has been discontinued.
The following problems have been reported with the MailSrv utility on theMicrosoft Windows NT Server 4.0 Resource Kit CD-ROM.
- Mail sent to the MailSrv server is held in the spool directory and is notdistributed to the appropriate user.
- Over a period of time, MailSrv might slowly take up to 100 percent of theavailable CPU cycles. Stopping or restarting local mail delivery service,POP3 service, and SMTP service will release the CPU cycles.
The Resource Kit development team is aware of these problems and will postfurther information as it becomes available. However, the MailSrvutility is no longer included with the Microsoft Windows NT Resource Kit.MailSrv.Exe was not included on the "Microsoft Windows NT Server ResourceKit, Version 4.0, Supplement One" CD-ROM, and MailSrv will not be includedwith any future supplements or releases.
Microsoft produces two robust, secure, and full-featured mail servicesolutions for an enterprise system: Microsoft Exchange Server and MicrosoftCommercial Internet System, formerly code-named Normandy.
More information about Microsoft Exchange Server can be found on thefollowing Web site:
More information about Microsoft Commercial Internet System and otherMicrosoft enterprise solutions can be found at:
by clicking the Product Information hyperlink.
If you are looking for a small-scale Windows NT mail server solution, youmight find that a suitable freeware or shareware mail server is available.You can find a list of third party mail server vendors by going to the following Web site and searching for the Mail Server product category:
This site is subject to regular change, and most of the freeware andshareware hyperlinks are updated and replaced with newer links.
NTPERL5.HTM File Missing
NTPERL5.HTM is referenced in the following text files:
\COMMON\COMMON\PERL\README.TXT and \SOURCE\GNU\PERL\README.TXT. However,NTPERL5.HTM is not on the NT Resource Kit CD-ROM.
The Windows NT 3.51 Resource Kit Update volume 2 contains NTPERL5.HTMand some additional files not found on the Windows NT 4.0 Resource KitCD-ROM. This is because the PERL documentation files are an image ofinformation posted on public domain Internet sites not controlled orauthored by Microsoft.
The following text should appear at the top of the above README.TXTfiles:
***** PERL Documentation disclaimer *****The PERL HTML documentation including the following README.TXT wascopied from public domain Internet sites.Microsoft does not claim responsibility for any inaccuracies ormissing files related to the PERL scripting documentationincluded with the Microsoft Windows NT Resource Kit. Pleasenote that NTPERL5.HTM is referenced in this file, but this filewas not included on the file image for this Windows NT ResourceKit CD-ROM.***************************************************
Microsoft is researching this issue and will post further information inthis article when available.
RKTOOLS.HLP: Desktop Themes Install Instructions Incorrect
In the RKTOOLS.HLP section for Desktop Themes for Windows NT 4.0, thelink to Run Desktop Themes will display installation instructions ifDesktop Themes is not already installed. However, these instructions areincorrect.
To properly install the Desktop Themes utility, insert the Windows NTResource Kit CD-ROM and run the following command (where D: is assumedto be the CD-ROM drive letter):
SYSDIFF.EXE: Unable to load sysdiff INF C:\RESKIT\sysdiff...
The following error message will occur if Sysdiff.inf is not in thedirectory containing SYSDIFF.EXE:
Unable to load sysdiff INF C:\RESKIT\sysdiff.inf.
This file is required in SNAP and DIFF modes. Consult the Windows
NT OEM Preinstall Kit documentation for more information.
The information below is from the following Knowledge Base article:
Err Msg: Incorrect Arguments. Consult the Windows NT
The Windows NT 4.0 Resource Kit CD-ROM does not include the Sysdiff.inffile that is required for the Sysdiff tool to work properly.
To resolve this issue, use one of the following methods:
- Use the Sysdiff tool from the Support\Deptools\<platform> folder on your Windows NT 4.0 CD-ROM.
- Copy Sysdiff.inf from your Windows NT 4.0 CD-ROM into the folder from where you are running the Sysdiff tool.
Microsoft has confirmed this to be a problem in Microsoft Windows NTResource Kit version 4.0 and will post new information in the MicrosoftKnowledge Base as it becomes available.
Sysdiff /diff "error=112" Caused By Insufficient Disk Space
Sysdiff /diff tries to generate a difference file containing a list ofdifferences between an earlier snapshot of the system and the system asit exists at the time /diff is used. If there is insufficient hard diskspace to generate this file, error 112 will occur.
Error 112 is a standard Win32 error code, and represents an "out of diskspace" error. Please check to ensure sufficient hard disk spaceavailable.
Note: If large amounts of changes were made since the initial snapshot,your diff_file will likewise be large. As per the Workstation ResourceGuide Chapter 2 (book online, index entry "Sysdiff utility"), "Theinformation in the difference file includes all the binary files for theapplications, as well as the initialization file settings and registrysettings for the applications." You can also use the /log switch totrace the activities of Sysdiff during the /diff operation.
Several NT 4.0 Resource Kit Utilities Missing
The following Resource Kit utilities are mentioned in the\COMMON\COMMON\RKTOOLS.HLP file, but they are not present on the WindowsNT Resource Kit CD-ROM:
* GLOBAL.EXE and LOCAL.EXE have been completed for the Intel x86platform and are available at the following ftp address:
** SHOWMBRS.EXE is present on the Windows NT Workstation Resource KitCD-ROM.
These utilities were planned for release with the Windows NT 4.0Resource Kit but were either incomplete or not stable when the ResourceKit released. Some utilities have been completed and added to theWindows NT ftp address. The Resource Kit team is working to provide theremaining utilities later either via the Resource Kit ftp site or infuture updates or supplemental volumes of the Windows NT Resource Kit.
Service Monitor Requires Update After Password Change
The Service Monitor uses your domain\username, password. If your passwordchanges the Service Monitor will no longer work correctly. To correct this- re-run the Service Monitor Configuration Wizard (smconfig.exe) and enteryour new password. The configuration wizard will re-install the servicebased on this new password.
TELNETD Service Does Not Install Properly
The Telnet Server service does not install properly as described inTELNET.WRI. When adding the Telnet service, the instructions state toselect the Remote Session Manager. However, the only selection availableis Telnet Service Beta (Inbound Telnet).
This issue has been addressed in a new OEMSETUP.INF file for the TelnetDservice. To obtain a copy of the latest OEMSETUP.INF for TelnetD,connect to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/reskit/nt40/ and download OEMSETUP.INF directly to your Resource Kit Telnet directory(typically C:\RESKIT\TELNET).
If you do not have access to ftp, you can e-mail RKINPUT@MICROSOFT.COMwith the following subject line:
TELNET OEMSETUP.INF REQUEST
The RKINPUT alias will reply by sending a corrected OEMSETUP.INF.
UPTOMP.EXE Error "Unable to locate the UPTOMP.INF file"
Clicking on the Uni to Multiprocessor icon in the Start Menu causes thefollowing error:
Unable to locate the UPTOMP.INF file. This file should be in the same directory as the executable file or in the windows directory.
Other error dialog boxes may follow as well.
This error occurs because the Start Menu shortcut for UPTOMP.EXE does notset the working directory to the RESKIT directory. Changing the Start Inshortcut property for the UPTOMP.EXE icon to C:\RESKIT will correct thisproblem for a default Resource Kit installation.
To successfully run the Uni to Multiprocessor conversion program, followthese steps:
- Click Start, then click Programs, and then click Command Prompt
- Change directory to your Windows NT Resource Kit directory. For instance:
- Type UPTOMP.EXE and then press Enter
UPTOMP.EXE Does Not Copy WIN32K.SYS
UPTOMP.EXE, included with the "Microsoft Windows NT 4.0 Resource Kit" toassist in copying the correct files, does not copy the file WIN32K.SYS.This file needs to be copied for multiprocessor operation.
An update to UPTOMP.INF is available to correct this problem and can beobtained from the following Internet ftp site:
To manually correct the UPTOMP.INF file, use the following steps:
- Open \RESKIT\UPTOMP.INF with Notepad or the editor of your choice.
- Add the following text directly below the line beginning with"Winsrv.dll":
Note: This new line must be entered above the black box that representsthe end-of-file marker for this file.
win32k.sys = 0, 2, win32k.sys
If you already ran UPTOMP.EXE and can no longer boot to Windows NT, youmight need to manually copy WIN32K.SYS from the Windows NT CD-ROM toyour Windows NT System32 directory. If you can boot to Windows NT,change UPTOMP.INF as noted above and re-run UPTOMP.EXE.
Cannot Read Help Files Due To Missing WINHLP32.exe
When opening RKTOOLS.HLP or one of the other help files included on theWindows NT 4.0 Server or Workstation Resource Kit CD-ROM, you might receivethe following error messages:
"This file is not a valid Windows help file."
"A newer version of help is required to view this file."
The Windows NT 4.0 Resource Kit help files require WINHLP32.EXE to beinstalled on the system. WINHELP.EXE will produce the errors listed above.
Check to make sure that WINHLP32.EXE is installed on your system.
- Click the Start button, then click Find, then click Files or Folders
- Type WINHLP32.EXE in the Named field, and then click the Find Now button
If WINHLP32.EXE is not present, reinstall or expand this file from theWindows NT product CD-ROM.If WINHLP32.EXE is installed on the computer butWINHELP.EXE is still started when you open any help file, then use thefollowing steps to check and update the application that is associated withHelp files:
- Click the Start button, then click programs, and then click Windows NT Explorer
- Click the View menu, and then click Options
- Click the File Types tab in the Options dialog box, then locate and select the Help File registered file type, and then click the Edit button.
- Double-click the Open action. The default value for the "Application used to perform this action" field should be:
C:\WINNT\system32\winhlp32.exe Note that your system32 path directory might differ. If this field references WINHELP.EXE instead of WINHLP32.EXE, update the field and then click OK.
- Click Close, and then click Close again to update the file association
Page 348 & 349: Addresses incorrect
Page 348, second command line example:
Interface: 172.16.48.190 Internet Address Physical Address Type 172.16.80.138 00-20-af-ld-2b-91 dynamic 172.16.90.32 00-60-8c-0e-6c-6a static
Interface: 172.16.113.190 Internet Address Physical Address Type 172.16.113.138 00-20-af-ld-2b-91 dynamic 172.16.90.32 00-60-8c-0e-6c-6a static
Page 349, command line example:
Interface: 172.16.112.190 Internet Address Physical Address Type 172.16.112.138 00-20-af-ld-2b-91 dynamic
Interface: 172.16.113.190 Internet Address Physical Address Type 172.16.113.138 00-20-af-ld-2b-91 dynamic
0Microsoft Press is committed to providing informative and accuratebooks. All comments and corrections listed above are ready for inclusionin future printings of this book. If you have a later printing of thisbook, it may already contain most or all of the above corrections.