Lpc2000

--- In lpc2000@yahoogroups.com, "Joel Winarske" <joelw@i...> wrote:
>
> > Sten Wrote:
> > This sounds good, but what about Richard's problem concerning 
file names
> > which are not 8.3 compliant? Is there a problem with this docs?
> 
> It start's on page 28 of the MS fatgen103 document:
> 
> "As a consequence of this pairing, the short directory entry 
serves as the
> structure that contains fields like: last access date, creation 
time,
> creation date, first cluster, and size.  It also holds a name that 
is
> visible on previous versions of MS-DOS/Windows.  The long 
directory entries
> are free to contain new information and need not replicate 
information
> already available in the short entry.  Principally, the long 
entries contain
> the long name of a file.  The name contained in a short entry 
which is
> associated with a set of long entries is termed the alias name, or 
simply
> alias, of the file." 
> 
> 
> Joel
>

Yes, the name conversion is described on pages 30 and 31 of the 
document.  All is well, right up until:

"However, one absolutely cannot count on this behavior.  In a 
directory with a very large mix of names of this type, the selection 
algorithm is optimized for speed and may select another "n" based on 
the characteristics of short names that end in "~n" and have similar 
leading name patterns."

It sounds like I would have to read all of the directory entries in 
a directory and sort them.  Then try to find a place to merge the 
new filename that doesn't collide.  Iterate the numbering scheme 
until it works...

I guess if I were to write the code to create the short file names I 
would just follow the yellow brick road and not try to optimize for 
speed.  Heck, I would create what, two or three files a month?  Not 
a big deal.  Most of the files will be loaded under WinXP.

What is a big deal is to write the entire FAT32 file system.  It 
might be better to back up to FAT16 and live with the 2GB partition 
size limit.  After all, how many sound effect files can a person 
have?  They are, almost be definition, only a very few seconds long 
so certainly less than 100k bytes.  Even a 64MB CF will hold a lot 
of files!

OTOH, I would like to have the long file names.  The 8.3 notation 
just isn't useful when describing an effect file.

So it comes down to lazy versus utility.  Unless I can find the code 
already written.