delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/02/06/12:15:36

X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <r DOT berber AT computer DOT org>
Subject: Re: Porting from SUN Solaris to Cygwin
Date: Mon, 06 Feb 2006 11:03:23 -0600
Lines: 32
Message-ID: <ds7vgs$ltf$1@sea.gmane.org>
References: <5BFC7E55C08B014E963E1A9AE957381B023C30D2 AT XCH-SE-2V2 DOT se DOT nos DOT boeing DOT com>
Mime-Version: 1.0
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
In-Reply-To: <5BFC7E55C08B014E963E1A9AE957381B023C30D2@XCH-SE-2V2.se.nos.boeing.com>
OpenPGP: url=ldap://keyserver.pgp.com
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Lerohl, John K wrote:

> We're porting several hundred SLOCs from a SUN Solaris environment to
> Windows XP PCs.  The initial port was done with MKS Toolkit on lab
> machines.  We're looking at using Cygwin for cost reasons.  We have a
> hundred or so users with desktops outside the lab.=20=20
>=20
> We're getting an odd error when we try and run some of the Aps on our
> "out-of-lab" machines.  These are the more complex, memory intensive
> Applications.  They're compiling cleanly with Cygwin, but fail to run.
> They return the following error message:
>=20
> "*** MapViewOfFileEx(0x740, in_h 0x740) failed, Win32 error 6"
>=20
> We had these applications running under Windows 2000, but over the
> holidays, our company upgraded to Windows XP.  Since then - no luck.
> We're currently using the MicroSoft 6.0 C-compiler and .NET Framework
> SDK v1.1.  The Cygwin version we're using is 1.5.11-1.
>=20
> Any ideas?

Yes, your problem has nothing to do with Cygwin.

If you are using Microsoft's C compiler then the executable produced only
depends on Microsoft's libraries.  That means they should run with or witho=
ut
Cygwin.

You are looking at the wrong place (and your Cygwin version is ancient).
--=20
Ren=E9 Berber


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019