http://bugs.winehq.org/show_bug.cgi?id=27889
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |dank@kegel.com Ever Confirmed|0 |1
--- Comment #4 from Dan Kegel dank@kegel.com 2011-07-24 23:55:38 CDT --- I think the interesting bit of the log is
trace:msi:ACTION_CustomAction Handling custom action L"InstallWordCruncherKeyboardsProperty" (33 L"InstallWordCruncherKeyboards" L"[Manufacturer]\[ProductName]")
... 002e:Call advapi32.RegOpenKeyExW(80000002,1001e4d8 L"SYSTEM\CurrentControlSet\Control\Keyboard Layouts",00000000,0002001f,005dd83c) ret=100011f2 002e:Ret advapi32.RegOpenKeyExW() retval=00000002 ret=100011f2 ... trace:msi:DllThread custom action (2e) returned 1603
Sounds like it's doing something really low level with keyboards, which might not work.
That registry key is somewhat documented at e.g. http://scripts.sil.org/cms/scripts/page.php?&item_id=Kbd_Registry#1f9f96...