Running PowerPoint for Windows from a Network Server PSS ID Number: Q69536 Article last modified on 10-29-1991 PSS database name: W_PowerPt
2.00
WINDOWS
Summary:
PowerPoint for Windows can run correctly in most network environments. It has been tested successfully with multiple users running from a single copy on network servers using Microsoft LAN Manager, Novell, and 3COM network software. However, because the PowerPoint program was not specifically designed to run from a network, a network administrator may experience some difficulties when using PowerPoint for Windows from a network server.
More Information:
Once PowerPoint for Windows has been correctly installed on the network server, multiple users can access the executable just as they would if they had the files installed on their local hard disk. However, some problems may occur.
PowerPoint-Specific INI Files
There are two files, POWERPNT.INI and GRAFLINK.INI, to which PowerPoint will try to write changes. This will cause error messages to occur because the files are stored in a read-only directory on the network server.
In the case of the POWERPNT.INI file, the only information that is written to it is the maximized state of PowerPoint’s windows, and the location of DLL files, help files, and embedded server application and filter files that have been used. Because changes cannot be written to this file when it is in a read-only directory, the windows in PowerPoint may not come up in the same state in which they were saved. Also, if the user asks for help, requires a DLL, or wants to embed a chart from Microsoft Excel 3.00, they will receive a dialog box asking where these files are located (provided they are not in the default locations).
On the PCSA network from Digital Equipment, a number of error messages are generated when you quit PowerPoint. When exiting, PowerPoint attempts to make changes to the POWERPNT.INI file, which it cannot do because the file is in a read-only directory. In most cases, these are “sharing violation” errors. Though they are annoying, they are benign.
On other networks, the error messages may not be generated, but nonetheless the information is not written to the POWERPNT.INI file.
The GRAFLINK.INI is specifically used by the telecommunications program (GrafLink) for sending PowerPoint files to Genigraphics for imaging. This file contains information pertaining to communications parameters as well as information the user may have entered prior to transmitting a file (such as billing information or Ship-To address, etc.). If the user has made changes to these parameters, the GrafLink application will attempt to update the GRAFLINK.INI file. However, it is stored in a read-only directory, so none of the changes will be saved. On a DCSA network, the same error messages will occur that appear when PowerPoint attempts to make changes to the POWERPNT.INI file.
Default Files
There are two default files that can be created to supersede the defaults built into PowerPoint and PowerPoint Graph. DEFAULT.PPT is the default presentation format and DEFAULT.PPG is the default data chart (for example, pie, bar, etc.).
DEFAULT.PPT is normally in the same directory as PowerPoint. If it is placed on the network drive, DEFAULT.PPT should be set to read-only to avoid changes by multiple users. However, this will prevent individual users from being able to redefine their default presentation format.
DEFAULT.PPG is normally in the same directory as PowerPoint. Unlike DEFAULT.PPT (which must be purposely saved with the name DEFAULT), this file is created/updated by a single menu command in PowerPoint Graph. On a network, where the file has been set to read-only, this can cause error messages to appear. It is recommended that the Set As Default command in PowerPoint Graph not be used when running from a network server because it will simply generate an error and no update will occur.
User Dictionary
When using the spelling checker in PowerPoint, the program looks for the file STDUSER.DIC in the directory where the PowerPoint program is located. When PowerPoint is installed on a network server, this file will be read-only because it needs to be shared by multiple users. This can lead to problems. Note that this is the “automatic” place where PowerPoint looks for a user dictionary. Users can use the Added Words/Open command in the PowerPoint spelling checker dialog box to open ANY user dictionary. These user dictionaries should be stored where the user can make changes to them without causing errors.
A solution is to modify the [Microsoft PowerPoint] section of the POWERPNT.INI file so that the PowerPoint program looks elsewhere for the spelling dictionary. Remember to remove the STDUSER.DIC file from the PowerPoint directory, or else the changed line will be ignored. For example
stduser=c:
OR
stduser.dic=c:.dic <— Most recent version of PowerPoint
would mean that each user could have his or her own user dictionary at the root of his or her own drive C.
Genigraphics Driver
When a user is preparing to send his or her PowerPoint presentation to Genigraphics for imaging, the Genigraphics driver automatically places the print files into a subdirectory called in the directory where the Windows file KERNEL.EXE resides. On a network server where Windows has been setup using EXPAND.EXE and SETUP /N, it is likely that the file KERNEL.EXE will be in a read-only volume or directory.
Because you cannot save anything to a read-only volume on a network server, this poses a problem. In order to avoid these problems, you must choose the option of sending the files to Genigraphics via disk, by selecting the disk option in the Send Via field of the Job Instructions dialog box which comes up when you choose the Print command. This option will provide a Save As dialog that you can use to direct the print file to a local drive or to a network directory where you have write and file-creation privileges.
If you want to send this file via modem, you will need to specify the location of the file, using the Switch Directories command of the File menu in the GrafLink telecommunications program.
Copyright Microsoft Corporation 1991.
