About the Windows for Workgroups Resource Kit

This guide is organized in seven parts that provide specific details about Windows for Workgroups architecture, installation and setup, networks, configuration, new and updated accessories, and troubleshooting.

Part 1: Technical Overview

•	Chapter 1, "Networking—A Technical Discussion," contains information targeted toward the support professional that may not have a local area network (LAN) background. This chapter provides a technical discussion of networking concepts and discusses the components that make up a LAN.
•	Chapter 2, "Windows for Workgroups Architecture," describes the architecture used by Windows for Workgroups and discusses the components of Windows for Workgroups that differentiate it from Windows version 3.1.

Part 2: Installation and Setup

•	Chapter 3, "Windows for Workgroups Installation," contains a technical discussion of the Wndows for Workgroups Setup program, details about setting up Windows for Workgroups on a network, and instructions for creating a custom installation routine for automated setup.
•	Chapter 4, "Windows for Workgroups Files," describes the purpose for each file installed by Windows for Workgroups in the WINDOWS directory and the Windows SYSTEM subdirectory.
•	Chapter 5, "Windows for Workgroups Setup Information Files," contains the details you need to understand to create custom Windows for Workgroups setup information files (SETUP.INF, NETWORK.INF, CONTROL.INF, APPS.INF, and OEMSETUP.INF) for multiple installations.
•	Chapter 6, "Windows for Workgroups Initialization Files," describes the contents of Windows for Workgroups initialization files, including WIN.INI, SYSTEM.INI, PROTOCOL.INI, MSMAIL.INI, and SCHDPLUS.INI, and explains how you can change entries in these files.

Part 3: Special Topics

•	Chapter 7, "Additional Windows for Workgroups Information," contains tips about using Microsoft Windows for Workgroups. This chapter also discusses special topics related to the components of Windows for Workgroups.
•	Chapter 8, "Network Integration with Microsoft LAN Manager and Novell NetWare," contains information about integrating a Windows for Workgroups workstation into an existing LAN environment. Topics covered include integrating Windows for Workgroups with Microsoft LAN Manager and Novell® NetWare® networks.

Part 4: Configuring Windows for Workgroups

•	Chapter 9, "Tips for Configuring Windows for Workgroups," presents tips about configuring your system, both for gaining optimal performance and for creating custom Windows for Workgroups configurations.

Part 5: Using Windows for Workgroups

•	Chapter 10, "New and Updated Accessories," discusses accessories new for Windows for Workgroups and provides new information about Windows 3.1 accessories that have been updated for Windows for Workgroups.
•	Chapter 11, "Network Dynamic Data Exchange," discusses how Dynamic Data Exchange (DDE) functionality has been extended to the network environment to enable information to be exchanged dynamically with other workstations in your Windows for Workgroups workgroup.
•	Chapter 12, "Mail," includes information about the Mail application provided with Windows for Workgroups. The architecture of Mail, tips for customizing Mail, and information about integrating Mail with other Windows-based applications are discussed in this chapter.
•	Chapter 13, "Schedule+," includes information about the Schedule+ application provided with Windows for Workgroups. Schedule+ architecture and key features of interest to system administrators are discussed in this chapter.

Part 6: Troubleshooting Windows for Workgroups

•	Chapter 14, "Troubleshooting Windows for Workgroups 3.1," provides specific information for troubleshooting problems with Windows for Workgroups, showing the key steps for isolating and solving common problems.

Part 7: References, Resources, and Appendixes

This part of the Windows for Workgroups Resource Kit contains a glossary, a directory of information resources, a configuration guide for Mail, information about using additional protocols with Windows for Workgroups, and an index.

Top of page

Conventions in This Manual

This document assumes that you have read the Windows for Workgroups 3.1 documentation set and that you are familiar with using menus, dialog boxes, and other Windows features. It also assumes that you have installed Windows for Workgroups on your system and that you are using a mouse with Windows. For keyboard equivalents to the actions described here, see the Microsoft Windows for Workgroups online Help.

This document uses several conventions to help you identify information.

Document Conventions

The following table describes the typographical conventions used in the Windows for Workgroups Resource Kit.

Type style	Used for
bold	MS-DOS® command names such as copy or dir, switches such as /? or /3, section and entry names in .INI and .INF files such as [386Enh] or emmexclude=, and text that you type to carry out actions at the command prompt.
italic	Parameter values for which you can supply specific values. For example, to supply a value for a parameter that calls for a filename, you must type a specific filename such as MYFILE.EXE.
ALL CAPITALS	Directory names, filenames, and acronyms. For example, "WINDOWS" is used to represent the Windows main directory, and "SYSTEM" represents the Windows System subdirectory. When you type directory names and filenames at the command prompt or in a dialog box, lowercase letters may be used.

Other conventions in this document include:

•	"Windows" refers to Microsoft Windows version 3.1 or later (including Windows for Workgroups).
•	"MS-DOS" refers to Microsoft MS-DOS version 3.1 or later.

•	The Microsoft Windows logo appears in the margin to highlight specific features that are new to Windows for Workgroups 3.1 or updated from Windows 3.1.
•	"Windows-based application" is used as a shorthand term to refer to an application that is designed to run with Windows and does not run without Windows. All Windows applications follow similar conventions for the arrangement of menus, style of dialog boxes, and keyboard and mouse use.
•	"MS-DOS-based application" is used in this document as a shorthand term to refer to an application that is designed to run with MS-DOS but not specifically with Windows and is not able to take full advantage of Windows features (such as graphics or memory management).
•	"Command prompt" refers to the command line where you type MS-DOS commands. Typically, you see characters such as "C:\>" to show the location of the command prompt on your screen. When Windows is running, you can double-click the MS-DOS Prompt icon in Program Manager to use the command prompt.
•	An instruction to "type" any information means to press a key or a sequence of keys, and then press the ENTER key.
•	Mouse instructions in this document, such as "Click the OK button" or "Drag an icon in File Manager," use the same meanings as the descriptions of mouse actions in the Windows for Workgroups User's Guide and the Windows online tutorial.

Check the glossary at the end of the Windows for Workgroups Resource Kit for definitions of terms that you are unfamiliar with.

Syntax Conventions

"Syntax" refers to the order in which you must type an item such as an MS-DOS command with its switches or an entry in a Windows initialization (.INI) file. Elements that appear in bold must be typed exactly as they appear in the syntax example. Elements that appear in italic are placeholders for parameter values for which you must supply specific information.

Unless specified otherwise, you can type commands, keynames, parameters, and switches in either uppercase or lowercase letters.

This example shows the syntax for a SYSTEM.INI entry, with each item in the sample explained in the following table.

[section]
keyname=value, string, source, destination

Entry item	Definition
[section]	The name of a section in an initialization file or setup information file. The enclosing brackets ([ ]) are required, and the left bracket must be in the leftmost column on the screen—f example, [standard].
keyname	The name of an entry, which usually can consist of any combination of letters and digits. For many entries described in this document, the keyname must be followed immediately by an equal sign (=)—f example, run=.
value	An integer, a string, or a quoted string, depending on the entry.
string	A group of characters to be treated as a unit. A string can include letters, numbers, spaces, or any other characters. Sometimes the syntax definition will indicate that the string must be enclosed in double quotation marks (" ").
source	The location of data to be transferred to a specific destination or to be used as input to a command. Source can consist of a drive letter and colon, a directory name, a filename, or a combination of these elements.
destination	A location to which the data specified by source is to be transferred.
	Destination can consist of a drive letter and colon, a directory name, a filename, or a combination of these elements.