cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/2003/08/29/14:45:06

From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Long file name support
Date: Fri, 29 Aug 2003 13:20:00 CDT
Organization: Rice University, Houston, TX
Lines: 15
Message-ID: <3f4f9950.sandmann@clio.rice.edu>
References: <TRL3b.3710$cQ1 DOT 1010044 AT kent DOT svc DOT tds DOT net>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1062181521 8816 128.42.105.3 (29 Aug 2003 18:25:21 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: Fri, 29 Aug 2003 18:25:21 +0000 (UTC)
X-NewsEditor: ED-1.5.9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> > The built-in C run-time functions (fopen, etc) work directly with long
> > names under all platforms which support the long file name DOS interrupts.

> Is the TSR to allow one to run in the just DOS (not in a DOS window), and
> still have long filename functionality?

There are TSRs for regular DOS which provide long filename functionality 
(file system may have long names when booted under Windows 95, for example).

There is a TSR designed to support long names under Windows NT - which
has a native file system that supports long names - but the DOS Window
does not support the long name DOS API.

So in general, if you aren't under DOS or Windows NT you don't need a
TSR for long names.

- Raw text -


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