免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
12下一页
最近访问板块 发新帖
查看: 3791 | 回复: 12
打印 上一主题 下一主题

[Server 2003] LINUX下能运行windows程序了。。。。。 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2005-01-25 09:45 |只看该作者 |倒序浏览
意外的发现了在redflag linux中有一个软件包wine的东东能够让windows里程序在linux中运行 。但我不知道这样会不会让windows下的一些病毒也能够在linux中运行了呢???

起因是这样子的,,本人的本本是个双系统。windows and redflag linux。平时很少用windows,因为反应 太慢。常常常会中毒 ,,我都怕了,,,,

用的是LINUX系统。但里面的备份盘和资料盘啊,我把它们也挂载到LINUX下了。无事无聊下,我双击了那FOXMAIL。呵   ,,居然 了安装的界面,,太不不可不可思
了,,于是我试着把好几个windows下 程序安装,结果还真 能行。。。。

本人比较细心,,发现了一个东东,,就是在每次运行windows程序时,都会先运行一个黑呼呼的东不,,他仔细 看 了看,,wine,,,哈哈,,,我想就是这个东东蒎原因原因原因原因,,,,,,
于是我 man wine。。。。

哈哈,,,,,,,看到了下面:
WINE(1)                         Windows On Unix                        WINE(1)



NNAAMMEE
       wine - run Windows programs on Unix

SSYYNNOOPPSSIISS
       wwiinnee _[_w_i_n_e___o_p_t_i_o_n_s_] [[----]] _p_r_o_g_r_a_m [[aarrgguummeennttss ...... ]]

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

DDEESSCCRRIIPPTTIIOONN
       wwiinnee _p_r_o_g_r_a_m 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 wwiinneeddbbgg _p_r_o_g_r_a_m instead.

       For running CUI executables (Windows console programs), use wwiinneeccoonnssoollee
       instead of wwiinnee run). Not using wwiinneeccoonnssoollee for CUI programs will  only
       provide  very limited console support, and your program might not func-
       tion properly.

       wwiinnee 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.

RREEQQUUIIRREEMMEENNTTSS AANNDD IINNSSTTAALLLLAATTIIOONN
       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.

OOPPTTIIOONNSS
       _-_-_d_e_b_u_g_m_s_g _[_x_x_x_]_#_n_a_m_e_[_,_[_x_x_x_1_]_#_n_a_m_e_1_]
              Turn debugging messages on or off.

              xxx is optional and can be one  of  the  following:  _e_r_r_,  _w_a_r_n_,
              _f_i_x_m_e_,  or  _t_r_a_c_e_.   If xxx is not specified, all debugging mes-
              sages for the specified channel are  turned  on.   Each  channel
              will  print messages about a particular component of wwiinnee..  # 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 matter
              for these.  You can do the same for snoop.

              For instance:

              _-_-_d_e_b_u_g_m_s_g _w_a_r_n_+_a_l_l will turn on all  warning  messages  (recom-
              mended for debugging)
              _-_-_d_e_b_u_g_m_s_g  _w_a_r_n_+_d_l_l_,_+_h_e_a_p will turn on DLL warning messages and
              all heap messages.
              _-_-_d_e_b_u_g_m_s_g _f_i_x_m_e_-_a_l_l_,_w_a_r_n_+_c_u_r_s_o_r_,_+_r_e_l_a_y will turn off all  FIXME
              messages, turn on cursor warning messages, and turn on all relay
              messages (API calls).
              _-_-_d_e_b_u_g_m_s_g _+_r_e_l_a_y will turn on all relay messages. For more con-
              trol  on including or excluding functions and dlls look into the
              [Debug] section of the wine configuration file.

              The full list of names is: all, accel,  advapi,  animate,  aspi,
              atom,  avifile,  bitblt, bitmap, caret, cdrom, class, clipboard,
              clipping, combo, comboex, comm, commctrl, commdlg, console, crt-
              dll,  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, graphics, 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, profile, progress, prop, propsheet, psapi,
              psdrv, ras,  rebar,  reg,  region,  relay,  resource,  richedit,
              scroll,  segment,  seh,  selector,  sendmsg,  server,  setupapi,
              setupx, shell, snoop, sound, static, statusbar, 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 _d_o_c_u_-
              _m_e_n_t_a_t_i_o_n_/_r_u_n_n_i_n_g_._s_g_m_l in the source distribution  (FIXME:  out-
              dated).

