(To get the best on-screen view in Windows Notepad, maximize the Notepad 
window. For best printed results, open this document in Windows Write, 
Microsoft Word, or another word processor, select the entire document 
and format the text in 10 point Courier before printing.)

-------------------------------------------------
Installing and Using Microsoft Excel on a Network
-------------------------------------------------

Contents

  Introduction
    Designating Network Connections

  Setting Up Microsoft Excel on a Network File Server

    Installation Requirements
      >To install Microsoft Excel on a network file server or a shared 
       directory
    Extracting Files from DMF Disks to a Network Server

  Creating Custom Installations for Workstation Users

    Editing SETUP.STF to Create a Script
      >To edit the information in SETUP.STF
    Supporting Vendor Independent Messaging sites    
    Distributing and Using a Script
    Distributing a Script with Microsoft Mail

  Network Considerations for Workstation Users

    Installing Microsoft Excel on a Workstation
    Sharing and Protecting workbooks on Networks
    Things to Remember About Shared Files
    Saving Files to a Network Drive
    Other Tools for Workgroup Users
    Changing links to QE.XLA after network installation

  List of Files and Sizes for Network Installations
    Administration
    Workstation

Note: To move directly to step-by-step instructions, search for the 
----  right-angle bracket character (>). This character marks the 
      beginning of each procedure.

-------------------------------------------------
Introduction
-------------------------------------------------

This document discusses how to install and use Microsoft Excel version 5.0 
for Windows on a network.

The first section, "Setting Up Microsoft Excel on a Network File Server," is 
for network administrators who install Microsoft Excel from floppy disks to 
a network. Before installing Microsoft Excel on any network workstations, 
the network administrator must install Microsoft Excel on a network file 
server.

The second section, "Creating Custom Installations for Workstation Users," 
is for network administrators who want to create custom installation scripts 
that end users can run to install or upgrade Microsoft Excel from a network 
file server.

The final section, "Network Considerations for Workstation Users," is for 
Microsoft Excel users who run Microsoft Excel from a network file server. It 
also includes information for users in workgroups.

Designating Network Connections

In this document, network connections are specified with a logical drive 
letter, such as N. If your network supports the use of universal naming 
convention (UNC) paths of the form \\server\share, workstation setup users 
can use a path instead of a logical drive letter. For network server setup, 
however you must use a logical drive letter. Setup remembers the paths to 
the components you install, so if you use logical drive letters to specify 
network file servers during installation, you have to make those network 
connections manually and use the same drive letters before you run Setup 
again. If you use UNC paths, Setup will make the correct connections 
automatically.

Note Every Microsoft Excel user must have a Microsoft Excel license. 
----  A license is obtained by buying a retail package or a Microsoft 
      License Pak. For more information about network use restrictions, 
      see your Microsoft Excel license agreement.

---------------------------------------
Setting Up Microsoft Excel on a Network File Server
---------------------------------------

This section is for network administrators who perform an administrator’s 
installation on a network file server or a shared directory.

Users on networks can share the Microsoft Excel program and files created in 
Microsoft Excel. Once you’ve installed Microsoft Excel on the network, end 
users can either install the program and its components on the workstation’s 
hard disk or run Microsoft Excel from the network file server. Note that 
users can run Microsoft Excel from a network server only after completing 
the workstation installation.

End users can install Microsoft Excel from the file server, instead of from 
floppy disks, by using the basic procedure discussed in Chapter 1, 
"Installing and Running Microsoft Excel," in the Microsoft Excel User’s 
Guide. Alternatively, you can create a script that end users can run to 
install Microsoft Excel. For more information about scripts, see 
"Creating Custom Installations for Workstation Users," later in this 
document.

This document assumes that you know how to use network software to connect 
to network drives and how to find files stored on network file servers.

Before you set up Microsoft Excel on a network file server, check the 
following:

*  The network must be operational, and you must have read, write, and 
    delete/erase privileges for the network directories in which you want 
    to install Microsoft Excel. For more information, see your network 
    software documentation.

