Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com From: Andy Moreton Subject: Re: WINE on Cygwin Date: Thu, 3 Nov 2005 16:36:56 +0000 (UTC) Lines: 21 Message-ID: References: <005101c5e080$1edf3ef0$8002a7c0 AT dir DOT sparsi DOT com> <1131033651 DOT 24439 DOT 32 DOT camel AT zipoli DOT prudsys DOT com> User-Agent: Xnews/06.08.25 X-IsSubscribed: yes On Thu, 03 Nov 2005 16:00:51 GMT, Alexander Gottwald wrote: > On Thu, 2005-11-03 at 07:41 -0800, Andrew DeFaria wrote: > >> I guess I don't see the point. Isn't Wine an emulator for running >> Windows apps on Unix/Linux? If so then why would you need it under >> Cygwin as Cygwin already runs on Windows so if your want to run a >> Windows apps, well then just run the Windows app! > > Sometimes it's useful to have a separation between the program and > windows. You could trace all registry or file access of a program. Wine > would be useful for remote program usage since it exports the display > via X11. This still sounds fairly pointless. the tools from sysinternals.com allow you to monitor all file and registry access from an application. A VNC client will solve your remote operation needs. So what is the real reason for wanting to do something so perverse ? AndyM -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/