The translation is temporarily closed for contributions due to maintenance, please come back later.


<prompt>#%</prompt> <userinput>pkg install konquerorwine /home/<replaceable>user</replaceable>/bin/program.exe</userinput>
(itstool) path: sect2/screen
<prompt>%</prompt> <userinput>wine /home/<replaceable>user</replaceable>/bin/program.exe</userinput>
Context English Persian State
On modern, 64-bit machine and want to run 64-bit <trademark class="registered">Windows</trademark> software, simply install the ports mentioned in the above sections. The ports system will automatically install the 64-bit version.
Alternately, users might have an older 32-bit machine that they do not want to run with its original, now non-supported software. They can install the 32-bit (i386) version of FreeBSD, then install the ports in the above sections. Again, on a 32-bit machine the ports system will install the corresponding 32-bit version of WINE by default.
However, given a 64-bit version of FreeBSD and need to run <emphasis role="strong">32-bit</emphasis> <trademark class="registered">Windows</trademark> applications, installing a different port is required to enable 32-bit compatibility. To install the pre-compiled package, use the following:
<prompt>#</prompt> <userinput>pkg install i386-wine</userinput> <prompt>#</prompt> <userinput>pkg install konqueror</userinput>
Or compile the port with the following:
<prompt>#</prompt> <userinput>cd /usr/ports/emulator/i386-wine</userinput>
<prompt>#</prompt> <userinput>make install</userinput>
Running a First WINE Program on FreeBSD
Now that WINE is installed, the next step is to try it out by running a simple program. An easy way to do this is to download a self-contained application, i.e., one can simply unpack and run without any complex installation process.
So-called "portable" versions of applications are good choices for this test, as are programs that run with only a single executable file.
Running a Program from the Command Line
There are two different methods to launch a Windows program from the terminal. The first, and most straightforward is to navigate to the directory containing the program's executable (<filename>.EXE</filename>) and issue the following:
<prompt>%</prompt> <userinput>wine program.exe</userinput> <prompt>%</prompt> <userinput>top</userinput>
For applications that take command-line arguments, add them after the executable as usual:
<prompt>%</prompt> <userinput>wine <replaceable>program2.exe</replaceable> -file <filename><replaceable>file.txt</replaceable></filename></userinput>
Alternately, supply the full path to the executable to use it in a script, for example:
<prompt>%</prompt> <userinput>wine /home/<replaceable>user</replaceable>/bin/program.exe</userinput> <prompt>#</prompt> <userinput>pkg install konqueror</userinput>
Running a Program from a GUI
After installation graphical shells should be updated with new associations for Windows executable (<filename>.EXE</filename>) files. It will now be possible to browse the system using a file manager, and launch the Windows application in the same way as other files and programs (either a single- or double-click, depending on the desktop's settings).
On most desktops, check to make sure this association is correct by right-clicking on the file, and looking for an entry in the context menu to open the file. One of the options (hopefully the default one) will be with the <emphasis role="strong">Wine Windows Program Loader</emphasis>, as shown in the below screenshot:
_ external ref='wine/wine-run-np++-1' md5='__failed__'
In the event the program does not run as expected, try launching it from the command line and review any messages displayed in the terminal to troubleshoot.
In the event WINE is not the default application for <filename>.EXE</filename> files after install, check the MIME associate for this extension in the current desktop environment, graphical shell, or file manager.
Configuring WINE Installation
With an understanding of what WINE is and how it works at a high level, the next step to effectively using it on FreeBSD is becoming familiar with its configuration. The following sections will describe the key concept of the <emphasis>WINE prefix</emphasis>, and illustrate how it is used to control the behavior of applications run through WINE.
WINE Prefixes
A WINE <emphasis>prefix</emphasis> is a directory, usually located beneath the default location of <filename>$HOME/.wine</filename> though it can be located elsewhere. The prefix is a set of configurations and support files used by the <application>wine</application> to configure and run the <trademark class="registered">Windows</trademark> environment a given application needs. By default, a brand new WINE installation will create the following structure when first launched by a user:
<filename>.update-timestamp</filename>: contains the last modified date of <filename>file /usr/share/wine/wine.inf</filename>. It is used by WINE to determine if a prefix is out of date, and automatically update it if needed.
<filename>dosdevices/</filename>: contains information on mappings of <trademark class="registered">Windows</trademark> resources to resources on the host FreeBSD system. For example, after a new WINE installation, this should contain at least two entries which enable access to the FreeBSD filesystem using <trademark class="registered">Windows</trademark>-style drive letters:
<filename>c:@</filename>: A link to <filename>drive_c</filename> described below.
<filename>z:@</filename>: A link to the root directory of the system.
<filename>drive_c/</filename>: emulates the main (i.e., <filename>C:</filename>) drive of a <trademark class="registered">Windows</trademark> system. It contains a directory structure and associated files mirroring that of standard <trademark class="registered">Windows</trademark> systems. A fresh WINE prefix will contain <trademark class="registered">Windows</trademark> 10 directories such as <emphasis>Users</emphasis> and <emphasis>Windows</emphasis> that holds the OS itself. Furthermore, applications installed within a prefix will be located in either <emphasis>Program Files</emphasis> or <emphasis>Program Files (x86)</emphasis>, depending on their architecture.


User avatar None

Source string changed

FreeBSD Doc (Archived) / books_handbookPersian

<prompt>#%</prompt> <userinput>pkg install konquerorwine /home/<replaceable>user</replaceable>/bin/program.exe</userinput>
a month ago
Browse all component changes

Things to check

XML markup

XML tags in translation do not match source



English Persian
Prompt پیام‌واره FreeBSD Doc (Archived)

Source information

Source string comment
(itstool) path: sect2/screen
Source string location
String age
a month ago
Source string age
a month ago
Translation file
books/fa/handbook.po, string 3287