Rockbox mail archiveSubject: Re: FAT Filename Mangling bug. (was: RE : Regarding the recent recording PANIC's)
Re: FAT Filename Mangling bug. (was: RE : Regarding the recent recording PANIC's)
From: Michael O'Quinn <michael_at_oquinn.info>
Date: Thu, 24 Apr 2003 14:59:41 -0700 (PDT)
On Thu, 24 Apr 2003, Michael O'Quinn wrote:
> On Thu, 24 Apr 2003, Björn Stenberg wrote:
> > Michael O'Quinn wrote:
> > > Not true.
> > >
> > > There are specific mapping rules that are defined for mangling long names
> > > into short. And if it's FAT (of whatever flavor) the short names are
> > > THERE, even if the OS normally hides them
> > >
> > > Here's what Micro$oft says in the Windoze-98 Resource Kit...
> > Yay, a docs arms race! :-) I'll raise you one:
> > http://www.microsoft.com/hwdev/download/hardware/fatgen103.pdf
> Ooooh! How fun! And, since we are across the Pond from each other, we'll
> have to use ICBD's, that is, Inter Continental Ballistic Documents...
O.K. My firecracker has fizzled. I can't get a disk editor working
across the USB link, so I'll have to disassemble the thing and insert the
drive where it belongs...
> > This document, "FAT32 File System Specification", states as the only
> > requirement that "the short name is automatically generated from the
> > long name in such a way that it does not collide with an existing short
> > name".
> It may be that the reason it's choking is something OTHER than the name
> not matching. It could be something with the association between the
> various directory entries, or the checksum, or some undocumented
> feature. (Not that THAT would EVER happen with such a large and
> professional outfit.) I'll poke around with a disk editor and see if
> anything obvious jumps out at me.
Here is the text from ScanDisk, which tends to support the association
====[ BEGIN ]====
The 'J:\Genres' folder contains incorrect information about the file or
folder whose MS-DOS name is 'CELTICM3.A41'.
The file or folder's long name ('Celtic.m3u') is either stored incorrectly
on your disk or is incorrectly associated with 'CELTICM3.A41'. ScanDisk
repairs the error by storing the name in the correct format or by deleting
the long name. If ScanDisk deletes the long name, you will still be able
to access the file or folder by using the name 'CELTICM3.A41'.
This file or folder's last-modified date or time is invalid or is in the
future. This may be because your computer's clock is set incorrectly.
ScanDisk repairs future dates by changing them to your computer's current
date setting. ScanDisk repairs out-of-range dates or times by changing
them to the nearest setting within the valid range.
====[ END ]====
I think the date issue is another topic, which I choose not to address at
> > > But this does affect the ability to open the file from WIndoes 98, and it
> > > also confuses JBSync when it sees a new playlist created by RockBox.
> > Interesting. We've done it this way since november and you are the first
> > to even notice it.
Maybe it has something to do with the drive size. It's 60 gig.
> Explosive Devices.
Not really, of course. Although I complain and whine a lot, I'm really
mostly interested in improving an already awesome product! I spent about
2 days with the Archos firmware, then found RockBox, and haven't looked
Received on 2003-04-24