Introduction
Introduction    1 of 1

There are two ways to install the Microsoft Works for Windows 95 software:

Install from the floppy disks.

Install from a network server location that contains all the Microsoft Works software.

This file describes installing and using Microsoft Works from a network server location by explaining how to create that server location, then giving an overview of how users will install Microsoft Works from the server.

See Also

Table of Contents


Licensing
How to use Microsoft Works on a network    1 of 6

Each user must have a Microsoft Works for Windows 95 license, no matter how your users install Works. One license is provided with each retail package of Microsoft Works, with the full text of the license printed on the package that contains the Microsoft Works disks.

If you don't want to purchase a complete copy of Microsoft Works for every user, you can purchase a License Pak or a concurrent license. A License Pak allows one additional user to access the Microsoft Works program files. You don't need to store extra copies of Microsoft Works or the documentation, and it's less expensive than purchasing a retail package of Microsoft Works.

If you are running Microsoft Works from a network and can track the number of users on the system, you can purchase a concurrent license. With a concurrent license, you pay only for the number of users using Microsoft Works at one time. For more information on licensing, contact any dealer that handles Microsoft products.

See Also

Sharing Microsoft Works program files

Sharing Microsoft Works data files

Rules for opening shared documents

To open a shared document

Sharing templates


Sharing Microsoft Works program files
How to use Microsoft Works on a network    2 of 6

Network users can share the Microsoft Works for Windows 95 program and documents created in Microsoft Works. Before you install Microsoft Works on a network, you must decide which type of network installation best suits your needs. There are several ways to run Microsoft Works in a network environment:

You can run Microsoft Works entirely off the network server without installing the program files locally on your own computer or network user's directory.

You can install Microsoft Works [image] in its entirety [image] on your own computer or network users directory.

You can install the Microsoft Works program files on your own computer and run the shared components from the network file server.

It is important to remember that any installation of Microsoft Works on a network is a two-step process:

1.	You must first create the administrative installation point by running SETUP.EXE from the diskettes/CD-ROM, using the /a command line option. You perform just one administrative setup to create the administrative installation point.

2.	Next, you perform the client installation from the administrative installation point to install the necessary Microsoft Works files on the users computer.

To perform a client installation, users run SETUP.EXE from the administrative installation point without the /a command-line option. You perform a client setup for every user who wants to install Microsoft Works on his or her own computer. During the client installation, you decide whether you will share Microsoft Works from the file server or install it on the users computer.

See Also

Licensing

Sharing Microsoft Works data files

Rules for opening shared documents

To open a shared document

Sharing templates


administrative installation point

The set of directories that will hold all the Microsoft Works software and from which client installations will be run.


/a command line option

The /a switch after the command name setup.exe indicates an administrator's installation. At the Open line of the Run option in the Start menu, type <drive letter>:\setup /a and then press ENTER.


Sharing Microsoft Works data files
How to use Microsoft Works on a network    3 of 6

There may be times when you want to open a document someone else is working on, or let others open documents you are working on. A shared document always resides on the network server or shared directory and can be opened by more than one person at a time. Shared documents can be documents that several people have created together or that several people use on a regular basis. For example, a copy of the company personnel manual can be a shared document on a network server.

A shared document can be opened one of two ways. You can:

Open the document but not be able to change the document. A document opened like this is called "read-only."

Open a document and make changes. A document opened like this is called "read-write."

How one user opens a shared document determines how another user can open the same document. To protect documents, only one user at a time can open a document as read-write. This prevents more than one person from making changes to the document while both have it open.

See Also

Licensing

Sharing Microsoft Works program files

Rules for opening shared documents

To open a shared document

Sharing templates


Rules for opening shared documents
How to use Microsoft Works on a network    4 of 6

Each Microsoft Works tool has specific rules for opening shared documents on a network. Listed below are the options each tool provides for one user or simultaneous users of the document.

Tools	Opened as	Available simultaneously to others as
Word Processor	Read-only	Read-only
	Read-write	Not available to others
Spreadsheet	Read-only or read-write	Read-only
	Read-write	Read-only
Database	Read-only	Read-only
	Read-write	Not available to others
Communications	Read-only or read-write	Read-only
	Read-write	Read-only

See Also

Licensing

Sharing Microsoft Works program files

Sharing Microsoft Works data files

To open a shared document

Sharing templates


To open a shared document
How to use Microsoft Works on a network    5 of 6

1.	Make sure the network connection to the server is functioning.

2.	If necessary, start Windows, and then start Microsoft Works.

3.	In the Microsoft Works Task Launcher, click the Existing Documents tab.

4.	In the list of files, click the file that you want to open, and then click the OK button.

If necessary, click the Open A Document Not Listed Here button and change the directory or drive, or change the type of files listed to locate the file you want to open.

If you do not want to make changes to a document you open, click the Open As Read-Only option.

5.	Once you have located the file, click the Open button.

See Also

Licensing

Sharing Microsoft Works program files

Sharing Microsoft Works data files

Rules for opening shared documents

Sharing templates


