ptitSeb / box86-compatibility-list

Box86 Compatibility List (Games and Software)
MIT License
62 stars 2 forks source link

Microsoft Office 2010 #96

Open TuxThePenguin0 opened 3 years ago

TuxThePenguin0 commented 3 years ago

Description

Seems to install and run fine, launches very slowly so be patient (multiple minutes waiting on OSPPSVC.EXE every time an app is launched)

Tested on

Pinebook Pro Debian Sid Mesa 20.3.5 Wine 5.13

Status

Previous behavior: None reported but never used to work in informal tests

Current behavior: Word, Excel, Access, Publisher all seem to work perfectly Powerpoint does not start

Screenshots

unknown unknown unknown

OpenGL

Probably none

Additional Information

Not fully tested

ptitSeb commented 3 years ago

It would be good to add the Wine version used also, just in case.

TuxThePenguin0 commented 3 years ago

Added

TuxThePenguin0 commented 3 years ago

Tested powerpoint and it doesn't start

TuxThePenguin0 commented 3 years ago

Oddly enough after rebooting it doesn't seem to want to start Word anymore. Although other programs like Excel seem to work fine. And what's really strange is that after starting Excel, Word works too, so I have no idea what's going on there. (The RpcRecieve fault packets appear even when starting programs that work, the first abnormal line is an extra box86 instance trying to start the debugger)

Office14 $ WINEPREFIX=~/.winepref/msoffice wine WINWORD.EXE 
Box86 with Dynarec v0.2.1 ca95cdcb built on May 20 2021 12:12:46
Box86 with Dynarec v0.2.1 ca95cdcb built on May 20 2021 12:12:46
Box86 with Dynarec v0.2.1 ca95cdcb built on May 20 2021 12:12:46
009c:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142
0024:err:mscoree:CLRRuntimeInfo_GetRuntimeDirectory error reading registry key for installroot
0138:err:ntdll:RtlpWaitForCriticalSection section 01427A1C "?" wait timed out in thread 0138, blocked by 0130, retrying (60 sec)
0138:err:ntdll:RtlpWaitForCriticalSection section 01427A1C "?" wait timed out in thread 0138, blocked by 0130, retrying (60 sec)
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0024:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
Box86 with Dynarec v0.2.1 ca95cdcb built on May 20 2021 12:12:46
wine: Unhandled page fault on read access to 000003B0 at address 6CB61FFB (thread 0024), starting debugger...
Box86 with Dynarec v0.2.1 ca95cdcb built on May 20 2021 12:12:46
winedbg detected, not launching it!
0024:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 32 804" (1359)
Read the Wine Developers Guide on how to set up winedbg or another debugger
TuxThePenguin0 commented 3 years ago

I was experimenting with Access and got it to crash unfortunately, I think it was trying to load a form. It had basically the same (relatively non-descriptive) error message as Word earlier. I'd try a higher box86 log level but the next step up spams the console with so many messages that Office itself seems to never start, likely from how slowly it's running.