From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28171 invoked by alias); 13 Apr 2018 08:45:43 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 26907 invoked by uid 89); 13 Apr 2018 08:45:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.4 required=5.0 tests=BAYES_00,GIT_PATCH_2,KAM_NUMSUBJECT autolearn=ham version=3.3.2 spammy=Hx-languages-length:1148, culprit, H*r:192.168.3 X-HELO: Ishtar.sc.tlinx.org Received: from ishtar.tlinx.org (HELO Ishtar.sc.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 13 Apr 2018 08:45:02 +0000 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id w3D8ivMU062678; Fri, 13 Apr 2018 01:45:00 -0700 Message-ID: <5AD06E0A.6010103@tlinx.org> Date: Fri, 13 Apr 2018 08:45:00 -0000 From: L A Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: lbmgmusic@gmail.com CC: cygwin@cygwin.com Subject: Re: Problem with NC.1.107 References: <1732290424.20180328171523@yandex.ru> <5ACC18BF.4080904@tlinx.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-04/txt/msg00143.txt.bz2 Jay Cotton wrote: > Here is the package listing at cygwin > > nc: A simple but powerful network tool (installed binaries and support > files) > > 2013-03-19 15:35 0 usr/ > 2013-03-19 15:35 0 usr/bin/ > 2013-03-19 15:35 24576 usr/bin/nc.exe > 2013-03-19 15:35 0 usr/share/ > 2013-03-19 15:35 0 usr/share/man/ > 2013-03-19 15:35 0 usr/share/man/man1/ > 2013-03-19 15:30 5052 usr/share/man/man1/nc.1.gz > > --- Right. It has the two files I mentioned below, and nc.exe isn't a text file or makefile -- but is shown by the cygwin "file" command as an executable. You said: > I don't see the PE32+ executable (console) x86-64, for MS Windows >> >>> string. Whereas, when I used the file command, it printed out exactly what you were searching for. Thus my assertion that your file command is the likely culprit. > file /usr/bin/nc > >> > /usr/bin/nc: PE32+ executable (console) x86-64 (stripped to external PDB), > for MS Windows As for the not-executable error message, have you checked, as suggested elsewhere, whether or not you have some cheap anti-virus installed that blocks programs that are not viruses like 'nc'? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple