Solved WINE on FreeBSD 13 - Am I Just Wasting My Time?

thindil

New Member

Reaction score: 9
Messages: 9

As a regular user, /usr/local/share/wine/pkg32.sh install wine-devel mesa-dri

Difference: wine-devel instead of wine.

As root you installed the development version of Wine, while as an user you trying to install the stable version of Wine. That's why it not working. :)
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66

As a regular user, /usr/local/share/wine/pkg32.sh install wine-devel mesa-dri

Difference: wine-devel instead of wine.

As root you installed the development version of Wine, while as an user you trying to install the stable version of Wine. That's why it not working. :)

This solved the version mismatch problem, but still wine will not install anything.

as reg user-
winecfg
Now starts and runs.

as reg. user
winetricks
Now starts and runs.

* * BUT * *
Cannot run the install on my windows program.
Nothing happens.
Run from command line, as follows:
as reg. user-
wine setup.exe
nothing happens.

QUESTION:
Why did this seem to "just work" under KDE desktop a few weeks ago,
but now never works now that I've switched to the MATE desktop?
Could this be something to do with Xorg or the desktop?
Running different patch levels because its now two weeks latter?
Unrelated / Just Coincidence?

???

Thoughts... ??
.
.
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66

Do you like to tell what are you trying to install?

I usually test wine by trying to install Borland Paradox for Windows v.9, Developer Edition,
It was originally released stating "runs on linux."
I've been running it on linux / wine for years, installs easily, runs rock-solid.

However, wine won't install anything if the install never starts.
 

msplsh

Aspiring Daemon

Reaction score: 318
Messages: 789

WordPerfect still sells Windows 10 compatible versions of Paradox.
 

monwarez

Active Member

Reaction score: 91
Messages: 190

Did you test with all hardening option enabled ?
You can try disabling aslr with proccontrol
WINEPREFIX=/path/to/my/wine/prefix proccontrol -m aslr -s disable wine ./setup.exe
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66

WordPerfect still sells Windows 10 compatible versions of Paradox.

But I hear not much has changed and I don't believe it runs on Linux / Wine.
I'm just using it to get by for now, will be doing better things in the near future.

And besides, I'm looking to get rid of Windows (and all related software, if possible), for good.
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66


I'll try to keep working on this over the next couple days.
Will post results.

I think the biggest problem is a lack of clear instructions.
It's incredibly complicated to start with, mostly thanks to Micro$oft,
but not having clear instructions make it pretty easy to get tripped up
and fall into a hole.

I had a hard-won routine for installing 64 & 32 bit wine on Devuan, had it working great,
but this is a whole different situation.

After reading yesterdays posts it seems there are issues but sounds like they are working on them.

I've never in my life seen such a great forum with such a bunch of helpful people.
Absolutely amazing.
That alone makes me want to stick with FreeBSD 100 percent.

.
.
.
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66


Okay, so I ran some tests.

It seems my main problem was the software version mis-match, caused by installing the wrong pkg32.sh (installed wine, rather than wine-devel).

Fixed that, then was able to run both winetricks and winecfg.

But was not able to install anything. It just sat there, no error, no nothing.

Deleted the default prefix, as follows:
as root-
rm -rf /home/dd/.wine

reboot

NOW can install software, as follows:
as reg user-
wine /home/dd/paradoxcd/setup.exe

It runs.
Some dialogue boxes seem to lag as I drag them across the screen, but it does run.

That might be just a setting.

- - -

Now, the next problem:

I cannot create a prefix.

I try with winetricks GUI. Nothing. (Also, no way to list existing prefixes with winetricks, which is pretty annoying.)

I try from command line,,
as reg. user-
Winearch=win32 WINEPREFIX="/home/dd/.paradox32/" winecfg

Nothing.


I check contents of directory:
ls -al /home/dd/
only shows .wine
No .paradox32

How do you create a wine prefix in FreeBSD?
Is there any way to list wine prefixes?
How do you install into a wine prefix?

Are there any better GUI's for wine / FreeBSD?
Winetricks GUI seems pretty primitive.

Thanks again for your help.
.
.
.
 

