Message-ID: <002d01c052eb$97550ea0$0400000a@alain-nb>
From: "Alain" <alainm AT pobox DOT com>
To: <opendos AT delorie DOT com>
Subject: Re: Beware of PTS-DOS
Date: Mon, 20 Nov 2000 10:11:14 -0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Reply-To: 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).
AB>     1. When copying files one-to-one (unlike addition mode or
explicitly
AB>pointed by /a ASCII mode) COPY (must) work in binary mode when ^Z
presence
AB>or missing is ignored.

See my previous message

>     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.

two coments: (1) it showed a message saying that the copy was being
made in binary, (2) this time it was not the FAT that was corrupted, but
the file contents. I checked with FreeDos's COMP and there were a few
bytes (first time it was 4 and second time it was 5) that were changed.
I didn't check the FAT after this operation, only after a few more

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

I agree with that, but it worked many times...

Alain