Message-ID: <c=US%a=_%p=SSG%l=SITE2S1-970207201506Z-29534@site2s1.sbservices.com>
From: Jonathan Tarbox - SSG <JonatTar AT sbservices DOT com>
To: "'opendos AT mail DOT tacoma DOT net'" <opendos AT mail DOT tacoma DOT net>
Subject: [opendos] Filesystems/Long Filename API
Date: Fri, 7 Feb 1997 15:15:06 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk


	Now, we are all decided that we want *SUPPORT* for other FS's..  That
is it comes default using FAT because the average user will not
need/want anything other..  Possibly supporting VFAT by default might be
an option also since alot of us, myself including have Win95 also
install on my system.

	But we are also discussing the method in which to support the LFN's for
'legacy' apps in 8.3 format.  Now instead of using several patches to
this and that, why not keep the Win95 LFN API and add our own support in
it to handle the other FS's.

	The thing is, true we all hate the way Win95 hashes the Long Filename
down to 8.3 standard, but if we then change this method for OD will not
Win95 not comprehend it when we go back into Windows?  What's so hard to
have our DIR and other basic DOS internal commands to list both the LFN
and hashed 8.3 name..  

	Also, the 4DOS file descriptions would be an awesome addition to the
basic OD install...  

	
Jonathan Tarbox
- Tech Support Specialist

 BTW - These are opinions.. I'm looking for compatibility between all of
my OS that I use (I'm a Tech Support Specialist, I support em all
basically: DOS, All Windows, OS/2, Mac, Linux..  I love System
>Commander(TM) for multi-booting..)