Solved 14.1 : Cannot run Windows executable after Wine installation

M

mauror

Good morning all, I've installed Wine following Manpage steps.
Apparently it went well, also Wine desktop object appears in the Apps folder.
Then tried to run a Windows executable first time, doubleclick on the file.
A Wine configuration-in-progress window has shown to work for some seconds, then nothing.
Have tried to make the executable start in the terminal by the command
wine program.exe

and received

/home/nomad/.i386-wine-pkg//usr/local/bin/wine doesn't exist!
Try installing 32-bit Wine with
/usr/local/share/wine/pkg32.sh install wine mesa-dri

applied /usr/local/share/wine/pkg32.sh install wine mesa-dri command

and received

pkg -o ABI_FILE=/usr/lib32/libc.so.7 -o INSTALL_AS_USER=true -o RUN_SCRIPTS=false --rootdir /home/nomad/.i386-wine-pkg install wine mesa-dri
pkg: Unable to determine the ABI, none of the ABI_FILEs can be read.
pkg: Cannot parse configuration file!

I'm stuck there, not catching what else to do.
Coud anyone give a help to me?
Thank you much
 
sorry about, no answers could mean no suggestion to give or otherwise maybe this is not the proper forum section?
Thank you
 
Just read your thread.
Sorry if the question sounds dumb or something, but with manpages you mean man wine ?
If so, I would suggest you reading Chapter 13. Wine from the FreeBSD handbook.

Did you check, whether the ABI_FILE is available on your system ?
Did you install FreeBSD with 32-bit support ?
 
Let's see.
Maybe this article could help.
Try to follow the steps of i386-compat, and then try to re-run this command: [I]/usr/local/share/wine/pkg32.sh install wine mesa-dri[/I].
 
given command:

sudo pkg install i386-compat

then

Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'i386-compat' have been found in the repositories

should mean that the packages is abandoned for 14.1 release
 
Right, the i386 packages are abandoned, but I thought this one, since it is for compatibility still remains...
Well, my recommendation is, download the 32-bit tar.gz file, extract it, put the 32 bit libraries into their appropriate directory, and then try wine again.

The other step would be to reinstall FreeBSD with all lib32-bit components enabled in bsdinstall.
 
good! That was what needed: found that the 32-bit libraries to add in Freebsd 14.1 were in the lib32.txz file downloadable from http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/14.1-RELEASE/
Once extracted and copied files in the right paths, I repeated the installation steps for Wine, then trying to run program.exe first time, it asked again for /usr/local/share/wine/pkg32.sh install wine mesa-dri , gave the command and it completed the necessary pkg operations. But still could not run any of the Windows executable, many lines telling files-dlls not found. Finally have read the fix on another sitepage for a similar issue: when the result give a lot of dlls missing, just uninstall wine package, delete the .wine directory, reinstall wine package.
Now the Windows executable are up 'n running.
Thank you much for your assistance
 
Congrats on your success.
I don't have a dog in this event, just observing.

It seems to me if you have need to run Windows executables, it is simpler to run them on Windows.
Otherwise, WINE has to keep a complete and accurate Win32Wow and Win64 emulator under the hood.
I very much doubt an emulator has all the hidden and undocumented functions that comprise Windows.

If you are an all 'Nix shop, keep a virtual machine available to run a native installation of Windows.
 
bgavin said:
It seems to me if you have need to run Windows executables, it is simpler to run them on Windows.
Otherwise, WINE has to keep a complete and accurate Win32Wow and Win64 emulator under the hood.
I very much doubt an emulator has all the hidden and undocumented functions that comprise Windows.
Click to expand...

of course it is, but since I like Freebsd too, which actually boots and run in an USB stick installation, find that the few old windows application useful to me can be handy from there by wine. Also have the possibility to boot same USB stick in a Virtualbox session hosted by Windows, but prefer to act directly in the real OS session when possible.
Then I also use VM machine on Virtualbox or VMware when find constrain to boot a system in a physical volume (i.e. no way with OS2 Warp 4.52 on contemporary hardware). Needless to say I'm doing same with Ubuntu as well
 
G
mauror said:
good! That was what needed: found that the 32-bit libraries to add in Freebsd 14.1 were in the lib32.txz file downloadable from http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/14.1-RELEASE/
Once extracted and copied files in the right paths, I repeated the installation steps for Wine, then trying to run program.exe first time, it asked again for /usr/local/share/wine/pkg32.sh install wine mesa-dri , gave the command and it completed the necessary pkg operations. But still could not run any of the Windows executable, many lines telling files-dlls not found. Finally have read the fix on another sitepage for a similar issue: when the result give a lot of dlls missing, just uninstall wine package, delete the .wine directory, reinstall wine package.
Now the Windows executable are up 'n running.
Thank you much for your assistance
Click to expand...
Glad to help.
One think I wanted to add, if some dlls are missing in the future, try out emulators/winetricks first on your $WINEPREFIX.
It might help :)
 
You must log in or register to reply here.
Back
Top