Closed stefek99 closed 8 years ago
That's normal behaviour. The command exited with error code 0
which is fine.
The error like err:ole
or err:toolbar
coming from wine
and should be reported against it (try googling them individually).
Could be related to not implemented or badly written functions which platform is using or missing hardware (like missing drivers for sound-card, etc.). Newer version of wine
potentially could have these implemented, but I'm not sure.
Some of the errors are already suppressed by WINEDEBUG
variable in .configrc
, e.g.
export WINEDEBUG="warn-all,fixme-all,alsa-all,ole-all"
which suppose to silence all ole
error, but it seems it doesn't. Maybe there is some extra syntax that we need to use to hide them, e.g. toolbar-all
?
But in general, there is nothing to worry about. Your platform should now be installed in ~/.wine
(find it by: find ~/.wine -name terminal.exe
).
You should be able to run the platform via:
wine "$(find ~/.wine -name terminal.exe)"
or:
shopt -s globstar
wine ~/.wine/**/terminal.exe
Related:
Potential duplicate #40