Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Bread for the World

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 102 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       wine [wine_options] [--] program [arguments ... ]

       For instructions on passing arguments to Windows programs,
       please see the PROGRAM/ARGUMENTS section of the man  page.


       wine  program  loads and runs the given program, where the
       program is a DOS, Windows 3.x, or  Win32  executable  (x86
       binaries only).

       For debugging wine, use winedbg program instead.

       For  running  CUI  executables (Windows console programs),
       use wineconsole instead of wine run). Not  using  winecon­
       sole  for CUI programs will only provide very limited con­
       sole support, and your program might  not  function  prop­

       wine currently runs a growing list of applications written
       for all kinds of Windows versions >= Win2.0, e.g.  Win3.1,
       Win95/98,  NT.   Older,  simpler  applications work better
       than newer,  more  complex  ones.   Using  Windows  ME  or
       Win2000  components  with  Wine  is  more problematic than
       using none at all or the ones from older Windows versions.
       A  large  percentage  of  the  API  has  been implemented,
       although there are still several major pieces of work left
       to do.


       Read  the  README file in the Wine source distribution and
       the wine.conf man page to know what Wine requires and  how
       it is installed from source.


       --debugmsg [xxx]#name[,[xxx1]#name1]
              Turn debugging messages on or off.

              xxx  is  optional  and can be one of the following:
              err, warn, fixme, or trace.  If xxx is  not  speci­
              fied,  all  debugging  messages  for  the specified
              channel are turned on.   Each  channel  will  print
              messages  about  a particular component of wine.  #
              is required and can be either + or  -.   Note  that
              there is not a space after the comma between names.
              yyy are either the name of a whole DLL or a  single
              API  entry  by  name  you either want to include or
              exclude from the relay listing.  Case doesn't  mat­
              ter for these.  You can do the same for snoop.

              For instance:

              cdrom,  class, clipboard, clipping, combo, comboex,
              comm, commctrl, commdlg, console,  crtdll,  cursor,
              datetime,   dc,   ddeml,  ddraw,  debug,  debugstr,
              delayhlp,  dialog,  dinput,  dll,  dosfs,   dosmem,
              dplay,  driver,  dsound, edit, elfdll, enhmetafile,
              event, exec, file, fixup, font, gdi, global, graph­
              ics,   header,  heap,  hook,  hotkey,  icmp,  icon,
              imagehlp, imagelist, imm, int, int10, int16, int17,
              int19,  int21, int31, io, ipaddress, joystick, key,
              keyboard, loaddll, ldt, listbox,  listview,  local,
              mci,  mcianim,  mciavi,  mcicda,  mcimidi, mciwave,
              mdi, menu, message, metafile,  midi,  mmaux,  mmio,
              mmsys,  mmtime,  module, monthcal, mpr, msacm, msg,
              msvideo, nativefont, nonclient, ntdll,  odbc,  ole,
              opengl,  pager, palette, pidl, print, process, pro­
              file, progress, prop, propsheet, psapi, psdrv, ras,
              rebar,  reg,  region,  relay,  resource,  richedit,
              scroll, segment, seh,  selector,  sendmsg,  server,
              setupapi, setupx, shell, snoop, sound, static, sta­
              tusbar, storage, stress, string, syscolor,  system,
              tab,  tape, tapi, task, text, thread, thunk, timer,
              toolbar, toolhelp,  tooltips,  trackbar,  treeview,
              ttydrv,  tweak, typelib, updown, ver, virtual, vxd,
              wave, win, win16drv, win32, winedbg, wing, wininet,
              winsock, winspool, wnet, x11 and x11drv.

              For more information on debugging messages, see the
              file documentation/running.sgml in the source  dis­
              tribution (FIXME: outdated).

       --dll name[,name[,...]]={native|builtin}[,{n|b}[,...]]
              Selects  the  override  type  and load order of dll
              used in  the  loading  process  for  any  dll.  The
              default is set in the configuration file. There are
              currently three types  of  libraries  that  can  be
              loaded  into  a process' address space: Native win­
              dows dlls ( native ), wine internal dlls (  builtin
              ).  The type may be abbreviated with the first let­
              ter of the type ( n, b ). Each sequence  of  orders
              must be separated by commas.
              Each  dll may have its own specific load order. The
              load order determines which version of the  dll  is
              attempted  to  be loaded into the address space. If
              the first fails, then the next is tried and so  on.
              Multiple  libraries with the same load order can be
              separated with commas. It is also possible  to  use
              the  --dll option several times, to specify differ­
              ent loadorders for different libraries
              --dll comdlg32,commdlg=n,b
              Try to load comdlg32 and commdlg as native  windows
              mdlg, shell/shell32, etc.)  having exactly the same
              load  order.  This  will prevent mismatches at run­
              time.  See also configuration file format below.


       The program name may be specified in DOS format ( C:\\WIN­
       DOWS\\SOL.EXE)  or in Unix format ( /msdos/windows/sol.exe
       ).  You may pass arguments to the program  being  executed
       by  adding  them  to  the end of the command line invoking
       wine (such as: wine notepad  C:\\TEMP\\README.TXT).   Note
       that  you  need  to  '\'  escape  special  characters (and
       spaces) when invoking Wine via a shell, e.g.

       wine C:\\Program\ Files\\MyPrg\\test.exe

       Command line processing goes as follows: first wine checks
       whether  one  or  more of the above mentioned wine options
       have been specified. These are removed  from  the  command
       line,  which is passed to the windows program. You can use
       the parameter -- to indicate that wine should stop command
       line  processing. This is needed in case a windows program
       understands an option that  is  usually  interpreted  (and
       thus removed from the command line) by wine.  For example,
       if you  want  to  execute  wine  with  the  options  --dll
       riched32=n  and  if  wine should run the program myapp.exe
       with the arguments --display 3d somefile , then you  could
       use the following command line to invoke wine:

       wine --dll riched32=n -- myapp.exe --display 3d somefile

       Note  that  in  contrast to previous versions of wine, you
       must not pass program name and program option in one argu­
       ment  to wine.  To run more than one windows program, just
       execute wine once with the name of each program  as  argu­


       wine  makes  the  environment  variables of the shell from
       which wine is started accessible to the  windows/dos  pro­
       cesses  started.  So  use  the appropriate syntax for your
       shell to enter environment variables you need.

              If set, the content of this variable  is  taken  as
              the  name  of  the  directory where wine stores its
              data (the default is $HOME/.wine ). This  directory
              contains also the socket, which is used to communi­
              cate with the wineserver.  All wine processes using
              the same wineserver (i.e.: same user) share certain
              things like registry,  shared  memory,  and  config
              file.   By  setting  WINEPREFIX to different values
              for different wine processes, it is possible to run
              "wine"  in the path and in a few other likely loca­

              Specifies  the  path(s)  in  which  to  search  for
              builtin  dlls  and  Winelib applications. This is a
              list of directories separated by ":".  In  addition
              to  any  directory  specified  in WINEDLLPATH, Wine
              will also look in /usr/lib/wine.

              Specifies the X11 display to use.


       wine expects a  configuration  file  (  $WINEPREFIX/config
       (~/.wine/config) ), which must conform to the format spec­
       ified in the wine.conf(5) man page. A sample configuration
       file  is  documentation/samples/config  in the wine source


       wine is available thanks to the work of  many  developers.
       For  a listing of the authors, please see the file AUTHORS
       in the top-level directory of the source distribution.


       wine can be  distributed  under  the  terms  of  the  LGPL
       license.  A  copy of the license is in the file LICENSE in
       the top-level directory of the source distribution.


       A status report on many  applications  is  available  from
       http://www.winehq.com/Apps.   Please  add  entries to this
       list for applications you currently run.

       Bug   reports   may   be   posted   to    Wine    Bugzilla
       http://bugs.winehq.com  If  you want to post a bug report,
       please read the file documentation/bugs.sgml in  the  wine
       source to see what information is necessary

       Problems  and  suggestions  with  this manpage please also
       report to http://bugs.winehq.com


       The most recent public version of wine can be obtained via
       FTP from ibiblio.org in the /pub/Linux/ALPHA/Wine/develop­
       ment directory.  The releases are  in  the  format  'Wine-
       yyyymmdd.tar.gz',   or   'Wine-yyyymmdd.diff.gz'  for  the
       diff's from the previous release. The same directory holds
       the  pre-built  contents  of  the documentation in various
       formats (wine-doc.xxx.gz).



              The wine program loader.
              The wine program loader for CUI (console)  applica­
              The wine server
              The wine debugger
              The wine clipboard server
              Directory containing wine's shared libraries
              User-specific configuration file
              Directory  containing user specific data managed by



Wine 20030813                May 2002                     WINE(1)



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds