Custom Query (292 matches)

I think that when the configuration wizard creates the initial configuration, it should use the "SYSTEM" charset for all of dos/unix/display charset settings, not "IBM-850" (which is a strange choice in any non-European country). As far as I understand "SYSTEM" means the current system codepage. This will cause Samba to use the system codepage both locally (which is obviously correct) and when talking to DOS clients (which is also correct as clients that have a different 8-bit local encoding won't be able to show the correct file names anyway).

I have two OS/2 machines. Setting all charsets to SYSTEM on both of them is the only way when they see each other's national (cyrillic in this case) file names correctly through the ndpsmp plugin (which uses the same smb.conf as the server AFAIR). Also, from my iMac (which is UTF-8 everywhere) I see correct file names on both machines w/o touching any configuration files.

When you start samba monitor 2.5.RC5, you will see a message box as on the screen shot if your LANG setting points to a language for which a .MSG file is missing (like ru_RU in my case). It should silently fall back to English (as it always did before).

If you set an invalid dos charset (e.g. "866") in smb.conf it will cause the Nethood tab to loop forever giving an error from init_iconv that it can't convert from various charsets to "866".