Michael wrote :

  There are filename mappings already in place for Samba/iX which replace
the traditionally non-available characters with their hexidecimal
equivalents.
For example, a space is replaced with _20_ so the Windows filename of
"test file" becomes "test_20_file" when written to the Samba share.  Beyond
this method which was placed into the source code, there are also some
configuration settings in smb.conf for 'name mangling', but those are
mainly
there to allow characters available on the Samba server to be represented
by alternatives on the client (something which is opposite of your
problem).
As long as the full compliment of characters are not equivalent between the
systems, you run the risk of duplicating names.  For example in HFS, case
is significant, and while you can ask Samba to retain the case of the
characters
in the filename, you can't access more than one of them.  "Test" looks the
same
as "test" that looks the same as "tesT", etc.  Another example is when
you've
stored files with names that happen to match the current Samba/iX
substitution
rules.  A file in HFS named "Nov_20_Backup" looks like "Nov Backup" to the
SMB client, but what if "Nov_20_Backup" really WAS the name of the file on
the client!  To complicate matters worse, what if you also had a "Nov
Backup"
named file on the client.  Only one can get stored on the host via
Samba/iX.

  For the most part the name substitutions work well, but they are not
perfect.
With the addition of more valid filename characters to the HFS (via some
patches to 5.5, or standard in 6.0), Samba/iX (version 7j) can deal a bit
better
with the problem.  As I've previously stated in other posts though, this
version
isn't compatible with what HP is currently shipping, and unless you have a
specific need for those additional characters (a good example is if you are
doing JAVA programming via an client based IDE with the files stored in
the HFS on the 3000), you're best to stick with their version for now.
 That
version as well as a nice 'find filter' utility written by Lars which can
show you
the different name mappings can be downloaded from www.sambaix.com if
your so inclined.

Regards,
Michael L Gueterman
Easy Does It Technologies
SIG Web Co-Chair
http://www.editcorp.com

I've circumvented my problem quite the low-key, low-tech way : I've just
removed all non-Posix characters from the filenames on my Window$ PC, like
blanks. I've also made sure that Window$ case-insensitivity will not map
back two distinct Posix files back to the same Window$ filename... With
that, I can now safely backup my PC onto my 3000.

Now, step# 3 ... Tweak the config to handle security, file access, logons,
passwords, and so forth.

Christian