During the Upgrade from Windows NT

Because Windows 2000 shares the same architecture as all releases of Windows NT, most value-add software continues to function correctly after the upgrade to Windows 2000. Incompatibilities typically come from value-add software programs that implement filter drivers or have bugs that only become apparent when run on Windows 2000. To solve these issues, Windows 2000 Setup offers an upgrade report. OEMs can provide information for this report to explain what course of action the customer should take.

This report also offers a Have Disk option that allows OEMs to provide a migration DLL to correct the problem.

During the Upgrade from Windows 95/98

The underlying architectures of Windows 95/98 and Windows 2000 are very different. However, because the Win32 API set is the same on both platforms, most applications continue to work after an upgrade. Incompatibilities can stem from reliance on the VxD driver model, dependencies on undocumented or OS-specific APIs, and 32- to 16-bit flat thunks. Platform-specific value-add binaries are also a problem. In some cases, assumptions made about folders, such as the system folder or user profile folders, can cause problems as well. Therefore, the Windows 95/98 upgrade path has a more comprehensive upgrade report, and a more sophisticated migration DLL mechanism (known as "upgrade packs").

You can find programming documentation on the upgrade pack interface in the Beta 3 Win32 SDK (see the most recent MSDN release). Upgrade packs can be pre-installed on your Windows 95/98 factory configurations to ensure a smooth future upgrade to Windows 2000.

While Using Windows 2000

Windows 2000 provides a way to alert users to known problems during the course of its operation using AppsHelp. Windows 2000 displays a message when the user attempts to run an incompatible program that has been added to AppsHelp. Then, when the user clicks the Details button on the message, text from the OEM is displayed.

Windows NT to Windows 2000

In a Windows NT to Windows 2000 upgrade, Microsoft offers the following assistance to OEMs:

• Block upgrades based on the presence of an incompatible OEM value-add service.
• Notify the user of potential incompatibilities, providing a full HTML page (with plain-text version) describing possible workarounds or locations of updates.
• Remove incompatible services on upgrade.

You should add a compatibility message entry for each upgrade message. See below for more information.

Windows 95/98 to Windows 2000

For a Windows 95/98 to Windows 2000 upgrade, Microsoft offers the following assistance to OEMs:

• Nofify the user of possible incompatibilities with the OEM value-add software via the Winnt32 upgrade report
• Remove the Windows 95/98-specific value-add components during installation of Windows 2000
• Notify users of upgrade packs (also known as migration DLLs) available on the OEM’s Web site.
• Helping add a known good entry for a Run key, Uninstall key, and so on.

Compatibility Messages

Microsoft also offers the ability to provide informative messages through Windows 2000. Text messages are displayed when the user launches an incompatible application. The messages can:

• Block the user from running the software.
• Provide a warning, but allow the user to run the software.
• Tell the user to reinstall.

  Bug Reports

When you contact Microsoft for assistance with these issues, please submit one bug per problem. In each bug, provide the following:

Required Information for a Bug Report

1. Contact information, including the person responsible for signing off on the alert and/or modification
2. Your PC product info,
3. OEM ‘Preload’ information, including preload version, service pack versions, etc, using identification terms that Microsoft will understand.
4. A clear description of the incompatibility
5. An attached copy of the value-add software binaries for reference (Microsoft uses these files to generate attributes that Windows 2000 Setup needs to uniquely identify the value-add software.)
   • For Start Menu applications: Right-click on the link and press Properties. Attach a copy of the file referenced in the “Target” field.
   • For Registry “Run” items: Attach a copy of the file referenced in the “Run”
   • For Control Panel applets, dll’s etc: Attach the file in question
6. Attach a Winnt32.log from a reproducing machine for each preload affected
7. A URL to a Web site that has value-add updates or upgrade packs (Make sure this URL will exist well into the future.)
8. Short one-line identifying description of the component
9. Extended text for the message that the OEM wishes to have displayed to the end-user. Provide in both TXT and HTM format.
10. Justification for the request Including an indication of the number of shipped computers that need this fix will help ensure that this issue is addressed in a timely fashion.

Windows NT to Windows 2000 Upgrades

11. Choose one of the following actions for the Windows NT to Windows 2000 upgrade:
    • Block upgrades if value-add service exists
    • Remove value-add service
    • Notify the user only
12. Provide a short title and include company name and product
13. Provide HTML and plain-text documents for any Windows NT to Windows 2000 incompatibility messages.
14. Provide an export of the services key from the registry (HKLM\System\CurrentControlSet\Services)
15. Provide a list of settings used to detect the software. Include any of the following:
    • An export of HKLM\System\CurrentControlSet\Services. Flag which services should be suppressed.
    • Registry Value: Key name, Value name, Expected value
    • Service Name: Service Name, complete path and filename (optional, but recommended), version (optional, but recommended)
    • File Name and Version: complete path and filename, version
    • Complete path and 64-bit version (from version stamp)

Windows 95/98 to Windows 2000 Upgrades

11. Choose one of the following actions for the Windows 95/98 to Windows 2000 upgrade:
    • Notify the user in the upgrade report
    • Remove problem component during upgrade
    • Supply Setup with known good registry settings that currently are removed during an upgrade
12. Indicate the type of user notification, if applicable. Choose one of the following:
    • Value-add software is incompatible.
    • User must reinstall value-add software after migrating to Windows 2000.
    • Minor problem with value-add software (or similar informational message). Provide short text. You can include a URL.

Compatibility Messages

Indicate what type of Windows 2000 compatibility message you would like:

• Block message. Setup will not continue while problem exists
• Notification message. A warning about possible incompatibilities will appear
• Notification message recommending reinstallation of the component after Installation is complete

OEM Expectations

All requests for Windows 2000 actions regarding incompatible applications must be submitted by 6/18/99. Microsoft will make a best-effort attempt to resolve these issues, but makes no guarantees that these requests will go into the Windows 2000 product or support Web page. The more complete and clear your OEM request is, the higher the likelihood that it will be resolved.

If you submit a bug as described above, that application becomes a candidate for migration, removal, or notification. Microsoft would prefer to automatically migrate or remove an application, rather than prompt the user to take some sort of action before the upgrade continues.

Microsoft will not delete any executable in an application upgrade scenario, unless leaving that item will cause data corruption or an unrecoverable. Windows 2000 Setup will not call any uninstall programs for an application.

OEMs should test the upgrade of each factory configuration. Microsoft performs its own testing, but the large quantity of OEM products limits the time spent on each factory configuration. Therefore, Microsoft recommends that you adopt an extensive application compatibility testing matrix.

Example Problem Report

This is an example of a bug report package supplied by Akrony Computers for a Pen Mouse solution that is shipped on both Windows 95/98 and Windows NT 4 preloads. The Pen Mouse solution includes driver (service), a Control Panel applet, and a Start Menu configuration applet.

Contact Information
===================
Tester: Bob Atkinson (BobA@Akronyy.com)
Text Manager: Koi Shetan (KoiS@Akronyy.com)

System Information
==================
Akronyy Otra 333 "Tantrum"
Preload information: Tantrum preload, available from Akronyy.
WINDOWS NT 4.0 + SP3 + Internet Explorer 4.0.

Problem Description
===================
Akronyy Systems provides a Pen Mouse solution on both our Windows NT 4.0 and Windows 95/98 upgrades. The software that comes with this solution is not Windows 2000 compliant and causes minor problems after upgrade.

Akronyy recommends Windows 2000 remove all aspects of this solution that the end-user may see.

We have attached the CPL, EXE called from the Start Menu, and the driver.

Web Site: www.akronyy.com/products/Otra333/PenMouse/

Component Description
=====================
Akronyy Pen Mouse Solution

Notification Text
=================
"The Akronyy Pen Mouse solution that shipped with your Akronyy system is incompatible with Windows 2000. Windows 2000 will replace this with similar functionality.

To remove the Pen Mouse Drivers prior to upgrade:

1. In Add/Remove Programs, choose to uninstall Akronyy Pen Mouse
2. Restart Windows.

For additional information, please see the following Web site: http://www.akronyy.com/products/Otra333/PenMouse/"

More Information
================
This text has been attached to the bug in both TXT and HTML format.

Export of Windows NT 4.0 Services directory is attached, as is Pmouse.sys, Pmouse.cpl.

• For Windows NT 4.0 Upgrades, please REMOVE the service.
• For Windows 95/98 migrations, please REMOVE the CPL, driver and Start Menu links.

Removing this solution will save the user from experiencing a faulting CPL and a broken start menu link.

DOSNET Architecture

This quick overview of DOSNETs architecture are provided so that the OEM can test prospective DOSNET fixes that may be requested of Microsoft.

To setup using a test DOSNET.inf, place the test DOSNET.inf in c:\tmp and install Windows 2000 using the syntax "Winnt32.exe /m:c:\tmp"

In Dosnet.inf, there are two INF section blocks:

[ServicesToDisable]

If an entry is added to [ServicesToDisable], then the user is warned that the entry may not work properly when the system is upgraded to Windows 2000. If the entry is a service, then the service is disabled. If the entry is not a service, then no action is taken, but the user is warned.

[ServicesToStopInstallation]

If an entry is added to [ServicesToStopInstallation], then the upgrade cannot continue. The user will have the option of reading any information provided by the OEM or Microsoft. The user has to exit and then fix the problem before continuing.

In each of these section blocks, incompatibilities can be specified using the following syntaxes.

To detect an incompatibility based on a registry value:

• r,key_name,value_name,expected_value,html_file,text_file,description

To detect an incompatibility based on a service name

• s,service_name,html_file,text_file,description, filename, version

To detect an incompatibility based on a file name and version

• f,file_name,version,html_file,text_file,description

• key_name refers to the complete registry key name under HKLM
• value_name refers to the registry value name
• expected_value refers to the optional value to compare against (equality only)
• service_name refers to the service name as it appears in the registry under services
• file_name refers to the complete path and file name; may contain environment variables
• version refers to the file version, major and minor; for example: "5.1"
• html_file refers to the optional HTML file name; path relative to where Winnt32 is run from
• text_file refers to the text file name, path relative to where Winnt32 is run from
• description refers to the short string describing the compatibility entry

When Winnt32 processes the service type (s) compatibility entry and finds the service present on the machine, it records an entry in the Winnt.sif file for Text-Mode Setup, which processes these entries and disables the bad services and drivers.

When Winnt32 processes the file (f) and registry type (r), the user is notified but no action is taken by Text-Mode Setup. These are considered warnings.

  General

Instructions Install each application on the released OS platform, then upgrade. Perform the following tests following a successful upgrade:

All startup menu program groups and icons for the application are created and work as expected

Save supported file types from application to desktop and test all context menu items

• Print
• Quick View (should be installed)
• Cut/Copy/Delete/Rename
• Create Shortcut
• Properties
• Verify that the app's registered file types function as expected after install, and again after migrating to the test platform
• (Windows 2000 only) After migrating to Windows 2000 (from Windows 95/98 only), check the ""Documents and Settings"" folder to insure profiles and settings migrated correctly.

Taskbar

• Minimize/restore app by clicking on taskbar window button
• Resize and move for apps that utilize systray and/or desktop toolbar
• Verify show desktop button operates as expected with app in foreground. This button is in the quick launch bar.

Recycle Bin

• The Recycle Bin's data format changed from Internet Explorer 4.0 or the Windows 98 Browsing Software to Windows 2000.
• If an application modifies the Recycle bin, do this:
  1. Delete a file with no attributes set
  2. Delete a file with the Read-Only attribute set
  3. Delete a file with the Archive attribute set
  4. Delete a file with the Hidden attribute set
  5. Delete a folder with no attributes set
  6. Delete a folder with the Read-Only attribute set
  7. Delete a folder with the Archive attribute set
  8. Delete a folder with the Hidden attribute set
  9. Restore all files/folders and verify that they are replaced properly

With application in foreground, switch the desktop between Web and non-Web view

Application Functionality

• Input Manager: Try using a mix of keyboard (commonly used accelerators) and mouse when testing
• Test all menus and the options they contained (File, Edit, View, Insert, etc..)
• File Operations
  • File Save
  • File Open
  • File Save UNC (network)
  • File Save LFN with illegal characters like / or : or , etc..
  • File Open UNC
  • Print (with and without driver installed)
• Help - verify Help is functional
• Check taskbar/titlebar context menus

UI Verification

• General
  • Command buttons
  • Option buttons
  • Check Boxes
  • Spin Boxes (up/down control)
  • Toolbar/Button
  • Tooltips
  • Progress Bar
  • Trackbar/Slider
  • Status Bar
  • Icons
  • Tab control (property sheets, etc.)
  • Wizards
• Listview
  • Icons
  • Column headings
  • Checkbox
  • Hot tracking
  • Hot tracking spin buttons
  • Drag drop
• Treeview
  • Tool tips
  • Checkbox
  • Hot tracking
  • Expanding/Collapsing
  • Drag drop

OLE (Object Linking & Embedding)

• General
  • Drag/drop a file from Windows Explorer into the application you are testing if it applies.
  • Drag/drop a file from the application into Windows Explorer.
  • Drag/drop a file from the application into Internet Explorer.
  • Drag/drop app file to printer icon.
  • Perform at least one of the below test cases for each of the following primary test areas:
• Insert objects (use different object each pass)
  • Insert new as an object
  • Insert new as an Icon
  • Create embedded from file as an object
  • Create embedded from file as an icon
  • Create linked from file as an object
  • Create linked from file as an icon
  • Create linked from file as an alternate icon
  • Create Toolbar object links (e.g. drag document to Office toolbar)
  • Reverse insert linked from file
  • Reverse insert embedded
• Paste object
  • Paste as embedded object
  • Paste as linked object
  • Reverse paste as linked object
  • Reverse paste as embedded object
• Activation - Inplace
  • Activate and edit an embedded object
  • Activate and edit an embedded icon
  • Activate and edit a linked object
  • Activate and edit a linked icon
  • Reverse edit a linked object
  • Reverse edit an embedded object
• File Save
  • Save with one or more objects active
• File Open
  • Open a file with an embedded object/icon
  • Open a file with a linked object/icon
  • Change server data and open linked file
  • Open a file with the server file/link deleted
  • Open network file via UNC from Internet address bar
  • Open local saved file from Internet address bar
• Exit App
  • Exit container with active objects
• Mapped and UNC objects
  • Create from file an embedded object from Mapped Network Folder
  • Create from file an embedded object (as icon) from Mapped Network Folder
  • Create from file a linked object from Mapped Network Folder
  • Create from file a linked object (as icon) from Mapped Network Folder
  • Create from file an embedded object from UNC named Folder
  • Create from file an embedded object (as icon) from UNC named Folder
  • Create from file a linked object from UNC-named Folder
  • Create from file a linked object (as icon) from UNC-named Folder
• OLE Scraps
  • Drag selected objects from app to desktop/shell
  • Attempt right-click drag from app to desktop/shell (otherwise, use Edit cut/paste)
  • Drag scrap from shell back to app
  • Cut/Paste scrap from shell back to app
  • Drag scrap from shell to Internet Explorer
  • Drag scrap from shell to WordPad or Microsoft Word^TM
  • Paste Special to Wordpad or Microsoft Word (Try multiple types)

Run each test for each application that supports OLE

• Drag the document onto Windows browsing software
• Enter a file path into the address bar for the document
  • Modify and save the document
• If applications support browsing, open an Internet document in the application
• If applications support browsing, create a hyperlink in the document and then launch it in place by clicking on the link.
• Active document hosting is another name for document object (docobj) which is completing the Microsoft concept of a document-centric design
• Microsoft Office, Visio, and Micrografx ABC Graphics Suite are examples of apps that support this technology. Examples include:
  • Launching a Microsoft Excel^TM document from a file link in the Internet Explorer, will cause the document to be opened in-place. When launching a document in-place, all menus are integrated within the client frame, which in this case is Internet Explorer.
  • Drag an Excel document into an open Windows browsing software window. The document should be opened in-place; this will cause Excel menus and toolbars to be integrated into the browser. You should be able to use back and forward buttons to navigate back to the web and back to the document. If document was modified, it should prompt you to save as well.
  • Browse to web sites such as http://www.microsoft.com

  Communication

Test a communications application.

Fax

• Send fax: text/binaries/attachments
• Receive Fax: text/binaries/attachments
• OCR
• Print to fax from another app
• Fax from another app

Terminal and FTP

• Send or Post binaries/ASCII files
• Download/Receive binaries/ASCII files
• AT commands
• File transfer protocols: Xmodem, Ymodem, Kermit, Zmodem

Browsers

• Proxy and DUN connection
• Download/Open file
• Scripting: Test Scripting, Microsoft ActiveXand#174;, and Java applets
• Multiple Windows Stop and Refresh multiple times
• Default browser settings
• Run URL from command line
• Launch local file in browser
• Test bookmarks/favorites functionality after upgrade and add/delete
• Microsoft ActiveX security settings
• Search functionality,
• Open JPEG, TIFF, BMP, WAV, MID, AU, AIF, MPG, MOV, GIF
• Mail: Send and receive
• Newsgroups: Read and Post
• Default settings remain after upgrade
• User should be able between hyperlinks, or on form buttons, go Back with , go Forward with , , , etc.
• Verify Back, Forward, Stop, Refresh, Home, Search, Favorites, Print, Font, etc. browser buttons work

