Office 97 FAQs from Support Online
| Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The following Microsoft Knowledge Base articles on Office 97 for Windows were compiled from the Microsoft Support Online Web site (https://support.microsoft.com). The articles below provide answers to questions frequently accessed by visitors to the Support Online site. Click on an issue of interest in the left column to jump to the answer.
Issue |
Symptom/Description |
|---|---|
How Can I Ensure that Setting Up Microsoft Office 97 Goes Smoothly? |
The top 10 issues that you should consider to ensure a proper installation of Microsoft Office 97 on a Non-Networked computer and on a Network Server. |
How Do I Perform a Network Installation of Microsoft Office 97? |
The netwrk8.txt file, located in the Office folder on the Microsoft Office 97 compact disc, has instructions for performing an administrative installation of Office. |
What Networks are Supported by Microsoft Office 97? |
Network servers and clients tested with Microsoft Office 97 Setup and the programs included with Microsoft Office 97: |
Why Does Setup Fails if Network Share Name Contains a Space |
An error occurs if you are running Microsoft Office 97 Setup on a computer running Microsoft Windows NT 4.0 and the name of the share on the server contains a space. |
Why Does Setup Incorrectly Report Free Disk Space During an Administrative Installation? |
Error message may occur if the network server to which you are installing contains more than 4 gigabytes (4 GB) of free space. |
Are There Any Problems I Should Be Aware of When I Install Office 97 on a Computer Running Microsoft Windows NT? |
To install and run any of the programs included with Microsoft Office 97 under Windows NT Workstation, your computer must have the appropriate service pack(s) installed. |
How Can I Customize a Run from Network Server Installation of Office? |
The Network Installation Wizard can be used to customize a Run from Network Server installation of Microsoft Office 97 for Windows. |
What Switches Can I Use with Setup in Microsoft Office 97? |
The Microsoft Office 97 Setup program accepts a number of optional switches that you can use to control how the Setup program operates. |
Is it Possible to Perform a Run From Network Server Installation of Office 97 Without Installing Microsoft Outlook So My Organization Can Use its Existing E-Mail Program? |
In Microsoft Office 97, it is possible to customize a post-administrative installation (setup /a) so that when your users run Office 97 Setup, Microsoft Outlook is not available for installation and none of the Microsoft Outlook components are installed. |
How Can I Ensure that Users Automatically Save Their Documents in the Earlier File Format While I'm Rolling Out Microsoft Office 97? |
Microsoft Office includes a set of templates for use with the System Policy Editor that you can use to establish default policies for users. |
How Do I Troubleshoot Errors that Occur in Module Kernel32.dll When I Work with Microsoft Office 97 Programs? |
Information on troubleshooting and eliminating invalid page faults that occur in module Kernel32.dll when you work with a Microsoft Office program under Microsoft Windows 95. |
How Can I Ensure that Setting Up Microsoft Office 97 Goes Smoothly?
This document discusses the top 10 issues that you should consider to ensure a proper installation of Microsoft Office 97. It contains the following two sections:
Installing Microsoft Office 97 on a Non-Networked computer
Installing Microsoft Office 97 on a Network Server
Installing Microsoft Office 97 on a Non-Networked Computer
To ensure that your installation of Microsoft Office 97 goes as smoothly as possible, use the following steps:
Confirm your computer meets the Microsoft Office 97 installation requirements. To install and use Microsoft Office 97, you'll need:
A personal or multimedia computer with a 486 or higher processor.
Microsoft Windows® 95 operating system or Microsoft Windows NT® 3.51 with Service Pack 5 or later (will not run on earlier versions). If you are using Windows NT 4.0, it is recommended that Service Pack 2 be installed in order for the Microsoft Office applications to run properly.
For use on Windows 95: 8 megabytes (MB) of memory required to run applications individually (12 MB required to run Microsoft Access); more memory may be required to run additional applications simultaneously. An additional 8 megabytes (MB) of memory is required for WordMail
For use on Windows NT Workstation: 16 MB of memory required to run applications individually; more memory may be required to run additional applications simultaneously.
54-158 MB hard disk space required; 112 MB required for typical installation, depending on configuration. Use the Office Upgrade Wizard during setup to maximize free disk space.
CD-ROM drive (Coupon enclosed for 3.5-inch high-density disks. CD-ROM product contains Microsoft Internet Explorer, additional clip art, fonts, video files, and sounds not available on 3.5-inch disks).
VGA or higher-resolution video adapter (Super VGA, 256-color recommended).
Microsoft Mouse, Microsoft IntelliMouse™, or compatible pointing device.
Additional items or services required to use certain features:
9600 baud or higher modem (14.4 baud recommended).
Multimedia computer required to access sound and other multimedia effects.
Microsoft Mail, Microsoft Exchange, Internet SMTP/POP3, or other MAPI- compliant messaging software required to use e-mail.
Publish to the Web feature in Microsoft Access requires Microsoft Internet Information Server for Windows NT or Microsoft Personal Web Server for Windows 95.
Microsoft Exchange Server required for certain advanced workgroup functionality in Microsoft Outlook™. Some Internet functionality may require Internet access and payment of a separate fee to a service provider
If you are using the upgrade version of Microsoft Office 97, confirm that you own one of the qualifying products. In order to use the upgrade version, you must have an earlier version of Microsoft Office or a competitive product that Microsoft has designated as a qualifying product. The qualifying products are:
Application
Version
Application
Version
Aldus Persuasion for Windows
2.1
Microsoft Access for Windows
1.1
3.0
2.0
Ami Pro for Windows
1.1
7.0
1.2
Microsoft Excel for Windows
4.0
2.0
5.0
3.0
7.0
3.01
Microsoft Exchange for Windows
4.0
3.1
Microsoft FoxPro for MS-DOS
2.6
Borland dBASE for Windows
5.0
Microsoft Mail for Windows
3.2
Borland dBASE IV for MS-DOS
1.0
Microsoft Office for Windows
4.2
1.5
4.3
Borland Office for Windows
2.0
NT
Borland Paradox for MS-DOS
4.5
7.0
Borland Paradox for Windows
1.0
Microsoft PowerPoint for Windows
3.0
4.5
4.0
5.0
7.0
Borland Quattro Pro for MS-DOS
3.0
Microsoft Schedule+ for Windows
1.0
5.0
7.0
Borland Quattro Pro for Windows
1.0
Microsoft Visual FoxPro for Windows
3.0
5.0
Microsoft Word for Windows
2.0
6.0
6.0
Borland Quattro Pro Special Edition
1.0
7.0
Claris FileMaker Pro for Windows
2.1
Microsoft Works for Windows
3.0
CompuServe for Windows
2.0.1
4.0
Corel WordPerfect Suite
7.0
Paradox for Windows
4.0
DataEase for Windows
5.0
Personal ORACLE for Windows
7.0
Harvard Graphics for MS-DOS
2.3
PowerBuilder for Windows
5.0
Harvard Graphics for Windows
1.01
Superbase
2.0
2.0
Superbase 4 for Windows
1.2
3.0
1.3
Lotus 1-2-3 for MS-DOS
2.01
Superbase 95 for Windows
3.0
2.2
SuperCalc for MS-DOS
3.1
2.3
3.2
3.1
4.0
3.1 Upgrade
5.1
3.4
5.5
3.4a
5.5b
4.0
WordPerfect for MS-DOS
5.1
Lotus 1-2-3 for Windows
4.0
WordPerfect for Windows
5.1
4.01
5.2
5.0
6.0
Lotus Approach for Windows
2.1
6.0a
3.0
6.1
Lotus Approach for Windows 95
96
WordStar 2000 for MS-DOS
3.0
Lotus Freelance for MS-DOS
4.0
WordStar for MS-DOS
3.0
Lotus Freelance for Windows
1.0
4.0
2.0
5.0
2.01
6.0
2.1
7.0
3.01
7.0 Upgrade
96
7.0c
Lotus Freelance Graphics for Windows
96
WordStar for Windows
1.0
Lotus SmartSuite
3.0
1.5
Lotus SmartSuite 96 for Windows
96
2.0
Lotus Word Pro for Windows
96
Note: that not all earlier versions of Microsoft Office are eligible for the upgrade.
Check that you have sufficient disk space to install Microsoft Office 97. The disk space required to install Microsoft Office depends on the installation option you choose. The installation options include Compact, Typical, Custom, Run From CD, Run From Network Server, and Administrative Setup. The following table lists the disk space required for each.
Installation option
Disk space required
Typical
112.9 MB
Custom (with Select All)
160.0 MB
Run From CD
60.2 MB
Run From Network Server..
..with shared files on your local drive
51.8 MB
..with shared files on a server
24.0 MB
Administrative (setup /a)
323 MB
Remove earlier versions of Microsoft Office before installing Microsoft Office 97.
The Microsoft Office 97 Setup program allows you to install directly over an earlier version of Microsoft Office. If you choose to remove the earlier version of Microsoft Office during Setup, the Setup program will remove earlier versions of Microsoft Office (Microsoft Office 4.2, Microsoft Office 4.3, and Microsoft Office 95) from your computer. However, Setup will not remove all the Microsoft Office files that have been installed into the \Windows\System folder. Files that may be used by other applications will not be removed.
To completely remove all the older system files, it is recommended that you use the stand-alone version of the Office Upgrade Wizard before running Setup. This application is located in the \OffClean\ValuPack folder on your Microsoft Office 97 compact disc. The application file is named OffCln97.exe. Running this file will start the stand-alone version of the Office Upgrade Wizard.
In the second step of the Wizard, choose Completely remove all of my old Microsoft Office applications to remove the system files and registry entries of the older Microsoft Office version (Microsoft Office 4.2, Microsoft Office 4.3, and Microsoft Office 95). You may, however, need to reinstall some other applications after using this option.
Note If you are using an earlier version of Microsoft Office to qualify for the upgrade edition of Microsoft Office 97, running the stand-alone version of the Office Upgrade Wizard will remove that earlier version from your computer. You will need to have the diskettes or compact disc of the earlier version of Microsoft Office available to insert into your computer when it prompts you for a qualifying product during the upgrade process.
Scan your hard disk for any errors.
The Windows 95 ScanDisk utility checks your disk's surface, files, and folders for any errors. Before installing Microsoft Office 97, run this utility to check your computer's hard disks and to correct any errors that are found. To run ScanDisk in Windows 95:
a. Click the Start button, point to Programs, point to Accessories, point to SystemTools, and then click ScanDisk.
b. Click the drive you want to check.
c. Click Thorough. If you want to change the settings ScanDisk uses when checking the disk's surface, click Options. If you want to change the settings ScanDisk uses when checking files and folders, click Advanced.
d. Click Start.
Note: If you are using Windows NT 3.51 or 4.0, the Windows NT operating system automatically scans your hard disk and corrects any errors at startup. You only have to restart your computer to have it check your hard disk and to correct any errors that are found.
Defragment your hard disk.
The Disk Defragmenter utility in Windows 95 rearranges files and consolidates unused space on your hard disk. Before running Microsoft Office 97 setup, defragment your hard disks so that Microsoft Office is installed to a consolidated hard disk. Periodically, use Disk Defragmenter after installing Microsoft Office 97 to keep your hard disk optimized for better performance. To run Disk Defragmenter in Windows 95:
a. Click the Start button, point to Programs, point to Accessories, point to System Tools, and then click Disk Defragmenter.
b. Click the drive you want to defragment, and then click OK.
c. Change the settings for Disk Defragmenter. Click Advanced. Choose Full Defragmentation.
d. Click Start.
Note: If you are using Windows NT 3.51 or 4.0, it is generally not necessary to defragment your computer. The Windows NT operating system does not include a disk defragmenter tool. However, if you have installed a third-party disk defragmenting tool, you may use it to further optimize your hard disk.
Virus Scan your Hard Disk.
Microsoft has rigorous quality control measures to ensure that viruses are not on disks that we ship. The Setup disks are distributed virus-free in sealed, clear plastic envelopes that display a message about the Microsoft software license agreement. If disks are purchased in any other type of package, they should not be used.
To check that viruses are not already present on your computer, scan the hard disk of your computer with a currently updated virus detector before installing Microsoft Office 97. Resident viruses on a computer may interfere with setup, may damage files after setup, and may infect the disks you are installing from. Some viruses will not interfere with the installation process. Instead, they may quietly infect your diskettes or remain on your hard disk until some event triggers them into damaging activity. If a virus is found on your computer, remove the virus before you run Setup.
Shut down all other programs that are running in Windows before installing Microsoft Office 97.
The speed and stability of the setup process are optimized if there are no other programs running in Windows as you install Microsoft Office 97. Turn off virus scanning software, screen savers, messaging systems, and any other computer applications. Disable any running desktop utilities and terminate-and-stay-resident software programs (TSRs).
It is especially important to turn off virus scanning software during the setup process. Virus software that runs in the background often detects changes in operating system configuration files and executable file sizes as signs of virus activity. Making changes to operating system configuration files and changing file sizes as files are copied and updated is a standard part of the Microsoft Office 97 setup process. Because of this, virus scanning software will often halt or interfere with the normal running of Microsoft Office Setup if both are being run at the same time.
If you're installing Microsoft Office 97 from a compact disc, have your CD key available.
When installing Microsoft Office 97 from a compact disc, you will be prompted for a CD key as part of the setup process. This key is printed on a sticker affixed to the back of the compact disc case.
If you're installing Microsoft Office 97 from diskettes, have all your diskettes available.
Microsoft Office 97 Standard edition is provided on a total of 45 diskettes. Microsoft Office 97 Professional edition is provided on a total of 55 diskettes. Depending on the options selected during Setup, you may not be prompted for every diskette.
Additional Information Microsoft recommends that you create backup copy of all Windows system configuration files. If your computer stops responding (hangs), or you receive a general protection fault or an illegal operation message during the Microsoft Office installation, system configuration files may become damaged and fail to function properly. You can use the Windows 95 Emergency Recovery Utility to make a backup of your system configuration files. For more information, see the following article in the **139437—**Windows 95 Emergency Recovery Utility. If you do not have the Windows 95 CD (or if you have OEM Windows or the diskette version) you can download the utility from theWindows 95 web.
Installing Microsoft Office 97 on a Network Server
To ensure that your installation of Microsoft Office 97 on a network server goes as smoothly as possible, use the following steps:
Make sure you have completed all the steps in the "Installing Microsoft Office on a Non-Networked Computer" section.
Review the Netwrk8.txt file.
For information about the process of installing Microsoft Office 97 on a network, review the Netwrk8.txt file. The Netwrk8.txt file is located on the first Microsoft Office 97 diskette or in the root directory of the Microsoft Office 97 compact disc.
Confirm that your network is supported for Microsoft Office 97. The supported networks for Microsoft Office 97 are:
Microsoft Networks (Lan Manager 2.x, Windows NT 3.5x and 4.x, and Windows 95)
Novell® 3.x and 4.x (32-bit client)
Banyan Vines® 5.52 or higher (32-bit client)
LANtastic® 6.x or higher (32-bit client)
DEC PATHWORKS™ 6.2
IBM™ LanServer
Check that you have sufficient disk space to perform an administrative installation (setup /a) to the network server. An administrative installation (setup /a) of Microsoft Office 97 requires 324 MB of disk space on the network server.
Perform the administrative installation (setup /a) from a workstation in the network to the network server.
It is recommended that an administrative installation be performed from a workstation in the network to the network server. Installing from a workstation to the server allows Microsoft Office 97 Setup to validate the path to the server during the installation process.
Perform the administrative installation (setup /a) to a clean directory.
Do not install over an earlier administrative installation on a network server. If you want to install to the same server and directory used with an earlier version of Microsoft Office, first delete the previous directory and subdirectories created by the earlier administrative installation before performing a new administrative installation.
Do not use special characters or spaces in the administrative directory name. Not all networks and operating systems allow the use of spaces and special characters in directory names. As a general rule, you should keep your administrative directory name generic.
For example, name an administrative directory Office97, instead of Office 97 (with a space in the name).
Be patient if the administrative installation (setup /a) displays the message "Setup is updating your system files" for a relatively long period of time.
The message "Setup is updating your system files" may appear after all files appear to have been copied to the network server during the administrative setup. The Setup program may seem to have halted. Although it appears that all files have been copied, the Microsoft Office 97 Setup program is still copying additional files to the network server. Specifically, Setup is copying ClipArt files to the network server during this phase of the administrative installation. Because Microsoft Office 97 includes approximately 3400 ClipArt files, Setup may take a long time (up to 30 minutes or more) to complete this operation.
Give your users the correct access rights to the administrative directory.
After completing the administrative installation of Microsoft Office 97 to the server, give the network users read-only access to the administrative installation directory. Network users require no higher access rights than read-only to install or run Microsoft Office 97 from an administrative directory on the network server. Granting users read-only access prevents them from inadvertently changing or damaging administrative directory files.
There is an exception to read-only access if you install Microsoft Office 97 Professional edition (which includes Microsoft Access), and if during the workstation installation you choose the Run From Network Server option. In this case the sub-directory named WORKDIR under the OFFADMIN directory must be set to read-write access to enable users to run Microsoft Access wizards.
When using Windows NT, install the latest service packs on network servers and workstations. Update Windows NT computers with the latest Service Pack before installing Microsoft Office 97 to or from the network. Service Packs are a cumulative build of updates to an operating system. They include additional functionality, enhancements, and fixes made since the initial release of the operating system.
Service Pack updates for Windows NT 3.51 and 4.0 can be found on TechNet and on the Web at ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/.
How Do I Perform a Network Installation of Microsoft Office 97?
The netwrk8.txt file, which is located in the Office folder on the Microsoft Office 97 compact disc, has instructions for performing an administrative installation of Office. In addition to the steps listed in this file, you must grant users read/write permission to the Msoffice\Workdir folder on the server. For the rest of the folders on the server, use read-only permission. You'll also find helpful information about this topic in the Knowledge Base article "159772: Contents of the Netwrk8.txt Readme File" and in the Microsoft Office 97 Resource Kit: Chapter 4—Installing MS Office.
What Networks are Supported by Microsoft Office 97
Last reviewed: September 18, 1998
Article ID: 160530
The information in this article applies to:
Microsoft Office 97 for Windows
Microsoft Excel 97 for Windows
Microsoft Word 97 for Windows
Microsoft Access 97 for Windows
Microsoft PowerPoint 97 for Windows
Microsoft Outlook 97 for Windows
Summary
This article lists the network server and client software that is supported by Microsoft Office 97 for Windows.
More Information
The following network servers and clients were tested with Microsoft Office 97 Setup and the programs included with Microsoft Office 97:
Server |
Client |
|---|---|
Microsoft Windows NT Server |
Client for Microsoft Networks |
Microsoft Windows 95 Workstation |
Client for Microsoft Networks |
*Novell NetWare, 3.x and 4.x |
32-bit NetWare client (see note) |
Banyan Vines 5.52 or later |
32-bit Vines client |
Artisoft LANtastic 6.x or later |
32-bit LANtastic client |
DEC Pathworks 5.0d or later |
32-bit Pathworks client |
IBM LanServer 4.0 |
32-bit LanServer client |
*Note that the client for NetWare Networks that is included with Microsoft Windows 95 is a 32-bit NetWare client. Novell also ships a 32-bit NetWare client. The two 32-bit clients from Novell that were tested were Netware 32b client for Microsoft Windows 95, version 2.11, and Netware client for Microsoft Windows NT beta, version 4.0.
addition, please note that although these networks have been tested, you may still encounter problems when you install or use Microsoft Office 97 with any of these networks. Information that addresses such issues will appear in the Microsoft Knowledge Base as we become aware of the issues.
For additional information about networks supported by Microsoft Access 97, please see the following articles in the Microsoft Knowledge Base:
159366—ACC97: Setup Requirements for Microsoft Access 97
109739—ACC: Microsoft Access and Untested Networks
Network servers and clients not listed in this article were not tested and are not supported by Microsoft Office 97. The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
Why Does Setup Fails if Network Share Name Contains a Space
Last reviewed: September 18, 1998
Article ID: 157022
The information in this article applies to:
Microsoft Office 97 for Windows
Microsoft Windows NT, version 4.0
Symptoms
When you start the Microsoft Office 97 Setup program, you receive the following error message:
Can't run 16-bit Windows program
Cannot find file \\Server\ShareName\setup.exe (or one of its components). Check to ensure the path and filename are correct and that all required libraries are available.
Cause
This will occur if both of the following conditions are true:
You are running Microsoft Office 97 Setup on a computer running Microsoft Windows NT 4.0.
The name of the share on the server contains a space. For example: \\MyServer\Office 97.
Workaround
To avoid this problem, use either of the following workarounds:
Don't include a space in the name of the share on the server. For example, if the share is named "Office 97" (without quotation marks), rename it "Office97". The Setup program should then run correctly.
Map a drive letter for the share and then run Setup.
a. Double-click My Computer.
b. On the toolbar, click Map Network Drive.
c. In the Drive list box, select the drive letter you want to use. In the Path edit box, type the path to the server and share. For example:
\\MyServer\My Share
If you are required to, enter your username in the Connect As box, then click OK.
A new window will appear, showing the contents of the share. The caption of the window will be the letter of the drive you mapped (for example, F:)
d. On the Start menu, click Run.
e. In the Open edit box, type the path to the Setup program, but use the drive letter (F:, for example) rather than the Universal Naming Convention path (\\MyServer\My Share, for example). Click OK.
Or locate the Setup program in Windows Explorer, and double-click it.
The Setup program should now run correctly.
Status
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
This problem does not occur when you run Office 97 Setup on Windows 95.
Why Does Setup Incorrectly Report Free Disk Space During an Administrative Installation?
Last reviewed: September 18, 1998
Article ID: 156815
The information in this article applies to:
- Microsoft Office 97 for Windows
Symptoms
When you perform an administrative installation ("setup /a") of Microsoft Office 97 to a network server, the Setup program may display the following error message:
There is not enough disk space to complete installation. You can change your installation options, continue installation, or exit Setup.
This occurs even though there is ample free space on the hard disk to which you are installing Microsoft Office 97.
Cause
This may occur if the network server to which you are installing contains more than 4 gigabytes (4 GB) of free space.
Resolution
If you receive the aforementioned error message, and you are sure that enough space is available, click "Install Now" to continue the administrative installation.
Status
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
More Information
When you run the Microsoft Office 97 Setup from a machine running Windows NT, the mechanism in the Setup program that calculates free disk drive space "wraps" at every 4 GB. So, if the disk to which you are installing Microsoft Office 97 contains more than 4 GB of free space, the Setup program incorrectly reports the amount of free space and may even warn you that there is not enough free space available.
For example:
Actual Free Space |
Free Space Calculated By Setup |
Amount of Free Space Ignored by Setup |
|---|---|---|
500 MB |
500 MB |
n/a |
2700 MB (2.7 GB) |
2700 MB (2.7 GB) |
n/a |
4200 MB (4.2 GB) |
200 MB |
4000 MB (4 GB) |
6700 MB (6.7 GB) |
2700 MB (2.7 GB) |
4000 MB (4 GB) |
8100 MB (8.1 GB) |
100 MB |
8000 MB (8 GB) (two intervals) |
If the hard disk to which you are installing has between 4 and 4.5 GB free, or between 8 and 8.5 GB free, you may receive an error message stating that not enough space is available. If you are sure that enough space actually is available, click "Install Now" to override the disk space warning.
Note, this error does not occur when you perform an administrative installation from a computer running Windows 95. However, in Windows 95, the Setup program indicates that a maximum of 2 GB of free space is available, even if the true amount of free space is higher.
Are There Any Problems I Should Be Aware of When I Install Office 97 on a Computer Running Microsoft Windows NT?
Last reviewed: September 18, 1998
Article ID: 156444
The information in this article applies to:
Microsoft Office 97 for Windows
Microsoft Office 97 for Windows, Service Release 1
Microsoft Excel 97 for Windows
Microsoft Word 97 for Windows
Microsoft Access 97 for Windows
Microsoft PowerPoint 97 for Windows
Microsoft Outlook 97 for Windows
Microsoft Windows NT Workstation, versions 3.51, 4.0
Summary
To install and run any of the programs included with Microsoft Office 97 under Windows NT Workstation, your computer must have the following service pack(s) installed:
Version of Windows NT |
Min. Service Pack Required |
|---|---|
Windows NT Workstation, version 3.51 |
Service Pack 5 |
Windows NT Workstation, version 4.0 |
Service Pack 2 |
More Information
Service Pack 5 for Windows NT 3.51 provides additional functionality to Windows NT version 3.51, including enhanced Internet functionality and an updated Oleaut32.dll file. These features are required in order for Microsoft Office 97 programs to work under Windows NT version 3.51.
Service Pack 2 or later for Windows NT 4.0 corrects some operating system problems that could affect Microsoft Office 97 programs. If you receive any error messages (such as application errors) when running Microsoft Office 97 programs, it is strongly recommended that you download and install Service Pack 2 or later.
The box for Microsoft Office 97, Service Release 1 (SR-1), may incorrectly state the service pack requirement for Microsoft Office 97 SR-1. Microsoft Office 97 SR-1 requires Service Pack 2 in order to run under Microsoft Windows NT Workstation, version 4.0. In addition, the box may not state that the version of Microsoft Office 97 included in the box is SR-1.
When you perform an administrative installation (Setup /a) of Microsoft Office 97, Microsoft Office 97 SR-1, or any of the Microsoft Office 97 programs to a server running Microsoft Windows NT Server, it is not necessary to install Service Pack 5 or Service Pack 2 on the workstation from which you are performing the administrative installation, or on the server. Service packs are required only when you perform a client installation on the workstation that actually runs the Microsoft Office programs.
For additional information, please see the following Microsoft Knowledge Base article:
- 122522—Office: Performing an Administrative Installation (Setup /a)
If you attempt to install Microsoft Office 97 programs on a computer that does not meet the minimum service pack requirements, you will receive one of the following error messages and Microsoft Office 97 will not install. One of these two message is displayed after you enter your CD key:
This operating system does not meet the minimum requirements to run Office 97. Please check the minimum requirements on the packaging or in the readme file for your product. The readme files are located in the \Office directory on the CD.
This operating system does not meet the minimum requirements to run Office 97. Service Pack 5.0 or higher is required for NT3.51. Service Pack 2.0 or higher is required for NT4.
Microsoft Windows NT Service Packs may be obtained from the following location on the Internet:
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/
For more information on obtaining and installing the Microsoft Windows NT 3.51 Service Pack 5, please see the following Microsoft Knowledge Base article:
- 128465—How To Obtain Windows NT Version 3.51 U.S. Service Pack
For more information on obtaining and installing the Microsoft Windows NT 4.0 Service Pack 2, please see the following Microsoft Knowledge Base article:
- 152734—How To Obtain the Latest Windows NT 4.0 Service Pack
How Can I Customize a Run from Network Server Installation of Office?
The Microsoft Office 97 Resource Kit includes the Network Installation Wizard, a utility located on the Client Utilities CD that you can use to customize a Run from Network Server installation of Microsoft Office 97 for Windows. For information about using this utility, see Chapter 6: Customizing Client Installations in the Microsoft Office 97 Resource Kit.
What Switches Can I Use with Setup in Microsoft Office 97?
Last reviewed: September 18, 1998
Article ID: 158503
The information in this article applies to:
- Microsoft Office 97 for Windows
Summary
The Microsoft Office 97 Setup program accepts a number of optional switches that you can use to control how the Setup program operates. This article lists the switches and describes the functionality of each switch.
More Information
The following table lists the Setup switches.
Switches are not case sensitive; for example, /A is the same as /a.
Except where specifically noted, these switches may only be used when performing an initial installation of Microsoft Office 97.
Multiple switches are separated by a blank space. For example, use the following command line to restore Office registry settings:
Setup /y /r
Switch |
Function |
|---|---|
/a |
Runs Setup in administrative mode and creates an administrative installation point. Available only when running Setup from compact discs or floppy disks. |
/b# |
Suppresses the dialog box for choosing an installation type by pre-selecting one of the large buttons. Substitute a digit for the # symbol: 1 represents the first button, 2 represents the second button, and so on. This option is ignored if an invalid digit is used. |
/c <COA> |
Enters and validates the 20-character Product ID from the original equipment manufacturer (OEM) Certificate of Authorization, replacing the user dialog box that normally appears. You must specify the Certificate of Authorization number. |
/f |
All files are created with the 8.3 MS-DOS naming convention. Long file names are not used. |
/g[+] "<filename>" |
Generates a log file that records details of the setup process. You must specify the log file. This switch may be used when running Microsoft Office 97 Setup in maintenance mode. |
/gc[+] "<filename>" |
Generates a log file that records details of the setup process. This switch also causes Setup to log all calls and returns from custom actions. This can make the log file very large. You must specify the log file. The file name specified must be an 8.3 MS-DOS short name. Longer file names are not allowed. This switch may be used when running Microsoft Office 97 Setup in maintenance mode. |
/k "<cdkey>" |
Enters and validates the 11-digit key from the compact disc sticker, replacing the user dialog box that would normally appear. |
/l <.lst file> |
Specifies the custom .lst file to use when running Setup. Use this switch after performing an administrative installation of Microsoft Office 97 and using the Network Installation Wizard to customize Setup. |
/m# |
Specifies the Multi-License Pak (MLP) licensing information needed to activate the MLP for floppy disks. Setup increments the multi-license count on the floppy disks by the number you specify. |
/n "" |
Setup uses the Windows registry Copy Disincentive name if it exists; otherwise, Setup prompts the user for the name. Ignored when you use the /a switch. |
/n "<name>" |
Specifies the user name. Setup uses the Windows registry Copy Disincentive name if it exists; otherwise, Setup uses the user name that you specify. Ignored when you use the /a switch. |
/o "" |
Setup uses the Windows registry Copy Disincentive organization name if it exists; otherwise, Setup prompts the user for the organization name. |
/o "<organization>" |
Specifies the organization name. Setup uses the Windows registry Copy Disincentive organization name if it exists; otherwise, it uses the organization name that you specify. |
/q# |
Specifies that Setup run in quiet installation mode. Performs a batch mode installation with no user interaction. Substitute any of the following values for #: nothing, 0, 1, or t. |
/qn# |
Specifies that Setup runs in quiet installation mode, and that the system is not rebooted. The option can be 1 or t (see the /q# switch); 0 is not valid. |
/r |
Reinstalls the program. This switch may be used when running Microsoft Office 97 Setup in maintenance mode. |
/s folder |
Specifies the folder from which files are installed. Overrides the default source (the folder containing Setup.exe or the source specified in the maintenance mode .stf file). |
/u[a] |
Use this switch to uninstall Microsoft Office. /u removes all program files except shared components; /ua always removes shared components without prompting you. This switch may be used when running Microsoft Office 97 Setup in maintenance mode. |
/x "<file>" |
Creates a network installation log file for tracking the number of installations made from an administrative installation point. This overrides the value, if any, specified in the .stf file. |
/y |
Prevents Setup from copying files. Setup proceeds normally, including setting registry entries, but does not copy any files. Use this switch for restoring registry entry values or for tracking down process problems without copying files. This switch may be used when running Microsoft Office 97 Setup in maintenance mode. |
? |
Displays Setup command line options. Using any invalid parameter (for example, /z) also displays these options. |
Is it Possible to Perform a Run from Network Server Installation of Office 97 Without Installing Microsoft Outlook So My Organization Can Use its Existing E-Mail Program?
Last reviewed: September 18, 1998
Article ID: 165571
The information in this article applies to:
Microsoft Office 97 for Windows
Microsoft Office 97 for Windows, Service Release 1 (SR-1)
Summary
In Microsoft Office 97, it is possible to customize a post-administrative installation (setup /a) so that when your users run Office 97 Setup, Microsoft Outlook is not available for installation and none of the Microsoft Outlook components are installed.
This article explains how to perform this task by editing the Office Setup .stf file.
More Information
WARNING: This modification may not be supported by Microsoft. Microsoft support engineers will support some modifications to a BACKUP copy of the Setup.stf file. Note also that while support engineers may help customers modify specific lines of an STF, we will not rewrite the entire file in order to achieve a desired configuration. As a general rule, support is limited to options that can normally be changed by a user during a standard installation of the application.
Note: The following steps work only if you have first performed an administrative installation (setup /a) of Office 97 to a server on your network. If you are performing a standalone installation using the Office 97 compact disc, you cannot use the following steps.
Before performing the following steps, make a backup copy of the Off97pro.stf or Off97std.stf file stored on your server. Rename the file to Backup.stf and do not open or edit it for any reason.
Edit the .STF file in a text editor such as Microsoft Word, Wordpad, or Notepad.
Note: MS-DOS Editor should NOT be used to modify the SETUP.STF file. MS- DOS Editor replaces tabs with spaces and will cause the same error. Other text editors that are known to replace tabs with spaces (and are thus unsuitable for modifying the .STF file) are Xtree Gold 2.0 by Executive Systems and QEdit by SemWare Inc.
Find the following Object IDs and delete the corresponding values from the Object Data column on the same line. Make sure you delete the trailing space after each number. Use the table that is appropriate for your version of Office.
For |
Remove the Reference to |
|---|---|
ObjID 46 |
198 |
ObjID 51 |
196 |
ObjID 53 |
196 |
ObjID 54 |
197 |
ObjID 56 |
202 |
ObjID 58 |
196 |
ObjID 59 |
197 |
ObjID 60 |
199 |
For |
Change |
To |
|---|---|---|
ObjId 12808 |
'Depend' |
'Group' |
ObjId 12808 |
'11917 ? : 12809' |
'12809' |
ObjId 12863 |
'Depend' |
'Group' |
ObjId 12863 |
'11917 ? : 12864' |
'12864' |
For |
Remove the Reference to |
|---|---|
ObjID 46 |
211 |
ObjID 52 |
209 |
ObjID 54 |
209 |
ObjID 55 |
210 |
ObjID 57 |
215 |
ObjID 59 |
209 |
ObjID 60 |
210 |
ObjID 61 |
212 |
For |
Change |
To |
|---|---|---|
ObjId 13108 |
'Depend' |
'Group' |
ObjId 13108 |
'12220 ? : 13109' |
'13109' |
ObjId 13163 |
'Depend' |
'Group' |
ObjId 13163 |
'12220 ? : 13164' |
'13164' |
For |
Remove the Reference to |
|---|---|
ObjID 35 |
110 |
ObjID 41 |
108 |
ObjID 43 |
108 |
ObjID 44 |
109 |
ObjID 46 |
114 |
ObjID 48 |
108 |
ObjID 49 |
109 |
ObjID 50 |
111 |
For |
Change |
To |
|---|---|---|
ObjId 11708 |
'Depend' |
'Group' |
ObjId 11708 |
'10817 ? : 11709' |
'11709' |
ObjId 11763 |
'Depend' |
'Group' |
ObjId 11763 |
'10817 ? : 11764' |
'11764' |
For |
Remove the Reference to |
|---|---|
ObjID 35 |
123 |
ObjID 42 |
121 |
ObjID 44 |
121 |
ObjID 45 |
122 |
ObjID 47 |
127 |
ObjID 49 |
121 |
ObjID 50 |
122 |
ObjID 51 |
124 |
For |
Change |
To |
|---|---|---|
ObjId 12108 |
'Depend' |
'Group' |
ObjId 12108 |
'11220 ? : 12109' |
'12109' |
ObjId 12163 |
'Depend' |
'Group' |
ObjId 12163 |
'11220 ? : 12164' |
'12164' |
For |
Remove the Reference to |
|---|---|
ObjID 43 |
204 |
ObjID 49 |
202 |
ObjID 51 |
202 |
ObjID 52 |
203 |
ObjID 54 |
208 |
ObjID 56 |
202 |
ObjID 57 |
203 |
ObjID 58 |
205 |
For |
Change |
To |
|---|---|---|
ObjId 12308 |
'Depend' |
'Group' |
ObjId 12308 |
'11420 ? : 12309' |
'12309' |
ObjId 12363 |
'Depend' |
'Group' |
ObjId 12363 |
'11420 ? : 12364' |
'12364' |
3. Save the File. Make sure that the file type is Text.
After you finish these steps, the Microsoft Outlook component is not installed and does not appear in the Add/Remove Programs Control Panel icon for any user who performs an installation of Office 97 using the modified setup table file (for example, you may call this file Custom.stf).
Note: Removal of ObjId 57 may not be absolutely necessary. Save the ObjId information to another location for re-entry purposes.
For more information about using custom setup table files with Office 97, please see the following Microsoft Knowledge Base article:
- 158281—OFF97: How to Use Custom STF Files with MS Office 97 Setup.
How Can I Ensure That Users Automatically Save Their Documents in the Earlier File Format While I'm Rolling Out Microsoft Office 97?
Microsoft Office includes a set of templates for use with the System Policy Editor that you can use to establish default policies for users. Chapter 7 - Customizing and Optimizing MS Office in the Microsoft Office 97 Resource Kit contains detailed information about using the System Policy Editor. Refer to Appendix C - Registry Keys and Values of the Microsoft Office 97 Resource Kit for more information about using the policy templates.
How Do I Troubleshoot Errors that Occur in Module Kernel32.dll When I Work with Microsoft Office 97 Programs?
Last reviewed: June 8, 1998
Article ID: 164519
The information in this article applies to:
Microsoft Office 97 for Windows
Microsoft Office for Windows 95, version 7.0
Microsoft Access 97
Microsoft Access 7.0
Microsoft Excel 97 for Windows
Microsoft Excel for Windows 95, version 7.0
Microsoft PowerPoint 97 for Windows
Microsoft PowerPoint for Windows 95, version 7.0
Microsoft Word 97 for Windows
Microsoft Word for Windows 95, version 7.0
Microsoft Publisher 97
Microsoft Publisher for Windows 95, version 3.0
Microsoft Windows 95
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.
Note: Because there are several versions of Windows, the steps in this article may be different on your computer. If they are, please consult your product documentation to complete these steps.
Summary
This article contains information about troubleshooting and eliminating invalid page faults that occur in module Kernel32.dll when you work with a Microsoft Office program under Microsoft Windows 95. When a Kernel32.dll error message appears, a message similar to the following appears:
<Program name> caused an invalid page fault in module Kernel32.dll
where <Program name> is the name of the program you are using.
More Information
When an invalid page fault occurs, an unexpected event occurs in the Microsoft Windows operating system. An invalid page fault typically indicates that a program improperly attempted to use random access memory, for example, when a program or a Windows component reads or writes to a memory location that is not allocated to it. When this occurs, the program can potentially overwrite and corrupt other program code in that area of memory.
An invalid page fault may occur when parameters are passed between programs and the Windows 95 operating system. An invalid parameter may cause a program to execute invalid instructions, which results in an invalid page fault. This behavior usually occurs because a program incorrectly passes data that Windows or a Windows-based program cannot interpret.
It is important that you follow the steps in each of the sections in this article in the order in which they are presented. Because invalid page faults are typically caused when two or more programs interact, skipping steps may prolong identifying the problem.
Determine Whether the Problem Is Documented
Many Kernel32.dll errors are already documented in the Microsoft Knowledge Base and have solutions. For more information, query on the following words in the Microsoft Knowledge Base:
"invalid page fault" kernel32.dll
Note: It may be helpful to add the program name in which the problem occurs at the end of the query to narrow your search.
For additional information on related kernel32.dll error messages, please see the following articles in the Microsoft Knowledge Base:
162398—OFF97: First Aid 97 Causes Invalid Page Fault
166125—OFF97: Problems with Millennium and Mystique Video Cards
159572—OFF97: Right-Clicking File Causes Error and Computer Stops
162153—OFF97: Problems After Reawakening Suspended Computer
Do Not Install Clipart, Binder and Find Fast
It has been reported that on some systems, when you encounter this error message during setup of Microsoft Office 97, bypassing installation of Clipart, Binder and Find Fast bypasses the Kernel32.dll error message. These components are installed by default with a Typical or Custom installation. You must perform a Custom installation and choose to not install these components. To do this, follow these steps:
Quit all programs.
On the Windows Start menu, click Run.
Type in the following syntax to start Setup
<Drive>:\Setup
where \<Drive\> is the drive letter you are installing from. So if you install from a CD-ROM drive (usually drive D), the syntax would look like this:
<pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">
D:\Setup
Proceed through Setup as you normally would, but select Custom as the installation type.
Click Office Tools, and then click Change Option.
Click to clear the Clipart Gallery, Popular Clipart and Find Fast check boxes, and then click OK.
Click to clear the Microsoft Binder check box. Click Continue. Proceed through the rest of Microsoft Office 97 Setup as you normally would. If the Setup program completes without error, you can install Clipart, Binder and Find Fast by running Setup in maintenance mode.
Start Windows in Safe Mode
Windows 95 has a built-in troubleshooting mode called Safe mode. It bypasses startup files and uses only basic system drivers, including basic networking. When you start Windows in Safe mode, Windows uses only the mouse, keyboard, and standard video graphics adapter (VGA) device drivers. This makes Safe mode useful for isolating and resolving error conditions that are caused by both real-mode and Windows-based drivers. Windows 95 also has troubleshooting features that may help you identify the problem. To start Windows 95 in Safe mode and make the additional troubleshooting features available, follow these steps:
In the Control Panel, double-click the System icon, and then click the Performance tab.
Click File System, and then click the Troubleshooting tab.
Click the following check boxes to select them:
Disable protect-mode hard disk interrupt handling
Disable synchronous buffer commits
Disable all 32-bit protect-mode disk drivers
Disable write-behind caching for all drive
Click OK, click Close, and then click Yes.
Press F8 when you see the "Starting Windows 95" message.
On the Windows Startup menu, select option 3 (Safe Mode).
After Windows 95 is running again, perform the same operation that caused the error.
When you use Safe mode or when you disable 32-bit protected-mode disk drivers, Windows 95 does not process protected-mode drivers, the Autoexec.bat file, and the Config.sys file. Therefore, the CD-ROM drive is not available. To use Safe mode with CD-ROM drive support, determine whether Windows 95 uses protected-mode drivers for the CD-ROM drive. If Windows 95 is using protected mode drivers, install the real-mode (MS-DOS) drivers for the CD-ROM drive on the computer. The real-mode drivers are usually located on a disk that is shipped with the CD-ROM drive or with the computer. The drivers are installed in the Autoexec.bat and Config.sys files.
For additional information on determining if Windows 95 is using protected- mode drivers, please see the following Microsoft Knowledge Base article:
- 151634—Protected-Mode CD-ROM Drive Support in Windows 95
For additional information on installing real-mode drivers for the CD-ROM, please see the following Microsoft Knowledge Base article:
- 167069—Installing Real Mode CD-ROM Drivers for Office Installation
Disable the CD-ROM Drive Cache
If the error message appears while you are reading from a CD-ROM drive, try disabling the CD-ROM drive cache. This may make the drive more reliable but reduce performance. To disable the CD-ROM drive cache, follow these steps:
In Control Panel, double-click System.
Click the Performance tab and click File System.
Click the CD-ROM tab, click No Read-Ahead in the "Optimize access pattern for" list.
Verify that the Supplemental Cache Size slider is positioned in the far left position (the Small setting), and then click OK.
If you are using real-mode CD-ROM drive drivers, the drive may be cached by the Smartdrv.exe program. If this is the case, remark the line from the Autoexec.bat by typing "REM" (without the quotation marks) at the beginning of the line.
Check for Registry Corruption
When you start Windows 95 in Safe mode, Windows does not read the entire registry. Therefore, damage to the registry may not be evident when you run Windows in this mode. It may be necessary to replace the existing registry (System.dat) with a backup to determine whether the problem is caused by a damaged registry. To troubleshoot a damaged registry, follow these steps:
Restart the computer. When the "Starting Windows 95" message appears, press F8.
On the Windows Startup menu, select option 6 (Command Prompt Only).
To remove the file attributes from the backup of the registry, type the following command, and then press ENTER.:
c:\windows\command\attrib -h -s -r c:\system.1st
To remove the file attributes from the current registry, type the following command, and then press ENTER:
c:\windows\command\attrib -h -s -r c:\windows\system.dat
To rename the registry, type the following command, and then press ENTER:
ren c:\windows\system.dat *.dax
To copy the backup file to the current registry, type the following command, and then press ENTER:
copy c:\system.1st c:\windows\system.dat
- Restart the computer. If the Windows 95 Startup Menu displays, choose Safe Mode, or Safe Mode With Network Support if you need network connectivity.
Note: The System.1st file is a backup of the registry that is created during the final stage of a Microsoft Windows 95 installation. Therefore, the "Running Windows 95 for the first time" banner appears, and Windows 95 finalizes settings as if you reinstalled it.
If replacing the System.dat file with the System.1st file resolves the issue, the problem may be related to registry damage. Note that you may have to reinstall programs and device drivers that you installed after you installed Windows 95 to update the new registry.
If the issue is not resolved, restore the original registry. To do this, follow these steps:
Restart the computer. When the "Starting Windows 95" message appears, press F8.
On the Windows Startup menu, select option 6 (Command Prompt Only).
Type the following commands:
c:\windows\command\attrib -s -h -r c:\windows\system.dat copy c:\windows\system.dax c:\windows\system.dat
- Restart the computer.
For additional information on resolving registry errors, please see the following Microsoft Knowledge Base article:
- 131431—How to Troubleshoot Registry Errors
The steps listed in this section are also known to resolve the following error message:
Fatal Exception OE @ 0028:C025C32F in VXD.VMM (06)
Check for a Valid Temporary Folder and Excess Temporary Files
There should be at least 3 megabytes (MB) of free space on the hard disk that contains the temporary folder. To check for a temporary folder and delete excess files from that folder, follow these steps:
Close any running programs and restart your computer by clicking Shutdown on the Start menu and clicking Restart Your Computer (Microsoft Windows 95) or Restart (Under Windows NT). Press F8 when you see the "Starting Windows 95" message, and then choose "Safe mode command prompt only."
Type "set" (without the quotation marks) and press ENTER. Note the location of the TEMP variable.
Change to the folder you noted in step 2. For example, if TEMP is set to C:\WINDOWS\TEMP, type the following line and then press ENTER:
cd\windows\temp
If the folder you noted in step 2 does not exist, create the folder. For example, you can create a temporary folder called win95tmp on drive C by typing the following line at the command prompt:
<pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">
md c:\win95tmp
Delete any temporary files in this folder. Temporary files typically have a .tmp file name extension. To delete these files, type the following line, and then press ENTER:
del *.tmp
Note: Do not delete these files from within the Windows 95 graphical user interface (that is, when you are running Windows 95) because Windows 95 or a Windows program may be using one of these files.
Check the Hard Disk for Disk Errors and Fragmentation
Use the ScanDisk program to check the hard disk for lost clusters and other file allocation table (FAT) errors and to test the hard disk integrity. You can also use the ScanDisk program to repair any of these problems. To run ScanDisk, follow these steps:
On the Start menu, point to Programs.
Point to Accessories, point to System Tools, and then click ScanDisk.
Hard disks that are very fragmented can affect the performance and reliability of Microsoft Office programs and other tasks in Windows 95. To resolve this problem, run Disk Defragmenter to defragment the hard disk. To run Disk Defragmenter, follow these steps:
On the Start menu, point to Programs.
Point to Accessories, point to System Tools, and then click Disk Defragmenter.
Verify That the Compact Disc Is Clean and Unscratched
If the error message appears while you are installing from a compact disc, verify that the compact disc you are using is clean. You can wipe the compact disc with a soft, lint-free cloth. Also ensure that there are no large scratches on the compact disc. If the compact disc is damaged and unreadable, error messages may appear during installation.
Check for a Corrupted Swap File
The Kernel32.dll error may also appear if your Windows swap file is corrupted. To create a new swap file, restart the computer in MS-DOS mode, delete the Win386.swp file in the Windows folder, and then restart the computer. To create a new swap file, follow these steps:
On the Start menu, click Shut Down.
In the Shut Down Windows dialog box, click "Restart the Computer in MS-DOS Mode," and then click Yes.
At the MS-DOS prompt, switch to the Windows folder by typing the following command
cd <drive>:\Windows
where \<drive\> is the drive letter that contains the Windows folder. Typically, \<drive\> is C.
**Note**: The swap file exists in the Windows folder if Windows manages virtual memory settings on your computer. If you chose to manage virtual memory settings on the computer, the swap file exists at the root level of the hard disk. To determine whether Windows manages virtual memory settings, right-click My Computer, click Properties, click Performance, and then click Virtual Memory.
To delete the swap file, type the following:
del Win386.swp
- After you delete the swap file, restart the computer.
Corrupted Custom Profile
Corrupted custom profiles have also been known to cause Kernel32.dll errors. Deleting and recreating the profile can possibly resolve this problem.
If you are using the Microsoft Office 97 system policy templates that are included in the Microsoft Office 97 Resource Kit, you must use the version of the System Policy Editor that is included in the Microsoft Office 97 Resource Kit or the Microsoft Windows NT 4.0 Resource Kit.
Note: You can download Policy.exe, a self-extracting executable file containing Poledit.exe, from online services. Download this file from the following Web site: https://www.microsoft.com/office/ork/appa/appa.htm#dex4#dex4
note that because the Microsoft Web site is constantly updated, the site address may change without notice. If this occurs, link to the Microsoft home page at the following address: https://www.microsoft.com/
Disable Enhanced BIOS Features
Most computers have several enhanced settings that allow the computer to fully use the computer hardware. These high-speed settings can cause the system to become unstable; disabling these features may make the computer more stable. Contact your computer manufacturer for information about entering the basic input/output system (BIOS) and changing the BIOS settings. You can enter the BIOS on most systems immediately after turning on the power. Usually a keystroke (such as DEL) is required to enter the BIOS. Below are the common features that can interfere with Microsoft Office programs:
Memory Shadow RAM
Video Shadow RAM
Internal Cache
External Cache
Built-in Virus Protection
Newer chipsets may have more advanced features (such as memory wait states) that may cause errors. Most BIOS installation programs have an option to load the BIOS default settings. This option usually disables all advanced features.
Warning: Incorrectly altering hardware BIOS settings can cause serious problems that may cause your computer to fail to start or function properly. Microsoft cannot guarantee that problems that result from the incorrect setting of hardware BIOS options can be solved. Alter the hardware BIOS settings at your own risk.
Customers have reported that the Dell A02 BIOS does not work with Windows 95. This BIOS version is used on the Dell Dimension models. Dell technical support can be contacted at (800) 624-9896.
Disabling the External Cache feature on Tyan Titan III VX and Tyan Tomcat III motherboards has been known to resolve Kernel32.dll error messages. Similar problems have also been reported when using Gigabyte motherboards.
Remove and Reinstall the Program
If the problem occurs after you run the Setup program, some of the dynamic link library (DLL) files may be damaged or corrupted. To troubleshoot this problem, first completely remove the program. For additional information, please see the following Microsoft Knowledge Base articles:
158658—How to Completely Remove Microsoft Office 97
176823—OFF97: Utility to Completely Remove Remaining Office 97 Files
133274—OFF7: Setup "Remove All" Doesn't Remove All Files
129285—Office Setup Doesn't Remove All Files Using Remove All
After you completely remove the program, reinstall the program.
Check for Software Updates
Outdated and incompatible software may also cause error messages to appear. Check with the manufacturer of the computer for various software updates, such as BIOS updates, OEM Windows updates, and hardware driver updates (such as CD-ROM drive drivers). If you are using third-party partitioning software (for example, EZDrive, or Ontrack Disk Manager), verify that you have the most recent versions of these products.
The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
Microsoft released three updated files that may affect whether you receive error messages when you run Setup or when you use a Microsoft Office program. Download the Windows 95 Service Pack 1, the Kernel32.dll update, and the Ole32.dll updates from the Microsoft Web Site. Also, determine whether other updates that may pertain to your system configuration are available. To check for updated files on the Microsoft Web site, use the following address: https://support.microsoft.com/support/downloads/
Note: Because the Microsoft Web site is constantly updated, the site address may change without notice. If this occurs, link to the Microsoft home page at the following address: https://support.microsoft.com
For additional information, please see the following articles in the Microsoft Knowledge Base:
Q65416—Hardware and Software Third-Party Vendor Contact List, A-K
Q60781—Hardware and Software Third-Party Vendor Contact List, L-P
Q60782—Hardware and Software Third-Party Vendor Contact List, Q-Z
Scan the Computer for Viruses
If a virus is present on your computer and has damaged some files, Kernel32.dll error messages may appear when you use a program. Scan the hard disk and floppy disks with a virus detector. If the virus detector finds a virus on your computer, remove the virus before you run the Office program again. If a virus is found on your Setup disk, you must obtain a new set of disks.
Note: Do not run a virus detector terminate-and-stay-resident (TSR) program while you run any of the Microsoft Office programs, including the Setup program. Run a virus detector before you run the Setup program, and then disable it.
For additional information, please see the following articles in the Microsoft Knowledge Base:
105212—Office: Setup Problems May Indicate that System Has Virus
135648—Troubleshooting Win95 Application Floppy Disk Problems
If you determine that you have a Setup disk that was damaged by a virus, you can order a new set of disks. To obtain replacement disks, call the Microsoft Order Desk at (800) 360-7561 and request a replacement set of disks. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, see the Microsoft World Wide Offices Web page at: https://www.microsoft.com/worldwide/
Reinstall Windows in a New Folder
Use this method only after you try all of the troubleshooting steps in this article. If you reinstall Windows in a new folder, you must reinstall all Windows-based programs under the new Windows 95 installation.
For additional information, please see the following Microsoft Knowledge Base article:
- **178400—**OFF97: Installing Win 95 to New Folder to Tshoot Office Problems.
Check Hardware
If you exhaust all other troubleshooting steps and you are still receiving error messages, it is possible that one or more pieces of your hardware are incompatible with Windows 95 or are damaged. To identify a problem with your computer hardware, contact your computer vendor.
Badly seated memory or bad memory has been reported to cause Kernel32.dll error messages. Switching memory around in the motherboard memory banks has been known to correct some of these issues.
It has also been reported that running the Atron 380 Bus Mastering Ethernet Card can cause Kernel32.dll errors. Removing this card from the computer may resolve these error messages.
WARNING:* *The information in this article has not been confirmed or tested by Microsoft. Some or all of the information in this article has been taken from unconfirmed customer reports. ANY USE BY YOU OF THE INFORMATION PROVIDED IN THIS ARTICLE IS AT YOUR OWN RISK. Microsoft provides this information "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Microsoft TechNet
December 1998
Volume 6, Issue 12