samba - Nov 1997 - problem with sef extracting exe-files...

>We are using samba version 1.9.17p4 en have a problem with
>self extracting exe-files on a samba-mounted disk from NT 4.0.
>( This problem also exists with earlier versions of samba e.g. 1.9.16p11 )
>
>If you place the exe-file in a directory called "12345678.123"
>( 8.3 filename ), there is no problem.
>
>If you place the exe-file in a directory called "123456789" ( long
filename),
>you get a message window which says it couldn't locate the exe-file.
I noticed a similar problem when using the dos edit command to open a file
on a samba share in a directory with a long file name and then trying to
print the file (from within edit that is).  You will get a "Edit was unable
to find the path 'LPT1'" error.

--------------------
Michael St. Laurent
Hartwell Corporation

"Whenever you find yourself on the side of the majority
it is time to pause and reflect."
               -- Mark Twain

>>self extracting exe-files on a samba-mounted disk from NT 4.0.
>>If you place the exe-file in a directory called "12345678.123"
>>( 8.3 filename ), there is no problem.
>>If you place the exe-file in a directory called "123456789" (
long filename),
>>you get a message window which says it couldn't locate the exe-file.
>
>I noticed a similar problem when using the dos edit command to open a file
>on a samba share in a directory with a long file name and then trying to
>print the file (from within edit that is).  You will get a "Edit was
unable
>to find the path 'LPT1'" error.
>

This doesn't look like a Samba problem to me. Try doing the same tests on an
NTFS volume with a long name in the path. I think you'll find the same
results. Both edit and the extractor are 16-bit programs and they therefore can
only deal with short names. Under certain circumstances they get very confused
when they try comparing truncated-long and tilde-converted-long names.

Nick Parker
Berger-Levrault, France