Mail Archives: opendos/2000/11/20/21:01:54.2
Message-ID: | <00a601c0535f$535a4fc0$6a4bdcc8@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 23:55:17 -0200
|
MIME-Version: | 1.0
|
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
|
>>> 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
>
AB> This definitely point to some peculiarity of your hard disk or
CPU
AB>overclocking. Most probably it (HD) can't correctly work at speed at
which
AB>PTD reads/writes data, but /V option brakes copying process and thus
cure
AB>this.
I used a very stable machine that has been working fine for many years
and
worked fine after I removed PTS-DOS. I agree that the /V might be
slowing
down the copy process and etc...
>>> 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...
AB> ? Who "worked many times"?
I just mean that without that it allways failed and with that it allways
worked
and I tested it many times
Alain
- Raw text -