Sharing templates
How to use Microsoft Works on a network    6 of 6

Templates are documents that contain information and settings that you can reuse. Creating a new document from a template gives you a head start over creating a new document from scratch. If Microsoft Works is installed on a network, templates created by one user can be used by other users if the template is placed in a shared Templates directory on the server.

When you create and save a template, it is saved to the Templates directory on your local hard disk. If you want to share that template with other users on the network, you must copy that template file to the Templates directory on the server. This shared Templates directory is located in the directory that Microsoft Works was installed to.

For example, if you create a template called MYTEMP.WPS and you want all other users on the network to have access to that template, copy MYTEMP.WPS to the shared Templates directory on the server. If the server location for the Microsoft Works program files is F:\MSWORKS, then copy MYTEMP.WPS to the F:\MSWORKS\TEMPLATES directory.

See Also

Licensing

Sharing Microsoft Works program files

Sharing Microsoft Works data files

Rules for opening shared documents

To open a shared document


Knowing your Windows installation
Knowing your Windows installation    1 of 1

It is important to know whether you have a local or shared installation of Windows 95. This will determine where the shared components and system files that are installed by Microsoft Works will be located.

Local Windows installation

If Windows is installed locally, then the entire operating system is located on the hard disk of the workstation. Any Windows system files installed by Microsoft Works are placed on the local hard disk even if you are performing a shared installation of Microsoft Works.

Shared Windows installation

If you are running a shared installation of Windows, most or all of the Windows program files reside on a server instead of the local workstation. In this case, the Windows system files installed by Microsoft Works are placed on the server, and the workstations will access those files from the server.

See Also

Table of Contents


Network installation requirements
Network installation requirements    1 of 3

To install Microsoft Works for Windows 95 on your network you must select one computer to be the workstation and a different computer to be the server or specify your dedicated file server. Click the topics below to see the specific requirements for each type of computer.

See Also

Workstation requirements

Server requirements


Workstation requirements
Network installation requirements    2 of 3

Operating system

You must be running Windows 95 or Windows NT 3.51 or later on the workstations you will be using to run and install Microsoft Works for Windows 95.

Disk space

To perform a workstation installation in which you share the Microsoft Works program files from the server, you need 1 MB of disk space on the workstation.

To perform a complete installation in which all the files are installed locally onto the workstation, you need 25 MB of disk space on the workstation.

To perform a workstation installation in which you install the Microsoft Works program files locally and run the shared components (accessories) from the server, you need 20 MB of disk space on the workstation.

Video

A VGA video adapter is required (SVGA 256-color recommended).

RAM

To run Microsoft Works using Windows 95, you need a minimum of 6 MB of memory; 8 MB is recommended for better performance.

Network must be functional

Your network must be functional and operating properly before you attempt to install a network installation of Microsoft Works.

Turn off anti-virus software during Setup

Before running the Setup program for Microsoft Works you should turn off any virus detection software that is running on either the server or the workstation. Anti-virus software can interfere with the Setup program and prevent system files from being modified properly.

See Also

Server requirements

Network installation requirements


Server requirements
Network installation requirements    3 of 3

Disk space

You need 30 MB of available disk space on the server.

Access privileges

Local install of Windows 95

You need read, write, delete, and create permissions for the server directory on which you are installing Microsoft Works for Windows 95.

Users need read access to the server share(s) you create for main and shared application files.

Either before or after performing the administrative installation, share the directory that will contain the Microsoft Works application files and the directory that will contain the shared components.

Directories must be locked to network user access during the administrative installation.

Shared install of Windows 95

In addition to the above requirements for a local installation of Windows 95, if you are performing a network installation of Microsoft Works using a shared copy of Windows 95, you must ensure that:

Users sharing applications or running a shared copy of Windows 95 from this server are logged off.

You are running the administrative setup while logged onto the same shared Windows environment.

You have write and create permissions to the shared Windows 95 directories.

Installation Location

When installing Microsoft Works onto the server, you must choose an empty directory as your destination. If you are installing to a directory on the server where you had a previous version of Microsoft Works installed, you must remove all of the files from that directory before installing Microsoft Works, or choose another directory for Microsoft Works.

See Also

Workstation requirements

Network installation requirements


Installing Works on your network
Installing Microsoft Works on your network
Installing Works on your network    1 of 4

Step 1:  Install Microsoft Works on your network server

You will be using the workstation to run the setup administration process from the diskettes. This process will copy the shared Microsoft Works for Windows 95 program files to a designated place on your file server. Workstations will then be able to run setup from this shared location, which is covered in Step 2.

To install Microsoft Works on a network server or shared directory

Step 2:  Install Microsoft Works on individual workstations

You will be using the shared setup which was created during Step 1 to install Microsoft Works for use on each workstation. This process will need to be repeated for each workstation on your network.

To install Microsoft Works on workstations

You can also run the client installation of Setup "silently" and perform a complete installation automatically without any additional input from the user by running Setup in batch mode.

Using batch mode to speed up workstation installations

See Also

Network installation requirements

Server requirements