PPRROOGGRRAAMM//AARRGGUUMMEENNTTSS
       The program name may be specified in DOS format ( _C_:_\_\_W_I_N_D_O_W_S_\_\_S_O_L_._E_X_E_)
       or in Unix format ( _/_m_s_d_o_s_/_w_i_n_d_o_w_s_/_s_o_l_._e_x_e ).  You may  pass  arguments
       to  the program being executed by adding them to the end of the command
       line invoking wwiinnee (such as: wine notepad C:\\TEMP\\README.TXT).   Note
       that you need to '\' escape special characters (and spaces) when invok-
       ing Wine via a shell, e.g.

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

       Command line processing goes as follows: first wwiinnee checks whether  one
       or  more of the above mentioned wwiinnee options have been specified. These
       are removed from the command line, which is passed to the windows  pro-
       gram.  You  can  use the parameter _-_- to indicate that wwiinnee 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 wwiinnee..  For example, if you  want  to  execute
       wwiinnee  with  the  options  _-_-_d_e_b_u_g_m_s_g _+_m_o_d_u_l_e and if wwiinnee should run the
       program _m_y_a_p_p_._e_x_e with the arguments _-_-_d_i_s_p_l_a_y _3_d _s_o_m_e_f_i_l_e ,  then  you
       could use the following command line to invoke wwiinnee::

       _w_i_n_e _-_-_d_e_b_u_g_m_s_g _+_m_o_d_u_l_e _-_- _m_y_a_p_p_._e_x_e _-_-_d_i_s_p_l_a_y _3_d _s_o_m_e_f_i_l_e

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

EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS
       wwiinnee makes the environment variables of the shell from  which  wwiinnee  is
       started  accessible  to  the  windows/dos processes started. So use the
       appropriate syntax for your shell to enter  environment  variables  you
       need.

       _W_I_N_E_P_R_E_F_I_X
              If set, the content of this variable is taken as the name of the
              directory where wwiinnee stores its data (the default is _$_H_O_M_E_/_._w_i_n_e
              ).  This  directory  contains  also the socket, which is used to
              communicate with the _w_i_n_e_s_e_r_v_e_r_.  All wwiinnee processes  using  the
              same  wwiinneesseerrvveerr  (i.e.:  same  user)  share certain things like
              registry, shared memory, and config file.  By setting _W_I_N_E_P_R_E_F_I_X
              to different values for different wwiinnee processes, it is possible
              to run a number of truly independent wwiinnee processes.

       _W_I_N_E_S_E_R_V_E_R
              Specifies the path and name of the  wwiinneesseerrvveerr  binary.  If  not
              set,  Wine  will  try  to  load //uussrr//bbiinn//wwiinneesseerrvveerr,, and if this
              doesn't exist it will then look for a file named "wineserver" in
              the path and in a few other likely locations.

       _W_I_N_E_L_O_A_D_E_R
              Specifies  the path and name of the wwiinnee binary to use to launch
              new Windows processes.  If  not  set,  Wine  will  try  to  load
              //uussrr//bbiinn//wwiinnee,, and if this doesn't exist it will then look for a
              file named "wine" in the path and in a few  other  likely  loca-
              tions.

       _W_I_N_E_D_L_L_P_A_T_H
              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 _W_I_N_E_D_L_L_P_A_T_H_, Wine
              will also look in //uussrr//lliibb//wwiinnee..

       _W_I_N_E_D_L_L_O_V_E_R_R_I_D_E_S
              Defines the override type and load order of  dlls  used  in  the
              loading  process for any dll. The default is set in the configu-
              ration file. There are currently two types of libraries that can
              be  loaded  into a process' address space: Native windows dlls (
              _n_a_t_i_v_e ), wwiinnee internal dlls ( _b_u_i_l_t_i_n ). The type may be abbre-
              viated with the first letter 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  specify
              different  loadorders  for different libraries by separating the
              entries by ";".
              Examples:

              WINEDLLOVERRIDES="comdlg32,commdlg=n,b"
                     Try to load comdlg32 and commdlg as  native  windows  dll
                     first  and  try  the  builtin  version if the native load
                     fails.

              WINEDLLOVERRIDES="shell,shell32=n;c:\\foo\\bar\\baz=b"
                     Try to load the libraries shell  and  shell32  as  native
                     windows  dlls.  Furthermore, if an application request to
                     load c:\foo\bar\baz.dll load the builtin library baz.

              WINEDLLOVERRIDES="comdlg32,commdlg=b,n;shell,shell32=b;com-
              ctl32,commctrl=n"
                     Try to load comdlg32 and commdlg as builtin first and try
                     the  native  version  if  the  builtin  load  fails; load
                     shell32/shell always  as  builtin  and  comctl32/commctrl
                     always as native.
                     Note:  It  is  wise  to keep dll pairs (comdlg32/commdlg,
                     shell/shell32, etc.)  having exactly the same load order.
                     This  will  prevent mismatches at runtime.  See also con-
                     figuration file format below.

       _D_I_S_P_L_A_Y
              Specifies the X11 display to use.

