delorie.com/archives/browse.cgi | search |
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: | <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin-apps/> |
List-Post: | <mailto:cygwin-apps AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs> |
Delivered-To: | mailing list cygwin-apps AT sources DOT redhat DOT com |
Message-ID: | <E94FF01DFF6CD31186F4080009DC361501F8C39D@nttwr2.tower.bldgs.butlermfg.org> |
From: | "Parker, Ron" <rdparker AT butlermfg DOT com> |
To: | cygwin-apps AT cygwin DOT com |
Subject: | RE: Forcing SYSTEMROOT (opinions needed) |
Date: | Wed, 2 May 2001 18:55:19 -0500 |
MIME-Version: | 1.0 |
X-Mailer: | Internet Mail Service (5.5.2653.19) |
> 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?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |