HCT 12.1, Pointing and Drawing Devices, DirectInput Mouse


A

Andrew

Hi All

The situation:

HCT 12.1, Pointing and Drawing Devices, DirectInput Mouse

This test correctly determines number of buttons (2), but invites to press
not only buttons #1 and #2, but also un-existing buttons #3, #4, #5.

BTW it works fine under the HCT 12.0

That's the failing case:





Start Case: ID 77:DI.GetDeviceData: Verify Mouse Data
550.2A4 : --- SetProperty DIPROP_AXISMODE, dwHow == DIPH_DEVICE, dwData ==
DIPROPAXISMODE_ABS
550.2A4 : Returned from SetProperty(DIPROP_AXISMODE,
DIPROPAXISMODE_ABS) (DI_OK == 00000000h)
550.2A4 : --- GetCapabilities said, the mouse has 2 axes, and 2 buttons
550.2A4 : --- Test Mouse axes data, the mouse has 2 axes
550.2A4 : The mouse's absolute position along the X-axis increased
17180
550.2A4 : Absolute X-axis data can increased more than 300
550.2A4 : DirectInputDevice::GetDeviceState() X-axis data was correct
550.2A4 : The mouse's absolute position along the Y-axis
increased -327
550.2A4 : Absolute Y-axis data can increased more than 300
550.2A4 : DirectInputDevice::GetDeviceState() Y-axis data was correct
550.2A4 : --- Test Mouse button data, the mouse has 2 buttons
550.2A4 : Correct button #2 was pressed
550.2A4 : !!! ERROR: Wrong button. Button #2 was pressed, while testing
button #3
550.2A4 : !!! ERROR: Wrong button. Button #1 was pressed, while testing
button #4
550.2A4 : !!! ERROR: Wrong button. Button #2 was pressed, while testing
button #5
550.2A4 : VAR[SEV1 ] 6 : Test Case - 77:DI.GetDeviceData
550.2A4 : +VAR+SEV1 6 : Test Case - 77:DI.GetDeviceData
550.2A4 : End Case: ID 77:DI.GetDeviceData: Verify Mouse Data

TIA

Andrew
 
Ad

Advertisements

Joined
Jul 8, 2005
Messages
7
Reaction score
0
This failure is acceptable by microsoft. It 's errata ID:1353. you can refer to the following link:
http://www.microsoft.com/whdc/hwtest/search/details.aspx?Type=err&ID=1353
Issue:

The Direct Input Mouse test does not test correct number of mouse buttons. The test keeps asking for buttons that do not exist even though the test has properly counted the buttons available on the mouse.


ERROR: Wrong button. Button #x was pressed, while testing button #y
VAR[SEV1 ] 6 : Test Case - 77:DI.GetDeviceData
VAR+SEV1 6 : Test Case - 77:DI.GetDeviceData


Where x and y may be any number
Error and SEV line may be repeated multiple times.

Solution:

This issue described is an acceptable failure. When making a submission with a failed log for this test, refer to this issue with the Errata ID number in the Readme.doc file included with your test submission package.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top