Remote Control

• Connect via modem, DCC, and Internet
• Connect and test over LAN with IPX and TCP/IP protocols
• Blank screen, reboot, send shortcut keys
• Host/client multi-platform
• Security Passwords
• File transfer
• Chat/whiteboard

NewsReaders\Tickers

• Subscribe
• Update Newsgroups and Schedule update
• Post
• Offline viewing
• Verify settings and content after upgrade
• Un-subscribe (cancel subscription)

Chat

• Initiate and Join chat session
• Voice
• Video
• Whiteboard

Streaming Media

• Test Audio and Video
• Multiples
• Browser and Stand alone
• Netscape
• Proxy and DUN when supported
• Defaults remain after upgrade

Messaging

• Send e-mail: text/binaries/attachments
• Receive e-mail: text/binaries/attachments
• Hyperlink functionality
• Attachments open with appropriate application (Microsoft Excel, Microsoft Word, etc.)
• MIME/UUENCODE
• Default settings remain after upgrade

  Software Developer

Open a project/program file

• Open a new project
• Open an existing project

Place visual objects

• Place a Label
• Place a Radio button

Edit visual object

• Insert text in Label
• Edit code associated with the object inserted

Save project

• Save project to a local drive
• Save project to UNC path

Compile code to exe

• Compile a new project to EXE
• Compile an existing project to EXE

Run code in interpreter

• Run a new project to the Run-Time environment
• Run an existing project in the Run-Time environment

  Internet Developer

Connect to a Web server

• Connect to a Web server inside the corporate firewall
• Connect to a Web server outside the corporate firewall

Open web files

• Open an HTML file
• Open an ASP file

Edit Web files

• Make changes to an existing HTML document
• Make changes to an existing ASP document

Publish to a Web server

• Publish to a Web server inside the corporate firewall
• Publish to a web server outside the corporate firewall

Publish to a local drive

• Publish to port 80 on the local machine
• Publish to a drive letter

  Business

Installation/Start

• Typical OS Install
• Default Settings
• Typical Application Install

Application/File Menu

• File New
• File Save
• File Open
• File Print

Application/Edit Menu

• Edit Cut
• Edit Copy
• Edit Paste

Applications/Help Menu

• Help Start
• Help Find

Font manipulation

• Open any document with modifiable text such as a word processor, spreadsheet or accounting program
• Select text and change font size
• Select text and change to bold font
• Select text and change to italic font
• Select text and underline selection
• Select text and change font type (style)

  Utilities

Installation/Start

• Typical OS Install
• Default Settings
• Typical Application Install

Application/File Menu

• File New
• File Save
• File Open
• File Print

Application/Edit Menu

• Edit Cut
• Edit Copy
• Edit Paste

Applications/Help Menu

• Help Start
• Help Find

  Games

Install application

• Install game with default settings
• Install game with different installation types (compact vs full...)
• Install and play game on machine with multimon
• If prompted to install older version of Microsoft DirectX®, answer 'yes', verify no changes were made to Microsoft DirectX® version

Shortcuts

• Try all shortcuts made in Start Menu, like register game, view readme...

Launch application

• Start game from desktop shortcut
• Start game from CD autorun
• Start game from Start Menu
• Start game from HD installation directory
• Start game using any supported 3D options
• Start game using main 2D/3D video device vs 3DFX (use a 3D switching shareware program to select default 3D device)
• Start game using software mode, if supported

Play game

• Play game in each supported resolution
• Play game with various joysticks (USB, Serial, Mouse, Keyboard control)
• Play game with various audio devices (USB, WDM, VXD[Windows 95/98])
• Try game with all supported networking options (TCP/IP, IPX, Serial, Online)
• Play game networked between two different operating systems

Toggle functions while playing the game

• Once into the game, try the Windows shortcut keys (ALT+TAB, ALT+ENTER, Windows Key, Windows Key + shortcut Keys, etc.)
• ALT+TAB back to game
• ALT+TAB out, click on taskbar icon to return to game

Save game

• Save game to hard drive, try to restore it
• Save game to network share, try to restore it

Exit and return

• CTRL+ALT+DEL on Windows 2000 to bring up the log off or lock dialog, cancel and try to return to game
• CTRL+ALT+DEL to bring up log-off/lock computer dialog if in Windows 2000, lock computer, log back on and try to return to game

Play game in different modes

• Try playing game when starting with a different screen resolution
• Try playing game with active desktop enabled

Uninstall application

• Uninstall game

  Multimedia

Creation/Editing

• Open all supported formats
  • Local
  • Network
• Close all supported formats
• Save all supported formats
  • Local
  • Network
• Edit pertinent formats
• Link pertinent format file with another
  • Same format
  • Different format
• Use and save files using all pertinent filters and FX
• Scanner input
• Midi device input
• Pen device input
• Drawing pad input
• Camera input
• Camera capture input

Learning/Entertainment

• Confirm proper information displayed
• Verify sound capabilities working

  Multimonitor

App Placement

• Open the app and move it around the screens.
• Close then reopen app and see if it opens in same monitor or in main monitor

Window Size

• Open the app and stretch it to cover as many monitors as possible
• Maximize window in each monitor
• Minimize window in each monitor

Color Depth/Screen Size

• Change color depth and screen size on all monitors

  Power Management

Control Panel

1. Open Control Panel/Power Management
2. Change turn off time for monitor to 1 minute
3. Change turn off time for hard disk to 2 minutes

Application functionality

1. Start application, let app run without keyboard or mouse intervention until the monitor turns off ("goes to sleep")
2. Move your mouse or press a key on the keyboard. Does the application return with expected display and sound?
3. Start application, let app run without keyboard or mouse intervention until the hard disk turns off ("goes to sleep")
4. Move your mouse or press a key on the keyboard. Does the application return with expected display and sound?

  Display Resolution

Activate DynaRes Icon in Systray

• Open Display Properties/Settings/Advanced and select "Show settings icon on task bar"

Application functionality

1. Launch application with default monitor resolution
2. Right click on Settings icon in systray
3. Change resolution up or down
4. Verify application performs and displays as expected

  Wheel Mouse

Manual scrolling

• Open any text document and using the wheel on the mouse, scroll up, down and sideways. Does the document scroll?

Automated scrolling

1. Open any text document and click the mouse pointer anywhere on the document
2. Move the mouse up, down or sideways and let go. Does the document automatically scroll in the direction you moved the mouse?

  Multiple Applications

Multiple applications running

1. Launch at least three applications
2. Send one application to print to file
3. Send one application to print to prn
4. Copy, paste and edit the third application

Multiple instances

1. Launch any application
2. Attempt to open the same application again, if available, through another means than the first launch. For example, use the desktop icon instead of the Start menu.

  Y2K

Testing functionality with date transition from 1999 to 2000

1. Install the application
2. Change system date to 12/31/99
3. Change system time to 5 minutes to midnight (23:55 or 11:55 pm)
4. After system clock has passed midnight and date has changed to 01/01/00, launch the application

Testing functionality after the year 2000

1. Change system date to 01/01/00 or later
2. Install and launch the application

Applications containing date functions

1. With system date set to current or any date before 01/01/00, install and launch the application
2. Change the date inside the application to 01/01/00 or later
3. With system date set to 01/01/00 or later, install and launch the application
4. Change the date inside the application to 01/01/00 or later

Displaying 4 digit dates

1. In the Regional Options from the Control Pannel, change the Short Date format from D/M/YY to D/M/YYYY.
2. Install and run the application.
3. Verify that the application displays the 4 digit date in a manner that is visible and correctly formatted.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  3rd Party Services

This test will verify the operation of system services written for previous versions of Windows.

• Install 3rd party software that uses a system service. (i.e. anti-virus, backup, etc.)
• Verify that the service loads, and that dependant functions are operational.

This test is considered successful if the software that installs and utilizes the service functions correctly.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  Driver Verifier

The Driver Verifier is a series of checks added to the Windows 2000 kernel to help readily expose errors in kernel mode drivers. Drivers must follow complex rules to safely interact with other drivers and operating system components. A slight deviation from these rules may result in some kind of corruption that is often difficult to reproduce or trace back to the errant code. The goal of the Driver Verifier is to expose and easily pinpoint errant driver code.

The Driver Verifier consists of three techniques:

• Detecting buffer overrun and underrun by use of a special pool
• Unmapping paged memory when raising an IRQ level (IRQL) to DISPATCH_LEVEL
• Enforcing read-only memory protection

For additional information, please visit http://www.microsoft.com/hwdev/driver/driververify.htm.

