Hi,
Unfortunately this documentation is a bit all over the place
in the wiki at present, and there's a lot of debugging information
available for mainstream Wine which is equally applicable in the
Crossover situation...I did hoist an 'umbrella' ticket on this a
week or so ago, and I believe the current resolve was one of this,
manual intervention, and pointing folks in the right direction...
http://www.codeweavers.com/support/wiki/CXOfficeStart
The first three topics there are pertinent, and wrt the second item
you can go see;
http://wiki.winehq.org/DebugChannels?action=show&redirect=WINEDEBUG
You use the methodology of how to create a debug log, as you would
in mainstream wine with the $WINEDEBUG env_var, specifying which
specific debug channels you believe are worth exploring. As a base
start-point, I always use +seh,+trace,+ntdll as it usually discloses
the most relevant information as to why an app is failing/crashing
or doing something else weird, and it gives you enough of a clue as
to what -other- debug channels are worth investigating.
It's always worthwhile seeing if there is a AppDB entry for the app
in question, over at WineHQ...some many times, solutions to problems
found by users there are typically applicable to Crossover as well.
http://appdb.winehq.org/
There's also this page..;
http://www.codeweavers.com/support/wiki/UnsupportedApps
...and...
http://www.codeweavers.com/support/wiki/CXOffice_UnsupportedTips
....and somewhere in this lot is more information that can turn
out to be useful...;
http://www.codeweavers.com/support/wiki/Home?action=tree
....and the app's forum itself of course, or the Tips&Tricks section
of the app C4 page (if it exists)....err...umm....I think that's all of it...
...oh...I think your first question is answered by...;
http://www.codeweavers.com/support/wiki/faq/defaultlogs
;)
Cheers!