To:	opendos AT delorie DOT com
References:	<125D1980A2D AT reze-1 DOT rz DOT rwth-aachen DOT de>
Organization:	Sechenov Institute of Evolutionary Physiology and
	Biochemistry, Russian Academy of Science
Message-Id:	<AA8byPtGJB@insect.mail.iephb.ru>
From:	pavel AT insect DOT mail DOT iephb DOT ru (Pavel V. Ozerski)
Date:	Wed, 16 Jun 1999 19:56:56 +0400 (MSD)
X-Mailer:	dMail [Demos Mail for Windows NT v1.4b1]
Subject:	Re: Again about NTFS problem.
Lines:	21
MIME-Version:	1.0
Reply-To:	opendos AT delorie DOT com

>Anyway, if NTFSDOS aborts with something like "Invalid DOS version"
>or "Cannot run on DR DOS.", I would try for example:
>
> SETVER NTFSDOS.EXE 6.128 /X

No, NTFSDOS seems to be "fully content", it does not find problems, it mountes drive without
any error message but this drive mistakenly shows as empty. The tricks with SETVER don't resolve
this problem. I'm not sure but I have some suppositions about cause of this bug. It is possible that
NTFSDOS works directly with FCBs. BTW, In QEMM technote is written:

 Q. Manifest reports more FILES than I have specified in
    CONFIG.SYS. Why?

 A. DR-DOS converts FCBS to FILE handles so Manifest and the
    FILES.COM program that comes with QEMM will report the total
    number of FILE handles to be the sum of the two.  The minimum
    number of FILE handles is 20 and the minimum number of FCBS is
    4. Another effect of this conflation of FCBS and FILE handles
    causes Manifest to report that there is only one FCB.

I suppose that could be the cause but I cannot check it.

- Raw text -