Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.1.0.14.0.20020319011213.00b3ada0@nemotse.net>
X-Sender: nemo AT nemotse DOT net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 19 Mar 2002 01:15:02 +0800
To: cygwin AT cygwin DOT com
From: Nemo Tse <nemo AT nemoathome DOT ods DOT org>
Subject: Re: Telneting/ftping to cygwin
In-Reply-To: <20020318170848.GA24475@redhat.com>
References: <2077-Mon11Mar2002135448+0000-starksb AT ebi DOT ac DOT uk>
 <01C1C6BD DOT CE90CFC0 DOT rafael DOT botejara AT sema DOT es>
 <3C88E12D DOT 2E6DBDCC AT iee DOT org>
 <20020308192353 DOT Q13590 AT cygbert DOT vinschen DOT de>
 <3C8C8487 DOT 60308 AT pace DOT co DOT uk>
 <20020311124504 DOT K29574 AT cygbert DOT vinschen DOT de>
 <2077-Mon11Mar2002135448+0000-starksb AT ebi DOT ac DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

I was having this problem too.
After carefully read the inetutil.readme file, I followed the instruction 
and inserted the required registry key and granted the required priviledges 
to the user.  Then the telnet work perfectly and no more "failed to init".

Hope this help.

Nemo.

At 01:08 AM 3/19/2002, you wrote:
>On Mon, Mar 11, 2002 at 01:54:48PM +0000, David Starks-Browning wrote:
> >On Monday 11 Mar 02, Corinna Vinschen writes:
> >> On Mon, Mar 11, 2002 at 10:18:47AM +0000, John Beranek wrote:
> >> > Corinna Vinschen wrote:
> >> > >On Fri, Mar 08, 2002 at 04:05:01PM +0000, Don Sharp wrote:
> >> > >
> >> > >>I can confirm that there is a problem. I telnetted from a linux box to
> >> > >>my cygwin on NT4 setup which has an up to date cygwin1.dll (see 
> cygcheck
> >> > >>output)
> >> > >>
> >> > >>On the cygwin side I get a pop-up
> >> > >>
> >> > >>bash.exe "The application failed to initialise properly (0x0000022)
> >
> >> Well, a "me too" isn't actually helpful.  Helpful would be if
> >> somebody who has that problem would debug that.  Gdb and strace
> >> are your friend.
> >
> >I have the same problem.  I notice it's only been reported on NT 4.
> >Corinna and Chris, are you unable to reproduce it on NT4, or are you
> >not running NT 4?
>
>It just occurred to me that this could be a protection problem, either
>with the cygwin DLL or with one of the executables that are being run.
>
>Do you have the same problem when you type in a command window:
>
>   set CYGWIN=ntsec
>   bash
>   ls -l /bin/cygwin1.dll
>
>?
>
>You should see that cygwin1.dll is executable in this scenario.
>
>cgf
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/