Far Manager Forum

Hi,
I've just finished installing CrossOver 9.1.0 on Mac, with the sole purpose to run FAR Manager. That was after an unsuccessful attempt to do that with my own custom-built Wine 1.2.
Unfortunately, I was equally unsuccessful. It runs well on Wine 1.2 on Linux, BTW.

I run:
wineconsole --backend=user "H:\FAR\Far.exe"

I get the following messages in the console:

_X11TransOpen: Unable to find transport for tcp
_X11TransOpen: Unable to find transport for tcp
_X11TransOpen: Unable to find transport for tcp
[... snip repeated text ...]
_X11TransOpen: Unable to find transport for tcp
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.

But I do have X running, and $DISPLAY is correct. Other X apps (xfig, gv, etc.) are running well.

The program does start, but it looks very bad, the characters in the range 128-255 are completely missing, the keys Ctrl, Alt and Shift are not working, etc. It's nowhere near as good as advertised in http://www.codeweavers.com/compatibility/browse/cat/?app_id=2488;tips=1
Moreover, I did not understand the tips: e.g. "Fonts must be installed before FAR installation." What fonts? I installed the MS core fonts; is there anything else specific that's required?

Even running wineconsole was a bit of a hack. It's perhaps that I'm new to Mac, but I run wineconsole by running wine directly from CrossOver.app; is this the correct way to run it?
/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine wineconsole --backend=user "H:\FAR\Far.exe"

Something I'm clearly missing here, or else I wouldn't get the results so different than what I'm getting on Linux.
I will appreciate any help or clarification.
--
Cosmin

Generally, the easiest way to run commands is with the Run Command dialog, accessible from the Programs menu. You don't specify the "wine" command, just the rest. So, something like:

wineconsole "H:\FAR\Far.exe"

(I recommend selecting the .exe with the Browse button and then inserting wineconsole before it.)

If you want to run wine commands in a shell, you need to get CrossOver to configure the shell for you. Toggle open the Debug Options section of the Run Command dialog and click the Open Shell button. That will open a new Terminal window and configure it to access CrossOver's wine and the bottle.

CrossOver has its own custom implementation of X11. It uses different X11 libraries and a separate DISPLAY namespace. So, you don't need X running (CrossOver is itself an X server) and the normal DISPLAY is not appropriate.

Never mind, I figured it out. It turns out I must actually run it in the CrossOver environment, otherwise it didn't work. And the console seems to be requiring the Courier font.
It seems to work well, so far.

BTW, the Courier font was also missing from my own Wine 1.2 installation.
--
Cosmin

Ken Thomases wrote:

If you want to run wine commands in a shell, you need to get
CrossOver to configure the shell for you. Toggle open the Debug
Options section of the Run Command dialog and click the Open Shell
button. That will open a new Terminal window and configure it to
access CrossOver's wine and the bottle.

Good to know, thanks!

Ken Thomases wrote:

CrossOver has its own custom implementation of X11. It uses
different X11 libraries and a separate DISPLAY namespace. So, you
don't need X running (CrossOver is itself an X server) and the
normal DISPLAY is not appropriate.

Also useful to know. It's good, at least, that I didn't start messing with my system's X11 config 😊
--
Cosmin