Windows Configuration
Proper configuration of Windows is critical for optimal performance. There are three methods for managing or changing Windows configuration: Control Panel, Windows Setup, and .INI files.
Control Panel
The primary method for changing the Windows configuration (and the one familiar to most users) is to use the Control Panel. This is a Windows application (found in the Main Program Group) that provides a visual way to make changes.
By selecting icons and using the associated dialog boxes, a user can customize the working environment. The following items can be changed from the Control Panel:
- Screen colors
- Other desktop options (such as screen savers and wallpaper)
- Fonts
- Printer
- Keyboard
- Mouse
- International settings
- COM port settings
- Network settings
- Date and time
- Sounds (used by system)
- Drivers for hardware
- Multitasking and virtual memory settings
Windows Setup
Windows setup will operate from within Windows if it is already loaded-click the Setup icon in the Main Group. Or it will start from MS-DOS-type SETUP when in the Windows directory. Using setup should be done only by experienced computer users. The results of improper setup can be disastrous-Windows won't run. If this happens, you can use the MS-DOS version of setup. From an MS-DOS prompt, change to the Windows directory and type the command SETUP.
Windows Initialization Files
The third method for modifying Windows configuration is to edit the Windows .INI files. As with the setup method, this should be used only by experienced operators. The Windows .INI files, which are found in the Windows directory of the bootable drive, initialize (configure) everything from device drivers to applications. Windows itself creates at least three .INI files, and any application can create initialization files of its own. Knowing how and what to edit in these files is critical to repairing and optimizing the performance of a computer.
You can use any text editor to edit .INI files. (MS-DOS provides a program for editing text files called EDIT. This program can be run from the MS-DOS prompt.) All .INI files are broken up into logical areas called groups. Each group starts with a line of text, in square brackets, called a group header. Underneath each group are its settings. They are organized as item=settings.
For example, see the following PROGMAN.INI file:
Windows uses two .INI files for configuration: SYSTEM.INI and WIN.INI. The SYSTEM.INI is the Windows version of the MS-DOS CONFIG.SYS file. It initializes all the resources. The WIN.INI file is like the AUTOEXEC.BAT used by MS-DOS. It defines the "personalization" of Windows such as screen savers, colors, fonts, associations, and how resources will interact with applications. The WIN.INI file is also the dumping ground for settings that do not seem to have a home anywhere else. The information stored in these two files holds the secret to operating, optimizing, and troubleshooting Windows. Even though Windows has SYSTEM.INI and WIN.INI, it still uses the CONFIG.SYS and AUTOEXEC.BAT files of MS-DOS for the basic setup of devices and the computer. Windows also needs to use the MS-DOS files to configure the machine so that it (Windows) can run.
Windows 3.x and Windows 95 offer a utility called SYSEDIT.EXE in the Windows\System directory that lets you edit the context on the WIN.INI, SYSTEM.INI, CONFIG.SYS, and AUTOEXEC.BAT files quickly within Windows, using a notepad-like editor.
NOTE
Starting with Windows 95, most of the tasks performed by SYSTEM.INI and WIN.INI are now performed by the Registry.
Configuring the SYSTEM.INI File
To know SYSTEM.INI is to understand Windows. This file is the primary hardware configuration file for Windows. During installation, Windows creates all the sections in SYSTEM.INI, which, for the most part, should never be changed. However, one section-[386Enh]-is very important. Most of the problems associated with Windows (as opposed to Windows applications) that users encounter can be directly attributed to problems within this section.
The [386Enh] section stores all the values for 386 Enhanced Mode. Some of the more important items are:
- 32BitDiskAccess=On/Off: 32-bit disk access can be turned off here if Windows won't start. If Windows won't start and you suspect this is the problem, use the win /d command. By starting Windows with this switch, you bypass 32-bit access. If Windows is OK, then turn this option off through the Virtual Memory/Change Menu in the Control Panel 386 Enhanced Menu, or just change on to off.
- ComXIRq=Number: This is where a COM port number and the port's IRQ are defined. Useful with devices that require nonstandard COM ports.
- EMMExclude=XXXX-XXXX: This command tunes the operation of the EMM range by excluding memory ranges that are required for specific drivers, thereby avoiding possible conflicts. Before Plug and Play, this command was often the only way to get some device drivers to load. Note that whenever an item=XXXX-XXXX statement is used in an EMM386 line or in the CONFIG.SYS file, an equivalent EMMExclude statement is required in this section of the SYSTEM.INI file.
- EmmInclude=XXXX-XXXX: This command is the reverse of the preceding EMM command, allowing one to force inclusion of memory areas that might otherwise be left unused.
- Max:Bps=768: Intermittent General Protection Faults (GPFs) can be caused by too few breakpoints. If this line is not in [386Enh] add it.
The following is an example of the [386Enh] section of a SYSTEM.INI file:
The [Boot] section lists the drivers that must be loaded when Windows starts. Windows might not work if you incorrectly modify or delete one of these settings.
Configuring the WIN.INI File
The WIN.INI file is not required, and Windows will run without it. However, it can be helpful. Two important commands used in WIN.INI are:
- Load=
- Run=
These lines autoload programs when Windows starts. They act like a hidden Startup Group. (Any program icon placed in the Startup Group of the Program Manager will automatically start when Windows is started.) If a program continues to automatically load and run, and it has no icon in the Startup Group, it's being loaded in WIN.INI. The difference between Load and Run is that programs invoked by Run will start minimized.
NOTE
Systems that have been upgraded to Windows 95 and 98 from Windows 3.1 might still have this file. Although it is not required-nor will Windows 95 or 98 create this file-Windows will use the file if it already exists. In that case, any Run and Load statements in this file will be activated as it was previously by Windows 3.1.
The WIN.INI file contains settings that affect the appearance of the Windows desktop, printer selections, and network connections. To edit this file, use the Control Panel or open it in any text editor (the Windows application Notepad will do the job). Close and save the file after you're done editing it.
NOTE
Windows needs to be rebooted before any changes to WIN.INI take effect. Be very careful when editing-a single typo will cause an error or unexpected results.
The WIN.INI file contains several sections of related settings. Each section is defined by its header, which is displayed in square brackets [Windows]. Within each section are entries in the format keyname=value:
- Keyname is the name of the setting.
- Keynames are made up of digits and letters with no spaces.
- Keynames must be immediately followed by an equal sign (=).
- Value can be an integer, a string, or a quoted string.
- Comments are preceded by a semicolon (;) and they work like the REM statements in CONFIG.SYS or AUTOEXEC.BAT files.
- Always backup the WIN.INI file before editing.
The [Windows] section of the WIN.INI file makes changes to the Windows environment-for example which applications run when Windows is started, and how information appears on the screen. Some of its parameters are:
- DoubleClickHeight=<pixels>: Specifies the height (in pixels) that the mouse can move between clicks when it is double-clicked. Default is 4. If movement exceeds this value, the double-click will be interpreted as two single clicks.
- DoubleClickWidth=<pixels>: Specifies the width (in pixels) that the mouse can move between clicks when it is double-clicked. Default is 4. If movement exceeds this value, the double-click will be interpreted as two single clicks.
- Load=<filename(s)>: Specifies applications to run (minimized) when Windows is started. Can include one or more filenames or applications-each must be separated by a space.
- MenuDropAlignment=<0-or-1>: Specifies whether menus open right-aligned or left-aligned with the menu title. 0 means left-aligned and 1 means right-aligned.
- Programs=<extensions>: Defines which files Windows considers to be applications. Defaults are .COM, .EXE, .BAT, and .PIF files.
- Run=<filename(s)>: When started, Windows will run any application listed.
The [Desktop] section contains optional settings that control the appearance of the screen background and the positioning of windows and icons on the screen. Most of these setting can be changed using the Control Panel.
The [Fonts] Section of WIN.INI describes the fonts to be loaded when Windows starts.
Configuring the CONTROL.INI File
All sections in the CONTROL.INI file can be changed from the Control Panel. This is the recommended method. The following are the sections in the CONTROL.INI file:
- [Current]: The current color scheme.
- [Color schemes]: Descriptions of color schemes.
- [Patterns]: Descriptions of the desktop patterns.
- [Installed]: Installed device drivers.
- [Screen Saver]: The current password used by the active screen saver (encrypted).
- [Screen Saver.xxxxx]: Individual screen saver settings.
- [Don't load]: This setting can be used to exclude items that are displayed in the Control Panel. List the name of the section to be excluded followed by "=1".
For example, you might want to edit the CONTROL.INI file directly if the screen-saver password has been forgotten. The screen-saver password can be removed by changing the following:
Configuring the PROGMAN.INI File
This file controls the settings for the Program Manager Group files. Adding a section to PROGMAN.INI called [Restrictions] will add some protection for the group files. If these statement are not present, the value is assumed to be the default of 0, which means that the opposite of the statement will happen. The commands and syntax are:
- NoRun=1: Disables the File Run command.
- NoClose=1: Prevents the user from exiting Windows.
- NoSaveSetting=1: Prevents the Program Manager layout from being saved on exit.
- NoFileMenu=1: Removes the File menu from the Program Manager.
- EditLevel=x: From 0, the default, to 4, establishes higher levels of restrictions.
NOTE
Setting attributes as "read-only" can protect individual groups. To do this, locate the .GRP file in the File Manager, select File, next select Properties, and then check the Read Only check box.
Using Sysedit
Windows provides a program for editing the system files (AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, SYSTEM.INI). This program resides in the Windows directory and is called Sysedit. Windows does not provide an icon for this program in the standard setup. However, if no icon exists, Sysedit can be run by selecting File and then Run from the Program Manager, and then typing Sysedit and pressing ENTER. If an icon does not exist, it can be created by selecting New from the File menu in the Program Manager.