\HELP\NETWARE\CLIENT32.TXT
NETGEAR FX310TX Fast Ethernet PCI Adapter
-----------------------------------------
Novell Client 32 Driver Installation for Windows 95 and DOS/Windows
-------------------------------------------------------------------
Getting Started
---------------
The necessary driver files for Client32 installation are stored in
a self-extracting compressed format. The FA310TX Client32 driver
and the related LDI files need to be extracted prior to driver
installation.
Client 32 for Windows 95
------------------------
Microsoft Windows 95 does not come bundled with the Client32 driver
for the NETGEAR FA310TX adapter. You must go through the following
procedure to install the device driver into the Windows 95 system for
the adapter to function correctly.
The Windows 95 installation disks or CD and the Novell Client32 diskettes
are needed to complete this installation. Similar procedure can be
followed for Microsoft Windows 98.
Installation Procedure
----------------------
This procedure assumes that Windows 95 and Novell Client 32 has been
successfully installed into the system prior to installing the FA310TX
adapter card.
1. Copy the compressed file NETWARE.EXE from the \NETWARE directory
of the driver diskette into your hard disk. Execute NETWARE.EXE
at MS-DOS prompt to extract the drivers. The Client32 driver
and the necessary LDI file are stored in the 32BITLAN sub-directory.
Make a note of the target path where the drivers are installed.
2. Shut down the computer and install the FA310TX adapter into the system.
3. Start your Windows 95 PC normally. Upon power up, the system will
indicate to you that new hardware has been found and the necessary
driver is being installed for the new hardware.
4. Click no when asked if you want to restart your computer.
5. When the system is started, open "My Computer" -> "Control Panel"
-> "Networks" icons.
6. If any of the following strings exist,
"PCI Ethernet DECchip 21040 Based Adapter"
"PCI Fast Ethernet DCEchip 21140 Based Adapter"
"PCI Ethernet DECchip 21041 Based Adapter"
You are currently using the Windows 95 built-in DECchip driver.
Make sure that you remove all of them before proceeding to the
following steps.
7. Select "Add adapter" -> "Have disk" icons.
8. When asked where the new driver is availble, provide the path where
the Client32 driver was priviously extracted.
9. Select the NETGEAR FA310TX Fast Ethernet PCI Adapter.
10. The system will copy the appropriate driver files into the operating
system. At this monent, Windows 95 will also copy the necessary files
from the Windows 95 CD-ROM and Novell Client32 diskette. Prepare your
Windows 95 CD-ROM or Novell Client32 diskettes for this process.
11. After finishing file copying, the system will ask you to restart the
system. Select YES to reboot.
12. During system boot up, the operating system will automatically detect
the NETGEAR FA310TX Fast Ethernet PCI adapter and install the driver for
the adapter.
Troubleshooting
---------------
1. Symptom: Even after the previously described procedure, Windows 95
still indentifies the FA310TX adapter card as some other vendor's
card.
Explanation: When a device driver is installed into Windows 95, the
device driver's accompanying information file (INF file) is copied
into the /WINDOWS/INF directory. Upon start up, Windows 95 looks
into the INF files in the /WINDOWS/INF directory for the PCI device ID
number that matches the one on the PCI adapter card. The first one
that Windows 95 finds, it identifies the physical device as the one
described in the INF file.
However, there might be PCI adapter cards coming from different
manufacturers using the same controller chip. There is only one vendor
ID and device ID for each controller chip. The Sub_vendor ID is what
differentiate one hardware manufacturer's card from another.
Since Windows 95 operates on a first come first serve basis, the
FA310TX's INF file, NGRPCI.INF, should be placed on the top of the
directory list for the adapter card to be correctly recognized and
Windows 95 to load the proper driver.
Solution:
The utility program provided in the driver disk, PUTINF32.BAT, is
provided to place the FA310TX INF file, NGRPCI.INF on top of the
directory list.
PUTINF32.BAT will to do the following.
Eg. > PUTINF32.BAT C:\WINDOWS ; assuming C:\WINDOWS is Windows 95
; default directory.
a. In Windows 95, go to the C:\WINDOWS\INF directory.
b. Remove the old NGRPCI.INF file (if it exists).
c. Create a temporary directory and copy all the files from the
\WINDOWS\INF directory to this temporary directory.
d. Delete all the files (*.INF) in the \WINDOWS\INF directory.
e. Copy the new NGRPCI.INF into \WINDOWS\INF directory.
f. Copy all the files from the temporary directory back to the
\WINDOWS\INF directory. Remove the temporary directory.
2. Symptom: No error appears in Device Manager and the NETGEAR FA310TX
driver is properly intalled. But you still have difficulty browsing
and locating other systems on the network.
Solution:
a. Check and make sure that you have unique computer names for each
computer in the whole network. You can change your computer
name in:
"My Computer" -> "Control Panel" -> "Network" -> "Identification"
b. Check and make sure that the adapter is properly connected to a
network device (eg. HUB) and the "connection type" for this adapter
is set to "AutoSense" or the correct connection type. You can
check it in:
"My Computer" -> "Control Panel" -> "Network" -> "Properties"
Select the "Advanced" tab to modify the operating speed or duplex
mode.
Possible selections are: Autosense, 10Base-T, 10Base-T full_duplex,
100Base-TX, 100Base-TX full_duplex.
Client 32 for DOS/ Windows 3.1X
-------------------------------
Install DOS Client 32 Driver During Client 32 Installation
----------------------------------------------------------
1. Copy the compressed file NETWARE.EXE from the \NETWARE directory
of the driver diskette into your hard disk. Execute NETWARE.EXE
at MS-DOS prompt to extract the drivers. The Client32 driver
and the necessary LDI file are stored in the 32BITLAN sub-
directory.
Make a note of the target path where the drivers are installed.
2. Shut down the computer and install the FA310TX adapter into the
system.
3. At MS-DOS prompt, start the Client 32 installation by executing
the "INSTALL" command.
4. Follow the installation procedure of Novell NetWare Client 32.
5. In "Select a LAN Driver Type" window, select "32-bit" LAN driver.
Note: You can also choose the "16-bit" LAN driver selection if
If you wish to use the 16-bit DOS ODI driver.
6. In "32-Bit Network Board Drivers" window, select "USER SPECIFIED
32-BIT DRIVER".
7. In "Insert The Driver Disk" window, input the path where the .LAN
driver and .LDI files were previously extracted.
eg. C:\NETWARE\32BITLAN for installing the 32-bit driver
C:\NETWARE\ODI.DOS for installing the 16-bit driver
8. Select "NETGEAR FA310TX Fast Ethernet PCI Adapter Driver"
and the desired parameters, eg. Media Type, Frame Type, Node
Address .. and continue the installation procedure.
Note: The Media Type default is AutoDetect and the other
options are
LINE_SPEED=10
LINE_SPEED=10
TP_FULL_DUPLEX LINE_SPEED=10
TP_FULL_DUPLEX LINE_SPEED=100
9. After the installation, a STARTNET.BAT batch file will be created.
Please check the STARTNET.BAT file for the right parameters.
Install Windows 3.1X Client 32 Driver During Client 32 Installation
-------------------------------------------------------------------
1. In Microsoft Windows environment, run "SETUP" command to start
Client 32 installation.
2. In "ODI Driver Selection" window, select "32 bit" mode and "Other
Boards".
3. Enter the path and filename of the ODI driver in "ODI Driver Path"
window. For exmaple, C:\NETWARE\32BITLAN\NGRPCI.LAN.
4. Follow the installation setps of Novell NetWare Client 32.
5. After the installation, a STARTNET.BAT batch file will be created.
Please check the STARTNET.BAT file contains the right parameters.
Install Client 32 Driver After Novell NetWare Client 32 for
DOS/Windows 3.1x is already installed
-----------------------------------------------------------
Copy the LAN driver, NGRPCI.LAN, and the LDI file, NGRPCI.LDI, from the
\32BITLAN directory to the \Novell\Client32 directory, and use a text
editor to edit the STARTNET.BAT file directly.
If desired, the 16-bit driver, NGRPCI.COM, and its associated INS file,
NGRPCI.INS, from the \ODI.DOS directory can be used.
Content of STARTNET.BAT (for 32-bit LAN driver)
-----------------------------------------------
SET NWLANGUAGE=ENGLISH
C:\NOVELL\DOSCLNT\NIOS.EXE
LOAD C:\NOVELL\CLIENT32\LSLC32.NLM
LOAD C:\NOVELL\CLIENT32\CMSM.NLM
LOAD C:\NOVELL\CLIENT32\ETHERTSM.NLM
LOAD C:\NOVELL\CLIENT32\NGRPCI.LAN FRAME=ETHERNET_802.2 SLOT=??
LOAD C:\NOVELL\CLIENT32\NGRPCI.LAN FRAME=ETHERNET_802.3 SLOT=??
LOAD C:\NOVELL\CLIENT32\NGRPCI.LAN FRAME=ETHERNET_II SLOT=??
LOAD C:\NOVELL\CLIENT32\NGRPCI.LAN FRAME=ETHERNET_SNAP SLOT=??
LOAD C:\NOVELL\CLIENT32\IPX.NLM <-- Binding driver
LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM <-- Finding server
Parameters supported by the NGRPCI.LAN driver
-----------------------------------------------------------------
SLOT 1 - Forces the driver to search for the specified board
AUTOSENSE - This keyword configures the adapter to conduct
NWay Auto-negotiation to determine the network
speed and the duplex mode of the network connection.
TP - This keyword selects the UTP port on the
adapter; either "TP" or "TP_FULL_DUPLEX" must be
used together with the "LINE_SPEED" keyword.
TP_FULL_DUPLEX - This keyword selects twisted pair connection to
work in full duplex mode; either "TP" or
"TP_FULL_DUPLEX" must be used together with the
"LINE_SPEED" keyword.
LINE_SPEED - This keyword selects line speed between 10Mbps and
100Mbps on the network card. This keyword must be
used in together with the keywords "TP" or
"TP_FULL_DUPLEX".
Format: LINE_SPEED=<value>
Allowed values are: 10,100
For example, to force the network adapter to operate at 100Mbps and
half duplex, use the following line in STARTNET.BAT or the NetWare
prompt:
: LOAD C:\NOVELL\CLIENT32\NGRPCI.LAN TP LINE_SPEED=100
Content of STARTNET.BAT (for 16-bit DOS driver)
-----------------------------------------------
SET NWLANGUAGE=ENGLISH
C:\NOVELL\CLIENT32\NIOS.EXE
C:\NOVELL\CLIENT32\LSL.COM
C:\NOVELL\CLIENT32\N16ODI.COM
C:\NOVELL\CLIENT32\NESL.COM
C:\NOVELL\CLIENT32\NGRPCI.COM
LOAD C:\NOVELL\CLIENT32\LSLC32.NLM
LOAD C:\NOVELL\CLIENT32\PC32MLID.LAN
LOAD C:\NOVELL\CLIENT32\TCPIP.NLM
LOAD C:\NOVELL\CLIENT32\IPX.NLM <-- Binding driver
LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM <-- Finding server
Parameters supported by the NET.CFG for NGRPCI.COM driver
-----------------------------------------------------------------
Link Driver NGRPCI
Frame Ethernet_802.2
Frame Ethernet_802.3
Frame Ethernet_II
Frame Ethernet_SNAP
;Optional driver keywords:
;TP ;Selects half-duplex mode.
;TP_FULL_DUPLEX ;Selects full-duplex mode
;AUTOSENSE
;Line_Speed 100 ;Selects between 10Mbps or 100Mbps port & line
;speed. Default is 100Mbps.
NetWare DOS Requester
FIRST NETWORK DRIVE = F
NETWARE PROTOCOL = NDS BIND
NOTE: You can run the NetWare Client installation program for each
workstation type from the CLIENT directory under SYS:PUBLIC or
directly from the CD-ROM.
TroubleShooting
---------------
If you experience the "Command Line Parameter for NGRPCI" warning
message when STARTNET.BAT is executed, provide the slot number
at the command line in STARTNET.BAT as illustrated below.
> LOAD C:\NOVELL\CLIENT32\NGRPCI.LAN FRAME=ETHERNET_802.3 SLOT=1
SLOT must be the correct value as found by the driver.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.