[advapi32/tests #2] Don't set last error to 0 so we can check if it has changed

[Paul Vriens]

Hi,

(Should be applied after the previous security.c patch "Skip tests when our 
language isn't LANG_ENGLISH")

We test for a last error of 0, so we shouldn't set it to 0 before the function 
is called. This however introduces a todo_wine.

I haven't seen a test yet that actually goes into this 'if (!ret)'. All tests 
I've seen (W2k and up) go the other route and show:

Couldn't get SE_SECURITY_PRIVILEGE (0xc00000a5), skipping ACCESS_SYSTEM_SECURITY 
test

Changelog
   Don't set last error to 0 so we can check if it has changed

-- 
Cheers,

Paul.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-Don-t-set-last-error-to-0-so-we-can-check-if-it-has.patch
Type: text/x-patch
Size: 0 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20080216/3ef76f46/attachment.bin