From: "Senden, Ruediger" <ruediger.senden@conti.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Cygwin Setup 2.893 on Windows 10 Version 1709
Date: Tue, 14 Aug 2018 12:26:00 -0000 [thread overview]
Message-ID: <DB7PR03MB4345369C70973E93D3DFF9F48C380@DB7PR03MB4345.eurprd03.prod.outlook.com> (raw)
Hello
The executed command line inside a .VBE program is
Errorcode is -1
cmd.exe /c d2u.exe -f -q -k SOURCEFILE.DAT && rcp SOURCEFILE.DAT USER-at-SERVER:DISKNAME:[DIRECTORY]TARGETFILE.DAT && u2d.exe -f -q -k SOURCEFILE.DAT 2>1>3
Errorcode is 1
Message: Copy successful
BUT NOTHING IS COPIED.
When I use the older CygWin version (32 bit) on Windows 10 and exactly the same program the following error message is returned:
Errorcode is -1
cmd.exe /c …
Message: 0 [main] u2d 7076 find_fast_cwd: WARNING: Couldn’t compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com<mailto:cygwin@cygwin.com>.
Errorcode is 1
BUT THE FILE IS COPIED.
This program has been used for years on Windows 7, 32 and 64 bit pcs, but with an older 32 bit version of CygWin.
The .DAT file contains normal text (like .txt od .csv files) and is produced by Excel.
It is used to copy data from Windows to VMS 7.3
The path variable begins with C:\cygwin\bin; … The CYGWIN variable is set to NODOSFILEWARNING
In the Cygwin\bin folder are Dos2Unix, Unix2Dos, d2u, u2d executables listed,
but, of course, I’m not sure whether it is a configuration problem somewhere or really a bug.
--
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
next reply other threads:[~2018-08-14 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 12:26 Senden, Ruediger [this message]
2018-08-14 17:12 ` Marco Atzeri
[not found] ` <DB7PR03MB4345281B806D86B4B27E51138C3D0@DB7PR03MB4345.eurprd03.prod.outlook.com>
2018-08-17 14:37 ` Marco Atzeri
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=DB7PR03MB4345369C70973E93D3DFF9F48C380@DB7PR03MB4345.eurprd03.prod.outlook.com \
--to=ruediger.senden@conti.de \
--cc=cygwin@cygwin.com \
/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).