[vwnc] Fat filenames

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[vwnc] Fat filenames

bqueyras
Hi,

How is it possible to handle FAT filenames with network prefixes like
this one ?
  '\\meru\home$\Bernadette.Queyras\po\PROJETS\TRES GROS PROJET\beta
version\AF 23 mars 09\biblio essai 23-03.tpbp'

Namely asFilename gives the following :
  a
FATFilename('\\meru\home$\bernadet.que\po\projets\tresgros\betavers\af23mars\biblioes.tpb')

Bernadette Queyras

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Fat filenames

Steven Kelly
As I previously stated here:
http://www.parcplace.net/list/vwnc-archive/0808/msg00062.html
> I've seen this problem occasionally over the years, when working with
> any network file (maybe only UNCs, not mapped drives). VW doesn't
> recognize the UNC network disk as NTFS and reverts to FATFilename and
> truncates the directory and file parts to 8.3. Most problems
> disappeared when FATFilename was corrected (5i.*?) to default to long
> (254 character) filename components when it couldn't get the correct
> result from the OS call in getFileSystemAttributes:. Still,
> occasionally we see the error: maybe getFileSystemAttributes: in the
VM
> still has some old default code? Line 1081 in 7.6 ntfile.c seems to
set
> the file type to FAT and maximum file component length to 12 (8.3) if
> GetVolumeInformation fails but the drive is not invalid, and then
> returns the result to the image as a valid set of file system
> attributes. Presumably that's what's happening here.

Andres Valloud kindly created AR 54969 for the VM problem.

Steve

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On
> Behalf Of bqueyras
> Sent: 16 April 2009 12:28
> To: [hidden email]
> Cc: [hidden email]
> Subject: [vwnc] Fat filenames
>
> Hi,
>
> How is it possible to handle FAT filenames with network prefixes like
> this one ?
>   '\\meru\home$\Bernadette.Queyras\po\PROJETS\TRES GROS PROJET\beta
> version\AF 23 mars 09\biblio essai 23-03.tpbp'
>
> Namely asFilename gives the following :
>   a
>
FATFilename('\\meru\home$\bernadet.que\po\projets\tresgros\betavers\af2
> 3mars\biblioes.tpb')
>
> Bernadette Queyras
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Fat filenames

Annick
No our bug is much more straightforward, " asFilename " does not  
produce the right stuff.

Le 16 avr. 09 à 14:03, Steven Kelly a écrit :

> As I previously stated here:
> http://www.parcplace.net/list/vwnc-archive/0808/msg00062.html
>> I've seen this problem occasionally over the years, when working with
>> any network file (maybe only UNCs, not mapped drives). VW doesn't
>> recognize the UNC network disk as NTFS and reverts to FATFilename and
>> truncates the directory and file parts to 8.3. Most problems
>> disappeared when FATFilename was corrected (5i.*?) to default to long
>> (254 character) filename components when it couldn't get the correct
>> result from the OS call in getFileSystemAttributes:. Still,
>> occasionally we see the error: maybe getFileSystemAttributes: in the
> VM
>> still has some old default code? Line 1081 in 7.6 ntfile.c seems to
> set
>> the file type to FAT and maximum file component length to 12 (8.3) if
>> GetVolumeInformation fails but the drive is not invalid, and then
>> returns the result to the image as a valid set of file system
>> attributes. Presumably that's what's happening here.
>
> Andres Valloud kindly created AR 54969 for the VM problem.
>
> Steve
>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]] On
>> Behalf Of bqueyras
>> Sent: 16 April 2009 12:28
>> To: [hidden email]
>> Cc: [hidden email]
>> Subject: [vwnc] Fat filenames
>>
>> Hi,
>>
>> How is it possible to handle FAT filenames with network prefixes like
>> this one ?
>>  '\\meru\home$\Bernadette.Queyras\po\PROJETS\TRES GROS PROJET\beta
>> version\AF 23 mars 09\biblio essai 23-03.tpbp'
>>
>> Namely asFilename gives the following :
>>  a
>>
> FATFilename('\\meru\home$\bernadet.que\po\projets\tresgros\betavers
> \af2
>> 3mars\biblioes.tpb')
>>
>> Bernadette Queyras
>>
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Fat filenames

Steven Kelly
In reply to this post by bqueyras
Yes, it's funny how often the full explanation of a bug is more complex than a simple description of its symptoms :-).

Steve

Annick Fron a écrit:

> No our bug is much more straightforward, " asFilename " does not
> produce the right stuff.
>
> Le 16 avr. 09 à 14:03, Steven Kelly a écrit :
>
> > As I previously stated here:
> > http://www.parcplace.net/list/vwnc-archive/0808/msg00062.html
> >> I've seen this problem occasionally over the years, when working
> with
> >> any network file (maybe only UNCs, not mapped drives). VW doesn't
> >> recognize the UNC network disk as NTFS and reverts to FATFilename
> and
> >> truncates the directory and file parts to 8.3. Most problems
> >> disappeared when FATFilename was corrected (5i.*?) to default to
> long
> >> (254 character) filename components when it couldn't get the correct
> >> result from the OS call in getFileSystemAttributes:. Still,
> >> occasionally we see the error: maybe getFileSystemAttributes: in the
> > VM
> >> still has some old default code? Line 1081 in 7.6 ntfile.c seems to
> > set
> >> the file type to FAT and maximum file component length to 12 (8.3)
> if
> >> GetVolumeInformation fails but the drive is not invalid, and then
> >> returns the result to the image as a valid set of file system
> >> attributes. Presumably that's what's happening here.
> >
> > Andres Valloud kindly created AR 54969 for the VM problem.
> >
> > Steve
> >
> >> -----Original Message-----
> >> From: [hidden email] [mailto:[hidden email]] On
> >> Behalf Of bqueyras
> >> Sent: 16 April 2009 12:28
> >> To: [hidden email]
> >> Cc: [hidden email]
> >> Subject: [vwnc] Fat filenames
> >>
> >> Hi,
> >>
> >> How is it possible to handle FAT filenames with network prefixes
> like
> >> this one ?
> >>  '\\meru\home$\Bernadette.Queyras\po\PROJETS\TRES GROS PROJET\beta
> >> version\AF 23 mars 09\biblio essai 23-03.tpbp'
> >>
> >> Namely asFilename gives the following :
> >>  a
> >>
> > FATFilename('\\meru\home$\bernadet.que\po\projets\tresgros\betavers
> > \af2
> >> 3mars\biblioes.tpb')
> >>
> >> Bernadette Queyras
> >>
> >> _______________________________________________
> >> vwnc mailing list
> >> [hidden email]
> >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
> >
> > _______________________________________________
> > vwnc mailing list
> > [hidden email]
> > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
> >
>


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Fat filenames

Andres Valloud-6
In reply to this post by Steven Kelly
It's not just the VM.  The debugger shows the image is also defaulting
to a FAT16 filename type when no information can be retrieved.  Even if
we fix the VM to just fail to retrieve attributes when the path cannot
be found, then the image has to be amended to default to something other
than FAT.  Otherwise, the filename will be dutifully truncated to 8.3.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On
Behalf Of Steven Kelly
Sent: Thursday, April 16, 2009 5:04 AM
To: VW NC
Subject: Re: [vwnc] Fat filenames

As I previously stated here:
http://www.parcplace.net/list/vwnc-archive/0808/msg00062.html
> I've seen this problem occasionally over the years, when working with
> any network file (maybe only UNCs, not mapped drives). VW doesn't
> recognize the UNC network disk as NTFS and reverts to FATFilename and
> truncates the directory and file parts to 8.3. Most problems
> disappeared when FATFilename was corrected (5i.*?) to default to long
> (254 character) filename components when it couldn't get the correct
> result from the OS call in getFileSystemAttributes:. Still,
> occasionally we see the error: maybe getFileSystemAttributes: in the
VM
> still has some old default code? Line 1081 in 7.6 ntfile.c seems to
set
> the file type to FAT and maximum file component length to 12 (8.3) if
> GetVolumeInformation fails but the drive is not invalid, and then
> returns the result to the image as a valid set of file system
> attributes. Presumably that's what's happening here.

Andres Valloud kindly created AR 54969 for the VM problem.

Steve

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On
> Behalf Of bqueyras
> Sent: 16 April 2009 12:28
> To: [hidden email]
> Cc: [hidden email]
> Subject: [vwnc] Fat filenames
>
> Hi,
>
> How is it possible to handle FAT filenames with network prefixes like
> this one ?
>   '\\meru\home$\Bernadette.Queyras\po\PROJETS\TRES GROS PROJET\beta
> version\AF 23 mars 09\biblio essai 23-03.tpbp'
>
> Namely asFilename gives the following :
>   a
>
FATFilename('\\meru\home$\bernadet.que\po\projets\tresgros\betavers\af2
> 3mars\biblioes.tpb')
>
> Bernadette Queyras
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Fat filenames

Andres Valloud-6
Or maybe not... when the attributes are nil, then FATFilename defaults
to long names...

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On
Behalf Of Valloud, Andres
Sent: Friday, April 17, 2009 1:57 PM
To: VW NC
Subject: Re: [vwnc] Fat filenames

It's not just the VM.  The debugger shows the image is also defaulting
to a FAT16 filename type when no information can be retrieved.  Even if
we fix the VM to just fail to retrieve attributes when the path cannot
be found, then the image has to be amended to default to something other
than FAT.  Otherwise, the filename will be dutifully truncated to 8.3.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On
Behalf Of Steven Kelly
Sent: Thursday, April 16, 2009 5:04 AM
To: VW NC
Subject: Re: [vwnc] Fat filenames

As I previously stated here:
http://www.parcplace.net/list/vwnc-archive/0808/msg00062.html
> I've seen this problem occasionally over the years, when working with
> any network file (maybe only UNCs, not mapped drives). VW doesn't
> recognize the UNC network disk as NTFS and reverts to FATFilename and
> truncates the directory and file parts to 8.3. Most problems
> disappeared when FATFilename was corrected (5i.*?) to default to long
> (254 character) filename components when it couldn't get the correct
> result from the OS call in getFileSystemAttributes:. Still,
> occasionally we see the error: maybe getFileSystemAttributes: in the
VM
> still has some old default code? Line 1081 in 7.6 ntfile.c seems to
set
> the file type to FAT and maximum file component length to 12 (8.3) if
> GetVolumeInformation fails but the drive is not invalid, and then
> returns the result to the image as a valid set of file system
> attributes. Presumably that's what's happening here.

Andres Valloud kindly created AR 54969 for the VM problem.

Steve

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On
> Behalf Of bqueyras
> Sent: 16 April 2009 12:28
> To: [hidden email]
> Cc: [hidden email]
> Subject: [vwnc] Fat filenames
>
> Hi,
>
> How is it possible to handle FAT filenames with network prefixes like
> this one ?
>   '\\meru\home$\Bernadette.Queyras\po\PROJETS\TRES GROS PROJET\beta
> version\AF 23 mars 09\biblio essai 23-03.tpbp'
>
> Namely asFilename gives the following :
>   a
>
FATFilename('\\meru\home$\bernadet.que\po\projets\tresgros\betavers\af2
> 3mars\biblioes.tpb')
>
> Bernadette Queyras
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Fat filenames

Steven Kelly
In reply to this post by bqueyras
Re: [vwnc] Fat filenames
Yes, the FATFilename behaviour when no attributes are received changed in the image sometime between 3.1 and 5i.3 to use long filenames. Maybe in the case mentioned below, the VM could return no attributes and let the image decide?
 
Steve


From: [hidden email] on behalf of Valloud, Andres
Sent: Sat 4/18/2009 00:03
To: VW NC
Subject: Re: [vwnc] Fat filenames

Or maybe not... when the attributes are nil, then FATFilename defaults
to long names...

-----Original Message-----
From: [hidden email] [[hidden email]] On
Behalf Of Valloud, Andres
Sent: Friday, April 17, 2009 1:57 PM
To: VW NC
Subject: Re: [vwnc] Fat filenames

It's not just the VM.  The debugger shows the image is also defaulting
to a FAT16 filename type when no information can be retrieved.  Even if
we fix the VM to just fail to retrieve attributes when the path cannot
be found, then the image has to be amended to default to something other
than FAT.  Otherwise, the filename will be dutifully truncated to 8.3.

-----Original Message-----
From: [hidden email] [[hidden email]] On
Behalf Of Steven Kelly
Sent: Thursday, April 16, 2009 5:04 AM
To: VW NC
Subject: Re: [vwnc] Fat filenames

As I previously stated here:
http://www.parcplace.net/list/vwnc-archive/0808/msg00062.html
> I've seen this problem occasionally over the years, when working with
> any network file (maybe only UNCs, not mapped drives). VW doesn't
> recognize the UNC network disk as NTFS and reverts to FATFilename and
> truncates the directory and file parts to 8.3. Most problems
> disappeared when FATFilename was corrected (5i.*?) to default to long
> (254 character) filename components when it couldn't get the correct
> result from the OS call in getFileSystemAttributes:. Still,
> occasionally we see the error: maybe getFileSystemAttributes: in the
VM
> still has some old default code? Line 1081 in 7.6 ntfile.c seems to
set
> the file type to FAT and maximum file component length to 12 (8.3) if
> GetVolumeInformation fails but the drive is not invalid, and then
> returns the result to the image as a valid set of file system
> attributes. Presumably that's what's happening here.

Andres Valloud kindly created AR 54969 for the VM problem.

Steve


> -----Original Message-----
> From: [hidden email] [[hidden email]] On
> Behalf Of bqueyras
> Sent: 16 April 2009 12:28
> To: [hidden email]
> Cc: [hidden email]
> Subject: [vwnc] Fat filenames
>
> Hi,
>
> How is it possible to handle FAT filenames with network prefixes like
> this one ?
>   '\\meru\home$\Bernadette.Queyras\po\PROJETS\TRES GROS PROJET\beta
> version\AF 23 mars 09\biblio essai 23-03.tpbp'
>
> Namely asFilename gives the following :
>   a
>
FATFilename('\\meru\home$\bernadet.que\po\projets\tresgros\betavers\af2
> 3mars\biblioes.tpb')
>
> Bernadette Queyras
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Fat filenames

Andres Valloud-6
Re: [vwnc] Fat filenames
Even better... what we are testing right now is letting the VM fail with an I/O error containing the actual error code that caused the problem.  The exception handling needs to be patched up a little bit, and then the default will become FAT with long file names.  Hopefully this will be done completely in a little bit.


From: Steven Kelly [mailto:[hidden email]]
Sent: Friday, April 17, 2009 3:26 PM
To: Valloud, Andres
Cc: [hidden email]
Subject: RE: [vwnc] Fat filenames

Yes, the FATFilename behaviour when no attributes are received changed in the image sometime between 3.1 and 5i.3 to use long filenames. Maybe in the case mentioned below, the VM could return no attributes and let the image decide?
 
Steve


From: [hidden email] on behalf of Valloud, Andres
Sent: Sat 4/18/2009 00:03
To: VW NC
Subject: Re: [vwnc] Fat filenames

Or maybe not... when the attributes are nil, then FATFilename defaults
to long names...

-----Original Message-----
From: [hidden email] [[hidden email]] On
Behalf Of Valloud, Andres
Sent: Friday, April 17, 2009 1:57 PM
To: VW NC
Subject: Re: [vwnc] Fat filenames

It's not just the VM.  The debugger shows the image is also defaulting
to a FAT16 filename type when no information can be retrieved.  Even if
we fix the VM to just fail to retrieve attributes when the path cannot
be found, then the image has to be amended to default to something other
than FAT.  Otherwise, the filename will be dutifully truncated to 8.3.

-----Original Message-----
From: [hidden email] [[hidden email]] On
Behalf Of Steven Kelly
Sent: Thursday, April 16, 2009 5:04 AM
To: VW NC
Subject: Re: [vwnc] Fat filenames

As I previously stated here:
http://www.parcplace.net/list/vwnc-archive/0808/msg00062.html
> I've seen this problem occasionally over the years, when working with
> any network file (maybe only UNCs, not mapped drives). VW doesn't
> recognize the UNC network disk as NTFS and reverts to FATFilename and
> truncates the directory and file parts to 8.3. Most problems
> disappeared when FATFilename was corrected (5i.*?) to default to long
> (254 character) filename components when it couldn't get the correct
> result from the OS call in getFileSystemAttributes:. Still,
> occasionally we see the error: maybe getFileSystemAttributes: in the
VM
> still has some old default code? Line 1081 in 7.6 ntfile.c seems to
set
> the file type to FAT and maximum file component length to 12 (8.3) if
> GetVolumeInformation fails but the drive is not invalid, and then
> returns the result to the image as a valid set of file system
> attributes. Presumably that's what's happening here.

Andres Valloud kindly created AR 54969 for the VM problem.

Steve


> -----Original Message-----
> From: [hidden email] [[hidden email]] On
> Behalf Of bqueyras
> Sent: 16 April 2009 12:28
> To: [hidden email]
> Cc: [hidden email]
> Subject: [vwnc] Fat filenames
>
> Hi,
>
> How is it possible to handle FAT filenames with network prefixes like
> this one ?
>   '\\meru\home$\Bernadette.Queyras\po\PROJETS\TRES GROS PROJET\beta
> version\AF 23 mars 09\biblio essai 23-03.tpbp'
>
> Namely asFilename gives the following :
>   a
>
FATFilename('\\meru\home$\bernadet.que\po\projets\tresgros\betavers\af2
> 3mars\biblioes.tpb')
>
> Bernadette Queyras
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc