Working with the NET.CFG File

The NET.CFG file is typically located in the same directory as the Novell transport software. Specifications in the NET.CFG file are in plain ASCII text, and may be edited using any text editor, such as the EDIT utility that comes with MS-DOS 6.22. (Word processors should not be used to create or modify this file). To avoid any confusion, be sure that there is only one NET.CFG file on your system.

Each line of text in NET.CFG will be categorized as:

1. a comment line,

2. an empty line,

3. a section header, or

4. a parameter within a particular section.

Comments lines contain a semi-colon (';') as the first visible character on the line; spaces and/or tabs may precede the semi-colon.

Empty lines have no text or other visible characters; they are typically found between sections of text to improve the readability of the file's contents.

Section headers have text starting at the very beginning of the line; there can not be any spaces or tabs preceding the section header text.

Parameters must begin with at least one space or tab character before the parameter text; that means they will appear indented. Each parameter line belongs with, or applies to, the section header that most immediately precedes it. The relative order of parameters within any particular section is, as a general rule, not significant; however, there are a few exceptions to that rule which will be pointed out as needed. A parameter may have one or more values which will be given on the same line immediately following the parameter text.

A section, therefore, consists of a section header line and one or more parameter lines indented below the section header. The relative order of sections in NET.CFG is, as a general rule, not significant; however, there are a few exceptions to that rule which will be pointed out as needed. Each network software module scans the file for information pertaining to its own functions and ignores the remainder of the file. If a parameter is not given in NET.CFG, then the module looking for it will use the default value for that parameter.

As a final note, remember that all alphabetic text within the NET.CFG file is treated in a case-insensitive manner; e.g., an 'A' is the same as an 'a'. Capitalization of some or all letters in the text is simply a matter of personal preference. Thus, “Ethernet_II”, “ethernet_ii”, and “ETHERNET_II” are all considered equivalent to each other.

Note: Additional reference material on configuration options for Novell's 16-bit TCP/IP Transport for DOS can be found in Novell's online documentation at:

http://occam.sjf.novell.com:8080/iamg.lwp50.english/transenu/1.toc

Note: Additional reference material on configuration options for Novell's 16-bit IPX network software and related NET.CFG options can be found in Novell's online documentation at:

http://occam.sjf.novell.com:8080/nw410.english/ws_d2enu/1.toc