Mail Archives: cygwin/2000/10/13/14:58:37
Thanks, that was definitely the problem. When you update the FAQ, it would
be great if you could explain why this symptom only occurs within BASH. If
I'm in a regular WinNT command window (with the same active path) and type a
command that doesn't exist, it says: "The name specified is not recognized
as an internal or external command, operable program or batch file." I
don't understand why the behavior would be different between the two shells.
Cheers,
ALF
> -----Original Message-----
> From: Earnie Boyd [SMTP:earnie_boyd AT yahoo DOT com]
> Sent: Friday, October 13, 2000 11:28 AM
> To: Larry Hall (RFK Partners, Inc); Farmer, Tony;
> 'cygwin AT sourceware DOT cygnus DOT com'
> Subject: Re: WinNT Lockup
>
> --- "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com> wrote:
> > At 01:52 PM 10/13/2000, Farmer, Tony wrote:
> > >I've setup Cygwin on two systems - one NT and one 98. The 98 system
> seems
> > >to work fine, but on the NT system whenever I type a command that
> doesn't
> > >exist ("XXX" for example), Cygwin locks up. Ctl-C, Ctl-Break, nothing
> will
> > >get me out of it short of closing the Cygwin window. Is this something
> I'm
> > >doing wrong or a peculiarity with NT?
> > >
> > >Thanks,
> > >alfarmer AT hotmail DOT com
> >
> >
> > Are you sure your path on the NT system doesn't have a network share in
> it?
> > The longer the path, the longer the search. Add several factors for any
> > network shares in the path. Add many more factors for network shares
> that
> > aren't reachable. This could look like a "lock up".
> >
>
> Good catch Larry. Sounds like an explaination for the FAQ.
>
> Cheers,
> Earnie Boyd
> mailto:earnie_boyd AT yahoo DOT com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -