Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	Joseph Toman <toman AT marge DOT cyber-dyne DOT com>
Message-Id:	<199908052045.NAA03876@marge.cyber-dyne.com>
Subject:	B20.1 problem with cp between NT and 9x
To:	cygwin AT sourceware DOT cygnus DOT com
Date:	Thu, 5 Aug 1999 13:45:50 -0700 (PDT)
X-Mailer:	ELM [version 2.4ME+ PL48 (25)]
MIME-Version:	1.0

I'm having a problem copying executables and DLLs from NT to a shared
directory on a Win98 system with cp. If I run cmp on the two
executables they differ, the original has a section of zero bytes and
the copy has what looks like fragments of source code. Stranger, this
was created with Borland C++ 5.01. If I make an executable with egcs,
no file corruption occurs on copying. Copying from an NT system to an
NT system works correctly, whether the target filesystem is NTFS or
FAT. The file name, i.e. bob.exe vs bob.txt, has no effect on the
process.  Copying with cut and paste or xcopy works fine. With
CYGWIN=binmode, sum returns different checksums on the two files, with
the CYGWIN variable unset the checksums are the same. The CYGWIN
variable doesn't seem to affect cp, and in fact that's what you see in
the source.  Ideas, suggestions, jeers? 

						J. Toman


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -