New install not working

perryh · Post by **perryh** » Thu Jul 03, 2008 1:49 am

OK, it has nothing to do with trying to run a setup.exe off of floppy.

I've installed 1.0.r4 -- yes, it's kind of old, but seems to be the
latest binary available for FreeBSD 7 -- and it doesn't want to run
anything I've tried. For example:

$ rm -rf .wine
$ wine notepad
wine: created the configuration directory '/home/perryh/.wine'
wineserver: fcntl /tmp/.wine-105/server-53-772d/lock : Invalid argument

Now what?

perryh · Post by **perryh** » Fri Jul 04, 2008 7:13 pm

I've installed 1.0.r4 -- yes, it's kind of old, but seems to be the
latest binary available for FreeBSD 7 -- and it doesn't want to run
anything I've tried. For example:

$ rm -rf .wine
$ wine notepad
wine: created the configuration directory '/home/perryh/.wine'
wineserver: fcntl /tmp/.wine-105/server-53-772d/lock : Invalid argument

Now what?

Anyone have an idea? Do I have to attempt building from source,
even though that's generally not recommended for non-experts?

vitamin · Post by **vitamin** » Fri Jul 04, 2008 7:36 pm

perryh wrote:
I've installed 1.0.r4 -- yes, it's kind of old, but seems to be the
latest binary available for FreeBSD 7 -- and it doesn't want to run
anything I've tried. For example:

$ rm -rf .wine
$ wine notepad
wine: created the configuration directory '/home/perryh/.wine'
wineserver: fcntl /tmp/.wine-105/server-53-772d/lock : Invalid argument

Now what?
Anyone have an idea? Do I have to attempt building from source,
even though that's generally not recommended for non-experts?

Wine always have problems with FreeBSD. If you really want to use Wine, *BDS is not an option.

jeffz · Post by **jeffz** » Fri Jul 04, 2008 10:03 pm

check to see if a bug report has been filed, if not file one.

vitamin · Post by **vitamin** » Fri Jul 04, 2008 10:17 pm

jeffz wrote:check to see if a bug report has been filed, if not file one.

That won't help. There are number of bugs for Wine not working on *BSD. From trivial to complete blockers. And in most cases there is nothing Wine can do - it's the OS limitations that cause all the problems.

perryh · Post by **perryh** » Sat Jul 05, 2008 3:12 am

There are number of bugs for Wine not working on *BSD ... in most
cases there is nothing Wine can do - it's the OS limitations that
cause all the problems.

Is there a list of those OS limitations somewhere? I'm a lot more
familiar with FreeBSD than with either Wine or Windows, so might
conceivably be able to work on fixing some of the limitations.

My interest in all this is to run one particular Windows app on
FreeBSD. I've gotten the impression that Wine is probably the most
promising way to accomplish this, in addition to being a Good Thing
as a matter of principle.

vitamin · Post by **vitamin** » Sat Jul 05, 2008 9:38 am

perryh wrote:
There are number of bugs for Wine not working on *BSD ... in most
cases there is nothing Wine can do - it's the OS limitations that
cause all the problems.
Is there a list of those OS limitations somewhere? I'm a lot more
familiar with FreeBSD than with either Wine or Windows, so might
conceivably be able to work on fixing some of the limitations.

My interest in all this is to run one particular Windows app on
FreeBSD. I've gotten the impression that Wine is probably the most
promising way to accomplish this, in addition to being a Good Thing
as a matter of principle.

Wine is the only thing you can use other then VM to run windows apps on *NIX.

You can search bugzilla for the list of FreeBSD bugs

perryh · Post by **perryh** » Sat Jul 05, 2008 10:25 pm

There are number of bugs for Wine not working on *BSD ...
in most cases there is nothing Wine can do - it's the OS
limitations that cause all the problems.
Is there a list of those OS limitations somewhere?
...
You can search bugzilla for the list of FreeBSD bugs ...

Unfortunately, at my level of (un)familiarity with Wine, it's not
at all clear which of those are caused by problems in FreeBSD, or
what those underlying problems are. Some have comments indicating
they also happen in other OS, thus presumably not caused by "OS
limitations" (or at least not by limitations unique to FreeBSD),
and some seem to happen on old FreeBSD releases; but I found only
two comments (in 12839 and 13607) to the effect of "this happens
because FreeBSD can't handle thus-and-such." (WRT those two, the
iphlpapi issue is already being worked on and may have been fixed
in FreeBSD 7.0, and ZFS cannot be a factor for me because I'm not
using it.)

Based on the description in 13526 it looks as if some FreeBSD Wine
users are getting a whole lot farther than I am. For that matter,
I was getting quite a bit farther before upgrading to 1.0.r4.