[PATCH 2/3] winmm: MCI_SYSINFO doesn't change the output buffer in case of error.

Joerg-Cyril.Hoehle at t-systems.com Joerg-Cyril.Hoehle at t-systems.com
Mon Nov 1 11:09:52 CDT 2010


as opposed to mciSendString, the mciSendCommand functions appear to
obey the common convention "don't touch the output buffer in case the
function returns an error". No \0 here.

You better not use dwRetLen = 0 with the MCI.  The behaviour varies
among the 5 MCI devices, some writing upto 4 bytes (a pointer?) into
the output buffer.

 Jörg Höhle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-winmm-MCI_SYSINFO-doesn-t-change-the-output-buffer.patch
Type: application/octet-stream
Size: 6003 bytes
Desc: 0002-winmm-MCI_SYSINFO-doesn-t-change-the-output-buffer.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20101101/4ad94bd5/attachment-0001.obj>

More information about the wine-patches mailing list