1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Specific client application problems</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
12 HREF="samba-faq.html"><LINK
14 TITLE="Configuration problems"
15 HREF="config.html"><LINK
18 HREF="errors.html"></HEAD
29 SUMMARY="Header navigation table"
73 NAME="CLIENTAPP">Chapter 4. Specific client application problems</H1
79 NAME="AEN174">4.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</H1
81 >When installing MS Office on a Samba drive for which you have admin
82 user permissions, ie. admin users = username, you will find the
83 setup program unable to complete the installation.</P
85 >To get around this problem, do the installation without admin user
86 permissions The problem is that MS Office Setup checks that a file is
87 rdonly by trying to open it for writing.</P
89 >Admin users can always open a file for writing, as they run as root.
90 You just have to install as a non-admin user and then use "chown -R"
98 NAME="AEN179">4.2. How to use a Samba share as an administrative share for MS Office, etc.</H1
100 >Microsoft Office products can be installed as an administrative installation
101 from which the application can either be run off the administratively installed
102 product that resides on a shared resource, or from which that product can be
103 installed onto workstation clients.</P
105 >The general mechanism for implementing an adminstrative installation involves
109 >, where X is the drive letter of either CDROM or floppy.</P
111 >This installation process will NOT install the product for use per se, but
112 rather results in unpacking of the compressed distribution files into a target
113 shared folder. For this process you need write privilidge to the share and it
114 is desirable to enable file locking and share mode operation during this
117 >Subsequent installation of MS Office from this share will FAIL unless certain
118 precautions are taken. This failure will be caused by share mode operation
119 which will prevent the MS Office installation process from re-opening various
120 dynamic link library files and will cause sporadic file not found problems.</P
126 >As soon as the administrative installation (unpacking) has completed
127 set the following parameters on the share containing it:</P
130 CLASS="PROGRAMLISTING"
132 path = /where_you_put_it
133 comment = Your comment
134 volume = "The_CD_ROM_Label"
145 >Now you are ready to run the setup program from the Microsoft Windows
146 workstation as follows: <B
148 >\\"Server_Name"\MSOP95\msoffice\setup</B
158 NAME="AEN194">4.3. Microsoft Access database opening errors</H1
160 >Here are some notes on running MS-Access on a Samba drive from <A
161 HREF="stefank@esi.com.au"
173 >Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</TD
177 >Make sure that you open the database as 'shared' and to 'lock modified records'</TD
181 >Of course locking must be enabled for the particular share (smb.conf)</TD
195 SUMMARY="Footer navigation table"
215 HREF="samba-faq.html"
234 >Configuration problems</TD