By default, the Driver Verifier is randomly enabled on two to five drivers at startup. Enabling all drivers at once is not supported. For best results, enable the Driver Verifier for one driver at a time, focusing on drivers you are shipping that will not be in the Windows 2000 box. To do so:

1. Run the Driver Verifier Manager, Verifier.exe.
2. Select the Modify Settings tab and choose the Verify Selected Drivers radio button.
3. Select the drivers that are not shipping in the Windows 2000 box and click the Verify button.
4. If you are shipping more than one driver that Windows 2000 will not support natively you should ensure each is tested. For example, enable the Driver Verifier for the first driver on the upgrade test pass, and then the second driver on the clean install.

If a driver does trigger a Driver Verifier bugcheck, debug the system to identify the failing driver. Driver Verifier bugchecks include:

• IRQL_NOT_LESS_OR_EQUAL (0xA)
• PAGE_FAULT_IN_NONPAGED_AREA (0x50)
• ATTEMPTED_WRITE_TO_READONLY_MEMORY (0xBE)
• SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (0xC1)
• DRIVER_VERIFIER_DETECTED_VIOLATION (0xC4)
• DRIVER_CAUGHT_MODIFYING_FREED_POOL (0xC6)
• TIMER_OR_DPC_INVALID (0xC7)

For additional information concerning the configuration of the debugger:

• Refer to Microsoft Knowledge Base article Q151981, "How to Set Up a Remote Debug Session Using a Null Modem Cable."
• Query the Microsoft Knowledge Base using the keyword, "debugref," for the Kernel Debug How To articles.
• Visit http://www.microsoft.com/hwdev/driver/windbg.htm for information concerning the setup and configuration of WinDbg.

The test is considered successful if all verified device drivers complete the test pass without failing.

  Multimonitor Support

1. Before performing this test, verify that the installed display adapter is multimonitor compatible and is running at least 256 colors.
2. Shut down the system and install a second display adapter and monitor. Disable VGA for the second display adapter. Refer to the hardware documentation from the adapter vendor for information on disabling VGA.
3. Turn on both monitors and boot the system. Windows should detect and install the new display adapter. If not, run the Add Hardware Wizard to install support for the adapter.
4. Once both adapters are installed, go to Display Properties/Settings. Select monitor 2, and check the Extend my Windows desktop to this monitor box.
5. Configure resolution, color depth, and relative positions as desired, and then restart the system.
6. Verify that multimonitor capabilities work as expected.

This test is considered successful if both monitors initialize and can be configured.

  USB

Simultaneously attach a series of USB devices in a chain to test USB.

Verify the following:

• All devices on the chain are detected.
• All devices on the chain function.
• Devices to attach should include: Mouse, Keyboard, a minimum of 1 hub, a game controller, a streaming device (i.e. camera or speaker), and a bulk device (i.e. a drive or scanner)
• Each USB hub is detected as a device.
• Verify devices work on all available ports.
• Operate multiple devices simultaneously, including at least a HID device, a streaming device, and a bulk device. For example, run a Microsoft Netmeeting^TM conference using a USB camera, microphone and speakers over a USB modem or network adapter.
• On systems providing real-mode USB keyboard support, enter and navigate the BIOS using the keyboard.

HID Devices

• Keyboard
• Mouse
• Fingerprint Scanner
• Game Controller

Streaming Devices

• Camera
• Speakers

Bulk Devices

• Modem
• Drive
• Network Adapter
• Printer
• Scanner

The test is successful if you can verify that the USB bus can be stressed without errors.

  1394

Test a series of IEEE 1394 devices simultaneously. Verify:

• All devices on the chain are detected.
• All devices on the chain function.
• IEEE 1394 camera continues to function after upgrade.

The test is successful if the IEEE 1394 devices function properly.

Note   

Windows 2000 natively supports IEEE 1394 cameras and IEEE 1394 storage devices. Windows 98 did not provide native support, so note 3rd party IEEE 1394 solutions and determine what, if any, functionality is lost after upgrading.

  Network Adapter

In Device Manager, select Network Adapters. Verify:

• All installed network adapters are detected correctly.
• Device Manager does not report a conflict for any installed device.
• All installed network adapters are functioning.
• Connect to a network share, transfer files, browse the network, and perform any additional network functions to verify connection.
• If more than one network adapter is installed on the system, each adapter should be tested individually.
• Disable additional adapters by selecting the adapter and then selecting Action/Disable in device manager.

This test is considered sucessful if device manager shows no conflicts and you are able to browse the network and transfer files successfully.

  SCSI/IDE Controllers

In Device Manager select IDE ATA/ATAPI Controllers. Verify:

• All installed controllers are detected correctly.
• Device Manager does not report a conflict for any installed device.
• All controllers are functioning.
• All devices or drives attached to the controllers are accessible.
• Repeat for SCSI and RAID Controllers.

This test is considered sucessfull if Device Manager shows no conflicts and drives attached to the controllers are accessible.

  Multimedia Controllers

In Device Manager, select Sound Video and Game Controllers. Verify:

• All installed multimedia devices are detected correctly.
• Device Manager does not report a conflict for any installed device.
• All multimedia devices are functioning.
• Play .wav, .mid, .mpg, .avi and other media types supported by the device.

This test is considered successful if Device Manager shows no conflicts and supported media types play successfully.

  DVD

In Device Manager, select DVD/CD-ROM Drives. Verify:

• All installed DVD drives are detected correctly.
• Device Manager does not report a conflict for any installed drive.
• All DVD drives are functioning.
• DVD movies play back (if the DVD device supports this capability).

This test is considered successful if Device Manager reports no conflict and supported media types play correctly.

  Modems

In Device Manager, select Modems. Verify:

• All installed modems are detected correctly.
• Device Manager does not report a conflict for any installed modem.
• In Modem properties select More Info for the modem and note any errors.
• For each installed modem, dial up a RAS server, connect with a remote network, connect to the Internet, and perform any additional modem functions to verify the connection.

This test is considered successful if Device Manager shows no conflicts and the modem successfully dials and connects to a remote system.

  Mice and other Pointing Device

In Device Manager, select Mice and Other Pointing Devices. Verify:

• All installed pointing devices are detected correctly.
• Device Manager does not report a conflict for any installed device.
• All pointing devices are functioning.

This test is considered successful if Device Manager shows no conflicts and mouse movement and all mouse buttons function.

  Keyboards

In Device Manager, select Keyboards. Verify:

• All installed keyboards are detected correctly.
• Device Manager does not report a conflict for any installed device.
• All keyboards are functioning.

This test is considered successful if Device Manager shows no conflicts and the keyboard is functional.

  Ports

In Device Manager, select Ports. Verify:

• All ports are detected correctly.
• Device Manager does not report a conflict for any installed device.
• All ports are functioning.

This test is considered successful if Device Manager shows no conflicts and the ports are functional.

  Smart Cards

In Device Manager, select Smart Card Readers. Verify:

• All installed smart card readers are detected correctly.
• Device Manager does not report a conflict for any installed device.
• All smart card readers are functioning.
• Read data from, and program data into a smart card to verify that it is working correctly.

This test is considered successful if Device Manager shows no conflicts and you are able to read data from and write data to the smart card.

  Display Adapters

In Device Manager, select Display Adapters. Verify:

• All installed Display Adapters are detected correctly.
• Device Manager does not report a conflict for any installed adapter.
• Open the Display Properties and change display resolution and color depth. Return to the original settings.

This test is considered successful if Device Manager shows no conflict and the primary display adapter can successfully change display resolution and color depth. If a secondary display adapter fails, please list the failure under Multimonitor Support.

  System Devices

In Device Manager, select System Devices. Verify:

• Installed system devices are detected correctly.
• Device Manager does not report a conflict for any device.
• All system devices are functioning.

This test is considered successful if Device Manager shows no conflict(s).

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  D3D Retain Mode

Test Microsoft Direct3D® retain mode

1. Run Globe.exe.
2. Verify textures in tunnel are loaded.
3. Exit by pressing the ESC key.

The test is successful if the sample launches and textures load. You should see a spinning globe with yellow and black radioactive symbols.

  D3D Immediate Mode

Test Microsoft Direct3D® Immediate Mode.

1. Run Tunnel.exe.
2. Verify textures in tunnel are loaded and frame rate is counted at top of window. The sample will run differently depending on the capabilities of the display adapter in the system and its drivers. No other selections need to be made inside the sample to touch the surface of the hardware and driver Direct3D functionality, although you are welcome to report any problems you encounter in doing so.
   • The sample is running in acceleration if selection under File menu is Direct3D HAL.
   • The sample is running in emulation if selection under File menu is RGB emulation.
3. Exit by pressing the ESC key.

