1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Specific client application problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.61.2"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Install.html" title="Chapter�2.�Compiling and installing Samba on a Unix host"><link rel="next" href="FAQ-errors.html" title="Chapter�4.�Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Specific client application problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-errors.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-ClientApp"></a>Chapter�3.�Specific client application problems</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-ClientApp.html#id2820864">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2820890">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2820986">Microsoft Access database opening errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2820864"></a>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</h2></div></div><div></div></div><p> 2When installing MS Office on a Samba drive for which you have admin 3user permissions, ie. admin users = username, you will find the 4setup program unable to complete the installation. 5</p><p> 6To get around this problem, do the installation without admin user 7permissions The problem is that MS Office Setup checks that a file is 8rdonly by trying to open it for writing. 9</p><p> 10Admin users can always open a file for writing, as they run as root. 11You just have to install as a non-admin user and then use "chown -R" 12to fix the owner. 13</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2820890"></a>How to use a Samba share as an administrative share for MS Office, etc.</h2></div></div><div></div></div><p> 14Microsoft Office products can be installed as an administrative installation 15from which the application can either be run off the administratively installed 16product that resides on a shared resource, or from which that product can be 17installed onto workstation clients. 18</p><p> 19The general mechanism for implementing an adminstrative installation involves 20running <b class="command">X:\setup /A</b>, where X is the drive letter of either CDROM or floppy. 21</p><p> 22This installation process will NOT install the product for use per se, but 23rather results in unpacking of the compressed distribution files into a target 24shared folder. For this process you need write privilidge to the share and it 25is desirable to enable file locking and share mode operation during this 26process. 27</p><p> 28Subsequent installation of MS Office from this share will FAIL unless certain 29precautions are taken. This failure will be caused by share mode operation 30which will prevent the MS Office installation process from re-opening various 31dynamic link library files and will cause sporadic file not found problems. 32</p><div class="itemizedlist"><ul type="disc"><li><p> 33As soon as the administrative installation (unpacking) has completed 34set the following parameters on the share containing it: 35</p><pre class="programlisting"> 36[MSOP95] 37 path = /where_you_put_it 38 comment = Your comment 39 volume = "The_CD_ROM_Label" 40 read only = yes 41 available = yes 42 share modes = no 43 locking = no 44 browseable = yes 45 public = yes 46</pre></li><li><p>Now you are ready to run the setup program from the Microsoft Windows 47workstation as follows: <b class="command">\\"Server_Name"\MSOP95\msoffice\setup</b> 48</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2820986"></a>Microsoft Access database opening errors</h2></div></div><div></div></div><p> 49Here are some notes on running MS-Access on a Samba drive from <a href="stefank@esi.com.au" target="_top">Stefan Kjellberg</a> 50</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</td></tr><tr><td>Make sure that you open the database as 'shared' and to 'lock modified records'</td></tr><tr><td>Of course locking must be enabled for the particular share (smb.conf)</td></tr></table><p> 51</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="FAQ-errors.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�2.�Compiling and installing Samba on a Unix host�</td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�4.�Common errors</td></tr></table></div></body></html> 52