To: opendos AT delorie DOT com
References: <F5AAC47C69 AT reze-1 DOT rz DOT rwth-aachen DOT de>
Organization: Sechenov Institute of Evolutionary Physiology and
    Biochemistry, Russian Academy of Science
Message-Id: <AANwqRvyn0@insect.mail.iephb.ru>
From: pavel AT insect DOT mail DOT iephb DOT ru (Pavel V. Ozerski)
Date: Fri, 14 Jul 2000 21:32:07 +0400 (MSD)
X-Mailer: dMail [Demos Mail for Windows NT v1.4b1]
Subject: Re: RCPT: Re: Again about NTFSDOS
Lines: 26
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: opendos AT delorie DOT com

Now I got an answer from the second author of NTFSDOS (Bryce Cogswell).
It seems to be more interesting (see below). But please, if possible, check the
behavior of NTFSDOS co-existing with Caldera longname TSR running. Unfortunately, I just
not have time to check it today (and must convert one logical drive on my comp to NTFS to
check it). But I'm doubt that loading of Caldera longname TSR could fix problem.


>There may be some issues with the 3.0R release being incompatible with
>DR-DOS, but I think these same issues also affect MS-DOS 5.0.  I believe it
>is due to poor support for 8.3 file names (it has been 6 months or so since
>I last looked at the issue).  If DR-DOS 7.03 supports LFN it should work
>fine.  Also, the most recent read/write release (3.03 I believe) should not
>have these problems under DR-DOS even without LFN.
>
>-- Bryce Cogswell
>   Winternals Software LP
>
>
>-----Original Message-----
>From: Pavel V. Ozerski <pavel AT insect DOT mail DOT iephb DOT ru>
>To: cogswell AT winternals DOT com <cogswell AT winternals DOT com>
>Date: Friday, July 14, 2000 5:11 AM
>Subject: NTFSDOS on DR-DOS