Situation:
You want to configure your Windows 95/98/Me system to run at peak efficiency, or you are troubleshooting system/software problems.
Solution:
This document contains a number of configuration changes that can be made to Windows 95/98/Me to ensure that it runs efficiently, and that no system settings are preventing Windows from using its resources effectively. It is not intended to resolve any specific problems, although in some cases it will resolve problems caused by incorrect settings.
The following topics are covered in this document: (You may click on the links below to jump ahead)
How to check the hard drive for problems [Back to menu]
Problems with the hard drive, such as bad sectors, can cause problems when running any software. In addition, a badly fragmented hard drive can cause programs to run slower than expected. Please closely follow the instructions in each section for the best results, as well as to avoid any additional problems.
NOTE: The following instructions are for ScanDisk and Disk Defragmenter that are provided with Windows. You may view more detailed instructions on these two important programs by visiting our section on them.
ScanDisk
ScanDisk is a Windows utility that examines hard drives for errors, damage, or defects, either to data or to the physical drive. We recommend that you check for such problems before you make any of the system changes discussed in this document.
Please follow these steps to run ScanDisk:
Disk Defragmenter
Disk Defragmenter is a Windows utility that organizes the way files are stored on the hard drive. A hard drive is composed of many sections, known as "sectors". Frequently, as files are written to the hard drive, they are divided into noncontiguous parts. This slows down the system because the file must be retrieved from different locations before it can be used. It also wastes space and increases the chances of files becoming damaged. Disk Defragmenter reassembles these file fragments so that each file is in only one location. We recommend that you run Disk Defragmenter before you make any of the system changes discussed in this document.
Please follow these steps to run Disk Defragmenter:
How to check for programs that load at startup [Back to menu]
When you install programs, they may configure themselves to load along with Windows. You may not know they are loading because they may run in the background. This can become a problem as more programs load with Windows and, therefore, reduce the amount of resources available to other programs.
Within the program
You can prevent most programs from loading with Windows through an "Option" or "Properties" menu within the program. Configure the program so that it does not load with Windows (or at Startup), and then restart the computer.
From the StartUp folder
Some programs create shortcuts in the StartUp folder to load with Windows. Follow these steps to move the shortcuts to a different location and see whether this solves the problem:
From the Windows registry
Some programs load from the Windows registry. You can temporarily prevent these from loading for testing purposes. For detailed instructions on how to do this, please see our section covering this topic.
System settings in the Config.sys file [Back to menu]
Settings in the Config.sys file can sometimes be configured incorrectly when programs - particularly older Windows or DOS programs - are installed. If they are not set correctly, then they may be limited by Windows default settings. Follow these steps to ensure that the Config.sys file is optimized:
FILES=200
FILES=250
BUFFERS=80,0
STACKS=12,256
DEVICE=C:\WINDOWS\HIMEM.SYS /M:1
(The /M:1 switch commands Himem.sys to identify the processor.)
System settings in the System.ini file [Back to menu]
The System.ini file is another place where configuration settings can affect how your system performs. Please follow the instructions in each section to ensure that the System.ini file is optimized.
Real Mode (16-bit) drivers
This is most frequently seen on computers that have been upgraded from older operating systems. In this case, the System.ini file may contain references to old 16-bit drivers that can cause problems with newer, 32-bit programs. Follow these steps to remove these 16-bit drivers:
NOTE: Skip steps 1 and 2 if the System Configuration Editor is already open.
Here is an example:
In this sample System.ini file, the second line of the [386Enh] section, device=mydriver,
does not have an * as does device=*dynapage.
[386Enh]
device=*dynapage
device=mydriver
Comment out the device=mydriver line by typing a semicolon and then a space to the left of the line, so that it looks like:
[386Enh]
device=*dynapage
; device=mydriver
7. Click the File menu, and then click Save to save your changes. Close the System.ini file, or, (recommended), go on to the next section.
[vcache]
Minfilecache=512
Maxfilecache=6144
Chunksize=512
System settings in the Win.ini file [Back to menu]
In some cases, 16-bit programs can also load from the Win.ini file. Follow these steps to check this:
NOTE: Skip steps 1 and 2 if the System Configuration Editor is already open.
If the Win.ini file now has:
[Windows]
load=c:\cctrol.exe
run=c:\wizard\wiz.exe
then type a semicolon and a space before each line so it is:
[Windows]
; load=c:\cctrol.exe
; run=c:\wizard\wiz.exe
System settings in the Autoexec.bat file
NOTE: Skip steps 1 and 2 if the System Configuration Editor is already open.
SET DOS16M=2
This line should be added as the first line before any other lines in the Autoexec.bat file. Its function is to extend memory in DOS for strings of information over 64 characters in length.
Temporary files [Back to menu]
Windows programs often need to temporarily store information on the hard drive. This is almost always done when installing software, but occurs at other times as well, for example when reindexing a database, extracting compressed files, or when using some programs such as Microsoft Word. This information is saved in a designated "Temp" folder. In some cases these files will have the ".tmp" extension. Windows - or the program which created them - is supposed to delete these files when they are no longer needed. Because this does not always happen, large numbers of temporary files can accumulate in the Temp folder. This can slow computer operation and cause other problems. In addition, corrupted temporary files can cause installation failures or, in some cases, can cause programs or the computer to stop responding.
To prevent this, you should regularly clean out files (and subfolders) that have accumulated in the C:\Windows\Temp folder. In some cases, you should change the location of the Temp folder. Please follow the instructions in each section to do this.
Enable show all files
Follow these steps to make sure that Windows is set to show all files:
WARNING: If your TEMP or TMP variables point to one of the following locations, then DO NOT follow the instructions in this section. Instead, proceed to the section titled Problems with Temp locations.
Problems with Temp locations
By default, Windows places the Temp folder in C:\Windows\Temp. Other locations, such as C:\Temp, or even another drive, are perfectly acceptable as long as there is room on the drive. There are, however, several locations - most often seen on older, upgraded computers - that can cause serious problems. They are:
SET TEMP=C:\Windows\Temp
SET TMP=C:\Windows\Temp
NOTE: If Windows is installed to a different location, then change this accordingly, so that both point to the Temp folder that is located in the folder where you have Windows installed.
Virtual memory [Back to menu]
Even computers with large amounts of RAM (memory) do not always have enough memory for every function. To work around this problem, Windows uses a portion of the hard drive for temporary memory storage. This is called virtual memory, also known as a swap file. This file is used to hold data for which there is not currently room in memory, as well as data that Windows is not currently using, but may need again soon. Because of this, you need a virtual memory allocation even if you have large amounts of RAM in the computer. The swap file can be placed on any local drive; we recommend that you have at least 100 MB of free space on this drive.
How to create a permanent swap file
By default, Windows will use whatever free space is available for its swap file. This is inefficient, and can slow down the computer, especially if the hard drive is highly fragmented. (See first section for information on defragmenting the hard drive.) It can also be misleading; when it is not in use, it does not take up space, so you may be led to believe you have more space than you will have when programs are running. To avoid this, you can create a permanent swap file with a fixed size. The recommended size of a swap file is 1.5 times the size of the physical RAM, so if you have 64 MB of RAM, a good swap file size might be 160 MB.
NOTES:


Following these instructions will enable you to troubleshoot different problems, as well as optimize Windows to run at peak performance. Remember, it is STRONGLY advised that you back up files before altering them in case you make a mistake or something goes wrong. If you have any questions, ask them first! Drop us an email and let us know how we can help you.
 
Copyright 1998-2001 ISC Unlimited ©. All rights reserved. Terms of Use. Privacy Statement.