Alexander88207

Aspiring Daemon

Reaction score: 698
Messages: 900

I check contents of directory:
ls -al /home/dd/
only shows .wine
No .paradox32
I try from command line,,
as reg. user-
Winearch=win32 WINEPREFIX="/home/dd/.paradox32/" winecfg

Nothing.

You should get a window like this for some seconds.

Screenshot_2022-05-13_05-47-03.png


How do you create a wine prefix in FreeBSD?

The way you have it done, you just init Wine in an new folder and then it creates its prefix.
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66

You should get a window like this for some seconds.

View attachment 13907

So you:
as reg user-
md /home/username/newwineprefixfolder
cd /home/username/newwineprefixfolder
winecfg
or
winetricks

Makes sense now that you say it.

But not obvious.

Wine needs a good and intiutive GUI.
Crossover office made it pretty easy.

What about:
Creating the prefix folder outside of the users home folder,
for the purpose of sharing wine profiles as multi-user, as long as
user is on that same machine?
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66

WINEPREFIX=/home/username/newwineprefixfolder winecfg or winetricks.

And, to create a 32-bit prefix, (I don't think they even had 64-bit ~25 years ago when this version of Paradox was released),

WINEPREFIX=/home/username/newwineprefixfolder WINEARCH="win32" winecfg or winetricks
.
Will give it a try today and report back.
.
 

Alexander88207

Aspiring Daemon

Reaction score: 698
Messages: 900

WINEPREFIX=/home/username/newwineprefixfolder WINEARCH="win32" winecfg or winetricks

You dont need to create an 32-bit prefix, wine can run both at once. Only in some cases its need to run an 32-bit only prefix.
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66

And, to create a 32-bit prefix, (I don't think they even had 64-bit ~25 years ago when this version of Paradox was released),

WINEPREFIX=/home/username/newwineprefixfolder WINEARCH="win32" winecfg or winetricks
.
Will give it a try today and report back.
.

This doesn't work.

We need clear instructions:
1. How to create a 32-bit (or 64-bit - likely the default if you don't specify) wine prefix (presumably from the command line)
2. How to Install a windows program into that same 32-or-64 bit prefix.
.
I'll have to mess around some more a little latter.
.
 

Alexander88207

Aspiring Daemon

Reaction score: 698
Messages: 900

This doesn't work.

Once again, we need clear instructions re: how to:
1. Create a 32-bit wine prefix (presumably from the command line)
2. Install a windows program into that same 32-bit prefix.
.
.

You dont need to use a seperate wine command to create a prefix, any wine command will do it.

So if you are using for example WINEPREFIX=$HOME/.newemptyfolder wine Setup.exe then wine creates the prefix first and then runs the executable.
 

hunter0one

Active Member

Reaction score: 140
Messages: 164


The TL;DR is that the binary packages in pkg are not 32-bit and therefore you must compile them yourself from ports with the 32-bit flags turned on (since they are turned off in the pkg versions).
Wait, 32-bit is a flag you can "turn on"? I thought you had to use a jail or something similar just to build a 32-bit package.

Good to hear that this is now solved.
 
OP
D

Dave-D

Member

Reaction score: 14
Messages: 66

Wait, 32-bit is a flag you can "turn on"? I thought you had to use a jail or something similar just to build a 32-bit package.

Good to hear that this is now solved.

I was able to create a 32-bit wine prefix.
But, at least so far, had to use winetricks to do it.
Type winetricks --help
there is a 32|64 bit flag.
I tried a number of times but still ended up with a 64-bit prefix.

Pretty sure I used:
as reg. user-
WINEPREFIX=/home/username/newwineprefixfolder WINEARCH=win32 winetricks

Then, see under winetricks --help, there is a flag to use for making a prefix active (or whatever language it uses).
When you run that command, it will show if you're now using a 32 or 64 bit prefix.

I think there's another command for installing software into a wineprefix.

I just messed around a half hour earlier today.
This needs more work.
.
I know that when I used codeweavers crossover office (GUI for wine) on linux a few years back,
it did create 32 or 64 bit "bottles" (prefixes).
 
Top