CCOONNFFIIGGUURRAATTIIOONN FFIILLEE
       wwiinnee expects a configuration file ( _$_W_I_N_E_P_R_E_F_I_X_/_c_o_n_f_i_g or  _~_/_._w_i_n_e_/_c_o_n_-
       _f_i_g  if  WINEPREFIX  is  not  set),  which  must  conform to the format
       specified in the wwiinnee..ccoonnff(5) man page. A sample configuration file  is
       documentation/samples/config in the wwiinnee source archive.

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

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

BBUUGGSS
       A    status   report   on   many   applications   is   available   from
       _h_t_t_p_:_/_/_w_w_w_._w_i_n_e_h_q_._c_o_m_/_A_p_p_s_.  Please add entries to this list for appli-
       cations you currently run.

       Bug  reports  may  be posted to Wine Bugzilla _h_t_t_p_:_/_/_b_u_g_s_._w_i_n_e_h_q_._c_o_m If
       you want to  post  a  bug  report,  please  read  the  file  _d_o_c_u_m_e_n_t_a_-
       _t_i_o_n_/_b_u_g_s_._s_g_m_l in the wwiinnee source to see what information is necessary

       Problems  and  suggestions  with  this  manpage  please  also report to
       _h_t_t_p_:_/_/_b_u_g_s_._w_i_n_e_h_q_._c_o_m

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

       The  latest snapshot of the code may be obtained via CVS.  For informa-
       tion on how to do this, please see _h_t_t_p_:_/_/_w_w_w_._w_i_n_e_h_q_._c_o_m_/_d_e_v_e_l_o_p_m_e_n_t_/

       WineHQ,    the     wwiinnee     development     headquarters,     is     at
       _h_t_t_p_:_/_/_w_w_w_._w_i_n_e_h_q_._c_o_m_/_.  This website contains a great deal of informa-
       tion about wwiinnee..

       The wwiinnee newsgroup is _c_o_m_p_._e_m_u_l_a_t_o_r_s_._m_s_-_w_i_n_d_o_w_s_._w_i_n_e_.  It is  used  for
       discussion of various wwiinnee eenndd uusseerr aassppeeccttss//hheellpp..

       For  further information about wwiinnee development, you might want to sub-
       scribe to the  wwiinnee  mailing  lists  at  _h_t_t_p_:_/_/_w_w_w_._w_i_n_e_h_q_._c_o_m_/_d_e_v_e_l_o_p_-
       _m_e_n_t_/_#_m_l

