Date: Wed, 19 Feb 1997 18:14:07 -0600 (CST)
From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
To: "'OpenDOS newsgroup'" <opendos AT mail DOT tacoma DOT net>
Subject: [opendos] Re: [opendos-developer] Potential serious FS problem
In-Reply-To: <199702191424.JAA17066@keeper.albany.net>
Message-ID: <Pine.GSO.3.95.970219180622.14555B-100000@sparkie.gnofn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Wed, 19 Feb 1997, Jim Lefavour wrote:
> I just realized - whatever FS we use, we have to be careful.  Most 
> DOS programs expect filenames to be uppercase, and many are written 

If we implement LFN support, we could not use the INT21 functions which
normally deal with the filesystem, we would _have_ to use a new set of
functions else how else would the OS know whether it's dealing with an
older app which can only handle 8.3 or a new app which likes the flavor of
LFN?  Say if a program calls for a directory search, if it calls the
current function AH=04Eh, then the OS knows to return it a properly parsed
and valid 8.3 name.  If on the other hand, the program calls AH=(YTBD),
then the OS will hand it a pointer to the LFN match.  (which ought to use
the current table of function 04Eh, with an extension to the table for
either adding a pointer to the LFN, or additional space for the LFN).

  <! PrePared HTML!  Just export as a HTML file and Click!>
A Christian Web Site!  The Light 
  <a href="http://www.thelight.org/">.</a><br>
A neat place to visit. HotSpot 
  <a href="http://www.hspro.com/hotspot/">.</a><br>
Caldera, Inc. / Makers of OpenDOS
  <a href="http://www.caldera.com/">.</a><br>
Caldera's OpenDOS page
  <a href="http://www.caldera.com/dos/dos.htm">.</a><br>