Support Home Contents Search Contact Us Intel Home Intel(r)
resources spacer graphic
Software & Drivers
spacer graphic
Troubleshooting
spacer graphic
Compatibility
spacer graphic
Manuals &
Literature

spacer graphic
Year 2000
spacer graphic
Intel Forum
spacer graphic
spacer graphic
spacer light bulb Intel Support
spacer graphic
spacer graphic EtherExpress™ Classic LAN Adapters
NetWare Server Driver [FL32LAN.EXE]

EtherExpress™ adapter FLASH32 NetWare* v4.x and v3.12 file server driver (F32.LAN v6.11). This archive contains the EtherExpress FLASH32 Novell NetWare 4.10 and NetWare 3.12 file server driver with v2.50 of the Novell NetWare ETHERTSM.NLM, MSM.NLM, and MSM311.NLM.

Also includes OEMSETUP.INF for F32.LAN for use with the Novell Windows NT* Requestor.

disk FL32LAN.EXE: Size:128200 Date:Jan 30,1996


textReadme of Archive FL32LAN.EXE
textDirectory of Archive FL32LAN.EXE





















Readme of Archive [FL32LAN.EXE]

Intel EtherExpress(TM) Flash32 LAN Adapter 
Version 6.11 of FL32.LAN


File Name:    		SIZE:   DATE:     Description:
------------    	------  --------  ----------------------------------------
FL32     LAN  		36,193  08-09-95  Flash 32 v6.11 NetWare* 4.10 server driver
FL32     LDI     	 6,554  08-15-95  Flash 32 v6.11 NetWare 4.x install file 
OEMSETUP INF  		33,771  08-15-95  Flash 32 NT Requester installation file 

\NLM4X\MSM      NLM    	20,252  11-23-94  Novell NetWare 4.x NLM  v2.50
\MLM4X\ETHERTSM NLM      9,362  11-29-94  Novell NetwWare 4.x NLM v2.50

\NLM312\MSM31X   NLM    21,308  11-23-94  Novell NetWare 3.12 NLM v2.50
\NLM312\ETHERTSM NLM     9,362  11-29-94  Novell NetwWare 3.12 NLM v2.50

\NLM311\MSM31X   NLM    21,308  11-23-94  Novell NetWare 3.11 NLM v2.50
\NLM311\ETHERTSM NLM     9,362  11-29-94  Novell NetwWare 3.11 NLM v2.50
\NLM311\PATCHMAN NLM     9,632  10-05-93  Novell NetWare 3.11 NLM V2.30
\NLM311\LSLENH	 NLM    11,641  10-05-93  Novell NetwWare 3.11 NLM V1.01
\NLM312\MONITOR  NLM   117,775  10-26-92  Novell NetWare 3.11 NLM V1.75



For 4.x Servers:
========================
You may need to load the following NLMs: 
   
       MSM.NLM       (11-23-94 v2.50)
       ETHERTSM.NLM  (11-29-94 v2.50)
   
Make sure you use these (or later) versions. Earlier versions won't work
properly.If you can log in to the server, copy the driver to the SYSTEM
subdirectory. If you do this, you won't need to specify a path on the load
line.  If you copy it to another directory, make sure the LOAD statement
includes the correct path.


For 3.12 Servers:
=================
You may need to load the following NLMs: 
   
       MSM31X.NLM    (11-23-94 v2.50)
       ETHERTSM.NLM  (11-29-94 v2.50)
   
Make sure you use these (or later) versions. Earlier versions won't work
properly. If you can log in to the server, copy the driver to the SYSTEM
subdirectory. If you do this, you won't need to specify a path on the load
line.  If you copy it to another directory, make sure the LOAD statement
includes the correct path.


For 3.11 Servers:
=================
You may need to load the following NLMs: 
   
       MSM31X.NLM    (11-23-94 v2.50)
       ETHERTSM.NLM  (11-29-94 v2.50)
       PATCHMAN.NLM  (10-05-93 v2.30)
       LSLENH.NLM    (10-05-93 v1.01)
       MONITOR.NLM   (10-26-92 v1.75)
   
Make sure you use these (or later) versions. Earlier versions won't work
properly. If you can log in to the server, copy the driver to the SYSTEM
subdirectory. If you do this, you won't need to specify a path on the load
line.  If you copy it to another directory, make sure the LOAD statement
includes the correct path.



TO LOAD THE DRIVER:
===================

   
   1. Before starting the server, copy the updated FL32.LAN and NetWare NLMs 
      driver a directory on the hard drive of the server.
   
      If you can log in to the server, copy the driver to the \SYSTEM
      subdirectory. If you do this, you won't need to specify a
      path on the load line.  If you copy it to another directory,
      make sure the LOAD statement includes the correct path.
   
  
   2. Start the server. At the server console, issue the load and
      bind statement(s) in this order:
  
	For NetWare 4.x:
 
        LOAD \MSM
        LOAD \ETHERTSM
        LOAD \FL32 SLOT=x FRAME=y NAME=z 
 

        For NetWare 3.12:     

        LOAD \MSM31X
        LOAD \ETHERTSM
        LOAD \FL32 SLOT=x FRAME=y NAME=z
        
	
	For NetWare 3.11:

  	LOAD \PATCHMAN
        LOAD \LSLENH  
        LOAD \MSM31X
        LOAD \ETHERTSM
        LOAD \FL32 SLOT=x FRAME=y NAME=z
	



Optional FL32.LAN parameters:
=============================
There are several Optional parameters that are used with the FLASH 32
adapters:

FIFO 

Range: 2-15		DEFAULT setting: FIFO=12 
FIFO defines the threshold for requesting bus access. For systems with high
bus latency, this setting should be increased.  For systems with very low
latency, this setting may be reduced. For best performance, this should be
set as low as possible without causing DMA over/underruns.

ON  

Range: 1-65535 		DEFAULT Setting: ON=200
The ON parameter limits the number of clock cycles the EtherExpress(TM) Flash32
adapter will hold the bus for data transfers.  For best performance, this
setting should be high enough for the Transmit FIFO, to be filled, or the
Receive FIFO emptied in a single bus access.  The default setting for this
parameter is 10 to insure wider compatibility.

OFF  

Range:1-65535 		DEFAULT Setting: OFF=2
This parameter is the minimum number of clock cycles the EtherExpress Flash32
adapter card will remain off the bus between data transfers. For best
performance, this setting should be set to a minimum, thus allowing the
Flash32 access as needed.

Example:

        LOAD \MSM
        LOAD \ETHERTSM
        LOAD \FL32 SLOT=x FRAME=y NAME=z FIFO=15 ON=10 OFF=100




NetWare server hanging or workstations lose connection to Flash32.
==================================================================
Description:

This problem could be caused by long wait states on the EISA bus. The
situation occurs when the PC gives long wait states when the memory
controller is doing some cache line manipulations while a bus master owns
the EISA bus.  These long wait states cause the Flash32 to hold the bus
too long and generate an EISA busmaster time out. This situation often occurs
in systems with several EISA bus master adapters, or in systems with PCI and
EISA busses.

Solution:

There are a two options to try.

1. Check the CMOS of the PC and look for settings fro WRITE BACK CACHE or
WRITE THROUGH CACHE. Enable the WRITE THROUGH.  Changing this parameter
should eliminate the problem of long wait states, although it may increase
CPU utilization.

2. Another method to avoid the bus time out problem is by using ON/OFF
parameters for the Flash32 to get it on and off the EISA bus earlier. The
ON/OFF timers provide a throttling mechanism to control how the 82596
requests bus ownership.  The units for the number is local clock periods
(25MHz clock). The ON parameter limits the number of clock cycles that the
card will hold the bus for on data transfers.  The default value is 200. The
OFF parameter sets the minimum number of clock cycles that the card will
remain off the bus between data transfers. The default value is 2. Thus a low
ON number causes the 596 to transfer data in a series of short bus-ownership
cycles (arbitration cycles) rather than fewer, longer transfers. Although
this may seem less efficient, the individual data transfer cycles actually
run at the same speed either way, so there is very little affect on
throughput.  One may have to try different values for these numbers.
Suggested values are ON=10, OFF=10 or ON=20, OFF=2

For NetWare server driver, the syntax would be as follows.

	LOAD FL32 SLOT=3 ON=10 OFF=10


Note for Multiple Frame Types:

The FL32.LAN driver will first parse the command line parameters to obtain
the ON/OFF values but the given parameters are used to initialize the 82596
only for the first instance of the driver (the first frame type loaded).
ON/OFF values should ONLY be given for the first frame type loaded on each
Flash 32 adapter.

*other brands and names are the property of their respective owners

Return to the
top of the document.

Directory of Archive [FL32LAN.EXE]

FileNameFileSizeFileDate
!136096-01-29
fl32.lan3619395-08-09
fl32.ldi655495-08-15
oemsetup.inf3377195-08-15
fl32lan.txt756696-01-30
nlm311/ethertsm.nlm936294-11-29
nlm311/msm31x.nlm2130894-11-23
nlm311/lslenh.nlm1164193-10-05
nlm311/monitor.nlm11777592-10-26
nlm311/patchman.nlm963293-10-05
nlm312/ethertsm.nlm936294-11-29
nlm312/msm31x.nlm2130894-11-23
nlm4x/msm.nlm2025294-11-23
nlm4x/ethertsm.nlm936294-11-29

Return to the top of the document.

spacer graphic

 
 
did you find your answer
spacer graphic
Please tell us if the information provided here was useful.
Yes   No   Partially   I have to try it
Please describe what you were looking for:
   
spacer graphic  
 
To top of page
spacer graphic
* Legal Information and Privacy Policy © 2000 Intel Corporation