Differential D26914 Diff 80297 en_US.ISO8859-1/books/handbook/wine/chapter.xml

Changeset View

Standalone View

en_US.ISO8859-1/books/handbook/wine/chapter.xml

				<!-- START SECTION 3 -->
				<sect1 xml:id="running-first-wine-program">
				<title>Running a First WINE Program on &os;</title>
				bcrUnsubmitted Done Inline Actions You can use &os; as a placeholder for "FreeBSD". Also, I think the 's is not needed here. To avoid the use of "You", how about writing: Running the First WINE Program on &os; bcr: You can use &os; as a placeholder for "FreeBSD". Also, I think the 's is not needed here. To…
				bcrUnsubmitted Done Inline Actions It still says "FreeBSD" instead of &os; bcr: It still says "FreeBSD" instead of &os;

				<para>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 you can simply
				unpack and run without any complex installation process.</para>

				<para>So-called "portable" versions of applications are good
				choices for this test, as are programs that run with only a single
				executable file.</para>

				<sect2 xml:id="running-a-program-from-the-command-line">
				<title>Running a Program from the Command Line</title>

				<para>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 (.EXE file)
				and issue the following:</para>

				<screen>&prompt;<userinput>wine program.exe</userinput></screen>

				<para>For applications that take command-line arguments, add them after
				the executable as usual:</para>

				<screen>&prompt;<userinput>wine program2.exe -file file.txt</userinput></screen>

				<para>Alternately, supply the full path to the executable to use it in a
				script, for example:</para>

				<screen>&prompt;<userinput>wine /home/user/bin/program.exe</userinput></screen>
				</sect2>

				<sect2 xml:id="running-a-program-from-a-gui">
				<title>Running a Program from a GUI</title>

				<para>After installation graphical shells should be updated with new
				associations for Windows executable (.EXE) 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).</para>

				<para>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:</para>

				<mediaobject>
				<imageobject>
				<imagedata fileref="wine/wine-run-np++-1.png"/>
				</imageobject>
				</mediaobject>

				<para>In the event the program doesn't run as expected, try launching it
				from the command line and review any messages displayed in the
				terminal to troubleshoot.</para>

				<para>In the event WINE isn't the default application for .EXE files
				after install, check the MIME associate for this extension in the current
				desktop environment, graphical shell, or file manager.</para>
				</sect2>
				</sect1>