Samba and InstallShield 5

Jeremy Allison jallison at
Tue Jan 6 18:40:03 GMT 1998


	This is a known bug with the NT redirector
when a 16 bit program accesses a directory name which is
a long (>8.3) filename. NT doesn't request the mangled
name for the 16 bit app (although Samba can supply
it). You can reproduce the same problem running
against a Windows 95 server (it only occurrs with
a 16 bit app on NT running against an SMB server
that doesn't support NT SMB calls).

I plan to fix this by adding NT SMB calls to Samba,
but this won't get into the 1.9.18 release - probably
the one after.

In the meantime you can get around it be adding a
symlink with a short (8.3) name and access the files
via that path.

Hope this helps,

	Jeremy Allison,
	Samba Team.

Laine Stump wrote:
> Sorry, I know this is a rather specific question, but it does seem to be
> Samba-related.
> I just purchased InstallShield 5 Professional and am attempting to use
> it in a development directory that is on a Samba-exported disk. My
> problem is that when I attempt to compile the setup.rul script, it
> fails, telling me:
>    Compiling...
>    (0) : fatal  C8503: Can't open script input file
>    Done-  1 error(s), 0 warning(s)
> When I put the same project on the shared disk of another WinNT machine,
> the compile completes without incident.
> Turning Samba's debug up to 3, I see that InstallShield is attempting to
> open the file "Script Files/.rul", which is of course failing (the
> script file is named setup.rul).
> Has anybody experienced this problem? Any idea how to get around it?
> BTW - one hint to InstallShield users - it erroneously attempts to
> determine if a given drive letter is valid by writing a file to the root
> directory of the drive. If the root dir of your share isn't writable (as
> mine wasn't), you won't even get as far as I have!

Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.

More information about the samba mailing list