PureBasic Forums - English

Oso wrote: Wed Nov 30, 2022 1:15 pm Something I saw on a Google group that interested me — Windows cannot store a filename ending with a period. It's thought to be a remnant from the old 8.3 filename limitation. Is this really the reason? I find it odd because filenames can contain periods within the first part of the name. Here is the test...

Code: Select all

ECHO xx > aa.            <------- Make sure to add the appended period
DIR                      Note how the period has been lost
TYPE aa                  There is your data!

I do a lot of work between Linux and Windows and transfer files between them using Samba. I just noticed that if I open the Samba share in Windows and copy a file with a period on the end (which is perfectly acceptable in Unix), Windows throws a tantrum and corrupts the filename to...

Code: Select all

MSMLDD~M

mangled names = no 

# killall smbd
# killall nmbd
# smbd -D
# nmbd -D

C:\> dir /b z:\tmp
aa.

Marc56us wrote: Wed Nov 30, 2022 2:15 pm Edit smb.conf
Add in [global]

Code: Select all

mangled names = no 

Cannot option file "test" for read access. The system cannot find the file specified.