The test is successful if the sample launches and textures load. You should see a moving tunnel with yellow and black radioactive symbols.

  Ddraw and Dsound

Test Microsoft DirectDraw® and DirectSound®.

1. Run Foxbear.exe.
2. Verify sample runs in full-screen and will perform mode switches after hitting F6.
3. Verify sounds are played when fox jumps after hitting home key or when fox is eaten by bear.
4. Exit by pressing the ESC key.

Test is successful if sample launches in full screen, performs at least 1 mode switch, and plays sound.

  Media Playback

Test Windows Media Playback.

1. Run Wmtst.exe.
2. Click the Tests menu and then select Run Tests from the file menu.
3. Watch the video clips run.
4. Examine the Status at the bottom of the Media Playback Test Application's display, or the Wmtst.log in the working directory, to determine if the test passes.

The test is successful if the media clips load and play.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  Local Install

Printer Installation

• With the computer in a powered off state attach a printer to the systems parallel port.
• Turn on the system, during OS startup the system should detect and install the printer.
• If the drivers for the printer are not shipped with Windows 2000, you will be prompted for the printer driver disks.
• Install multiple drivers on the same system for printers using a combination of LPT, I/R, and USB ports.
• Install both the OEM's printer driver, and the Windows 2000 driver and attempt to use them both.

This test is considered sucessfull if the printer successfully installs and displays no errors.

  Local Port

Test printing in Windows.

Print Test Page

• Open the printer folder from My Computer.
• Right-Click the desired printer, select properties from the pop-up menu.
• From the General tab, click the Print Test Page button.

Print *.bmp files from Paint

• Run MSPaint.exe.
• Open a bitmap (*.bmp) in the Windows directory.
• Select Print on the File menu.
• Print the bitmap.

Print *.doc files from WordPad

• Run WordPad.exe.
• Open a formatted document, such as %windir%\WOSTest\docs\SysParse.doc.
• Select Print on the File menu.
• Print the formatted document.

Print *.txt files from Notepad

• Run Notepad.exe.
• Open a text file (*.txt) in Notepad.
• Select Print on the File menu.
• Print the text file.

Print to File

• When printing, check the Print to File box.
• When prompted for a filename, type "C:\TestFile.prn" and click OK.
• At a command prompt, copy the file to the printer port (ie. LPT1) to ensure it was successfully created.

Print *.htm from Windows 2000 Browsing Software

• Click this Web page.
• Select Print on the File menu.
• In the Page Range, select the radio button for Pages and ensure it is set to 1.
• Print the Web page.

This test is considered successfull if all testing scenarios print out as expected.

  Point and Print

Test Point and Print on client and/or server.

Server

1. The printer associated with driver being tested should be installed as a local printer, using the Add Printer Wizard from printer folder.
2. Add additional drivers for that printer (either from Printer Properties, Sharing - Additional driver or from printer folder - Server Properties - Drivers - Add)

Client

1. Create a connection to server printer (run Add Printer Wizard for connection)
2. Print a test page

The test is successful if the following requirements are met:

• After connecting to server printer, on client printers folder should appear a printer icon with the following text: printer_name ON server_name
• Driver files should be under %windir%\system32\spool\drivers\w32x86 if client is an X86 or %windir%\system32\spool\drivers\w32alpha if client is an Alpha.
• The printed test page should appear on both client and server queue after printing

  Driver Management

Test printer driver management.

Test steps: locally or remotely

1. Add/delete/update/see properties (from printer folder - server properties - Drivers tab- Add / Remove / Update / Properties buttons)
2. Add additional drivers for a given printer (from printer properties - sharing - additional driver)

Expected results

• Driver files should be under %windir%\system32\spool\drivers\w32x86 if the driver is for an X86, and %windir%\system32\spool\drivers\alpha if the driver is for an Alpha.
• The next sub-directory is:
  • \3 if driver = Windows 2000
  • \2 if driver = Windows NT4
  • \1 if driver = Windows NT3.51 /3.1
  • \win40 if driver is for Windows 95/98

The test is successful if the administrator can successfully install, update, and delete a printer driver remotely or locally.

  ICM

Test Image Color Matching.

ICM Features

Upon installation of the driver, the appropriate profile(s) for the available media must be loaded into the Winnt\system32\spool\drivers\color folder and installed onto the system. A printing device driver implementation of ICM2 color management should be able to perform the following and/or provide control of any or all of the following features through the UI:

