******************************** WINDOWS 2000 PROFESSIONAL STRESS ******************************** NOTE: These tests and tools were designed to run on Microsoft's internal network with no intention of distribution. As a result some of these tool may not function externally. It is only in response to repeated customer requests that we have began to make them available. This is an on-going process. Expect some problems. While there are a number of MIPS and PPC binaries on this disk, these formats are no longer supported. What is Workstations Stress? **************************** Workstation Stress is a set of tests run on a daily basis against Windows 2000. These tests are run on various workstations throughout the Windows 2000 organization by individuals and in special labs in order to achieve maximum coverage of various hardware configurations. The tests are designed to target both specific areas of the operating system and to load the system in general. The failures produced by these tests are triaged and tracked by the Stress team and assigned to the appropriate design team for further study. What's on the Stress CD? ************************ The Workstation Stress CD contains the tests and a number of the tools we use in this process. Its contents will allow you to run Workstation Stress on your internal network and track the status of the systems running Stress. What you will need? ******************* In order to install and run Workstations Stress you will require a Server with at least 2 Gig free space on its 'systemdrive'. While you can install with about 500 meg, once symbols are added space requirements increase greatly. If you can name this server \\ntstress, installation will be much simpler and many more of the tools will become usable. (\\ntstress2 can also be installed to mirror \\ntstress for better results.) How to Install ************** To install simply run the setup program on the CD. This will put all necessary files in their required directories. When this is completed run the shareout.bat file as instructed. This file will share out the necessary directories with the necessary names and create a shortcut in your startup group to run regsrv whenever the machine is started. (regsrv is the program that will help you track the machines that have run stress and will allow you to know when a machine has failed without manually checking each machine.) Once installed, it will be necessary to edit a number of files to reflect the name of your stress server. In the following files it will be necessary to change all occurrences of \\ntstress and \\ntstress2 with the name of your server in the stress and autostress directories: - xstat.ini - kdbg.bat - autostress.cmd - stress.cmd - stress.ini - stressl.cmd - uptostrs.bat With this done you should now populate your \\yourserver\symbols directory with the symbols for the builds you will be stressing. Recommended directory structure is \\yourserver\symbols\(x86 or alpha)\(build # - eg 1877)\symbols. Running stress ************** If you are reading this it is expected that you know how to set up a debugger, and it will not be explained here. Set a debugger on the client that will run stress. From that client type \\yourserver\stress\stress.cmd or \\yourserver\autostress\autostress.cmd. Stress will directly start stress on that machine. Autostress will upgrade your system to the newest build and then run stress.(This may require making additional changes to autostress.cmd.) At this point Munger will pop up on the client. It is recommended that you accept the default settings. Once you have pressed OK, the stressui will appear. Fill in the info as requested. The 'Type of stress' field will be discussed below. With this done, the machine should show up on the regsrv 'GUI' that you started on the server. The info on this screen will allow you to track failed and running machines. Occasionally machines will show as DEAD when they have been hard restarted. To reset regsrv stop the process and restart regsrv with the '/n' switch. Type of stress ************** The values in this listbox is controlled by the stress.ini file. This file allows you to control the stress mix of the machines you are running. The file is set up in a hierarchical structure with types containing groups and groups containing tests. Use this to adjust your stress testing. ================================ Disclaimer for Working Documents ================================ The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Microsoft Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you any license to the patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any written license agreement from Microsoft Corporation. Microsoft does not make any representation or warranty regarding specifications in this document or any product or item developed based on these specifications. Microsoft disclaims all express and implied warranties, including but not limited to the implied warranties or merchantability, fitness for a particular purpose and freedom from infringement. Without limiting the generality of the foregoing, Microsoft does not make any warranty of any kind that any item developed based on these specifications, or any portion of a specification, will not infringe any copyright, patent, trade secret or other intellectual property right of any person or entity in any country. It is your responsibility to seek licenses for such intellectual property rights where appropriate. Microsoft shall not be liable for any damages arising out of or in connection with the use of these specifications, including liability for lost profit, business interruption, or any other damages whatsoever. Some states do not allow the exclusion or limitation of liability or consequential or incidental damages; the above limitation may not apply to you. (c) 1999 Microsoft Corporation. All rights reserved. Direct3D, DirectDraw, DirectInput, DirectMusic, DirectPlay, DirectShow, DirectSound, DirectX, IntelliMirror, MSDN, Microsoft, MS-DOS, Outlook, Visual C++, WebTV, Win32, Win64, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners