Rainbow 6 Siege and some other games require this. Type is printed in the FIXME to determine which type the application requires.
--
v8: gdi32: Add stub for D3DKMTQueryAdapterInfo.
https://gitlab.winehq.org/wine/wine/-/merge_requests/3777
> Since MCI_UnmapMsgAtoW handles all the cases where MCI_MapMsgAtoW allocates memory. Why not just call MCI_UnmapMsgAtoW to do its thing in all cases?
Fine, but it would need to be a separate commit to that of changing the return values of `MCI_MapMsgAtoW()`.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3854#note_47829
On Fri Oct 6 06:52:42 2023 +0000, Maarten De Braekeleer wrote:
> Hey!
> First, thanks for addressing this. The fact that CTRL+C closes cmd was
> the reason I created https://bugs.winehq.org/show_bug.cgi?id=55197.
> I have some questions about the current cmd behavior:
> - `CTRL+C` creates a new line, but does not write a new prompt to stdout.
> Typing text will make text appear again on the original line.
> Microsoft cmd will create a new prompt, and make new text input appear
> after that.
> - This is probably a feature request, but I think it would be useful to
> close cmd by pressing CTRL+D (EOF). Other repl's, such as python have
> this behavior.
> If you prefer me to create bugzilla issues for these, let me know.
please file a bug report for the missing prompt after ctrl-c in cmd (note: it should be also pointed out that ctrl-c in builtin cmd doesn't stop current command: e.g. try to stop 'dir /s c:\\')
I'm afraid that ctrl-d will not be supported as you'd like. this is a unix shell behavior, not windows console one.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3312#note_47820
This goes on top of MR 345.
--
v20: tests/shader-runner: Test shaders with dxcompiler.
tests/shader-runner: Replace immediate shader type strings with an enum.
tests/shader-runner: Do not exit if a 'require' directive is not met.
tests/shader-runner: Handle individual keywords in shader directives.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/346
This clears up much of the todo list for mspatcha. GetFilePatchSignature* and NormalizeFileForPatchSignature have now been implemented in these changes.
These changes bring better support for things like the Adobe Acrobat installer without the need for things like the winetricks mspatcha.dll native dll override. Still needed is support for interleaved streams in the LZXD decompression logic, however this is a great start to better supporting software installers that use the Windows interface for creating and applying patches to files.
This is the beginning of the fixes required for bug 12501: https://bugs.winehq.org/show_bug.cgi?id=12501
--
v38: mspatcha: Handle PE format errors properly
https://gitlab.winehq.org/wine/wine/-/merge_requests/3870
On Thu Oct 5 21:34:01 2023 +0000, Aidan Khoury wrote:
> It's a publicly available Adobe DLL binary in LZXD compressed form, so
> I'm not sure, perhaps you need a distribution license from Adobe. Maybe
> better to consult someone well versed in copyright law.
Seems okay according to Adobe's terms:
`3.6 Content Files. “Content Files” means Adobe assets provided as part of the Services and Software. Unless documentation or specific licenses (including but not limited to Additional Terms) state otherwise, we grant you a personal, non-exclusive, non-sublicensable (except if you are a Business, then sublicensable only to your Business Users), and non-transferable license to use the Content Files to create your end use (i.e., the derivative application or product authored by you) into which the Content Files, or derivations thereof, are embedded for your use (“End Use”). You may modify the Content Files prior to embedding them in the End Use. You may reproduce and distribute Content Files only in connection with your End Use, however, under no circumstances can you distribute the Content Files on a stand-alone basis, outside of the End Use.`
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3870#note_47786