WiimoteReal/IOWin: Don't try to print error message for non-errors.

[AdmiralCurtiss]

I'm getting an S_FALSE here every couple seconds on Windows, which is not an error and thus triggers an assert in winrt::hresult_error. I have no idea what this means -- I can't find any documentation on what S_FALSE from WriteFile() means -- but it seems to not actually cause problems...?

e: Further debugging this, this is actually caused by my keyboard of all things. I guess it tries to figure out if my keyboard is a bluetooth device...? I'm surprised there isn't a better way for that.

[mzji]

GetLastError() always returns Win32 error codes, so that 0x00000001 actually is an ERROR_INVALID_FUNCTION but not a S_FALSE. Then google will tell us that when using ReadFile/WriteFile functions to access devices sometime we could get an ERROR_INVALID_FUNCTION because of the OS (compatibility?) or the device driver (not implement the read function on the device object).

[AdmiralCurtiss]

Hm, does that mean the Common::HRWrap() is wrong in general here, did we mix up enums here?

e: Should this use https://learn.microsoft.com/en-us/windows/win32/api/winerror/nf-winerror-hresult_from_win32 ?

[mzji]

Don't use FAILED() and Common::HRWrap here - in this case the value GetLastError() returns is a Win32 error, not an HResult. If the explanation text is needed, you could use FormatMessageA/W() to convert the error code to the human-readable localized text.
P.S. HRESULT_FROM_WIN32() is for converting/wrapping a Win32 error to/in an HResult value, not suitable to use in this case.