X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: "Joe Smith" Subject: Re: 1.0:Question about Cygwin1.dll crashing with DEP/NX Date: Tue, 30 May 2006 14:50:02 -0400 Lines: 22 Message-ID: References: <447C72E6 DOT 3BD5573A AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 "Brian Dessent" wrote in message news:447C72E6 DOT 3BD5573A AT dessent DOT net... > I'm afraid you are probably not going to find anybody on this list > interested in even considering problems with these ancient versions. If > you can reproduce the problem you experience with a current Cygwin > snapshot then post more details, otherwise I think you're on your own. > It's kind of like calling Ford and asking if the model-T will run on > unleaded -- so much has changed over the last 7 or so years. Except that ford might actually provide support for the model-T, because Ford owes its success to that car. Imagine the commercial, and what offically supporting the out of date cars might do to improve Fords image. A better example might be asking MS tech support about a problem in Windows 1.0 (except that was more than 7 years ago). > Brian > -- 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/