https://bugs.winehq.org/show_bug.cgi?id=47092
Bug ID: 47092 Summary: "IOPL not enabled" when trying to execute Office RT 2013 Product: Wine Version: 4.7 Hardware: arm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs@winehq.org Reporter: salva.liebana@gmail.com Distribution: ---
Created attachment 64289 --> https://bugs.winehq.org/attachment.cgi?id=64289 some warnings didnt appears on 4.0 but they are just warnings
Hi, ive read some topics about this problem on x86_64 and x86, and maybe this problem with office software its solved on that platforms, not on arm. The same problem appears on 4.0 and 4.7. the weird thing its than "IOPL" should be an x86 related thing... and how the hell this its happening on arm software. weird. maybe someone could explain something about it. Its just a fun project of run windows RT programs on rpi3, and Office could be the most funnier of all. but for now, I get that error. The compilation was the normal release mode.
https://bugs.winehq.org/show_bug.cgi?id=47092
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|gdiplus |-unknown CC| |xerox.xerox2000x@gmail.com
--- Comment #1 from Louis Lenders xerox.xerox2000x@gmail.com --- haha, just updated to Staging-4.7 and I get the same infamous "IOPL not enabled"...
I don`t get it anymore, WINWORD starts fine for me with self-compiled wine (no hacks, just -fPIC -O2) but now i run into this bug with Staging, and POWERPOINT and EXCEl just crash in Staging. (Note, i`m on linux x86_64)
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #2 from Salvador salva.liebana@gmail.com --- Thanks to respond! Ive just compiled the latest master.. So, thats no make sense here... Does it? I will paste the git clone commands but I think Iam clear about that.
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #3 from Salvador salva.liebana@gmail.com --- I am on default wine 4.7 compiled by myself with default configuration, no on staging.
https://bugs.winehq.org/show_bug.cgi?id=47092
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net, | |nerv@dawncrow.de
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #4 from Salvador salva.liebana@gmail.com --- I will tray to drag some dll from windows rt. Maybe its the most stupid idea, but its what I could do. If someone think than there is any compilation flag than could enable IOPL please respond. I didnt install any vc libs on my wine with winetricks because winetricks will try to install x86 libs...
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #5 from Salvador salva.liebana@gmail.com --- I am close, now it trought another error. But I am on 4.0. Going back to 4.7. I place the office folders inside the .wine folder, included shared libs on common files. Thats the trick I think... Dont know if wine could use the rt libs... But the IOPL error doesnt appeard.. So, time to test everything. If the error persist i will upload the crash log.
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #6 from Anastasius Focht focht@gmx.net --- Hello Salvador,
--- quote --- the weird thing its than "IOPL" should be an x86 related thing --- quote ---
If you think of IOPL = x86 I/O Privilege Level, no. In context of Microsoft Office, IOPL error code/text has an entirely different meaning.
It's simply a shorthand for:
* damaged/incomplete Office installation (missing dlls, corrupt registry, failing COM inproc servers etc.) * unexpected win32/64 API behaviour
I mentioned it a few times in the past:
* https://bugs.winehq.org/show_bug.cgi?id=45703#c21 * https://bugs.winehq.org/show_bug.cgi?id=9422#c15
Regards
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #7 from Salvador salva.liebana@gmail.com --- Thanks for such a great answer!
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #8 from Salvador salva.liebana@gmail.com --- Created attachment 64307 --> https://bugs.winehq.org/attachment.cgi?id=64307 Unhandled exception on 4.0-rc1 and 4.7 devel
it happens on 4.6 too.
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #9 from Salvador salva.liebana@gmail.com --- so, the IOPL thing seems resolved, now I get this "Unhandled exception".. maybe related to wine libs... who knows.. maybe you could give me some advice. it happens on 4.0.rc1, 4.6 and 4.7 master.
we should change the title of the bug.
OFFTOPIC: right now wine armhf (and arm64) its not a great topic, but if WoA success it will be, and we must be ready.
https://bugs.winehq.org/show_bug.cgi?id=47092
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|"IOPL not enabled" when |Microsoft Office RT 2013 |trying to execute Office RT |(15.0)(Windows RT 8.1) apps |2013 |crash on startup, reporting | |'Unhandled illegal | |instruction'
--- Comment #10 from Anastasius Focht focht@gmx.net --- Hello Salvador,
I don't think there is much that can be done here. Most of the problems with legacy ARMv7 and current ARM64 target platforms can't be diagnosed just by looking at trace logs. One would need to debug the crashing app live, like I did many times or alternatively an "offline" analysis of the crashing module.
Regards
https://bugs.winehq.org/show_bug.cgi?id=47092
--- Comment #11 from Salvador salva.liebana@gmail.com --- Ok, thanks as always!
-
wine-bugs＠winehq.org