To: opendos AT delorie DOT com
X-Comment-To: "Da Silva, Joe" <Joe DOT daSilva AT emailmetering DOT com>
References: <67BAFB085CD7D21190B80090273F74A45B7D61 AT emwatent02 DOT meters DOT com DOT au>
Message-Id: <2.07b7.MXEH.G4ASCB@belous.munic.msk.su>
From: "Arkady V.Belousov" <ark AT belous DOT munic DOT msk DOT su>
Date: Mon, 20 Nov 2000 03:36:11 +0300 (MSK)
Organization: Locus
X-Mailer: dMail [Demos Mail for DOS v2.07b7]
Subject: RE: Beware of PTS-DOS
Lines: 27
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Reply-To: opendos AT delorie DOT com

X-Comment-To: Da Silva, Joe

Hi!

20-ξΟΡ-2000 11:02 Joe DOT daSilva AT emailmetering DOT com (Da Silva, Joe) wrote to
"'opendos AT delorie DOT com'" <opendos AT delorie DOT com>, FreeDos AT delorie DOT com,
List AT delorie DOT com "'opendos AT delorie DOT com'" <opendos AT delorie DOT com>,:

>> After that I discovered that if I copy a big file 1,2Mb from a diskette it
>> gets corrupted :( after a long time I discovered that this could be fixed
>> with the /V option :(((
DJ> Thanks for the warning ...
DJ> However, two things to clarify :
DJ> 1. Did the 1.2M file have a Control-Z character in it, such that
DJ>     "copy" didn't copy the whole file (this behaviour depends
DJ>     also on the filename extension, of course).

     1. When copying files one-to-one (unlike addition mode or explicitly
pointed by /a ASCII mode) COPY (must) work in binary mode when ^Z presence
or missing is ignored.

     2. /V only turns on VERIFY mode (when DOS checks result of writing on
disk by hardware) at the time of copying and have absolutely no relation
with possible FAT file system (logical) destruction.

     3. /V practially gives nothing, because hardly brakes hard disk speed
and not gives floppy disk writing quality assurance.