http://bugs.winehq.org/show_bug.cgi?id=59550 --- Comment #4 from Eric Pouech <eric.pouech@gmail.com> --- (In reply to smcclenahan from comment #3)
See the terminal output attachment. the terminal output gives insight on where the error is triggered what I'm asking is the input to cmd.exe
A game exe is trying to run cmd.exe with how is it run? from CreateProcess, from ShellExecute, from inside another .bat, from inside another .cmd, from inside another .bat with start, from inside another .cmd with start, with start.exe, from another method ? which exact parameters? (with quotes, escapes, which parameters to cmd.exe? /s, /c, ...
I've tried a couple of these options without showing differences between Wine and Windows that's why I'm trying to find the set of input to trigger the problem -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.