Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Wed, 2 May 2001 22:28:50 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Forcing SYSTEMROOT (opinions needed) Message-ID: <20010502222849.A1238@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from rdparker@butlermfg.com on Wed, May 02, 2001 at 06:55:19PM -0500 On Wed, May 02, 2001 at 06:55:19PM -0500, Parker, Ron wrote: >>So we have to trade the possibility of someone wanting complete control >>of his environment versus the possibility of someone not specifying >>SYSTEMROOT but needing it for the program that is about to be run. >> >>Should I flip a coin? > >Since the Winsock dll is dynamically loaded via LoadLibrary, would it >be possible to fill out SYSTEMROOT just prior to the load? Hmm. If we could be guaranteed that the program being loaded was a cygwin program we could. Or, maybe we don't care... This is a creative approach to this problem. I like it. cgf