To: opendos AT delorie DOT com
X-Comment-To: "Alain" <alainm AT pobox DOT com>
References: <002d01c052eb$97550ea0$0400000a AT alain-nb>
Message-Id: <2.07b7.A8SQ.G4CNUF@belous.munic.msk.su>
From: "Arkady V.Belousov" <ark AT belous DOT munic DOT msk DOT su>
Date: Tue, 21 Nov 2000 03:54:15 +0300 (MSK)
Organization: Locus
X-Mailer: dMail [Demos Mail for DOS v2.07b7]
Subject: Re: Beware of PTS-DOS
Lines: 25
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: Alain

Hi!

20-ξΟΡ-2000 10:11 alainm AT pobox DOT com (Alain) wrote to <opendos AT delorie DOT com>:

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

     This definitely point to some peculiarity of your hard disk or CPU
overclocking. Most probably it (HD) can't correctly work at speed at which
PTD reads/writes data, but /V option brakes copying process and thus cure
this.

>>     3. /V practially gives nothing, because hardly brakes hard disk speed
>>and not gives floppy disk writing quality assurance.
 A> I agree with that, but it worked many times...

     ? Who "worked many times"?