Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Sat, 24 Jun 2000 00:34:04 -0400 From: Chris Faylor To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Introducing slight binary incompatibility in newer executables? Message-ID: <20000624003404.A5942@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com References: <20000623224947 DOT A612 AT cygnus DOT com> <200006240300 DOT XAA13573 AT envy DOT delorie DOT com> <20000623230704 DOT A754 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000623230704.A754@cygnus.com>; from cgf@cygnus.com on Fri, Jun 23, 2000 at 11:07:04PM -0400 On Fri, Jun 23, 2000 at 11:07:04PM -0400, Chris Faylor wrote: >I'll check for the actual error message when I finish making the changes. The error is: "The procedure entry point _cygwin_user_data could not be located in the dynamic link library cygwin1.dll." That's not as bad as I thought. Of course, this is the superior Windows 2000 OS, so maybe it's different int Windows 95 or NT 4.0. cgf