Shulou(Shulou.com)06/02 Report--

Wine (Wine Is Not an Emulator) [that is, Wine is not just a simulator] is an implementation of Windows 3.x and Windows APIs on top of Linux and UNIX. It is a Windows compatibility layer, which, in popular words, is a Windows simulator that provides both a development kit (Winelib) for entering and leaving UNIX from Windows sources, as well as a program loader that allows you to run under Intel Unix and its derivative versions without any modification to Windows 3.1/95/NT binaries. Wine works in most UNIX versions, including Linux, FreeBSD And Solaris. Wine does not need Microsoft Windows because it is an optional implementation made up of 100% free code, but it is free to use the DLLs of the local system if they can be exploited. The release of Wine is fully open source and is distributed free of charge.

Wine is still in development, but newer versions can run some famous software, even Photoshop CS3!

The official site of Wine is http://www.winehq.com/, although you can download the source code from its official site and configure and compile it yourself, but this process is quite tedious!

Compilation and installation

If you have installed the software you need to compile (such as gcc flex bison fontforge), you can compile!

First, visit http://www.winehq.com/ to download the latest version of wine and extract it to a directory

Open the terminal ("Terminal")

Enter the following command:

Cd # enter the directory

. / configure # check the compilation environment

How do you compile unsuccessfully, prompting you to install something? I guess some tools are not installed.

If nothing happens, you can run:

Yum install X*

Yum install * freetype*

Yum install * FreeType*

And then:

Make # can be compiled if the previous step is successful

The compilation of Wine can be completed by installing make install #.

Note: it usually takes an hour to compile WINE (depending on the performance of the machine). If you are new to Linux, it is best not to compile.

Download and install

If you use a distribution such as Debian or Ubuntu, you only need one command to complete the installation:

Sudo apt-get install wine

If you are using another distribution, please visit http://winehq.org/site/download to query the installation method

Configuration of Wine

Just run winecfg with detailed configuration. Note: winecfg versions of Wine 1.1.27 and above already have a Chinese interface.

The solution of Chinese garbled Code in Wine

Chinese support for Wine version 1.1.4 and above has been greatly improved. If you are using an earlier version of WINE or are not satisfied with the Chinese support of WINE, you can save the following text as a zh.reg file

Just run regedit and import it.

REGEDIT4

[HKEY_LOCAL_MACHINE\ Software\ Microsoft\ Windows NT\ CurrentVersion\ FontSubstitutes]

"Arial" = "WenQuanYi Zenhei"

"Arial CE,238" = "WenQuanYi Zenhei"

"Arial CYR,204" = "WenQuanYi Zenhei"

"Arial Greek,161" = "WenQuanYi Zenhei"

"Arial TUR,162" = "WenQuanYi Zenhei"

"Courier New" = "WenQuanYi Zenhei"

"Courier New CE,238" = "WenQuanYi Zenhei"

"Courier New CYR,204" = "WenQuanYi Zenhei"

"Courier New Greek,161" = "WenQuanYi Zenhei"

"Courier New TUR,162" = "WenQuanYi Zenhei"

"FixedSys" = "WenQuanYi Zenhei"

"Helv" = "WenQuanYi Zenhei"

"Helvetica" = "WenQuanYi Zenhei"

"MS Sans Serif" = "WenQuanYi Zenhei"

"MS Shell Dlg" = "WenQuanYi Zenhei"

"MS Shell Dlg 2" = "WenQuanYi Zenhei"

"System" = "WenQuanYi Zenhei"

"Tahoma" = "WenQuanYi Zenhei"

"Times" = "WenQuanYi Zenhei"

"Times New Roman CE,238" = "WenQuanYi Zenhei"

"Times New Roman CYR,204" = "WenQuanYi Zenhei"

"Times New Roman Greek,161" = "WenQuanYi Zenhei"

"Times New Roman TUR,162" = "WenQuanYi Zenhei"

"Tms Rmn" = "WenQuanYi Zenhei"

Official introduction

Wine is an Open Source implementation of the Windows API on top of X, OpenGL, and Unix.

Think of Wine as a compatibility layer for running Windows programs. Wine does not require Microsoft Windows, as it is a completely free alternative implementation of the Windows API consisting of 100% non-Microsoft code, however Wine can optionally use native Windows DLLs if they are available. Wine provides both a development toolkit for porting Windows source code to Unix as well as a program loader, allowing many unmodified Windows programs to run on x86-based Unixes, including Linux, FreeBSD, Mac OS X, and Solaris.

More information can be read in the articles Why Wine is so important, and Debunking Wine Myths. If you are wondering how well a particular application works in Wine, please examine the Applications Database. For installation instructions and step-by-step help with running Wine, take a look at the User Guide.

Wine is free software. The licensing terms are the GNU Lesser General Public License.

Simple usage of Wine

Wine can work with most Unix versions, but it still can't run all Windows programs, but with new versions almost every month, more and more Windows programs have been able to run in Linux with the help of Wine.

1. Run the program directly using the command wine [root@localhost root] # wine

2, use the program manager [root@localhost root] # progman to launch the manager window, select File (F)-execute (X) from the menu, a directory browser will pop up, and you can select the program.

3, double-click the EXE program directly when some distributions install win, it will automatically associate the EXE program, so you can run it by double-clicking directly. Some simple programs can be run directly without installation.

For example: Wine runs Guotai Junan stock software

If you often use the Linux desktop (such as Ubuntu), you can use the following methods to install Guotai Junan stock software into the Ubuntu system.

1. Install Wine sudo apt-get install wine

two。 Download Guotai Junan stock installation software

3. Change the current directory to a directory with Guotai Junan stock software and run the following command: wine setup_dzh6_fuyi.exe

At this point, the same installation interface as in Microsoft Windows will appear and follow the prompts to install.

Note: if there is garbled code at this time, it may be due to a problem with font replacement in Wine, please refer to the following link: http://forum.ubuntu.org.cn/viewtopic.php?t=72933--

4. Run Guotai Junan stock software

Run the following command:

Cd / .wine/drive_c/DZH5/internet/ wine Hypmain.exe

What can Wine do?

In this article, we discuss the installation of Wine on pure Linux, without any Windows partitions.

1. Windows executables: Wine fully supports binary loading of Windows executables (.exe and DLL).

2. DLL: Wine has hundreds of internal implementations of Windows DLL-- but not many of them are complete. For example, userd32.dll, which contains user interface-related functions, is implemented at 92% in open source Wine.

3. COM: this is a Windows technology used by almost all large Windows applications that supports features such as embedding an Excel spreadsheet into an Word document. This technology is well supported by Wine.

4. Registry: this is another key technology used by almost any Windows application. Wine implements about 90% of the Windows registry management API.

5. Core functions: core system functions are also well supported. As mentioned earlier, although there are differences between Linux and Windows, there are many similarities at the basic level, so the core system API related to processes, threads, files, and message queues is supported almost perfectly.

6. Audio and video: Wine supports the operation of Windows audio and video files (you can also use a Windows media player).

7. Printing: it is also supported to print from a Windows application running in Wine.

8. ODBC: Wine supports Windows applications that need to access the database through ODBC.

9. Debugging: Wine has a very robust and powerful built-in debugger that, in addition to supporting standard debugging capabilities, is customized for debugging Windows binaries running on Linux. It is one of the most important tools that Wine provides to its developers. Wine also has a well-designed module for tracking and logging, which can help debugging. The reason we emphasize this is that although the framework is robust, there are many uncertainties when installing and running Windows applications in Wine, and sooner or later you will stop debugging when using open source Wine.

What can't Wine do?

Unfortunately, many users find Wine difficult to use. Admittedly, it can be difficult to use an application like MS Office on Linux; let's look at some reasons why this is true. Before we begin, we should point out that the commercial Wine (CrossOver) provided by CodeWeavers has solved most of these problems (see Resources for a link). Over time, these issues will probably be solved in open source Wine as well.

1. Using the command line, like most applications in Linux, Wine must be installed on the command line. The user must return to the command line to run the application under Wine. For example, to run Internet Explorer, users usually need to enter wine IEXPLORE.EXE in shell. Although experienced users like to do this, beginners will find it difficult and are less likely to know shortcuts such as aliases. However, users can now directly double-click the EXE file to run it (if associated), although this can make it difficult to view error messages.

two。 The configuration of Wine is more complex. But now that there is a simplified Chinese interface, for beginners, the configuration is a lot easier.

3. Unhide hidden files if you do not use the special unhide option when mounting CDROM, some files on the installation CD may not be found, resulting in installation failure.

4. Tuning the configuration of the Wine installation is rarely used directly (for it, that is, untying it from tarfile). General adjustments are usually required; for example, the installation of a program may not be compatible with the version of Windows that you set in the configuration file, and changing that version may affect some installed applications. The same is true for many DLL. To do this, Wine provides an ingenious fix that allows you to set application-specific properties. However, the average user may not be as satisfied as we are.

5. Additional installation steps the installation process for most applications is not standard. For example, when we install Internet Explorer 6, we have to skip some steps, such as locating and installing DCOM98. For users, this kind of thing may be the biggest obstacle. Note that these are not symptoms, but examples of what kinds of things make Wine seem complex and difficult for the average user. More what Wine can't do.

After looking at the usability issues of Wine, let's summarize some common technical problems when trying to use Wine.

1. Missing DLL is probably the most common problem: many installations fail due to lack of DLL. People should be proficient in using debuggers to decide what to do next. (the debugger will be discussed in depth later).

2. DLL version problems some installers check the existing system DLL before starting. Wine's solution to this problem is to create a fake DLL to meet the needs of the installer. However, there are installers that take a closer look at DLL and drill down to get their version. This is too demanding for a fake DLL and can cause the installation to fail.

3. The DLL load order Wine has implementations of many Windows DLL, and if available, it can also use the original Windows DLL. If both DLL are available, it seems obvious that you should always choose to use Windows's own DLL, but in fact Windows DLL sometimes contains dependencies that cannot be satisfied. The only way to determine whether you should use Wine's DLL or native DLL is to experiment over and over again based on each application.

4. Functions in DLL when a Wine DLL does not implement all the functions of the corresponding DLL in Windows, the application may encounter function call failure. Because DLL is dynamically loaded, there may be no way to know in advance that this is going to happen. This is a complex issue, and there is some work to be done, but in the end, it just depends on how the application's code is written. There are some factors that will alleviate these problems. On the one hand, you will encounter these problems one by one, rather than all at once, which is easier to deal with. In addition, the problems you encounter may have been encountered and resolved by others (and the solution has been announced). The Wine user group is very active and provides a lot of help, and the weekly Wine newsletter (see Resources) is an excellent information resource. Win32 API that has not yet been implemented in Wine in Wine, many of the functions of Win32 API5 are incomplete. The most common reason is that a considerable number of Win32 API are not documented. This means that a particular application may call a function without any available information about that function. For example, we found the function RtlAnsiCharToUnicodeChar when running a simple RPC program. The search results on MSDN show that there is no information about this function, and there is no information about all RtlXXXX class functions. So if their implementation in Wine is critical to some applications, people may have to guess their behavior.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.