Re: [MiNT] Bug in FATFS

[Standa Opichal <opichals@seznam.cz>]

Here is a log from Single TOS. The Fopen() is able to open the 
VDI_BASE.GFA.GFA and it actually opens the VDI_BASE.GFA file that exists 
in the filesystem of the drive f:.

So the Fopen() is the syscall to be fixed.. Actually the fatfs.c, but 
only for the case when the VFAT extensions are not enabled.... OR maybe 
better when VFAT extension is found for that name then only the first 
extension should be considered in fatfs.c: fatfs_lookup() ?

What do you think?

regards

STan

=========
GFA_BCOM G_61    Fopen          "F:\VDI_BASE.GFA.GFA" ReadOnly  -> 7
GFA_BCOM G_63    Fread          H 7 Cnt $0000000C Buf $013675A2 -> 
$0000000C/12
                                < "
GFA_BCOM G_63    Fread          H 7 Cnt $00000098 Buf $013675A2 -> 
$00000098/152
GFA_BCOM G_63    Fread          H 7 Cnt $0000020A Buf $0136BD44 -> 
$0000020A/522
                                < "
I
A
I\bsVQ_EXTND\tabVQ_EXTEND
GFA_BCOM G_62    Fclose         H 7 -> 0   <Ok>
=========


Frank Naumann wrote:
> Hello!
>
> > Well, IMHO the newfatfs should be compatible (from the user/app 
> > perspective) to the old TOSFS (not counting obvious bugs, of course).
> >
> > So... users were used to that only a single filename extension is used 
> > no matter what is behind. IMO the newfatfs should handle that the same 
> > way.
>
>
> Maybe you give an example what system calls are involved and which names 
> should be ignored/modified/specially handle in which way.
>
> > And in case there is a trailing '.' than it is the same as the same 
> > filename without extension.
>
>
> Yes, I bugfixed this.
>
>
> Regards,
> Frank
>
> --
> ATARI FALCON 060 // MILAN 060
> -----------------------------------------
> http://www.cs.uni-magdeburg.de/~fnaumann/
> e-Mail: fnaumann@freemint.de