[PATCH 4/7] wintab32: Use registry to query primary adapter key.

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?

Full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=48811

Your paranoid android.


=== debian9 (32 bit report) ===

user32:
monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0
monitor.c:118: Test failed: #0: wrong DeviceKey:
monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0
monitor.c:118: Test failed: #0: wrong DeviceKey:

=== debian9 (32 bit Chinese:China report) ===

user32:
monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0
monitor.c:118: Test failed: #0: wrong DeviceKey:
monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0
monitor.c:118: Test failed: #0: wrong DeviceKey:

=== debian9 (32 bit WoW report) ===

user32:
monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0
monitor.c:118: Test failed: #0: wrong DeviceKey:
monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0
monitor.c:118: Test failed: #0: wrong DeviceKey:

=== debian9 (64 bit WoW report) ===

user32:
monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0
monitor.c:118: Test failed: #0: wrong DeviceKey:
monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0
monitor.c:118: Test failed: #0: wrong DeviceKey: