BUG: 16-bit setup.exe issues [Virus checked by FIDUCIA]

[tschweikle at FIDUCIA.de]

Greg
>> -----Original Message-----
>> From: tschweikle at FIDUCIA.de [mailto:tschweikle at FIDUCIA.de]
>> Sent: Monday, September 20, 1999 12:10 PM
>> To: Multiple recipients of list SAMBA-NTDOM
>> Subject: Re: BUG: 16-bit setup.exe issues
>>
>>
>[snip]
>> There is a workaround for this sort of problem:
>>
>> make dafault case lower/upper an set samba to ignore case
>> (don't preserve
>> case on the server):
>>
>>         preserve case = No
>>         short preserve case = No
>>         mangled names = No
>
> What about the
> mangle case
> parameter?  I'm just curious if this will fix my Office2K problem.
>
> Greg

try "dir" on a samba share holding long names. You'll get something
like:

  licenses       <DIR>        12.07.99  18:31 licenses
  LINUX~K!       <DIR>        07.06.99  14:07 LinuxInst
  venus          <DIR>        06.07.99  17:28 venus
  winxx          <DIR>        16.09.99  19:06 winxx
  33l3939  txt        27.538  30.08.99  20:43 33l3939.txt
  BONES~LE Z         622.499  08.07.99  23:55 bones_tar.Z
  IDE_D~EQ IMG     1.474.560  17.09.99  10:46 IDE_DISK1.IMG
  INSTA~%_ HTM       120.220  03.09.99  15:38 INSTALL.html
  LC252~GL ZIP     1.051.998  06.07.99  10:58 lc252install.zip
  NT4PR~O0 EXE       173.280  05.08.99  12:40 nt4prep_deu.exe
  READM~6P EXP           791  03.09.99  22:51 README.export
  WIN98~1S TGZ    25.514.291  04.08.99  14:31 win98-buch.tgz

BONES~LE.Z or LINUX~K! are mangled names. Both containing at least one
illegal character seen from DOS 5.xx: '~'. It was possible to include
these in a filename (unsing turbo-pascal for example) but not with
'cmd.com'.

switching mangled names off gives a more straightforward behavior:
'LinuxInst' will become 'LINUXINS.T' for dos (no dot). 'bones_tar.Z'
will become 'BONES_TA.Z' ('bones_tar.Z' has a dot).

>> The third option is a bit dangerous.

If I would have two files named 'bones_tar.Z' and 'bones_tar_123_4_5.Z'
they would give the same 'BONES_TA.Z' with this scheme. Making only one
out of two files accessible without additional tools.

>> But there are 16-bit
>> programs arround
>> checking file names for 'illegal characters' thinking they would save
>> users time this way, not thinking about changes in future file systems
>> allowing these...
>>
>> It should help.
>> BTW.: IBM-LAN-Server has the same problem. But there is no
>> Workaround known.

--