This fixes Trials Fusion often crashing when disconnecting a controller while there are more still connected.
--
v14: ntoskrnl/tests: Use the 'Nt' version of the CancelIo APIs.
ntoskrnl/tests: Test the thread ID the cancellation routine runs from.
ntoskrnl/tests: Add more cancellation tests.
ntoskrnl/tests: Fix tests on current Windows 10 / 11.
ntdll/tests: Test IOSB values of the cancel operation.
ntdll/tests: Add more NtCancelIoFile[Ex]() tests.
ntdll: Wait for all asyncs to handle cancel in NtCancelIoFile().
server: Factor out a cancel_async() function.
server: Introduce a find_async_from_user helper.
ntdll: Factor out a cancel_io() function.
https://gitlab.winehq.org/wine/wine/-/merge_requests/7797
--
v9: maintainers: Add a section for Windows.Devices.Enumeration.
windows.devices.enumeration: Create DEVPROP_FILTER_EXPRESSIONs from AQS filter strings and pass them to DevGetObjects.
windows.devices.enumeration: Support parsing AQS filters in IDeviceInformationStatics::FindAllAsyncAqsFilter.
https://gitlab.winehq.org/wine/wine/-/merge_requests/8890
Giving this one final shot. If this is not deemed acceptable, I will abandon the effort and just move on to other things, no hard feelings.
This is IMO a cleaner, more conservative/less invasive change.
What is fixed:
- Bug #56381, "TYPE c:\windows\winhelp.exe >foo", i.e. binary mode operation. I would probably consider this the main reason for this change. I'm trying to get the compiler mentioned in the bug report working.
- Ctrl-Z termination of TYPE output to the console.
- "TYPE con >foo", with Ctrl-Z handling, functionally equivalent to "COPY con foo".
--
v4: cmd: Fix TYPE behavior (now uses WCMD_copy_loop).
cmd: Refactor WCMD_copy_loop out of WCMD_ManualCopy, and stop copy loop at EOF for /a mode.
https://gitlab.winehq.org/wine/wine/-/merge_requests/8920
Giving this one final shot. If this is not deemed acceptable, I will abandon the effort and just move on to other things, no hard feelings.
This is IMO a cleaner, more conservative/less invasive change.
What is fixed:
- Bug #56381, "TYPE c:\windows\winhelp.exe >foo", i.e. binary mode operation. I would probably consider this the main reason for this change. I'm trying to get the compiler mentioned in the bug report working.
- Ctrl-Z termination of TYPE output to the console.
- "TYPE con >foo", with Ctrl-Z handling, functionally equivalent to "COPY con foo".
--
v3: cmd: Fix some TYPE command behavior.
cmd/tests: Add test to check for TYPE truncation in binary mode.
https://gitlab.winehq.org/wine/wine/-/merge_requests/8920
In order to improve cmd.exe's test, we need to generate arbitrary binary files.
There's already a hack in tests to generate from test executable some
binary that will be lated used by the tests in .cmd file.
That's not neati: this spreads tests across three different spots (batch input,
batch output, binary file generator).
We introduced the @\x??@ sequence in .cmd tests. Even if this supports
most of the wanted BYTE:s, it doesn't work with EOF, \r and ctrl-Z (as
they are always interpreted in ECHO command) (we can work around \n even
it's ugly).
After various testings, it looks like adding hex decoding to certutil
is the decent solution:
- it's supported on all Windows versions from the testbot VM,
- it's rather straightforward to use (if you keep tests simple and short,
which a good idea anyway).
Even if our certutil implementation is empty, we have preliminary material
from bcryp32 that shall provide the correct implementation.
So this MR:
- adds the -decodehex command to programs/certutil,
- make use of it in order to generate existing binary test file inside
the .cmd file.
Pending MR!8920 will also make use of it.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8947