Message-ID:	<00e701c0527d$e5132280$0400000a@alain-nb>
From:	"Alain" <alainm AT pobox DOT com>
To:	"FreeDos List" <fd-dev AT topica DOT com>, <opendos AT delorie DOT com>
Subject:	Beware of PTS-DOS
Date:	Sun, 19 Nov 2000 20:57:34 -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

Hi,

There was a very interesting series of messages about
PTS-DOS in fd-dev, with a final conclusion that it works OK...

I have a very different tale to tell: Beware - PTS-2000 is dangerous

Here is what happend to me: first I set up a test machine changing
my HD to a 1.7Gb and had it running in DR-DOS 7.03 format in
FAT16 created under DR-DOS's FDISK.

Then I made a download of the evaluation version with fat32 and put
it on a diskette. It booted ok on my notebook, it could see my fat32
partition but changed my partition's letters (in the same non-standard
way as dr-dos does). I didn't make any more test on this machine.

After that I went to my test machine, booted from the diskette and tried
the "SYS C:" command which didn't work, so I tried "SYSFAT32 C:"
which didn't work too, but destroyed many files (I noticed because
Dos Navigator was getting crazy). After that, SCANDISK could repair
the FAT and the files and I could restore the damaged files.

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 :(((

Then I tried to unzip this file (one of the damaged programs) and after
a few atempts THE WHOLE HARD DRIVE WAS DESTROYED: many
files were corrupted and many garbadge directory had aperaded in
the root dir. As expected, after scandisk there was nothing useable
left anywere. Thanks god it was a test machine!

Worse of all, I sent a message to Paragon and one week is passed
and I got no answer.

Alain

- Raw text -