FFIILLEESS
       _/_u_s_r_/_b_i_n_/_w_i_n_e
              The wwiinnee program loader.
       _/_u_s_r_/_b_i_n_/_w_i_n_e_c_o_n_s_o_l_e
              The wwiinnee program loader for CUI (console) applications.
       _/_u_s_r_/_b_i_n_/_w_i_n_e_s_e_r_v_e_r
              The wwiinnee server
       _/_u_s_r_/_b_i_n_/_w_i_n_e_d_b_g
              The wwiinnee debugger
       _/_u_s_r_/_b_i_n_/_w_i_n_e_c_l_i_p_s_r_v
              The wwiinnee clipboard server
       _/_u_s_r_/_l_i_b_/_w_i_n_e
              Directory containing wwiinnee''ss shared libraries
       _~_/_._w_i_n_e_/_c_o_n_f_i_g
              User-specific configuration file
       _~_/_._w_i_n_e
              Directory containing user specific data managed by wwiinnee..

SSEEEE AALLSSOO
       wwiinnee..ccoonnff(5)



Wine 1.0                           May 2002                            WINE(1)

论坛徽章:
0
2 [报告]
发表于 2005-01-25 14:54 |只看该作者

LINUX下能运行windows程序了。。。。。

鄙视倒垃圾的人

论坛徽章:
0
3 [报告]
发表于 2005-01-25 15:03 |只看该作者

LINUX下能运行windows程序了。。。。。

WIN的病毒能感染LINUX下的文件吗?他们的文件格式不同,病毒的原程序在LINUX下能否运行呢,请指点下

论坛徽章:
0
4 [报告]
发表于 2005-01-25 15:36 |只看该作者

LINUX下能运行windows程序了。。。。。

no

论坛徽章:
0
5 [报告]
发表于 2005-01-25 16:19 |只看该作者

LINUX下能运行windows程序了。。。。。

据说可以中毒,但是病毒不能发作,所以只是存在,并不会有什么影响!

论坛徽章:
0
6 [报告]
发表于 2005-01-25 16:29 |只看该作者

LINUX下能运行windows程序了。。。。。

我的天啊,3年前就已经在linux下的xwindows玩暗黑和war3和金山糍粑这些了。。。您发的这个还真是古董帖啊

论坛徽章:
0
7 [报告]
发表于 2005-01-25 16:35 |只看该作者

LINUX下能运行windows程序了。。。。。

http://www.linuxfans.org/nuke/modules.php?name=Forums&file=viewtopic&t=18681&highlight=
看看这个帖子吧。。。呵呵,当年玩xwindows的一帮朋友们都把自己在xwindow下跑的win下的程式抓了图的。。。偶也有抓~~~

论坛徽章:
0
8 [报告]
发表于 2005-01-27 19:44 |只看该作者

LINUX下能运行windows程序了。。。。。

原帖由 "netyu" 发表:
ection of the wine configuration file.

              The full list of names is: all, accel,  advapi,  animate,  aspi,
              atom,  avifile,  bitblt, bitmap, caret, cdrom, class, clipboard,..........

什么意思

论坛徽章:
0
9 [报告]
发表于 2005-01-27 20:59 |只看该作者

LINUX下能运行windows程序了。。。。。

曾经在linux下玩qq2004
现在不玩了
现在我在windowsxp下玩mplayer了

论坛徽章:
0
10 [报告]
发表于 2005-01-27 21:55 |只看该作者

LINUX下能运行windows程序了。。。。。

原帖由 "linuxsir_XP" 发表:

现在我在windowsxp下玩mplayer了


有4win的版本啊。
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP