delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/2005/01/30/13:00:30

X-Authentication-Warning: delorie.com: mail set sender to opendos-bounces using -f
Message-Id: <200501301800.j0UI0P5k005660@delorie.com>
From: "Michal H. Tyc" <mht AT bttr-software DOT de>
Organization: BTTR Software
Date: Sun, 30 Jan 2005 19:00:09 +0100
X-Mailer: Arachne V1.75+/3C+
To: opendos AT delorie DOT com
Subject: Re: LFN-drivers
MIME-Version: 1.0
Reply-To: opendos AT delorie DOT com

On Sun, 30 Jan 2005 02:14:33 +0100 (MET), paul_spam AT gmx DOT at wrote:

> What I don't get is the LFNDOS and DOSLFN-driver thing. I know that they
> implement the LFN-API and enable some programs to have LFN support. But what
> about the DOSes themselves, does e.g. a "dir" display the long filenames?

Older DOSes (i.e., MS-DOS 6.x) are not aware of the LFN API and
therefore are unable to make any use of them. In DR-DOS 7.02+,
only COMMAND.COM is aware of the LFN API -- so, e.g., DIR displays
long filenames, when a DOS LFN driver is loaded, or when DR-DOS
COMMAND.COM is running in a Windows DOS box. But other system
programs (like CHKDSK, etc.) cannot handle LFNs. In MS-DOS 6.x,
you don't have any LFN support, as far as I know, unless you have
a third party command interpreter, like 4DOS -- but you still need
Windows tools for disk maintenance (or you can try some FreeDOS
tools).

Regards,

Michal

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019