------------------------------------------ Known Issues for the Microsoft Windows OEM Test Kit v1.1 ------------------------------------------ (c) Copyright Microsoft Corporation, 1999 This document provides complementary or late-breaking information to supplement the Microsoft Windows OEM Test Kit documentation. ------------------------ How to Use This Document ------------------------ To view Known.txt on-screen in Notepad, maximize the Notepad window. To print Known.txt, open the file in Notepad or another word processor, then on the File menu, click Print. -------- CONTENTS -------- SETUP FAILS WITH TSTSHELL.INI ERROR UNINSTALL ALWAYS STATES IT IS SUCCESSFUL UNINSTALL DOES NOT REMOVE EVERYTHING MULTIPLE WOSTEST SHORTCUTS ON DESKTOP NO TABS AVAILABLE ON CLEAN INSTALL PROCESSOR TYPE IS NOT LISTED NO WAY TO ENTER MULTIPLE BUGS FOR ONE TEST WOSREP - ERROR CREATING CAB FILE(S) PROFILE NAME CANNOT CONTAIN SOME CHARACTERS WOSTEST HANGS WHILE RUNNING AUTOMATED TESTS WOSTEST DOES NOT SUPPORT DBCS =================================== SETUP FAILS WITH TSTSHELL.INI ERROR =================================== When running setup for the OEM Test Kit, the following error may be generated: Error writing to file TSTSHELL.INI This may be the result of either insufficient disk space, or the existence of a TSTSHELL.INI file in the source directory. Free up 100MB of disk space on the destination drive and search the source directory for the existence of the file, TSTSHELL.INI, and delete it. Running WOSTEST.EXE from the source directory may create a TSTSHELL.INI. Install the OEM Test Kit on the local machine before running WOSTEST.EXE. ======================================== UNINSTALL ALWAYS STATES IT IS SUCCESSFUL ======================================== Setup states uninstall is successful, even if setup has never been run on the system to be tested. Uninstall will remove the OEM Test Kit if it does exist. ===================================== UNINSTALL DOES NOT REMOVE EVERYTHING ===================================== Setup states uninstall is successful, even though the shortcut on the desktop to WOSTEST.EXE remains. There are several known issues with uninstalling the OEM Test Kit. Please workaround this limitation by manually deleting the following: - Shortcut(s) on desktop - %windir%\Wostest directory and its subdirectories - C:\qtzvtst directory ===================================== MULTIPLE WOSTEST SHORTCUTS ON DESKTOP ===================================== Setup may generate more than one shortcut to WOSTEST.EXE on the desktop. ================================== NO TABS AVAILABLE ON CLEAN INSTALL ================================== When selecting Clean Install, no tabs after Main are available. Clicking tabs or the Next button results in the following error message: Selected tab is to be used after upgrade. Clean Install should only be selected if the system is already running Windows 2000. Choose Upgrade if the OEM Test Kit will be run on a system that is currently running Windows 95/98, or Windows NT 4.0. The OEM Test Kit locks tabs to ensure testing validity, and to determine when to run automated tests. ============================ PROCESSOR TYPE IS NOT LISTED ============================ The Main tab in Wostest does not list the specific processor type; it lists processor speed. The list cannot be configured. Wostest determines the processor type and vendor, and records it. The user is prompted for processor speed because determining this information is problematic. ========================================== NO WAY TO ENTER MULTIPLE BUGS FOR ONE TEST ========================================== The OEM Test Kit does not provide a means for entering multiple bug reports for one test case failure. The Other test cases are placeholders to address this limitation. 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. =================================== WOSREP - ERROR CREATING CAB FILE(S) =================================== The profile name entered in the Main tab of Wostest may not contain spaces, or characters that are invalid for filenames. The following characters cannot be used: \ / : * ? " < > | This is a limitation in the current version of the OEM Test Kit that may result in the following error when running the OEM Test Kit Bug Reporting Tool (WOSRep): Error creating cab file(s). Workaround this error message by following these steps: 1. Close Wostest if it is open. 2. Open the file, %windir%\Wostest\Wosrep.csv in a text editor such as Notepad.exe. 3. Note the Profile Name value that is listed approximately 10 lines down. 4. Change directory to the %windir% and find the SysParse log file, *.csv. The first word(s) should match the beginning of the profile name. For example, if you typed, "OTK version 1.1" in the Main tab, you would find an exact match in the Wosrep.csv. However, the SysParse file would be named, "OTK_version_1.1" or "OTK-w2k.csv." 5. Rename the SysParse log file and/or modify the Profile Name value listed in Saved.csv so that they match up to the SysParse log file's "-w2k.csv" 6. Run %windir%\Wostest\Tools\Wosrep.exe manually to generate the bug reports. =========================================== WOSTEST HANGS WHILE RUNNING AUTOMATED TESTS =========================================== When running Wostest on a Windows 95/98 system, the test shell may hang while automated tests run. Click the MS-DOS command prompt on the task bar, and close it to workaround this error. ============================= WOSTEST DOES NOT SUPPORT DBCS ============================= The OEM Test Kit does not support Double-Byte Character Set languages at this time. An update will be released for DBCS.