Workstation requirements


To install Works on a network server or shared directory
To install Microsoft Works on a network server or shared directory
Installing Microsoft Works on your network    2 of 4

This is step 1 in a process that will copy the shared Microsoft Works for Windows 95 program files to a designated place on your file server. Once completed, workstations will be able to run setup from this shared location; that topic is covered in step 2.

1.	Ask all users who are sharing Windows or Microsoft applications to disconnect from the network file server or shared directory.

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

3.	Insert the Microsoft Works for Windows 95 Setup Disk 1 in drive A or drive B.

4.	If you are using Microsoft Windows 95, click Run on the Start menu. If you are using Microsoft Windows NT, choose Run from the File menu in either Program Manager or File Manager.

5.	Type <drive letter>:\setup /a and then press ENTER. (The /a switch indicates an administrator's installation.)

For example, if you are using drive B, type B:\setup /a

Note that double-clicking the SETUP.EXE filename in File Manager (Windows NT) or Explorer (Windows 95) will not perform an administrative installation. You must use the Run command in the File menu of File Manager or Program Manager (Windows NT), or the Run command in the Start menu (Windows 95) with the /a command line option.

6.	Setup asks you for an organization name. When users perform workstation installations from this installation point, the client Setup program asks them only for their user name, but it uses the organization name you type here as the organization name for each user.

7.	In Setup, verify the product identification number.

8.	In Setup, specify the directory on the server where you want to install the main application files.

9.	In Setup, specify the directory where you want to install the shared components. The shared components are accessories that are used with Microsoft Works and can be used by other Windows applications. The shared components included with Microsoft Works are:

ClipArt Gallery	System information

WordArt	Proofing tools

Equation Editor	Graphics filters

Draw	Text converters

Note-It

10.	Setup attempts to detect the network path for the shared components directory. This part of the setup allows you to specify how network users will connect to the shared components directory.

If your network supports the use of UNC paths of the form \\server\share, you can specify the network location of the shared components using the UNC path. For example, if you are installing shared components onto c:\msapps on server SERVER1 and you share that directory as "msapps", then specify here

Network Server:	\\SERVER1\msapps	Network Path:	<blank>

and click the Server Name option to indicate that the shared components directory will be accessed using the UNC path.

Or, if you are installing onto c:\msWORKS\msapps and are sharing the c:\MSWORKS directory, then specify here:

Network Server:	\\SERVER1\MSWORKS	Network Path:	\msapps

and click the Server Name option to indicate that the shared components directory will be accessed using the UNC path.

If your network does not support UNC, you can specify the network location of the shared components using a logical drive letter. For example, if you are installing the shared components onto c:\msapps on the server SERVER1, with the directory shared as "MSAPPS" and you will always have drive G mapped to the MSAPPS directory on SERVER1, then specify here:

Network Server:	<blank>	Network Path:	<blank>	Drive:	G:

and click the Drive Letter option to indicate that the shared components directory will be accessed using a logical drive letter instead of the UNC path.

11.	Setup will ask how the shared components will be installed by the end user; this determines whether the user will have the choice of installing the shared components locally or running them off the server. The options are:

Server - Shared components are run from the server and users do not have a choice during the client installation.

Local hard disk - Shared components are put on the users hard disk and users do not have a choice during the client installation.

Users choice - Users are asked during the client installation whether they want to run the shared components from the server or install them on their hard disk.

12.	Setup checks for available disk space on the server and then copies all the files from the floppy disks to the administrative installation point.

If you are running a shared copy of Windows, some system files are also be copied to the Windows System directory so that all workstations that use the shared copy of Windows have access to the necessary system files.

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

See Also

To install Microsoft Works on workstations

Files installed on your network server

Files installed on workstations


To install Works on workstations
To install Microsoft Works on workstations
Installing Microsoft Works on your network    3 of 4

This is Step 2 in the installation. You will use the shared setup that was created in Step 1To install Microsoft Works on a network server or shared directory. This process should be repeated for each workstation on your network.

1.	If you are using Microsoft Windows 95, click Run from the Start menu. If you are using Microsoft Windows NT, choose Run from the File menu in either Program Manager or File Manager.

2.	In the Open box (Windows 95) or the Command Line box (Windows NT) type the drive and the complete path name of the directory where Microsoft Works was installed on the server, followed by \setup.

If your network supports UNC paths of the form \\server\share, you can use a path instead of a logical drive letter.

For example, if you are using a logical drive letter and you have mapped drive F to \\SERVER1\MSWORKS, type F:\setup

If you are using UNC paths, type \\SERVER1\MSWORKS\SETUP

3.	Setup asks for the users name (the organization name was defined when you created the administrative installation point).

4.	In Setup, verify the Product Identification Number.

5.	Setup asks for the destination directory for Microsoft Works; the directory you specify here can be on the users local hard disk, or it can be a network drive on which the user has read, write, create, and delete privileges.

Note: Even if the software will not be installed locally, Setup still creates a small directory that contains some specific files for Microsoft Works.

6.	When you created the administrative installation point, if you elected to allow the user to choose where shared components are installed ("User's Choice" option), the client Setup displays the following options for the user:

Server - Setup configures the users system to point to the server share you defined during administrative installation (the server location of the MSAPPS directory); the shared components will be accessed over the network.

Local hard disk - Setup copies the shared component files to the \WINDOWS\MSAPPS directory on the user's local hard disk.

7.	Setup asks for one of three installation types:

Complete installation - All options and components of Microsoft Works are installed to the users local hard disk or network drive.

Custom installation - Setup displays a series of lists that allow the user to choose which components are to be installed to the user's local drive or network drive.

Workstation installation - The main Microsoft Works application files are left on the server to be executed over the network.

If the user chooses Custom Installation, Setup displays a series of lists so the user can choose which components to instal. The first list contains the main Microsoft Works components:

Program files

Wizard files

Help files

Introduction to Microsoft Works 4.0

Setup files

Clip art files

Proofing Tools

Accessories

Text converters

Graphic filters

For Proofing tools, Accessories, Text converters, and Graphic filters, the user can select the Change Option button to view the list of sub-options within the component. For example, selecting Proofing tools and clicking the Change Option button displays the list:

Spell Checker

Thesaurus

Hyphenation

For each option displayed in the list, a check mark next to the option indicates that the option will be installed; no check mark indicates that the option will not be installed.

8.	Once the user chooses the installation type and options (if required), Setup starts copying files.

See Also

To install Microsoft Works on a network server or shared directory

Files installed on workstations

Files installed on your network server

Using batch mode to speed up workstation installations


Using batch mode to speed up workstation installations
Installing Microsoft Works on your network    4 of 4

By running Setup in batch mode, you can run the client installation of Setup "silently" and perform a complete installation automatically without any additional input from the user.

1.	If you are using Microsoft Windows 95, click Run from the Start menu. If you are using Microsoft Windows NT, choose Run from the File menu in either Program Manager or File Manager.

2.	In the Open box (Windows 95) or the Command Line box (Windows NT), type the drive and the complete path name of the directory where Microsoft Works was installed on the server, followed by \setup /q.

If your network supports UNC paths of the form \\server\share, you can use a path instead of a logical drive letter.

When you use this switch, Setup installs Microsoft Works in the default program directory C:\MSWORKS without prompting the user for information. If you want to specify a user's name, you can use the /n switch followed by the users name.

For example, suppose you installed Microsoft Works in the MSWORKS directory of a file server [image] and you have mapped drive X to the file server [image] and you want to perform a complete installation of Microsoft Works for a user named Paul Tanner. The command line would be x:\msworks\setup.exe /n Paul Tanner /q

See Also

Network installation requirements

To install Microsoft Works on a network server or shared directory

To install Microsoft Works on workstations


Shared components and system files
Troubleshooting    1 of 4

Shared components installed to wrong location

There are a few special cases in the way shared components are installed during a workstation installation:

If client Setup finds a local copy of shared components already installed on the user's computer (it checks the registry), Setup will update the local installation of the shared components with the new versions, regardless of whether you or the user requested that the shared components be accessed over the network.

To avoid this situation, run Setup for the application that installed the shared components initially and remove these components from the users system.

If the combined UNC path defined for the shared components, including the server share and directory, is greater than 63 characters (beyond the legal limit for a UNC path), then Setup will attempt to map a drive letter to the server share.

To avoid this situation, be sure that the combined UNC path to the shared components is less than 63 characters.

If Setup is unable to use the defined UNC path to access the server (or if the drive letter connection fails, see above), Setup will install the shared components locally to ensure they can be accessed. The UNC path could fail for a number of reasons, including the share being down; the user's network software does not recognize UNC paths, or the user does not have access to the share, and so on.

To avoid this situation, ensure that your users have access to the shared components server share; if your network does not recognize UNC paths, then see To install Microsoft Works on a network server or shared directory to learn how to define a drive letter instead of a UNC path for shared components.

System files installed locally on workstations with shared Windows 95

The client Setup will install some system DLLs to the users local Windows 95 directory if, during client installation, Setup is unable to locate the DLLs in the shared Windows directory. This could happen for the following reasons:

The administrative installation was not performed under the same shared Windows installation.

You didn't have full rights to the shared Windows 95 directory on the server.

During administrative installation another user was also running the shared installation of Windows 95.

To avoid this problem, be sure you are performing the administrative installation under the same shared copy of Windows that your users are using. You must have read, write, create, and delete permissions in the Windows and Windows System directories, and all users must be logged off the server while you are installing.

See Also

Extracting files manually

Files installed on your network server

Files installed on workstations


UNC

universal naming convention


Extracting files manually
Troubleshooting     2 of 4

With the exception of the Setup disk (Disk 1), the Microsoft Works for Windows 95 diskettes 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.

WARNING

Because DMF is a new format, many existing utilities such as Norton Disk Doctor, Microsoft ScanDisk, MS-DOS DiskCopy, and Microsoft Windows Copy Disk do not recognize DMF. You should not use disk utilities to examine a DMF formatted disk, as these utilities can corrupt the DMF disk. You cannot copy DMF formatted disks using MS-DOS DiskCopy or Microsoft Windows Copy Disk.

Using EXTRACT.EXE

To copy the Microsoft Works disks onto a network server or other permanent storage drive, you can use the copy switch (/c) with the EXTRACT.EXE utility to copy the Microsoft Works installation files to the target location. A copy of EXTRACT.EXE is in the C:\WINDOWS\COMMAND directory on any computer that has Windows 95 installed.

1.	Create a directory called C:\DISKS on your hard disk, and then create a subdirectory for each disk called C:\DISKS\DISK1, C:\DISKS\DISK2, and so on.

2.	Copy all the files on Disk 1 to the C:\DISKS\DISK1 directory. (Since Disk 1 does not use DMF, you can use the standard MS-DOS Copy command, COPY A:\*.* C:\DISKS\DISK1.)

3.	Copy the EXTRACT.EXE utility from the C:\WINDOWS\COMMAND directory to the C:\DISKS directory.

4.	From the C:\DISKS directory, type the following command to copy Disk 2 to the C:\DISKS\DISK2 directory:

EXTRACT /C A:\MSWORKS2.CAB C:\DISKS\DISK2

5.	Repeat step 4 for each of the remaining disks, substituting the appropriate disk number for the cabinet file name and the disk directory name.

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 can 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

This replaces the cabinet filename with the name of your specific cabinet file.

To list all the files in a cabinet file that have an EXE extension:

EXTRACT /D A:\cabinet filename *.EXE

This replaces the cabinet filename with the name of your specific cabinet file.

Here are some examples of how to use EXTRACT.EXE to copy a single file out of a cabinet file.

To extract a file named SAMPLE.EXE from a cabinet file called FILES.CAB to the current directory:

EXTRACT A:\FILES.CAB SAMPLE.EXE

To extract a file named SAMPLE.EXE to C:\MSWORKS:

EXTRACT A:\FILES.CAB /L C:\MSWORKS SAMPLE.EXE

See Also

Shared components and system files

Files installed on your network server

Files installed in workstations


Files installed to your network server
Files installed on your network server
Troubleshooting     3 of 4

The following are locations and names of files installed during an administrative installation of Microsoft Works for Windows 95. For this example, the administrative installation point was created using F:\MSWORKS as the shared directory for the main Microsoft Works components and F:\MSAPPS was the shared directory for the shared components.

See Also

Shared components and system files

Extracting files manually

Files installed on workstations

Directory: F:\MSWORKS

ACCTREC.TZ3	ACMSETUP.HLP

ACMSETUP.GID	ADDBOOK1.PRV

ADDBOOK2.PRV	ANSI.TRD

AWARD.TZ3	BIBLIO.TZ3

BID.TZ3	BROCHURE.TZ3

BUSINV.TZ3	COMPLINC.DLL

FAX.TZ3	FLYER.TZ3

FNDWORKS.FND	GRADEBK.TZ3

HOMEINV.TZ3	HYPH32.DLL

HY_EN.LEX	IMPACT.TTF

INVOICE.TZ3	KERMIT.FTD

LAUNCH.DAT	MEMO.TZ3

MLETTER.PRV	MORTGAGE.TZ3

MRESUME.PRV	MSSETUP.DLL

MSTATMNT.PRV	MSWIZL3.TWZ

MSWKSINT.EXE	MSWORKS.EXE

MSWORKS.TWZ	MSWORKS.QKT

MSWORKS.WPS	MSWORKS.WKS

MSWORKS.WDB	MSWORKS.WCM

MSWORKS.M14	MSWORKS4.REG

MSWORKS4.INF	MVBK14N.DLL

MVCL14N.DLL	MVFS14N.DLL

MVIX14N.DLL	MVMC14N.DLL

MVMG14N.DLL	MVSR14N.DLL

MVTL14N.DLL	MVUT14N.DLL

NETWORK.HLP	NEWSLTTR.TZ3

ORDERFRM.TZ3	PHONE.TZ3

PREVIEW.VBX	PRICELST.TZ3

PROPFORM.TZ3	PSS.GID

PSS.HLP	QUOTE.TZ3

README.HLP	REPORT.TZ3

SCHEDULE.TZ3	SCRATCH.PRV

SETUP.EXE	SETUP.INI

SETUP.STF	SSALL.BIN

STCLB.TZ3	TESTS.TZ3

THREED.VBX	TIMESHEE.TZ3

VBRUN300.DLL	VT100.TRD

VT220.TRD	VT52.TRD

WKS4CHID.HLP	WKSGRPH.VBX

WKSLANG.DLL	WKSMSNFM.MCC

WKSOLE32.DLL	WKSPAGES.VBX

WORKS_BB.DLL	WPALL.BIN

WZ3DLL.DLL	WZ3DLL16.DLL

XMODEM.FTD	YMODEM.FTD

ZMODEM.FTD

Directory: F:\MSWORKS\CLIPART

2PALMTRS.WMF	3ARROWS.WMF

3DSKYLN.WMF	525DISK.WMF

ANIDEA.WMF	ANNOUNCE.WMF

ANTIQUE.WMF	APPLE.WMF

AROWTAIL.WMF	ATOM.WMF

ATTHETOP.WMF	BALLOON.WMF

BASEBALL.WMF	BIGTREE.WMF

BILLS.WMF	BOOKS.WMF

BSKTBALL.WMF	BTTLSHIP.WMF

CADUCEUS.WMF	CALCULTR.WMF

CHAMPGNE.WMF	CHECKMRK.WMF

CLIMBER.WMF	CNSTRUCT.WMF

COFFEE.WMF	COINS.WMF

CONVNSTR.WMF	CROWD.WMF

CTYBLOCK.WMF	DAFFODIL.WMF

DARTS.WMF	DEMANDNG.WMF

DISKETTE.WMF	DISKSTAK.WMF

DOCTOR.WMF	EXPLAIN.WMF

FOOTBALL.WMF	GENCOINS.WMF

GHOST1.WMF	GHOST2.WMF

GHOST3.WMF	GHOST4.WMF

GIFTS.WMF	GOLFER.WMF

GRAPES.WMF	HNDSHAKE.WMF

LECTURE.WMF	MANCOMP.WMF

MANDESK.WMF	MANHATS.WMF

MANPHONE.WMF	MAPMEN.WMF

MOLSTRUC.WMF	MONYHNGY.WMF

MSWORKS4.CAG	MUSIC.WMF

NAMERICA.WMF	NOTEBOOK.WMF

OFFICBLD.WMF	ORBIT.WMF

PALMTREE.WMF	PC.WMF

PCDUCK.WMF	PCMOUSE.WMF

PCSHOW.WMF	PEOPLE.WMF

PERSUADE.WMF	PHNCORD.WMF

PLANE.WMF	POINTING.WMF

PRESENT2.WMF	PRESENT4.WMF

PROFESSR.WMF	RESHOUSE.WMF

RIBBON.WMF	RUNNER.WMF

SEDAN.WMF	SEMINAR.WMF

SHOPCART.WMF	SKIING.WMF

SOCCER.WMF	SOCRBALL.WMF

SPHERE.WMF	SPLASH.WMF

SPRTSCAR.WMF	STOREFRT.WMF

SUNFLOWR.WMF	SUPPLIES.WMF

SWAMPED.WMF	TALKING.WMF

TAXI.WMF	TELPHONE.WMF

TENNIS.WMF	TRAIN.WMF

TROPHY.WMF	TSTTUBES.WMF

TULIPS.WMF	USMAP.WMF

USSTATES.WMF	VAN.WMF

VICTRIAN.WMF	VOLLEYBL.WMF

WOMNCOMP.WMF	WOMSHAKE.WMF

WORLD.WMF	WORRIED.WMF

WRLDEAST.WMF	WRLDWEST.WMF

Directory: F:\MSWORKS\CONVERT

DZSDM.DLL	PICT2WMF.DLL

WK30DB.DLL	WK30WP.DLL

WK40DB.DLL	WK40SS.DLL

WK40WP.DLL	WKSS.DLL

WMF2PICT.DLL	WORKSXM.DLL

WWKDB3.DLL	WWKSS3.DLL

WWRK30WP.DLL

Directory: F:\MSWORKS\SHARED

16COLORS.PAL	17GRAYS.PAL

47COLORS.PAL	86COLORS.PAL

ARTGALRY.EXE	ARTGALRY.REG

ARTGALRY.HLP	ARTGALRY.CNT

ARTGALRY.GID	BMPIMP32.FLT

CGMIMP32.FLT	DOSWRD32.CNV

EPSIMP32.FLT	EQNEDT32.HLP

EQNEDT32.REG	EQNEDT32.EXE

EQNEDT32.CNT	EQNEDT32.GID

EQNEDT32.FTS	IMGWALK.DLL

MFCANS32.DLL	MSBMP32.DLL

MSDRAW.EXE	MSDRAW.REG

MSDRAW.HLP	MSDRAW.CNT

MSDRAW.GID	MSINF16H.EXE

MSINFO32.EXE	MSINFO32.HLP

MSINFO32.GID	MSINFO32.CNT

MSPCD32.DLL	MSPCX32.DLL

MSSP232.DLL	MSSP2_EN.LEX

MSTH32.DLL	MSTH_AM.LEX

MSTIFF32.DLL	MSWRD632.CNV

MTEXTRA.TTF	NOTE-IT.EXE

NOTE-IT.REG	NOTE-IT.HLP

NOTE-IT.GID	PCDIMP32.FLT

PCDLIB32.DLL	PCXIMP32.FLT

PICSTORE.DLL	PUBDLG.DLL

PUBOLE32.DLL	QARTGLRY.HLP

QARTGLRY.FTS	QWRDRT32.HLP

QWRDRT32.FTS	TIFFIM32.FLT

WMFIMP32.FLT	WNWRD232.CNV

WORKS432.CNV	WPFT532.CNV

WPFT632.CNV	WPGEXP32.FLT

WPGIMP32.FLT	WRDART32.EXE

WRDART32.REG	WRDART32.HLP

WRDART32.CNT	WRDART32.GID

WRDART32.FTS	WRITE32.CNV

Directory: F:\MSWORKS\SYSTEM

ARIALNB.TTF	ARIALNBI.TTF

ARNAR.TTF	ARNARI.TTF

CTL3D32.DLL	E95THK16.EXE

ENCAPI32.DLL	IMPACT.TTF

MISTRAL.TTF	MSVCRT20.DLL

WINGDNG2.TTF

Directory: F:\MSAPPS\ARTGALRY

ARTGALRY.EXE	ARTGALRY.REG

ARTGALRY.HLP	ARTGALRY.CNT

ARTGALRY.GID	QARTGLRY.HLP

QARTGLRY.FTS

Directory: F:\MSAPPS\EQUATION

EQNEDT32.HLP	EQNEDT32.REG

EQNEDT32.EXE	EQNEDT32.CNT

EQNEDT32.GID	EQNEDT32.FTS

Directory: F:\MSAPPS\GRPHFLT

BMPIMP32.FLT	CGMIMP32.FLT

EPSIMP32.FLT	MSBMP32.DLL

MSPCD32.DLL	MSPCX32.DLL

MSTIFF32.DLL	PCDIMP32.FLT

PCXIMP32.FLT	TIFFIM32.FLT

WMFIMP32.FLT	WPGEXP32.FLT

WPGIMP32.FLT

Directory: F:\MSAPPS\MSDRAW

MSDRAW.EXE	MSDRAW.REG

MSDRAW.HLP	MSDRAW.CNT

MSDRAW.GID

Directory: F:\MSAPPS\MSINFO

IMGWALK.DLL	MSINF16H.EXE

MSINFO32.EXE	MSINFO32.HLP

MSINFO32.GID	MSINFO32.CNT

Directory: F:\MSAPPS\NOTE-IT

NOTE-IT.EXE	NOTE-IT.REG

NOTE-IT.HLP	NOTE-IT.GID

Directory: F:\MSAPPS\PROOF

MSSP232.DLL	MSSP2_EN.LEX

MSTH32.DLL	MSTH_AM.LEX

Directory: F:\MSAPPS\TEXTCONV

DOSWRD32.CNV	MSWRD632.CNV

WNWRD232.CNV	WORKS432.CNV

WPFT532.CNV	WPFT632.CNV

WRITE32.CNV

Directory: F:\MSAPPS\WORDART

QWRDRT32.HLP	QWRDRT32.FTS

WRDART32.EXE	WRDART32.REG

WRDART32.HLP	WRDART32.CNT

WRDART32.GID	WRDART32.FTS


Files installed to workstations
Files installed on workstations
Troubleshooting     4 of 4

The following are locations and names of files installed during a complete client installation of Microsoft Works for Windows 95 with all files installed to the user's local hard disk. For this example, the program was installed into the C:\MSWORKS directory.

See Also

Shared components and system files

Extracting files manually

Files installed on your network server

Directory: C:\MSWORKS

ACCTREC.TZ3	ADDBOOK1.PRV

ADDBOOK2.PRV	ANSI.TRD

AWARD.TZ3	BIBLIO.TZ3

BID.TZ3	BROCHURE.TZ3

BUSINV.TZ3	COMPLINC.DLL

FAX.TZ3	FLYER.TZ3

FNDWORKS.FND	GRADEBK.TZ3

HOMEINV.TZ3	HYPH32.DLL

HY_EN.LEX	INVOICE.TZ3

KERMIT.FTD	LAUNCH.DAT

MEMO.TZ3	MLETTER.PRV

MORTGAGE.TZ3	MRESUME.PRV

MSTATMNT.PRV	MSWIZL3.TWZ

MSWKSINT.EXE	MSWORKS.EXE

MSWORKS.TWZ	MSWORKS.M14

MSWORKS.QKT	MSWORKS4.REG

MVBK14N.DLL	MVCL14N.DLL

MVFS14N.DLL	MVIX14N.DLL

MVMC14N.DLL	MVMG14N.DLL

MVSR14N.DLL	MVTL14N.DLL

MVUT14N.DLL	NEWSLTTR.TZ3

ORDERFRM.TZ3	PHONE.TZ3

PREVIEW.VBX	PRICELST.TZ3

PROPFORM.TZ3	PSS.GID

PSS.HLP	QUOTE.TZ3

README.HLP	REPORT.TZ3

SCHEDULE.TZ3	SCRATCH.PRV

SSALL.BIN	STCLB.TZ3

TESTS.TZ3	THREED.VBX

TIMESHEE.TZ3	VBRUN300.DLL

VT100.TRD	VT220.TRD

VT52.TRD	WKS4CHID.HLP

WKSGRPH.VBX	WKSLANG.DLL

WKSMSNFM.MCC	WKSOLE32.DLL

WKSPAGES.VBX	WPALL.BIN

WZ3DLL.DLL	WZ3DLL16.DLL

XMODEM.FTD	YMODEM.FTD

ZMODEM.FTD

Directory: C:\MSWORKS\CLIPART

2PALMTRS.WMF	3ARROWS.WMF

3DSKYLN.WMF	525DISK.WMF

ANIDEA.WMF	ANNOUNCE.WMF

ANTIQUE.WMF	APPLE.WMF

AROWTAIL.WMF	ATOM.WMF

ATTHETOP.WMF	BALLOON.WMF

BASEBALL.WMF	BIGTREE.WMF

BILLS.WMF	BOOKS.WMF

BSKTBALL.WMF	BTTLSHIP.WMF

CADUCEUS.WMF	CALCULTR.WMF

CHAMPGNE.WMF	CHECKMRK.WMF

CLIMBER.WMF	CNSTRUCT.WMF

COFFEE.WMF	COINS.WMF

CONVNSTR.WMF	CROWD.WMF

CTYBLOCK.WMF	DAFFODIL.WMF

DARTS.WMF	DEMANDNG.WMF

DISKETTE.WMF	DISKSTAK.WMF

DOCTOR.WMF	EXPLAIN.WMF

FOOTBALL.WMF	GENCOINS.WMF

GHOST1.WMF	GHOST2.WMF

GHOST3.WMF	GHOST4.WMF

GIFTS.WMF	GOLFER.WMF

GRAPES.WMF	HNDSHAKE.WMF

LECTURE.WMF	MANCOMP.WMF

MANDESK.WMF	MANHATS.WMF

MANPHONE.WMF	MAPMEN.WMF

MOLSTRUC.WMF	MONYHNGY.WMF

MSWORKS4.CAG	MUSIC.WMF

NAMERICA.WMF	NOTEBOOK.WMF

OFFICBLD.WMF	ORBIT.WMF

PALMTREE.WMF	PC.WMF

PCDUCK.WMF	PCMOUSE.WMF

PCSHOW.WMF	PEOPLE.WMF

PERSUADE.WMF	PHNCORD.WMF

PLANE.WMF	POINTING.WMF

PRESENT2.WMF	PRESENT4.WMF

PROFESSR.WMF	RESHOUSE.WMF

RIBBON.WMF	RUNNER.WMF

SEDAN.WMF	SEMINAR.WMF

SHOPCART.WMF	SKIING.WMF

SOCCER.WMF	SOCRBALL.WMF

SPHERE.WMF	SPLASH.WMF

SPRTSCAR.WMF	STOREFRT.WMF

SUNFLOWR.WMF	SUPPLIES.WMF

SWAMPED.WMF	TALKING.WMF

TAXI.WMF	TELPHONE.WMF

TENNIS.WMF	TRAIN.WMF

TROPHY.WMF	TSTTUBES.WMF

TULIPS.WMF	USMAP.WMF

USSTATES.WMF	VAN.WMF

VICTRIAN.WMF	VOLLEYBL.WMF

WOMNCOMP.WMF	WOMSHAKE.WMF

WORLD.WMF	WORRIED.WMF

WRLDEAST.WMF	WRLDWEST.WMF

Directory: C:\MSWORKS\CONVERT

DZSDM.DLL	PICT2WMF.DLL

WK30DB.DLL	WK30WP.DLL

WK40DB.DLL	WK40SS.DLL

WK40WP.DLL	WKSS.DLL

WMF2PICT.DLL	WORKSXM.DLL

WWKDB3.DLL	WWKSS3.DLL

WWRK30WP.DLL

Directory: C:\MSWORKS\SETUP40

ACMSETUP.HLP	ACMSETUP.GID

IMPACT.TTF	MSSETUP.DLL

MSWORKS4.INF	SETUP.EXE

SETUP.INI	SETUP.STF

WORKS_BB.DLL

Directory: C:\WINDOWS\FONTS

MISTRAL.TTF	ARNAR.TTF

ARNARI.TTF	ARIALNB.TTF

ARIALNBI.TTF	WINGDNG2.TTF

MTEXTRA.TTF

Directory: C:\Windows\Shellnew

MSWORKS.WPS	MSWORKS.WKS

MSWORKS.WDB	MSWORKS.WCM

Directory: C:\Windows\System

ENCAPI32.DLL	E95THK16.EXE

PUBDLG.DLL	PICSTORE.DLL

PUBOLE32.DLL	PCDLIB32.DLL


Table of Contents

Introduction

How to use Microsoft Works on a network

Licensing

Sharing Microsoft Works program files

Sharing Microsoft Works data files

Rules for opening shared documents

To open a shared document

Sharing templates

Knowing your Windows installation

Network installation requirements

Workstation requirements

Server requirements

Installing Microsoft Works on your network

To install Microsoft Works on a network server or shared directory

To install Microsoft Works on workstations

Using batch mode to speed up workstation installations

Troubleshooting

Shared components and system files

Extracting files manually

Files installed on your network server

Files installed on workstations