X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <3759e04c0710040621p7ea473a2rc40bb994911b6704 AT mail DOT gmail DOT com>
Subject: RE: Bad EXE format (error 193)
Date: Thu, 4 Oct 2007 14:56:10 +0100
Message-ID: <013f01c8068e$51a85c50$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <3759e04c0710040621p7ea473a2rc40bb994911b6704@mail.gmail.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 04 October 2007 14:21, Lynn Winebarger wrote:

>    I am trying to get the Larceny Scheme compiler
> (http://www.ccs.neu.edu/home/will/Larceny/) to compile (and work)
> under the most recent stable Cygwin release.  While I have managed to
> get it to produce a file that very closely resembles a PE file, it
> apparently is not close enough to satisfy Windows XP Home Edition SP
> 2.
>    Unfortunately, objdump and other file analyzers have no problem
> with the file, while none of the debuggers I tried had anything
> helpful to say about the problem.  I have compiled other things under
> Cygwin (PLT Scheme, for example) that not only produced an executable
> image but produced one Windows would actually run.  I have tried doing
> a diff against the headers between this and the Larceny image and
> cannot see a glaring error (but I am not an expert in either Windows
> executables or Larceny's source code).
>     I cannot find anything helpful on this error in the mailing list
> archives.  Is there a tool that would identify the problem, or maybe a
> kind expert with some guidance on resolving this issue?

  We might be able to make guesses at what was wrong with the compiled program
if you told us *in what way* it is "not close enough to satisfy Windows XP".



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/