• Enable or disable color management. This may be the preferred implementation because it is the easiest for the customer. In this implementation, the OEM needs to verify that the appropriate functions described below, 2-7, occur in the code and transparent to the user.
• Source Profiles. Define a source color space or profile for color graphics in the document being printed. Source profiles for graphics in a document can be defined for individual images (bitmap, raster) and vector graphics (postscript, illustrative) depending on the driver specifications. ICM currently specifies this globally. Default for ICM is the sRGB color space profile and will be the source used for testing in this document.
• Destination Profiles. Define the profile of the media on which the document will be printed. This is the "destination" ICC profile. In this case the OEM may use separate profiles or may have a different method of mapping to the different media.
  1. Rendering Intents
     Set the rendering intents (perceptual, relative colorimetric, saturation, and absolute colorimetric). Optionally these can be set for image data or computer-generated color elements separately.
  2. Simulation Profiles (optional)
     For the purpose of proofing, it is necessary to provide a third ICC profile that defines the color space of the device used for the final output of the document, such as a printing press or a proofer. This is used when the user would like to use an inexpensive and/or local printer to simulate a press or film proofer.
  3. Embedded Profiles (optional)
     Recognize embedded profiles in image files. Applies to *.tif images or images written with V5 header information (not currently supported for testing currently.

Testing Requirements

1. Obtain or create test images that are in the sRGB color space. Microsoft Imaging for Windows and Photoshop 5.0 are good tools for doing this if such images are not already available.
2. Obtain or create illustrative artwork in sRGB space. MS paint, current versions of Illustrator or Freehand are good tools for this.
3. Create test documents that contain the test images and illustrative artwork.
4. Obtain or create known good printer and proofer/press profiles, good generic profiles.
5. Acquire miscellaneous, printer, and generic RGB and CMYK profiles loaded into the color folder and installed into the system.
6. The Microsoft sRGB or other known good ICM compliant sRGB profile must loaded into the color folder and be installed into the system.
7. The Windows NT displays control panel should be set to the profile of the monitor. Optimally, the monitor could be calibrated to 6500 Kelvin at a gamma of 2.2 and a custom profile generated after calibration. If this is not available, a monitor running at 9300 with an appropriate profile is acceptable.
8. Optimize the viewing conditions of your prints so they can be viewed with as little cast as possible. For example, use natural light or, optimally, a viewing booth.
9. Connect the printer locally to the system.

Test Case 1-Component installation

1. Install NT5 and the driver. Confirm that the driver files have installed correctly and that the appropriate .icm file(s) have been installed into the Winnt\system32\spool\drivers\color folder, are installed into the system, and that the icons are white.
2. Right click on the .icm file icon and do an uninstall profile. Confirm that the profile icon turns grey.
3. Right click on the .icm file icon and do an install profile. Confirm that the profile icon turns white.
4. Right click on the .icm file icon and do an associate. Associate the profile to the printer and remove the association to the printer confirming that no errors occur.

Test Case 2- On or Off

1. Turn off color management in the application (if the application supports ICM) so that only the driver controls this function.
2. Turn off or disable color management in the driver.
3. Print the image and illustration document without color management and set the document aside for comparison.
4. Turn on or enable color management in the driver.
5. Print the image and illustration document with color management.
6. Confirm that the results are an improvement relative to the print made with no color management OR that in the case where improvement made be subjective that option for color management provides an additional good choice for the customers preferences.
7. Repeat steps 1 through 6 for each type of media available for the printer.

Test Case 3- Source Profiles

1. Turn off color management in the application (if the application supports ICM) so that only the driver controls this function.
2. Open a document with test images.
3. Access the print driver/ color management dialog and confirm the default source color space is sRGB.
4. Set the rendering intent to perceptual.
5. Print the document to the printer with the destination and simulation profiles set to none. Mark the document accordingly and set it aside for comparison.

Case 4- Destination Profiles

1. Turn off color management in the application (if the application supports ICM) so that only the driver controls this function.
2. Open document with test images.
3. Access the print driver/ color management dialog and confirm the default source color space is sRGB.
4. Set the rendering intent to perceptual.
5. Set the destination to the known good printer profile, simulation to none and print the document.
6. Confirm that all profiles for this printer appear.
7. Confirm that the document printed is different and that the result is improved from the result in test case 1.
8. Confirm that the resulting print is reasonably close to the display and closer to the display than not using ICM. Take into careful consideration the viewing conditions under which the comparison is being made.
9. If your driver permits, try using a profile for a different printer. The results should be a mis-mapping of the colors.

Case 5- Rendering Intents

1. Turn off color management in the application (if the application supports ICM) so that only the driver controls this function.
2. Open document with illustrative artwork.
3. Access the print driver/ color management dialog and confirm the default source color space is sRGB.
4. Set the rendering intent to Saturation.
5. Set the destination to the known good printer profile, simulation to none and print the document.
6. Confirm that all profiles for this printer appear.
7. Confirm that the document printed is different and that the result is improved from the result in test case 1.
8. If your driver permits, try using a profile for a different printer. The results should be a mis-mapping of the colors.
9. Repeat steps 10-14 using the remaining available rendering intents.
10. Compare the prints and confirm the appropriate results for vector artwork.

Case 6- Simulation Profiles

1. Turn off color management in the application (if the application supports ICM) so that only the driver controls this function.
2. Open document with test images.
3. Access the print driver/ color management dialog and confirm the default source color space is sRGB.
4. Set the rendering intent to perceptual.
5. Set the destination to the known good printer profile.
6. Set the simulation to a proofer/press profile and confirm that all proofer/press profiles that are installed appear in the dialog.
7. Print the document.
8. Confirm that the document printed is different from the result in test case 1 and 2 and that it appears closer to the actual proof/press print than the prints from case 1 or 2.

The test is considered successful if all pertinent tests can be completed without errors.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  Startup

Test Windows normal startup. The test is considered successful if Windows starts and the user logs in without errors.

  Shutdown

Test Windows normal shutdown. The test is considered successful if Windows shuts down without errors or hanging.

  Safe Mode with Networking

From the Windows 2000 boot menu, press F8 and select Safe Mode with Networking from the Advanced Options menu. Verify:

• System successfully boots Safe Mode with Networking.
• Devices supported by Safe Mode function (ie. keyboard, mouse, display, etc.)
• Network drivers are loaded and the system logs on.

This test is considered successful if the system boots into Safe Mode and can access the network.

  Last Known Good Configuration

From the Windows 2000 boot menu press F8 and select Last Known Good Configuration from the Advanced Options menu. Verify:

• System boots into last known good configuration.
• Hardware Profile/Configuration menu is presented.

The test is successful if Windows boots through to the desktop.

  Boot Safe Mode

From the Windows 2000 boot menu press F8 and select Safe Mode from the Advanced Options menu. Verify:

• System successfully boots in Safe Mode.
• Devices supported by Safe Mode function.(ie. keyboard, mouse, display, etc.)

This test is considered successful if the system boots into Safe Mode.

  Safe Mode Command Prompt

From the Windows 2000 boot menu press F8 and select Safe Mode with Command Prompt from the Advanced Options menu. Verify:

• System successfully boots Safe Mode with Command Prompt.
• Devices supported by Safe Mode function (ie. keyboard, mouse, display, etc.)
• The command prompt window opens.

This test is considered successful if the system boots into Safe Mode and the command prompt window opens.

  Debug Mode

Test Debug mode on Windows 2000 Server, Advanced Server, or Datacenter. This option is not available on Windows 2000 Professional.
From the Windows 2000 boot menu press F8 and select Debug Mode from the Advanced Options menu.

The test is a success if the system successfully boots into Debug Mode.

  Repair Command Console

The command console is integrated into Windows 2000 text-mode and can be started from the following paths:

1. After booting using the Windows 2000 Startup floppies or the Windows 2000 CD-ROM, press the function key, F10 when the Welcome screen appears to start the console. Or select it from the Repair options.
2. Winnt32 will have a /cmdcons switch that will add an entry to the OS Loader for the console. In this case the system will boot straight to the console. (The user does not need to press F10)
3. When the console is started you will be prompted to select a Windows 2000 installation to log into as Administrator. You then have access to a restricted set of commands to repair the installation. HELP prints a list of available commands.

The test is successful if Windows 2000 boots to the repair command console.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  File System Conversion

This test will convert a previously formatted partition to NTFS5.

• Type conversion of the file system is done with the convert utility, which will convert a FAT volume to an NTFS volume.
• The command line is:

  convert[drive:]/fs:ntfs[/v]

This test is considered successful if conversion the file system conversion completes with no errors.

  Defrag

After setup or file system conversion, run Defrag. Verify:

• Defrag completes successfully.
• There are no errors.

The test is successful if there are no errors.

  Chkdsk

This test should be run following setup or file system conversion.

From the Storage tab in WOSTest select Chkdsk. This will launch Chkdsk in a command prompt window. Allow chkdsk to complete.

This test is considered successful if Chkdsk completes without errors.

  Dual-Boot

Test Windows 2000 dual boot with Windows 95/98.

1. Minimum of two partitions required.
2. Install Windows 95/98 to one partition.
3. Install Windows 2000 to second partition.
4. Boot to Windows 2000 and Windows 95/98 to verify dual boot support.

The test is successful if Windows 2000 starts and Windows 95/98 starts.

  Create NTFS Partition

Using unallocated space, create and format a NTFS partition. The test is successful if you can copy a file to the newly created partition.

  Create FAT32 Partition

Using unallocated space, create and format a FAT32 partition. The test is successful if you can copy a file to the newly created partition.

  Create FAT16 Partition

Using unallocated space, create and format a FAT16 partition. The test is successful if you can copy a file to the newly created partition.

  Remote Disk Management

This test evaluates Remote Disk Administration.

• To run remote disk administration, both systems must be on the same domain or trusted domain.
• The user must be a member of the Administrator or Server operator group on the remote computer.

To test Remote Disk Administration:

1. Open the Microsoft Management Console in author mode.
   • Click the Start button and choose Run.
   • Type MMC.EXE /A and press the Enter key.
2. Select Add/Remove Snap-in from the Console menu.
3. With the Console Root selected, click the Add button.
4. Click Disk Management, click Add, select Another computer.
5. Type the name of the remote computer, click Finish and then Close the dialog.
6. Click OK to return to MMC in author mode.
7. Choose Exit from the Console menu. When prompted, save the settings as C:\OTK.msc.
8. Run MMC.EXE C:\OTK.MSC.
9. To manage the remote disk(s), click Disk Management(computer name).

The test is considered successful if you can manage the remote system's disks.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  Wake by Keyboard or Mouse

Test resume Wake from Keyboard or Mouse.

1. On Start menu, choose Shutdown.
2. Choose Standby from the list of shutdown options.
3. Use the mouse or keyboard to resume from Standby.
4. Test each hardware device to ensure the drivers support power management. For example, copy a file to a network share and play a sound.

This test is considered succesful if the system wakes and all devices are functional.

  Standby and Resume

Test resume from Standby.

1. On Start menu, choose Shutdown.
2. Choose Standby from the list of shutdown options.
3. Resume from Standby.
4. Test each hardware device to ensure the drivers support power management. For example, copy a file to a network share and play a sound.

This test is considered successful if the system resumes and all devices are functional.

  Hibernate and Resume

Use Hibernate to test drivers' ability to resume from Standby

1. In Control Panel, open Power Options.
2. Select the Hibernate tab.
3. Enable Hibernate support and click OK.
4. On Start menu, choose Shutdown.
5. Choose Hibernate from the list of shutdown options.
6. Power off the system when prompted to do so.
7. Turn the system on and allow it to resume from Hibernate.
8. Test each hardware device to ensure the drivers support power management. For example, copy a file to a network share and play a sound.

This test is considered successful if the system resumes and all devices are functional.

  APMStat

Click the hyperlink for APMStat to run the tool that inspects the APM BIOS. The test is considered successful if APMStat does not find fault with the APM BIOS.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  ACPIEnable

Test to determine if the system can run Windows 2000 with ACPI enabled.

Good BIOS List or BIOS Date >= 1/1/99

• ACPIEnable = 2 in Txtsetup.sif (default).
• Setup completes without ACPI related errors.
• ACPI enabled in Windows 2000.

Disable ACPI List

• ACPIEnable = 2 in Txtsetup.sif (default).
• Setup completes without ACPI related errors.
• ACPI is disabled.

BIOS Date < 1/1/99

• Set ACPIEnable = 1 in Txtsetup.sif.
  1. On the test system, open a command prompt and change to the root directory of the C:\ partition by typing CD\ and then press the [Enter] key.
  2. On the test system, make a directory by typing MD OTK and then press the [Enter] key.
  3. Change to that directory by typing CD\OTK and then press the [Enter] key.
  4. Copy the file Txtsetup.sif to the \OTK directory from the \i386 directory on the Windows 2000 CD-ROM. For example, you would type COPY D:\i386\Txtsetup.sif and press the [Enter] key if the CD-ROM were drive D:\.
  5. Type Edit Txtsetup.sif and press [Enter].
  6. Open the Search menu with [Alt] + S and then press F for Find.
  7. Type ACPIEnable = 2 and press [Enter].
  8. Set the value to ACPIEnable = 1.
  9. Choose Save from the File menu, and then Exit.
• Run Winnt32.exe /m:c:\otk when upgrading, or Winnt.exe /m:c:\otk on clean installs.
• Setup completes without ACPI related errors.
• ACPI enabled in Windows 2000.

The test is considered successful if the system completes the appropriate checklist without errors. If the test is not successful, please run ABIOSDMP.EXE and include its log file in your bug report.

• To run ABIOSDMP.EXE on Windows 95/98, go to a command prompt and type %windir%\Wostest\Tools\Fat32ebd\ABIOSDMP.EXE > C:\ABIOSDMP.TXT.
• To run ABIOSDMP.EXE on a Windows NT 4.0 system, you must use a MS-DOS boot disk. To create a boot disk, run %windir%\Wostest\Tools\Fat32ebd\Makedisk.BAT. Boot using the floppy to automatically run ABIOSDMP.EXE and generate C:\ABIOSDMP.TXT.

Important!

The Windows 2000 ACPI HCT is not available for distribution at this time. If Windows 2000 setup fails to enable ACPI, please install Windows 98 with ACPI support enabled to run the HCT. Install the HCT from the %windir%\WOSTest\Tools\ACPI directory by running ACPIINST.EXE.

  Device Manager

Determine if all devices are enumerated beneath the ACPI devnode.

• In Control Panel, open System Properties.
• Select the Hardware tab and click Device Manager.
• Inspect the devices enumerated beneath the ACPI devnode for omissions and anomolies.

The test is considered successful if all devices are successfully enumerated beneath the ACPI devnode.

  Power Button

Test the power button.

• Power button takes system to Standby (S3).
• Power button takes system to Hibernation (S4).
• Power button takes system to Shutdown (S5) after 4 seconds.
• System resumes.

The test is considered successful if the power button successfully takes the system to each of the supported system states listed, and then resumes.

  Sleep Button

Test the sleep button.

• Sleep button takes system to Standby (S3).
• Sleep button takes system to Hibernation (S4).
• Sleep button takes system to Shutdown (S5).
• System resumes.

The test is considered successful if the power button successfully takes the system to each of the supported system states listed.

  Monitor Power Down

Test monitor power down.

1. In Control Panel, open Power Properties.
2. Select the Power Schemes tab.
3. Select the Turn off monitor dropdown, and select 2 minutes.
4. Allow the system to power the monitor down.

The test is considered successful if the monitor powers down at the specified time.

  IDE Drive Spindown

Test IDE drive spindown.

1. In Control Panel, open Power Properties.
2. Select the Power Schemes tab.
3. Select the Turn off hard disks dropdown, and select 3 minutes.
4. Allow the system to spindown the drives.

The test is considered successful if the drives spindown at the specified time.

  Resume from USB Mouse

Test resume from USB mouse.

1. If you have not already done so, enable this feature in Device Manager.
2. From the Start menu, select Shutdown.
3. Select Standby from the shutdown options menu.
4. When the system is fully suspended (1-3 minutes depending on system), click button on the USB mouse. The system should wake.

This test is considered successful if the system wakes.

  Resume from USB Keyboard

Test resume from USB Keyboard.

1. If you have not already done so, enable this feature in Device Manager.
2. From the Start menu, select Shutdown.
3. Select Standby from the shutdown options menu.
4. When the system is fully suspended (1-3 minutes depending on system), press a button on the USB keyboard. The system should wake.

This test is considered successful if the system wakes.

  Resume from Timer

This is an automated test that uses the program SUSPEND.EXE to verify wake from Real Time Clock (RTC) in all supported sleep states, 5 iterations each.

• Install and Run WOSTest.
• Select Resume from Timer from the ACPI tab.
• Play a WAV file after the system has resumed from Standby.

This test is considered successful if SUSPEND.exe completes without errors.

  Resume from Extended Sleep

This is an automated test that uses the test tool Suspender (Suspend.exe) to verify wake from RTC in all supported sleep states, 5 iterations each, with an increase of 15 minutes suspend time for each iteration.

• Install and run WOSTest.
• Select Resume from Extended Sleep from the ACPI tab.
• Play a WAV file after the system has resumed from Standby.

This test is considered successful if Suspender completes without errors.

  Wake on LAN

Wake on Ring and Wake on LAN are conducting using DOZER.EXE. If the system does not include a network interface card, the results of the Wake on Ring test will determine if the system passes the test. Both tests must pass if the system includes both a modem and a NIC.

The test requires at least two machines. The machine undergoing testing must meet the BIOS, operating system, and networking requirements for Wake on Lan. The modem or network card to be tested should be installed on this machine.

The purpose of the second machine is to wake up the test machine. Think of it as a wake-up server. This server only needs to satisfy the networking requirement.

The Wake on Ring/Wake on LAN test consists of two applications: DOZER.EXE and WAKER.EXE.

• DOZER runs on the test machine and conducts the Wake on Ring/Wake on LAN testing and validation.
• WAKER runs on the wake-up server. The two applications communicate through a TCP/IP socket connection.

For more information, please refer to WakeTest.htm.

• Copy \%windir%\WOSTest\Tools\ACPI\WakeTest\Waker.exe to the wake-up server.
• Run Dozer.exe on the machine to suspend by clicking its hyperlink on the ACPI tab. If you would like to run it from a command line, run the following: \%windir%\Tools\ACPI\WakeTest\Dozer.exe -q
• Dozer will prompt for the name of the WAKER machine and for the phone number.
• Do not enter the phone number; this is how the program knows it is testing Wake on LAN.
• Run Waker.exe on the wake-server machine to resume the DOZER machine.

This test is considered successful if WAKER can resume the DOZER machine.

  Wake on Ring

Wake on Ring and Wake on LAN are conducting using DOZER.EXE. If the system does not include a network interface card, the results of the Wake on Ring test will determine if the system passes the test. Both tests must pass if the system includes both a modem and a NIC.

The test requires at least two machines. The machine undergoing testing must meet the BIOS, operating system, and modem requirements for Wake on Ring. The modem to be tested should be installed on this machine.

The purpose of the second machine is to wake up the test machine. Think of it as a wake-up server. This server must have a modem to wake the test machine.

The Wake on Ring/Wake on LAN test consists of two applications: DOZER.EXE and WAKER.EXE.

• DOZER runs on the test machine and conducts the Wake on Ring/Wake on LAN testing and validation.
• WAKER runs on the wake-up server. The two applications communicate through a TCP/IP socket connection.

For more information, please refer to WakeTest.htm.

• Copy \%windir%\WOSTest\Tools\ACPI\WakeTest\Waker.exe to the wake-up server.
• Run Dozer.exe on the machine to suspend by clicking its hyperlink on the ACPI tab. If you would like to run it from a command line, run the following: \%windir%\Tools\ACPI\WakeTest\Dozer.exe -q
• Dozer will prompt for the name of the WAKER machine and for the phone number.
• Enter the phone number; this is how the program knows it is testing Wake on Ring.
• Run Waker.exe /p ###-#### on the wake-server machine to resume the DOZER machine, where /p indicates the phone number of the DOZER machine.

This test is considered successful if WAKER can resume the DOZER machine.

  Hibernate and Resume

Use Hibernate to test drivers' ability to resume from Standby

1. In Control Panel, open Power Options.
2. Select the Hibernate tab.
3. Enable Hibernate support and click OK.
4. On Start menu, choose Shutdown.
5. Choose Hibernate from the list of shutdown options.
6. Power off the system when prompted to do so.
7. Turn the system on and allow it to resume from Hibernate.
8. Test each hardware device to ensure the drivers support power management. For example, copy a file to a network share and play a sound.

This test is considered successful if the system resumes and all devices are functional.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  PC Card/Cardbus

In Device Manager, select the device class for the PCCARD/CardBus device. Verify:

• All PCCARD/CardBus devices are detected correctly.
• Device Manager does not report a conflict for any installed device.
• All PCCARD/CardBus devices are functioning.
• Insert and remove PC Cards dynamically. Test card function (i.e. modem dials and connects, NIC logs onto network, etc.)

This test is considered successful if device manager shows no conflicts and the device is functional.

  External Display

1. Attach an external monitor to the docking station or the VGA out connector on the laptop.
2. If connected to a docking station, cold dock and boot the laptop.
   Verify:
   • Windows detects and installs monitor.
   • Display is initialized at boot.

This test is considered successful if the external display initializes.

  Cold Docking

Test cold docking on legacy systems. For this test:

• Windows should be installed in an undocked state.
• With the laptop powered off, insert it into the docking station, and power on.

Upon completion of any necessary reboots, verify:

• Additional devices present in dock are detected and installed.
• Device Manager does not report a conflict.
• Devices in docking station function. Refer to the Plug and Play section for device specific test instructions.

This test is considered sucessful if all of the devices in the docking station are detected and functional.

  Warm Docking

Test Warm docking if it is supported. For this test, the machine should be configured with hardware profiles for the docked and undocked state.

With the laptop in a suspended state, insert it into a docking station, and verify:

• Machine recognizies state change when it resumes and switches to the docked configuration.
• Additional devices present in dock are detected and installed.
• Device manager does not report a conflict.
• Devices in docking station function.(Refer to Devices section for device specific test instructions.)

This test is considered successful if the machine configures itself with the correct hardware profile and all devices in the docking station function.

  Hot Docking

Test Hot docking if it is supported. For this test, the machine should be configured with hardware profiles for the docked and undocked state.

With the laptop in an operational state, insert it into a docking station, and verify:

• Machine recognizies state change and switches to docked configuration.
• Additional devices present in dock are detected and installed.
• Device manager does not report a conflict.
• Devices in docking station function.(Refer to Devices section for device specific test instructions.)

This test is considered successful if the machine configures itself with the correct hardware profile and all devices in the docking station function.

  Swap Peripherals

Test hot swapping of notebook peripherals if it is supported.

• CD-ROM or DVD-ROM drive
• Floppy drive
• Hard disk drive

The test is considered successful if the added peripheral is recognized and accessible after swapping.

  Devices in Docking Station

Determine if devices continue to function when the laptop is docked.

With the laptop turned off, insert it into the docking station, and power it on. Upon completion of any necessary reboots, verify:

• Additional devices present in dock are detected and installed.
• Device manager does not report a conflict.
• Devices in docking station function. Refer to the Plug and Play section for device specific test instructions.

This test is considered successful if device manager does not report a conflict, and all devices are functional.

  ACPI Lid

Test the notebook lid.

• Lid takes system to Standby (S3).
• Lid takes system to Hibernation (S4).
• Lid takes system to Shutdown (S5).
• System resumes.

The test is considered successful if the notebook lid successfully takes the system to each of the supported system states listed.

  Battery Tab Updates

Unplug the A/C adapter to determine if the BIOS updates battery status.

• Start Windows with the A/C adapter.
• Verify the battery tab in Power Properties displays A/C power.
• Remove the A/C adapter while Windows is running.
• Verify the battery tab in Power Properties updates to reflect battery power.

The test is considered successful if the notebook automatically updates the state of its power source when the A/C adapter is removed. If it does not, the most likely cause is the BIOS.

  Multiple Batteries

Test multiple batteries simultaneously if the notebook supports it.

• Insert multiple battery packs at once.
• Ensure system makes us of all batteries.

The test is considered successful if the notebook takes advantage of each battery.

  A/C Only

Test the notebook with no batteries.

• Remove all batteries from the notebook.
• Start Windows with A/C power only.

The test is successful if the system successfully boots to Windows with no batteries.

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.

  RAID Controllers

In device manager select SCSI and RAID Controllers. Verify:

• All installed RAID Controllers are detected correctly.
• Device manager does not report a conflict for any installed controller.
• All RAID Controllers are functioning.

This test is considered successfull if device manager shows no conflicts and drive arrays attached to the controller are accessable.

  Stripe with Parity (RAID 5)

Test a Stripe Set with Parity (Raid 5). A stripe volume can be moved from one system to another.

1. First, ensure the volume status is healthy.
2. Turn the system off and install the disks on another system.
3. Open Disk Management. If the disks did not automatically import, right-click the new disks and select Import Foreign Disks.
4. With the disks imported, run Chkdsk and Defrag on the volume.
5. Access any programs or data on the volume to check for corruption.

This test is considered successful if the imported volume is accessible and there is no corruption.

  Disk Stripe Set (RAID 3)

Test a Stripe Set with Parity (Raid 3). A stripe volume can be moved from one system to another.

1. First, ensure the volume status is healthy.
2. Turn the system off and install the disks on another system.
3. Open Disk Management. If the disks did not automatically import, right-click the new disks and select Import Foreign Disks.
4. With the disks imported, run Chkdsk and Defrag on the volume.
5. Access any programs or data on the volume to check for corruption.

This test is considered successful if the imported volume is accessible and there is no corruption.

  Disk Mirror Set (RAID 1)

Test a Disk Mirror Set (RAID 1). A mirror set requires at least 2 dynamic disks.

To create the mirrored volume, right click on unallocated space on the disk where you want to create the volume, and select Create Volume.

In the Create Volume Wizard, select Mirrored Volume.

To test the volume, disconnect the primary drive. This test is considered successful if the system boots from the secondary drive.

  Enable Group Policies

Test Group Policies.

• Create a sample set of group policies and user members. This is done through Computer Management.
• Create users as members of multiple groups with varying levels of access restrictions.
• Log in as group members and test policy enforcement.

This test is considered successful if all policies are enforced.

  Distributed File System

Test the Distributed File System.

1. Attach the client machine to several available shares on the test network.
2. Rename the links on the client and restart.

The test is successful if the name changes are retained, the links refer to the correct resource, and the resource is accessible.

  Active Directory

Test the Active Directory. For effective results, the test network should include a representative sampling of resources available on the production network.

• Create one or more Active Directory Trees on the test network. This must be performed during the upgrade of the test servers, selecting to create the first tree in a forest or install a child domain as appropriate.
• When migrating an existing domain structure to Windows 2000, the Primary Domain Controller should be upgraded first, followed by all Backup Domain Controllers, and then any member servers.
• User and Machine accounts on domain controllers will be added to the Active Directory during migration. Accounts on the member servers must be published to the Active Directory manually after migration.
• Organize migrated users and groups from the Users container in the Active Directory into logical groupings and assign rights to directory objects.
• Verify that changes to the Active Directory are replicated.
• Verify that user access restrictions are functioning as expected.
• Perform directory searches for users and resources which have been published to the directory.

The test is successful if the Active Directory is populated correctly during the migration, and resource management can be performed without errors.

  Cluster Services Setup

Setup a Windows 2000 Server cluster.

Important!

Microsoft Cluster Services are only supported under Windows 2000 Advanced server and Windows 2000 Datacenter Server. This test will require a minimum of two machines running either Advanced or Datacenter Server and one machine to act as the client using any OS. It is highly recommended that you review the online documentation for Server clusters prior to configuring Cluster Services for the first time.

Prerequisites for running Microsoft Cluster Services with Windows 2000

• In order to install clustering services you must be logged into both nodes using an Administrator account.
• Both nodes must have computer accounts on the domain and be members of the same domain.
• Password restrictions such as requiring password changes should be turned off on the domain account clustering services are to run under.
• Each node should have a physical connection to one or more shared storage devices.
• All nodes in the cluster should be interconnected using physically independant network connections.
• All cluster interconnects must be on the PCI bus.
• All interconnects must utilize TCP/IP and static addresses on the same network.

Setting up the Cluster

1. Ensure TCP/IP is set up correctly on each node. All nodes must have static IP addresses assigned to the interconnect interface.
2. Configure shared disks. Once you have installed your shared disks you should not start more than one computer at a time until at least one computer has the Cluster Service installed. If you start more than one computer without first installing the Cluster Service you could corrupt the disk.
3. Install and configure the Cluster Service on one node at a time.
   • From the Control Panel, select Add/Remove Programs.
   • From the Add/Remove Programs window select Add/Remove Windows Components.
   • In the right pane, select the Components button and click Next.
   • Select Cluster Service and click Next.
   • Select Finish when file copying is complete.
   • From the Add/Remove Programs window select Configure next to Configure Cluster Service.
   • Follow the instructions to configure the cluster.
4. Repeat services installation on each node.
5. Refer to the online documentation for additional information and checklists to help walk you through the installation procedure.

This test is considered successful if the cluster can be established and configured without errors.

  Cluster Fault Tolerance

Test failover on a Windows 2000 Server cluster.

1. Setup a Windows 2000 cluster as described in the Cluster Services Setup test.
2. On one node of the cluster, connect an externally-powered shared resource (i.e. external SCSI drive unit.)
3. Ensure the resource is accessible from client machines.
4. With the server in a fully operational condition, disconnect the power from the CPU.
5. Verify the shared resource is still accessible from the client machine.

This test is considered successful if the external shared resource on the unpowered node is still accessible from the client machine(s).

  Other

Please reserve the Other designation for system failures that lack an associated test case. Your notes will be reviewed prior to the next release for potential additions to the test matrices.