Verifying or Modifying NIC Parameters
when a nic configuration is saved, the netware install program adds load and bind statements to the autoexec.ncf file. by accessing this file, you can verify the parameters configured for each nic, modify them, or enter additional parameters.
the novell monitor program and the config command are also useful for verifying driver configuration. for information on how to use these programs, see the utilities reference in your novell netware online documentation.
the parameters that can be defined in the load statements are described in the table in "installing novell netware server 4.2" on page 51. a valid autoexec.ncf file is shown below. one set of load and bind commands (in bold) is shown for each frame type the nic is configured to support.
set time zone = pst8pdt
set daylight savings time offset = 1
set start of daylight savings time = (april sunday first 2:00:00 am)
set end of daylight savings time = (october sunday last 2:00:00 am)
set default time server type = single
set bindery context = o=lan
# warning!
file server name novellserver51
# warning!
# if you change the name of this server, you must update
# all the licenses that are assigned to this server. using
# nwadmin, double-click a license object and click
# certificate assignments. if the old name of
# this server appears, you must delete it and then add the
# new server name. do this for all license objects.
serverid 1c8ee2c
load odineb.nlm
load tcpip
load b57 slot=2 frame=ethernet_802.2 name=b57_1_e82
bind ipx b57_1_e82 net=fafd3d25
load b57 slot=2 frame=ethernet_802.3 name=b57_1_e83
bind ipx b57_1_e83 net=5a2d8d6d
load b57 slot=2 frame=ethernet_snap name=b57_1_esp
bind ipx b57_1_esp net=477a35bd
load b57 slot=2 frame=ethernet_ii name=b57_1_eii
bind ipx b57_1_eii net=c3c8f2e4
bind ip b57_1_eii addr=172.16.1.1 mask=ff.ff.ff.0
mount all
search add sys:\java\bin
search add sys:\java\nwgfx
if you modify any nic parameters, you must reboot the system before the changes will take effect. if you make changes and do not reboot, you may experience configuration problems. if the driver was loaded at console, however, no reboot is necessary.