cmd: Fix cmd's mishandling of quote-enclosed command strings

[testbot at testbot.winehq.org]

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
http://testbot.winehq.org/JobDetails.pl?Key=3340

Your paranoid android.


=== WNT4WSSP6 (32 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d

=== W2KPROSP4 (32 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d

=== WXPPROSP3 (32 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d

=== W2K3R2SESP2 (32 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d

=== WVISTAADM (32 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d

=== W2K8SE (32 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d

=== W7PRO (32 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d

=== W7PROX64 (32 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d

=== W7PROX64 (64 bit) ===
batch.c:188: Test failed: unexpected end of output in line 46, expected 0x4d