http://bugs.winehq.org/show_bug.cgi?id=14417
Summary: Yamaha PM5D editor MSI install Product: Wine Version: 1.1.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs@winehq.org ReportedBy: reuben.m@gmail.com
This is yet another msi problem. I'm 95% sure this program would run quite easily if I could just get past all the msi install crap.
For a bit of background, the Yamaha PM5D is a digital audio console. Very big, and expensive. It's the kind of mixing console used in large concerts, music festival, events where guys run around with those silly "All Access" passes.
Anyway, you can create programs on the computer to save as a file and load later on the actual console. I would like to run this on Linux, but I can't get past the msi problems.
The software is free to download.
The Studio Manager (v2.1.7) does install and run. It's needs to be installed before the editor.
http://www.yamahaproaudio.com/downloads/firm_soft/smv2/smv2.html
The editor (v2.2.2) gets hung up on the msi part of the install though. Output from the console reads:
fixme:advapi:LookupAccountNameW (null) L"root" (nil) 0x32f88c (nil) 0x32f890 0x32f884 - stub fixme:advapi:LookupAccountNameW (null) L"root" 0x150270 0x32f88c 0x1501f8 0x32f890 0x32f884 - stub err:msi:ITERATE_Actions Execution halted, action L"ISVerifyScriptingRuntime" returned 1603
This package can be found here:
http://www.yamahaproaudio.com/downloads/firm_soft/pm5d/pm5dv2_edt.html
If you get that editor to install, you might want to test and make sure the editors for the M7CL and LS9 consoles install as well. (I use all of them)
http://bugs.winehq.org/show_bug.cgi?id=14417
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|msi |-unknown
--- Comment #1 from Juan Lang juan_lang@yahoo.com 2008-07-11 15:28:47 --- Just because msi is reporting an error doesn't make it the source of the error. Try 'winetricks wsh56' and see if it works.
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #2 from reuben.m@gmail.com 2008-07-12 00:12:18 --- Nope, didn't fix it. I installed msi2 as well. Same problem. Any other packages you would recommend installing?
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #3 from reuben.m@gmail.com 2008-07-12 00:15:21 --- BTW: sorry to just assume the problem was with MSI. But I though that was the best category to file it under since I tried running msiexec using the msi file the installer left in the temp dir, and that's what was failing.
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #4 from James Hawkins truiken@gmail.com 2008-07-12 00:22:31 --- (In reply to comment #3)
BTW: sorry to just assume the problem was with MSI. But I though that was the best category to file it under since I tried running msiexec using the msi file the installer left in the temp dir, and that's what was failing.
Wait. Why are you running msiexec on a temp msi file? What happened when you ran the *real* installer?
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #5 from reuben.m@gmail.com 2008-07-12 01:42:52 --- I ran the msiexec because I was trying to hunt down where the failure with the real installer was taking place. The msi file was one of the files left behind by the installer when it crashed. The console gave the same error output from both the real installer and the msi file I tested. Hence I assumed the msi file was where the problem was at.
I may be wrong of course. I really don't use wine much at all. (Which is why I filed a bug :)
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #6 from reuben.m@gmail.com 2008-07-12 01:48:35 --- Errr.. I just re-checked and the output is the same _except_ for the line
err:msi:ITERATE_Actions Execution halted, action L"ISVerifyScriptingRuntime" returned 1603
which only comes when running the msiexec. the other fixme:advapi lines are the same.
Sorry if that makes any difference.
Besides that there's not any other output from the console. The installer just crashes.
Is there a switch for a more verbose mode to generate more useful output?
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #7 from James Hawkins truiken@gmail.com 2008-07-12 01:50:56 --- What do you mean by 'crash'? If the installer crashed, there would be a backtrace in the output.
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #8 from reuben.m@gmail.com 2008-07-12 02:17:56 --- Created an attachment (id=14741) --> (http://bugs.winehq.org/attachment.cgi?id=14741) sterr from the install file
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #9 from reuben.m@gmail.com 2008-07-12 02:21:17 --- By crash, I simply mean the window disappears and nothing seems to have been installed. None of the install files are cleaned up. It just seems to stop right in the middle of the install after extracting the msi file.
I set WINEDEBUG=warn+all and dumped sterr to a log file. Perhaps you can sift through all that garbage and get a better idea of what is going on.
http://bugs.winehq.org/show_bug.cgi?id=14417
--- Comment #10 from James Hawkins truiken@gmail.com 2008-07-12 02:33:27 --- Both installers work perfectly well for me. Remove your wineprefix 'mv ~/.wine ~/.wine-save', make sure you're using the latest release, and try both installers again.
http://bugs.winehq.org/show_bug.cgi?id=14417
reuben.m@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #11 from reuben.m@gmail.com 2008-07-12 02:42:58 --- That fixed it. Thank you for the help!
http://bugs.winehq.org/show_bug.cgi?id=14417
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from James Hawkins truiken@gmail.com 2008-07-12 03:01:55 --- Closing.
-
wine-bugs＠winehq.org