http://bugs.winehq.org/show_bug.cgi?id=29997
--- Comment #20 from Justin Chevrier jchevrier@gmail.com 2013-12-08 10:56:07 CST --- (In reply to comment #19)
(In reply to comment #18)
Bug 32988 has a workaround for the 'Invalid command line' error dialog.
Still fails for me if run from ~/.wine/drive_c.
I think the issue here that publisher keeps updating the executable on their site. The crash I identified related to TRUST_E_NOSIGNATURE no longer seems to be an issue with the current version on their site. I'm running a clean prefix (with and without 'dotnet40') on wine 1.7.8 and the latest executable:
MD5Sum: 2930a1beff76babc503b2f0f707feb97 StudioTax2011Install.exe
and don't get the 'Invalid Command Line' dialog; instead the installer just hangs after accepting the license agreement and clicking 'Install'. The other issue is that I have revert to a clean prefix on every install attempt because on the second run the installer crashes much earlier while attempting to 'Computing space requirements' (see attached image). Can you confirm, or are you still recieving the 'Invalid Command Line' dialog?