*  You must install the Windows operating system, version 3.1 or later,
   on the workstation you use to install Microsoft Excel on the network 
   file server, and on any workstations that will run Microsoft Excel. 
   For information about installing Windows, see your Windows documentation.

*  If any network users share the Windows operating system or other 
   applications, they must be logged off from the network. The directories 
   that contain shared components on the file server or shared volume must 
   be locked from user access - for example, W:\WINDOWS and 
   W:\MSAPPS. You must have create, write, and delete privileges in 
   these directories.

*  You should determine in which network file server directories the 
   components of Microsoft Excel should be installed. Setup suggests 
   installing EXCEL.EXE in the EXCEL directory and installing shared 
   components in the MSAPPS directory of the network file server or 
   the shared volume. You can specify other paths if you want to.

Setting up Microsoft Excel on network workstations is a two-step process. 
First install Microsoft Excel on the network file server. Then set up the 
workstations, either by installing Microsoft Excel on each workstation’s 
hard disk or by setting up the workstations to run Microsoft Excel from the 
file server.

Installation Requirements

>To install Microsoft Excel on a network file server or a shared directory

  1.  Ask all users who are sharing Windows or Microsoft applications
      such as Microsoft Excel and Microsoft Word (which share components) 
      to disconnect from the network file server or the shared directory.

  2.  Start Microsoft Windows, and quit any other applications.

  3.  Insert the disk labeled "Setup Disk 1" in drive A or drive B.

  4.  From the File menu in either Program Manager or File Manager, 
      choose Run.

  5.  Type <drive letter>:setup /a and then press Enter. (The /a switch 
      indicates an administrator’s installation.) For example, a:setup /a

  6.  Follow the instructions on the screens that Setup displays. 
      You need to supply your company name, which will be included 
      with workstation installations made from the file server. You 
      will have one opportunity to confirm the company name. Make 
      sure that the name is correct before you proceed; once you’ve 
      confirmed it, you cannot change it.

      You also need to supply the network directory in which you want 
      to install the main Microsoft Excel program (for example, N:\EXCEL), 
      and the directory for storing shared components, such as MSSPELL.DLL, 
      the spelling checker. Shared components are usually stored in the 
      MSAPPS directory at the same directory level as the directory that 
      contains EXCEL.EXE - for example, N:\MSAPPS.

     If you are running the Windows operating system from a shared 
     installation, the proposed location for the shared components is 
     at the same directory level as the shared Windows directory - for 
     example, N:\MSAPPS.

     When users install Microsoft Excel on their workstations by running 
     Setup from this administrator’s installation, the shared components 
     can be installed on the user’s workstation or run from the network. 
     Before you complete the administrator’s installation, decide if the 
     shared components will be automatically installed on individual 
     workstations, automatically shared from the network, or if the choice 
     will be left to the workstation user.

  7. Set the access privileges to read-only for the server 
     directories in which you installed Microsoft Excel components, 
     and ensure that all users who may need to install Microsoft Excel 
     on their workstations from the network have read privileges for 
     those directories.

Note: If you install Microsoft Excel to a network file server, complete
----  one or more workstation installations and then move Microsoft Excel
      to another file server, your workstation users will not be able to 
      change their installation. Each workstation installation includes a 
      SETUP.STF file that points back to the original file server at the 
      time of the workstation's first installation. The workstation user 
      must manually update their SETUP.STF file to point to the new 
      network server. This is a text file, so it can be opened in a text 
      editor or word processor.


Extracting Files from DMF Disks to a Network Server

With the exception of the Setup disk (Disk 1), your Microsoft Excel disks
use a new format called DMF (Distribution Media Format). DMF increases
the capacity of a 3.5-inch floppy disk, reducing the number of disks needed
to install your application and therefore speeding up the installation process.

If you need to copy the Microsoft Excel disks onto a network server or 
other permanent storage drive, you may use the copy switch (/C) with the 
EXTRACT.EXE utility on Disk 1 to copy the Microsoft Excel installation 
files to the target location.

For example, after creating a directory called C:\DISKS on your hard 
drive for the Microsoft Excel files, copy all the files on Disk 1 to 
that directory. (Since Disk 1 does not use DMF, you can use the standard MS-
DOS Copy command, COPY A:\*.* C:\DISKS.) Switch to drive A and type the
following command to copy the rest of the disks to the directory C:\DISKS:

	FOR %I IN (*.*) DO C:\DISKS\EXTRACT /C A:\%I C:\DISKS\%I

A cabinet (.CAB) file includes many files stored as a single file.
If you need only a single file that is contained in one of the cabinet 
files, you may search for it using the /D switch with EXTRACT.EXE. Once 
you find the file, you can use EXTRACT.EXE again to copy the file to the 
desired location. You can also type EXTRACT /? to get help on the EXTRACT
command options. Here are some examples of how to use the EXTRACT command
to find files.
To list all files in a cabinet file:
	EXTRACT /D A:\<cabinet filename>
To list all EXE files in a cabinet file:
	EXTRACT /D A:\<cabinet filename> *.EXE
Here are some examples of how to use EXTRACT to copy a single file out 
of a cabinet file.
To extract ANY.EXE to the current directory:
	EXTRACT A:\<cabinet filename> ANY.EXE
To extract ANY.EXE to C:\OFFICE:
	EXTRACT A:\<cabinet filename> /L C:\OFFICE ANY.EXE

--------------------------------------
Creating Custom Installations for Workstation Users
--------------------------------------

Before you can create custom installations for end users, you must install 
Microsoft Excel on your network file server. See "To install Microsoft Excel 
on a network file server or a shared directory" above.

If the workstation can run Windows version 3.1, it can run Microsoft Excel, 
provided that it has sufficient RAM and disk space. Each workstation should 
have at least 4 MB of RAM and 2 MB of available disk space for the basic 
Microsoft Excel program.

Once you've installed Microsoft Excel on your network file server, you can 
create scripts to run Setup "silently" and control how Setup installs 
Microsoft Excel on workstations. With a script, you can do the following:

*  Perform a complete installation silently, without input from the user.

*  Control which type of installation - Typical, Complete/Custom, 
   Laptop (Minimum), or Workstation - you want Setup to perform.

*  Specify the directory in which to install Microsoft Excel.

*  Ensure that all installations in a workgroup are the same.

Setup uses information in the file SETUP.STF to determine which files to 
install and where they should be copied.

To automate workstation setup with a script, use one of the following
switches:
  /q to complete the setup and notify you when completed. When you use this
switch,Setup reads information from SETUP.STF and installs Microsoft Excel 
in the program directory for the previous version of Microsoft Excel or in 
the default Microsoft Excel program directory, C:\EXCEL, without prompting 
the user for information.
  /q1 to complete the setup and, if no other running applications are
detected, restart the workstation. 

With the /q switch, Setup notifies you when it has completed while with
the /q1 switch Setup gives no notification - it is completely silent.

To perform a typical installation by default, just add the /q or /q1 
switch when you run Setup. For example, at the command prompt, type the
path to the server or directory where Setup is installed, and then type
setup /q to start an automatic installation. 

To control which type of installation Setup performs and specify the
directory where Microsoft Excel is installed, edit SETUP.STF to create a
custom script that end users can run to install Microsoft Excel.

Editing SETUP.STF to Create a Script

This section describes how to create a script that automatically
performs a Typical, Complete/Custom, Laptop (Minimum), or Workstation
installation and how to specify a directory where Setup will install 
Microsoft Excel.

>To edit the information in SETUP.STF

  1.  Copy the file SETUP.STF from the network location in which you 
      installed the main Microsoft Excel program and give it a 
      new name. Open the copy of SETUP.STF (not the original) 
      with any spreadsheet application or word processor. It is easiest 
      to work with the table in Microsoft Excel.

  2.  To specify the type of installation you want the script to 
      perform, scroll through the table until you see the following 
      list of installation options in the third column:

        Typical
        Complete/Custom
        Laptop (Minimum)
        Workstation

      Type yes in the column labeled "Install During Batch Mode" 
      to the left of the type of installation you want the script 
      to perform. Type no next to the other options.

  3.  If you want the script to perform a Complete/Custom installation, 
      scroll down until you see the following list of components in 
      the third column:

       Microsoft Excel
       Online Help and Lessons
       Data Access
       Graphics Filters
       Addins
       Tools

      Type yes in the column to the left of each component you 
      want the script to install. Type no next to the other options.

  4.  To specify a directory where Setup will install Microsoft Excel, 
      scroll through the table until you see "c:\excel" in the column 
      labeled "Object Data." Replace the "c:\excel" with the name of the 
      directory where you want Setup to install Microsoft Excel.

      Important
      To ensure that Setup works properly, do not edit any other part 
      of the table file. If the initial value in a cell is empty, do 
      not edit the cell. If you are using a text editor, do not delete 
      tab characters that separate table columns.

  5.  Save the edited table in text-only format with the new name 
      you assigned in step 1.

Supporting Vendor Independent Messaging sites

Microsoft Excel supports Vendor Independent Messaging (VIM) 1.0, which 
means that you can use the Send and Add/Edit Routing Slip commands (File 
menu) in Microsoft Excel to send or route Microsoft Excel documents with 
mail applications such as Lotus cc:Mail that support VIM 1.0. To provide 
this support for users who install Microsoft Excel with the SETUP.STF 
script, make the following change. Edit line 322 of SETUP.STF.  Replace 
the string "323 324 325" with "329".
 

Distributing and Using a Script

After you create a script, you can copy it to the file server or shared 
volume from which you want users to install Microsoft Excel, or you can 
distribute it with Microsoft Mail or another application that can send  
items across a network.

Use one of the following methods to distribute a script:

*  To create one script for all users, rename the SETUP.STF file 
   that comes with Microsoft Excel to something else, such as 
   SETUP.OLD. Name the copy of the script that you edited SETUP.STF, 
   and save it in the same network directory as SETUP.EXE. Direct 
   your users to run SETUP.EXE /q from the file server or the shared 
   volume.

*  Copy SETUP.EXE and give the copy the same filename you gave 
   the script but use the .EXE filename extension. For example, 
   if you named the script NEWSETUP.STF, name the copy of Setup 
   NEWSETUP.EXE. Put the renamed setup file and the script in the 
   same directory as SETUP.EXE on the file server or the shared volume. 
   Direct your users to run the copy of Setup (for example, NEWSETUP.EXE, 
   not SETUP.EXE).

*  To create different installation scripts for different groups 
   of users, distribute the script with Microsoft Mail or another 
   application as a Program Manager icon. The command line specifies 
   the script and switches, as shown below.

/t tablename  Substitute the name of the new script for tablename. 

/n username  (Optional) Substitute a value for username to prevent Setup 
from prompting the user for a name. The name must be enclosed in quotation 
marks as shown in the example that follows. To automatically register the 
workstation copy of Microsoft Excel with the workstation’s existing user 
name, type the quotation marks with no name (""). Setup uses the name 
specified in the WIN.INI file on the workstation in the DefName line of 
the [MS User Info] section.

/q  Causes Setup to run without any user interaction. 

For example, suppose you installed Microsoft Excel in the EXCEL directory 
of a file server - where X designates the file server - and distribute a 
silent script that uses the MYSCRIPT.STF table file to a user named Paul 
Tanner. The command line to run the script would be:

	x:\excel\setup.exe /t myscript.stf /n "Paul Tanner" /q

Distributing a Script with Microsoft Mail

If you use Microsoft Mail to distribute a script, create a new message and 
then choose Insert Object from the Edit menu. In the Object Type box, select 
Package, and then choose the OK button. From the Edit menu in Object 
Packager, choose Command Line. Type the full path to SETUP.EXE in the 
EXCEL directory of the file server or the shared directory. (If your network 
supports UNC pathnames, use that syntax. If not, users will need to make the 
network connection themselves by using the same drive letter you specified 
before running Setup.) Type setup and the switches and arguments as needed, 
and then choose the OK button.

To attach the Microsoft Excel Setup icon to the command line, choose the 
Insert Icon button in Object Packager. Choose the Browse button to locate 
SETUP.EXE in the EXCEL directory of the network file server, and then 
choose the OK button. Choose Update from the File menu to add the icon to 
the Mail message, and then choose Exit from the File menu to close Object 
Packager. The icon is now ready to distribute. Anyone who receives the 
message can double-click the icon to run Setup from the network and 
install Microsoft Excel by using the script you specified with the /t 
switch.

--------------------------------------
Network Considerations for Workstation Users
--------------------------------------

There are two ways to run Microsoft Excel in a network environment:

*  You can run Microsoft Excel entirely off the network, without 
   installing it on your own computer.

*  You can install Microsoft Excel on your own computer.

Installing Microsoft Excel on a Workstation

If your computer is connected to a network file server or a shared 
directory, your network administrator may have installed a copy of 
Microsoft Excel on the network that you can then install on your 
workstation. The administrator may also have created a process you can use 
to install Microsoft Excel automatically. Check with your administrator to 
determine the best way for you to install Microsoft Excel.

The procedure for installing Microsoft Excel on a workstation is discussed 
in Chapter 1, "Installing and Running Microsoft Excel," in the Microsoft 
Excel User’s Guide. Once you have installed Microsoft Excel, read the 
following section for important information about using Microsoft Excel in 
a network environment. You may also need special network software to manage 
and synchronize shared files on the file server. For more information, 
check with your network administrator.

Sharing and Protecting Files on Networks

Using Microsoft Excel on a network is essentially the same as using 
Microsoft Excel on a stand-alone computer. On a network, however, you can 
use the network file server to store files and exchange them with other 
users, so you may want to protect some files from unauthorized access.

Things to Remember About Shared Files

*  In order for everyone who works on a shared file to display and 
   print it the same way, the fonts used in the file must be 
   available on the other computers and printers in your workgroup. 

*  If you assign a file-protection password, you should write it 
   down. Without the password, no one can open the file. Also 
   bear in mind that some kinds of protection - such as protecting 
   an individual sheet or range of cells - do not prevent other users 
   from setting a file-protection password.

For more information about sharing and protecting files, see Chapter 39, 
"Protecting a Workbook" and Chapter 42, "Importing and Exporting 
Documents" in the Microsoft Excel User’s Guide.

Saving Files to a Network Drive

When saving Microsoft Excel files to a Sun PC-NFS network, you should use 
version 5.1a of the network software. There is a possibility that you can 
corrupt a Microsoft Excel version 5.0 workbook if you use Sun PC-NFS 5.1 
without record locking. This problem is fixed in the Sun PC-NFS 5.1a 
release.

There have been reports of problems saving Microsoft Excel files to a 
Hewlett-Packard Lan Manager/Unix server while using HP Lan Manager 2.2 
Basic Workstation. Please obtain HP LanMan Basic Workstation revision 
A.00.01.002 or later to resolve the problems.

Other Tools for Workgroup Users

Microsoft Excel provides features such as audit tools, workbook routing, and 
password protection that make sharing and editing workbooks in a workgroup 
setting easier. For more information about these features, see Part 8 in the 
Microsoft Excel User's Guide.

Changing links to QE.XLA after network installation

If you run Microsoft Excel version 5.0 from a network server and use macros 
that rely on functions in a previous version of QE.XLA, you must change the 
links to those functions so that they point to the new version of QE.XLA.  
The links in your macros should now use the pathname 
server_directory\LIBRARY\MSQUERY\QE.XLA where server_directory is 
the directory containing Microsoft Excel on the network server. 

-------------------------------------------------
  List of Files and Sizes for Network Installations
-------------------------------------------------

NETWORK INSTALL:  ADMINISTRATION				
		
\Xl5usadmin						
_mssetup.exe			14121				
acmsetup.hlp			19125
cnf2ini.exe			23667
excel.exe			4246912
excel_bb.dll			353088
excel5.inf			22360
excel5.reg			10287
macrofun.hlp			930014
mainxl.hlp			2992556
mscpydis.dll			14832
mssetup.dll			191360
network.txt			30907
odbcinst.dll			82704
setup.exe			251600
setup.ini			149
setup.stf			172653
vba_xl.hlp			2080609
wrkstn.inf			23128
xlconvmp.dll			45600
xlen50.olb			230400
xlhelp.dll			13728
xlintl.dll			489536
xlpss.hlp			68645
xlreadme.hlp			41198
xlsetup.ttf			79720
\Xl5usadmin\Examples		
bookst.xls			88064
sales.xls			13824
samples.xls			139264
\Xl5usadmin\Examples\Solver		
solverex.xls			16896
solvsamp.xls			43520
\Xl5usadmin\Excelcbt		
93sales.xls			79360
accounts.xls			53248
analysis.xls			28160
art.xls				19968
budget.xls			36352
cbtlib4.dll			17328
chart.xls			29696
chart2.xls			23552
excelcbt.cbt			108880
excelles.cbt			750521
exotic.fmt			701
exotic.wk1			3255
home.xls			25088
parts.fmt			527
parts.wk1			861
products.xls			77824
qtrsales.xls			23552
quickprv.cbt			164351
sales.xlt			11776
schedule.fmt			587
schedule.wk1			1041
stocks.xls			14336
summary.xls			33280
trend.xls			18944
vbstock.xls			23552
xlcbt.dex			9104
\Xl5usadmin\Library		
addinfns.xla			22016
autosave.xla			44544
reports.xla			135680
updtlink.xla			20480
views.xla			112640
\Xl5usadmin\Library\Analysis		
analysf.xla			113664
analysis.xla			45568
analysis.xll			360608
atpvbaen.xla			129024
funcres.xla			75264
procdb.xla			99328
\Xl5usadmin\Library\Crosstab		
crossfnc.xla			2617
\Xl5usadmin\Library\Msquery		
qe.xla				158208
qexla.dll			10240
xlodbc.dll			66224
xlodbc.xla			50176
xlquery.xla			204288
\Xl5usadmin\Library\Slides		
slides.xla			160256
slides.xlt			20992
xlslides.dll			44992
\Xl5usadmin\Library\Solver		
solver.dll			166992
solver.xla			283136
\Xl5usadmin\Shared		
cgmimp.flt			44912
cuecard2.dll			1655
custom.dic			0
customer.dbf			13364
customer.mdx			4096
employee.dbf			4582
employee.mdx			4096
epsimp.flt			71984
hpglimp.flt			215376
iffpcx.dll			10640
ifftiff.dll			32624
msinfo.exe			40960
msquery.cue			209228
msquery.exe			622592
msquery.hlp			437165
mssp_am.lex			176839
mssp_br.lex			176298
msspell.dll			86016
orddtail.dbf			1754
orddtail.mdx			4096
orders.dbf			7885
orders.mdx			4096
pcximp.flt			11728
product.dbf			5729
product.mdx			4096
qryintl.dll			35391
supplier.dbf			6621
supplier.mdx			4096
tiffimp.flt			11728
wmfimp.flt			5104
\Xl5usadmin\System		
ccapi200.dll			46400
ccard200.exe			127424
commtb.dll			40784
compobj.dll			102400
ctl3d.dll			21008
ctl3dv2.dll			21648
dbnmp3.dll			10704
ddeml.dll			39424
drvaccss.hlp			50469
drvdbase.hlp			54455
drvfox.hlp			55004
drvpardx.hlp			54540
drvssrvr.hlp			87839
mapivim.dll			62096
msffile.dll			177840
msjetdsp.dll			85792
mstoolbr.dll			9200
odbc.dll			49584
odbcadm.exe			6496
odbcinst.dll			82704
odbcinst.hlp			17412
ole2.dll			313344
ole2.reg			24606
ole2conv.dll			57328
ole2disp.dll			98366
ole2nls.dll			147568
ole2prox.dll			55808
pdx110.dll			189168
red110.dll			238416
scp.dll				11920
sdm.dll				102032
shareres.dll			37888
simadmin.dll			160080
simba.dll			469904
sqlsrvr.dll			155776
stdole.tlb			4322
storage.dll			157184
typelib.dll			153312
vba.dll				820064
vbaen.dll			9360
vbaen.olb			31060
ver.dll				9696
vshare.386			14933
xbs110.dll			263840
xlcall.dll			1600
\Xl5usadmin\Xlstart		
xl5galry.xls			11776
\Xl5usadmin\Msapps\Grphflt		
cgmimp.flt			44912
epsimp.flt			71984
hpglimp.flt			215376
iffpcx.dll			10160
ifftiff.dll			32624
pcximp.flt			11728
tiffimp.flt			11728
wmfimp.flt			5104
\Xl5usadmin\Msapps\Msinfo		
msinfo.exe			40960
\Xl5usadmin\Msapps\Msquery		
cuecard2.dll			1655
customer.dbf			13364
customer.mdx			4096
employee.dbf			4582
employee.mdx			4096
msquery.cue			209228
msquery.exe			622656
msquery.hlp			437165
orddtail.dbf			1754
orddtail.mdx			4096
orders.dbf			7885
orders.mdx			4096
product.dbf			5729
product.mdx			4096
qryintl.dll			35391
supplier.dbf			6621
supplier.mdx			4096
\Xl5usadmin\Msapps\Proof		
mssp_am.lex			176839
mssp_br.lex			176298
msspell.dll			86016

