This guide is for anyone who uses or administers a NeTraverse Merge system and wants to understand more about how NeTraverse Merge operates and how it can be customized. It complements your UNIX documentation, but it is not meant to be a complete administrator's guide for the UNIX operating system. For complete information on using the UNIX operating system, including comprehensive descriptions of commands, refer to the Operating System User's Guide and the System Administration Guide. This guide covers NeTraverse Merge on the OpenServer, UnixWare 7 and OpenUNIX 8 systems.

You will find the information you need more quickly if you are familiar with:

• ``How this guide is organized''

• ``Typographical conventions''

Although we try to present information in the most useful way, you are the ultimate judge of how well we succeed. Please let us know how we can improve this guide.

Other documents

• Release Notes
  The Release Notes include installation and removal instructions for NeTraverse Merge, as well as the current limitations and known problems. The Release Notes are also the place for additional or late-breaking information that did not make it into the User's Guide. There are also some tips about how to best make use of NeTraverse Merge.
• Manual Pages
  The manual pages document the command line utilities.

• ``About this guide'' provides an overview of the contents of this guide and gives a list of the notational conventions used.

• Chapter 1, ``Getting started with NeTraverse Merge'', shows you how to use NeTraverse Merge to start and stop a NeTraverse Merge session.

• Chapter 2, ``Installing Windows'', explains how to install Microsoft® Windows.

• Chapter 3, ``Working in the NeTraverse Merge environment'', describes the default NeTraverse Merge environment that NeTraverse Merge makes available to you, including the ways in which it differs from a stand-alone DOS or Windows environment.

• Chapter 4, ``Configuring DOS and Windows sessions'', shows you how to use the various NeTraverse Merge tools to change the default environment to suit your needs.

• Chapter 5, ``NeTraverse Merge resource administration'', describes how to administer your system's hardware resources for use with NeTraverse Merge.

• Chapter 6, ``Using NeTraverse Merge from the command line'', describes how to run and configure NeTraverse Merge sessions from the command line.

• Chapter 7, ``Mixing Windows and UNIX'', describes how to effectively use Windows and the UNIX system together.

• Appendix A, ``X server issues'', describes the special setup of your X server or X terminal that is required to use NeTraverse Merge.

• Appendix B, ``National language support'', describes NeTraverse Merge features that support local languages in an environment shared by the Windows and UNIX operating systems.

• Appendix C, ``Filename mapping'', describes how NeTraverse Merge maps long filenames to short DOS compatible names.

Example . . . . . . . . Used for:

lp, lp(C) or lp(1)

commands, device drivers, programs, and utilities

The letter (used with OpenServer) or number (used with UnixWare and OpenUNIX) in parentheses indicates the reference manual section in which the command, driver, program, or utility is documented.

/new/client.list

files, directories, and desktops

root

system, network, or user names

filename

placeholders (replace with appropriate name or value)

<Esc>

keyboard keys

Exit program?

system output (prompts, messages)

yes or yes

user input

Cancel

button names

Edit

menu names

Copy

menu items

File > Find > Text

sequences of menus and menu items

$HOME

environment or shell variables

To help us implement your suggestions, include relevant details, such as the chapter, section name, and document version. We would appreciate information on how to contact you in case we need additional explanation.

To contact us, use the card at the back of the OpenServer Handbook or write to us at:

Technical Publications
Attn: CFT
The Santa Cruz Operation, Inc.
PO Box 1900
Santa Cruz, California 95061-9969
USA

or e-mail us at:

techpubs@sco.com or ... uunet!sco!techpubs

Thank you.