Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: WINE on Cygwin From: Alexander Gottwald To: cygwin@cygwin.com In-Reply-To: References: <005101c5e080$1edf3ef0$8002a7c0@dir.sparsi.com> <1131033651.24439.32.camel@zipoli.prudsys.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-U6AnfBvpKBoMjthsybmk" Date: Thu, 03 Nov 2005 17:54:42 +0100 Message-Id: <1131036882.24441.41.camel@zipoli.prudsys.com> Mime-Version: 1.0 X-IsSubscribed: yes --=-U6AnfBvpKBoMjthsybmk Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2005-11-03 at 16:36 +0000, Andy Moreton wrote: > > 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.=20 >=20 > This still sounds fairly pointless. the tools from sysinternals.com allow= =20 > you to monitor all file and registry access from an application. A VNC=20 > client will solve your remote operation needs. >=20 > So what is the real reason for wanting to do something so perverse ? Because it can be done! VNC is slow, there is no integration with the local desktop. You can't work without interfering with the local desktop. Using wine just to redirect the graphic display is overkill but unfortunatly the most promising solution. Separation is yet another reason. --=-U6AnfBvpKBoMjthsybmk Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBDakDSXcoKXzCJOfgRAtvsAJ9zEB8P2lONuAVlSzd+xDBHcwFeNgCgqrQQ 1nh4QRYU2wvD3DnuAC+q0f0= =goE9 -----END PGP SIGNATURE----- --=-U6AnfBvpKBoMjthsybmk--