Total size of files installed with Excel Admin:	25864908



NETWORK INSTALL: WORKSTATION		
Assumes that MSAPPS are installed on local drive		
\Excel\Setup
setup.stf			172653
\Windows
ccard200.exe			127424
excel5.ini			1492
msquery.ini			116
odbc.ini			695
odbcinst.ini			645
odbcisam.ini			129
\Windows\Msapps\Grphflt		
cgmimp.flt			44912
epsimp.flt			71984
hpglimp.flt			215376
iffpcx.dll			10640
ifftiff.dll			32624
pcximp.flt			11728
tiffimp.flt			11728
wmfimp.flt			5104
\Windows\Msapps\Msinfo		
msinfo.exe			40960
\Windows\Msapps\Msquery		
cuecard2.dll			1655
customer.dbf			13364
customer.mdx			4096
employee.dbf			4582
employee.mdx			4096
msquery.cue			209228
msquery.exe			622592
msquery.hlp			437165
orddtail.dbf			1754
orddtail.mdx			4096
orders.dbf			7885
orders.mdx			4096
product.dbf			5729
product.mdx			4096
qryintl.dll			35391
supplier.dbf			6621
supplier.mdx			4096
\Windows\Msapps\Proof		
mssp_am.lex			176839
mssp_br.lex			176298
msspell.dll			86016
\Windows\System		
ccapi200.dll			46400
commtb.dll			40784
compobj.dll			102400
ctl3d.dll			21008
ctl3dv2.dll			21648
dbnmp3.dll			10704
ddeml.dll			39424
drvaccss.hlp			50469
drvdbase.hlp			54455
drvfox.hlp			55004
drvpardx.hlp			54540
drvssrvr.hlp			87839
mapivim.dll			62096
msffile.dll			177840
msjetdsp.dll			85792
mstoolbr.dll			9200
odbc.dll			49584
odbcadm.exe			6496
odbcinst.dll			82704
odbcinst.hlp			17412
ole2.dll			313344
ole2.reg			24606
ole2conv.dll			57328
ole2disp.dll			98336
ole2nls.dll			147568
ole2prox.dll			55808
pdx110.dll			189168
red110.dll			238416
scp.dll				11920
sdm.dll				102032
shareres.dll			37888
simadmin.dll			160080
simba.dll			469904
sqlsrvr.dll			155776
stdole.tlb			4322
storage.dll			157184
typelib.dll			153312
vba.dll				820064
vbaen.dll			9360
vbaen.olb			31060
xbs110.dll			263840
xlcall.dll			1600

Maximum size of files installed on Workstation:		7136620
Size of files installed to \Windows\msapps:		2254751
Total size of files installed without MSAPPS:		4881869
