HP Vectra VE C/xxx 7 HP Vectra VE C/xxx Series 7 PC - Network Administration G - Page 46

LAN Manager 2.x DOS and OS/2 Client Driver

Get HP Vectra VE C/xxx 7 PDF manuals and user guides View all HP Vectra VE C/xxx 7 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 46 highlights

3 Installing Microsoft Network Drivers LAN Manager 2.x DOS and OS/2 Client Driver LAN Manager 2.x DOS and OS/2 Client Driver The hardware for the Microsoft LAN Manager environment may be configured to run as an OS/2 client, enhanced MS-DOS client, or a basic MS-DOS client. Refer to the Microsoft documentation for hardware and software requirements. The PCnet Family NDIS 2.01 driver is located in the MSLANMAN.DOS and MSLANMAN.OS2 directories. The directory structure provided on the LAN Disk has been set up for automatic installation. This section provides a brief explanation regarding driver installation. Follow the guidelines in the Microsoft LAN Manager Installation Guide for more details about installing the PCnet Family driver from the LAN Disk. LAN Manager has a SETUP program that may be used to import and configure drivers. The SETUP utility for LAN Manager will install the PCnet NDIS driver that is provided on the LAN Disk. SETUP requires that two information files be present in order to install the drivers: NIF, and PROTOCOL.INI. These files are located in the MSLANMAN.OS2 and MSLANMAN.DOS directories of the LAN Disk. The NIF file provides the information that the SETUP utility needs to coordinate and install the various drivers that are available. Information that is contained in the two files includes driver names, paths on the LAN Disk where the driver is stored, and the type of driver. The PROTOCOL.INI file is used by the LANMAN Protocol manager and NETBIND program at startup time. This file contains the NDIS and Transport specific parameters for the network. Both NDIS (PCnet driver) and Transport (NETBEUI) have their own PROTOCOL.INI, and when SETUP installs NDIS and Transport, the two PROTOCOL.INI files will be merged into one file. 46 English

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
3
Installing Microsoft Network Drivers
LAN Manager 2.x DOS and OS/2 Client Driver
46
English
LAN Manager 2.x DOS and OS/2 Client Driver
The hardware for the Microsoft LAN Manager environment may be configured to
run as an OS/2 client, enhanced MS-DOS client, or a basic MS-DOS client. Refer to
the Microsoft documentation for hardware and software requirements. The PCnet
Family NDIS 2.01 driver is located in the MSLANMAN.DOS and MSLANMAN.OS2
directories.
The directory structure provided on the LAN Disk has been set up for automatic
installation. This section provides a brief explanation regarding driver installation.
Follow the guidelines in the
Microsoft LAN Manager Installation Guide
for more
details about installing the PCnet Family driver from the LAN Disk.
LAN Manager has a SETUP program that may be used to import and configure
drivers. The SETUP utility for LAN Manager will install the PCnet NDIS driver that
is provided on the LAN Disk. SETUP requires that two information files be present
in order to install the drivers: NIF, and PROTOCOL.INI. These files are located in
the MSLANMAN.OS2 and MSLANMAN.DOS directories of the LAN Disk.
The NIF file provides the information that the SETUP utility needs to coordinate
and install the various drivers that are available. Information that is contained in the
two files includes driver names, paths on the LAN Disk where the driver is stored,
and the type of driver.
The PROTOCOL.INI file is used by the LANMAN Protocol manager and NETBIND
program at startup time. This file contains the NDIS and Transport specific
parameters for the network. Both NDIS (PCnet driver) and Transport (NETBEUI)
have their own PROTOCOL.INI, and when SETUP installs NDIS and Transport, the
two PROTOCOL.INI files will be merged into one file.