From: Eliot Moss <moss@cs.umass.edu>
To: Krishnaveni K S <kveni07@gmail.com>,
Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: Problem with grow.exe demo test file for SLEUTH Urban growth model
Date: Thu, 28 Jul 2022 23:30:34 -0400 [thread overview]
Message-ID: <0578f142-0ca1-2407-81ca-ed402ba469e8@cs.umass.edu> (raw)
In-Reply-To: <CAEv0NdciAXAEiNqJ9mUSZvBrEFKHA+ASr79p_3wzXUgXZL+xYQ@mail.gmail.com>
On 7/28/2022 11:20 PM, Krishnaveni K S wrote:
> Dear Yano,
> Thank you so much for the support.
> I have use 64 bit download from cygwin and used the demo files for test run.
> Haven't used 32 bit..
> Can you please suggest how to solve this?
>
> With regards
> Krishnaveni
What is grow? Where is it coming from? How was it compiled?
Cygwin has a huge number of packages; generally one installs a selection.
Doing them all verges on craziness. So what is "all the required packages"
in this case?
I feel there's a lot you aren't telling us. Is this some app from a
third party? They may not have packaged it well with Cygwin.
Presumably, you meant ./grow.exe, not ../grow.exe (unless you were in
a subolder and rally wanted grow.exe from the parent folder).
Etc.
Hope this helps advanced the cause a bit .... EM
>> On Fri, 29 Jul 2022 02:30:34 +0530
>> Krishnaveni K S wrote:
>>> Hi,
>>> I tried installing Cygwin 64 in my machine with windows 11 OS. Installed
>>> all the required packages. Till testing of the growth file everything was
>>> fine. When I entered " ../grow.exe test scenario.demo_test" it is showing
>>> an error. " grow.exe Application error The application was unable to
>> start
>>> correctly 0xc0000o7b)....Please help..
>>> I tried with Windows 10 and 8 also....Same error popping up...
>>> Please help
>>
>> Perhaps, you are running the application in 64 bit cygwin
>> which is compiled with 32 bit cygwin. Or vice versa.
>>
>> --
>> Takashi Yano <takashi.yano@nifty.ne.jp>
>>
>
next prev parent reply other threads:[~2022-07-29 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 21:00 Krishnaveni K S
2022-07-29 0:20 ` Takashi Yano
2022-07-29 3:20 ` Krishnaveni K S
2022-07-29 3:29 ` Takashi Yano
2022-07-29 3:30 ` Eliot Moss [this message]
2022-07-29 19:01 ` Marco Atzeri
[not found] <104898279.297262.1659119846645@kpc.webmail.kpnmail.nl>
[not found] ` <CAEv0NddY3cw-k8Z2v-oKh2x_dfGf8fAxbY=_un=giUBeJGsz=g@mail.gmail.com>
2022-07-29 22:57 ` Takashi Yano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0578f142-0ca1-2407-81ca-ed402ba469e8@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=kveni07@gmail.com \
--cc=takashi.yano@nifty.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).