?? rhl58.htm
字號:
<HTML>
<HEAD>
<TITLE>Red Hat Linux Unleashed rhl58.htm </TITLE>
<LINK REL="ToC" HREF="index-1.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/index.htm">
<LINK REL="Index" HREF="htindex.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/htindex.htm">
<LINK REL="Next" HREF="rhl59.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhl59.htm">
<LINK REL="Previous" HREF="rhl57.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhl57.htm"></HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080">
<A NAME="I0"></A>
<H2>Red Hat Linux Unleashed rhl58.htm</H2>
<P ALIGN=LEFT>
<A HREF="rhl57.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhl57.htm" TARGET="_self"><IMG SRC="purprev.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>
<A HREF="index-1.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/index.htm" TARGET="_self"><IMG SRC="purtoc.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purtoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>
<A HREF="rhl59.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhl59.htm" TARGET="_self"><IMG SRC="purnext.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purnext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>
<HR ALIGN=CENTER>
<P>
<UL>
<UL>
<UL>
<LI>
<A HREF="#E68E447" >Current Status of Wine</A>
<LI>
<A HREF="#E68E448" >Setting Up Wine</A>
<UL>
<LI>
<A HREF="#E69E575" >System Requirements</A>
<LI>
<A HREF="#E69E576" >Where To Get the Wine Distribution</A>
<LI>
<A HREF="#E69E577" >How To Install Wine</A>
<LI>
<A HREF="#E69E578" >How To Configure Wine Before Building</A>
<UL>
<LI>
<A HREF="#E70E37" >Initially Configuring Runtime Parameters with Configure</A>
<LI>
<A HREF="#E70E38" >Automatic System-Specific Configuration</A></UL>
<LI>
<A HREF="#E69E579" >How To Build Wine</A></UL>
<LI>
<A HREF="#E68E449" >Using Wine</A>
<UL>
<LI>
<A HREF="#E69E580" >Specifying Configuration Parameters</A>
<LI>
<A HREF="#E69E581" >Using Command-Line Options</A>
<LI>
<A HREF="#E69E582" >The Wine Debugger</A></UL>
<LI>
<A HREF="#E68E450" >How Wine Works</A>
<UL>
<LI>
<A HREF="#E69E583" >How Wine Loads Programs</A>
<LI>
<A HREF="#E69E584" >The Wine Library</A></UL>
<LI>
<A HREF="#E68E451" >Where Does Wine End and MS Windows Begin?</A>
<LI>
<A HREF="#E68E452" >Limitations of Wine</A>
<UL>
<LI>
<A HREF="#E69E585" >Software That Works</A>
<LI>
<A HREF="#E69E586" >Using winestat To Analyze Windows Programs</A>
<LI>
<A HREF="#E69E587" >Major Pieces That Are Missing from Wine</A>
<LI>
<A HREF="#E69E588" >Software Unlikely to Ever Work</A></UL>
<LI>
<A HREF="#E68E453" >History of Wine</A></UL></UL></UL>
<HR ALIGN=CENTER>
<A NAME="E66E58"></A>
<H1 ALIGN=CENTER>
<CENTER>
<FONT SIZE=6 COLOR="#FF0000"><B>58</B></FONT></CENTER></H1>
<BR>
<A NAME="E67E58"></A>
<H2 ALIGN=CENTER>
<CENTER>
<FONT SIZE=6 COLOR="#FF0000"><B>The Wine Project</B></FONT></CENTER></H2>
<BR>
<P>Wine stands for Windows Emulator. It enables Microsoft Windows programs to run under a UNIX X Windows environment. Like DOSemu, Wine takes direct advantage of the Intel 386 architecture to actually run the MS Windows application. Wine simply translates
any MS Windows API calls into appropriate UNIX and X Windows calls. Like OS/2, MS Windows programs running under Wine get to take advantage of features of the underlying operating system. Wine is simply another user-mode Linux process that is protected
from corruption by other process. This is dubbed crash-protection under OS/2. Because Linux uses preemptive multitasking, Wine processes can coexist with other processes without some of the problems experienced by applications running under native MS
Windows.
<BR>
<BR>
<A NAME="E68E447"></A>
<H3 ALIGN=CENTER>
<CENTER>
<FONT SIZE=5 COLOR="#FF0000"><B>Current Status of Wine</B></FONT></CENTER></H3>
<BR>
<P>As with most of the Linux community, developers of Wine are volunteers. Wine is currently Alpha or pre-release code. Only a few of the simplest MS Windows applications run without incident. My favorite MS Windows Entertainment Pack game, Pipe Dream by
Lucas Arts, runs acceptably under Wine, as shown in Figure 58.1.
<BR>
<P><B> <A HREF="58rhl01.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/58rhl01.gif">Figure 58.1. Pipe Dream running under Wine.</A></B>
<BR>
<P>Although Pipe Dream and other simple games are certainly playable under Wine, everything is not perfect. Some speed degradation is noticeable, as is the occasional screen glitch.
<BR>
<P>Sun Soft has implemented a similar product, called WABI, for its UNIX-based workstations. WABI has been on the market for over a year and supports some of the more complex MS Windows applications such as Microsoft Excel and Lotus Smart Suite. Given
enough development time, it is reasonable to expect that Wine will be capable of running general MS Windows applications as well.
<BR>
<BR>
<A NAME="E68E448"></A>
<H3 ALIGN=CENTER>
<CENTER>
<FONT SIZE=5 COLOR="#FF0000"><B>Setting Up Wine</B></FONT></CENTER></H3>
<BR>
<P>Wine is available only as source code. If you have the prerequisite software and a little patience, setting Wine up is not very difficult—even if you are not a programmer.
<BR>
<BR>
<A NAME="E69E575"></A>
<H4 ALIGN=CENTER>
<CENTER>
<FONT SIZE=4 COLOR="#FF0000"><B>System Requirements</B></FONT></CENTER></H4>
<BR>
<P>Any Linux machine suitable for running X Window will run Wine applications at a reasonable speed. In theory, Wine should have some advantages running under Linux as opposed to under MS Windows, which is confined to the MS-DOS environment. Experiences
with current versions of Wine show that an application running under Wine is slower on the same machine running MS-DOS and MS Windows.
<BR>
<P>To make full use of Wine, you need MS Windows 3.1 installed on a disk partition that is accessible under Linux. It is also convenient to run existing MS Windows applications from the same directory in which they are installed under native MS-DOS and MS
Windows. The typical Linux user also has MS-DOS and MS Windows installed on a hard drive; thus it is only a matter of making the directories available under Linux. Linux kernels as of Version 1.1.83 do not support compressed MS-DOS file systems made by
MS-DOS utilities such as stacker and drvspace.
<BR>
<BLOCKQUOTE>
<BLOCKQUOTE>
<HR ALIGN=CENTER>
<BR>
<NOTE>Some Linux installation programs will prompt you through setting up an MS-DOS partition as a Linux subdirectory. If you did not set up such a partition, add the following line to your /etc/fstab,
<BR>/dev/hda1 /c MSDOS defaults
<BR>where hda1 is the partition that contains MS-DOS, and /c is the Linux subdirectory to use. In this example it is assumed that the /c subdirectory exists. Otherwise, use mkdir to create the subdirectory.</NOTE>
<BR>
<HR ALIGN=CENTER>
</BLOCKQUOTE></BLOCKQUOTE>
<P>Wine is distributed as source code, and must be compiled before use. It requires approximately 10MB of disk space. 3.5MB of that disk space is the source code alone. To build Wine, you need to have the following:
<BR>
<UL>
<LI>GCC
<BR>
<BR>
<LI>LibC
<BR>
<BR>
<LI>XFree with development parts loaded
<BR>
<BR>
<LI>Linux kernel newer than 99.13
<BR>
<BR>
</UL>
<BR>
<A NAME="E69E576"></A>
<H4 ALIGN=CENTER>
<CENTER>
<FONT SIZE=4 COLOR="#FF0000"><B>Where To Get the Wine Distribution</B></FONT></CENTER></H4>
<BR>
<P>A new version of Wine is released approximately once a week. Major Linux FTP sites on the Internet contain the most recent release. On <A HREF="tppmsgs/msgs0.htm#72" tppabs="ftp://sunsite.unc.edu/">sunsite.unc.edu</A>, look in the /pub/Linux/ALPHA/wine/development directory. Wine
releases are named after the date they are released. Wine-950727.tar.gz was released on 7/27/95. The most current release is the one with the latest date. For more information, check out the Web page at <A
HREF="tppmsgs/msgs2.htm#200" tppabs="http://daedalus.dra.hmg.gb/gale/wine/wine.html">http://daedalus.dra.hmg.gb/gale/wine/wine.html</A>.
<BR>
<BR>
<A NAME="E69E577"></A>
<H4 ALIGN=CENTER>
<CENTER>
<FONT SIZE=4 COLOR="#FF0000"><B>How To Install Wine</B></FONT></CENTER></H4>
<BR>
<P>Unlike DOSemu, the Wine distribution is not sensitive to where it is installed. For brevity, make a symbolic link from the actual directory (say /usr/src/Wine950122) to /usr/wine using the ln command as follows:
<BR>
<BR>
<PRE>
<FONT COLOR="#000080"># ln -s /usr/src/Wine950122 /usr/wine</FONT></PRE>
<P>A Wine distribution consists of a compressed tar file. To unpack the distribution, use a shell command such as
<BR>
<BR>
<PRE>
<FONT COLOR="#000080"># tar -zxvf filename.tar.gz</FONT></PRE>
<BR>
<A NAME="E69E578"></A>
<H4 ALIGN=CENTER>
<CENTER>
<FONT SIZE=4 COLOR="#FF0000"><B>How To Configure Wine Before Building</B></FONT></CENTER></H4>
<BR>
<P>Wine must be configured before being built. The Configure utility prompts the user for the necessary information, and automatically builds the appropriate configuration files. There are three major steps to configuring Wine:
<BR>
<OL>
<LI>Compilation configuration
<BR>
<BR>
<LI>Run-time parameters
<BR>
<BR>
<LI>Automatic system specific configuration
<BR>
<BR>
</OL>
<P>The configure script begins with the following questions.
<BR>
<PRE>
<FONT COLOR="#000080">Build Wine as emulator or library (E/L) [E]?
Short filenames (Y/N) [N]?
Use the XPM library (Y/N) [N]?
Language [En/De/No] ?
Global configfile name /usr/local/etc/wine.conf</FONT></PRE>
<P>It is safe to press Enter and accept the defaults for these questions. These parameters are added to a global configuration file, autoconf.h. If parameter changes are necessary, re-run Configure. To avoid errors, do not attempt to edit this file.
<BR>
<BR>
<A NAME="E70E37"></A>
<H5 ALIGN=CENTER>
<CENTER>
<FONT SIZE=4 COLOR="#FF0000"><B>Initially Configuring Runtime Parameters with </B><B>Configure</B></FONT></CENTER></H5>
<BR>
<P>The questions in this section relate to lines in the global configuration file /usr/local/etc/wine.conf. Following each question is an explanation of its meaning.
<BR>
<PRE>
<FONT COLOR="#000080">Which directory do you want to use as A:
Which directory do you want to use as C:</FONT></PRE>
<P>Answer these questions with the Linux directory where the MS-DOS A: and C: drive are mounted. If your disk partition on which MS Windows is mounted is /c, then use /c. If you do not plan on using a floppy disk, do not worry if A: does not point to a
valid directory.
<BR>
<PRE>
<FONT COLOR="#000080">Where is the Windows directory 'c:\windows\'
Where is the System directory 'c:\windows\system'
Where should Windows apps store temp files 'c:\windows\temp'
Which path should be used to find progs/DLL's 'c:\windows;c:\windows\system'</FONT></PRE>
<P>These directories should match where MS Windows is installed on your MS-DOS partition. Because the default MS Windows installation is in c:\windows, the default answers are usually sufficient.
<BR>
<BR>
<PRE>
<FONT COLOR="#000080">Where is sysres.dll /usr/wine/sysres.dll'</FONT></PRE>
<P>The sysres.dll is a DLL that contains Wine specific resources. These resources include bitmaps and dialog boxes for things like the About Wine menu item. The default value is sufficient here as well.
<BR>
<PRE>
<FONT COLOR="#000080">Where is COM1" CF_Com1 '/dev/cua0'
Where is COM2" CF_Com2 '/dev/cua1'
Where is LPT1" CF_Lpt1 '/dev/lp0'</FONT></PRE>
<P>As with DOSemu, the communication and printer ports under Wine can be configured as any similar port under Linux. For simplicity, it is best to map the COM and LPT ports to the same ones that would appear under native MS-DOS.
<BR>
<BR>
<PRE>
<FONT COLOR="#000080">Log messages to which file (CON = stdout) 'CON'</FONT></PRE>
<P>This defines where the system messages generated by Wine will go. Sending messages to CON will send them to stdout. This is the most useful place, as these messages can easily be redirected elsewhere. By default, Wine generates a lot of informational
messages, which slows things down a bit. A casual user will likely want to redirect these messages to /dev/null. To make this be the default action, use /dev/null for the log file.
<BR>
<P>Configure displays a long list of message types and asks the following question:
<BR>
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -