.TOPIC:
Contents
1STEP Help Menu Netware ODI Driver
Technical Support Netware Client 32 Driver
MPX2 Driver Netware Server 4.11 Green River
Netware Server Driver
NDIS Driver Windows for Workgroups 3.11
LAN Manager Windows NT
LAN Server Windows 95
LANtastic Windows 98
SCO Unix r3.2 v4 DEC PATHWORKS
SCO Unix r3.2 v5 SUN PC-NFS
Packet Driver
[TAB]: Forward [SHIFT+TAB]: Backward [C]: Contents [E]: Exit
.TOPIC:
1STEP Help Menu
[ 1Step Help Menu ]
< Function Key>
Software Installation
F1 : Help
F2 : Install Driver
F3 : Update Driver
F6 : Dos Shell
F10: Exit
< Control Key >
ALT : Menu
ARROWS : Change parameter
TAB : Move cursor forward
SHIFT+TAB: Move cursor backward
ALT : List parameters
ESC : Exit
-- THE END --
.TOPIC:
Technical Support
EN166x Ethernet Adapter Technical Support
=========================================
Accton provides free technical support to registered users
at one of the following numbers:
Accton Taiwan
Phone: (03) 5770-270 8:00am to 6:00pm
FAX: (03) 5770-267
Accton USA
Phone: (949) 707-4847 7:00am to 5:00pm Pacific Time
(888) 398-4101
FAX: (949) 707-2460
Internet address: support@accton.com.tw
To obtain software upgrades connect via ftp to ftp.edu.tw
-- THE END --
.TOPIC:
MPX2 Driver
MPX2 DRIVER INSTALLATION
========================
File Description
----------------
a. MPX2PNP.COM is Accton's new MPX2 DOS/ODI driver
It is included in your Driver Diskette
(\DOS\MPX2PNP.COM)
High performance MPX2 DOS/ODI driver
------------------------------------
MPX2PNP.COM is Accton's MPX2 DOS/ODI driver which can improve network
performance not only for Netware 3.11 but also for Netware 4.xx.
To use MPX2PNP, it is not necessary to change the server driver, just run
it in client site for a big improvement in performance.
LSL
MPX2PNP -----------> MPX2 workstation driver
IPXODI
NETX
-- THE END --
.TOPIC:
Netware ODI Driver
NetWare DOS/ODI WORKSTATION DRIVER INSTALLATION
===============================================
This file describes the contents of the \DOS
subdirectory. For more detailed information about
NetWare installation, please refer to the
"NOVELL NetWare ODI Shell for DOS" manual.
List Of Files You Need
----------------------
------------------------------------------------------
Filename Description
------------------------------------------------------
LSL.COM This file implements the Link Support
Layer for DOS ODI workstations
and is the program that is generally
loaded first when booting. The Link
Support Layer file enables the
workstation to communicate over
several protocols.
IPXODI.COM This is Novell's protocol stack for
DOS ODI workstations. It performs
the same functions as IPX.COM, which
is used for DOS workstations. However
it is optional and is loaded after the
LAN driver. Other protocols can be loaded
in its place or with it. This is one
of the key features of the ODI
environment.
NETX.COM NetWare Network program.
--------------------------------------
If you use You Need
--------------------------------------
Conventional memory NETx.COM
Expanded memory EMSNETx.EXE
(LIM 4.0 EMS Compatible)
Extended memory XMSNETx.EXE
(XMS 2.0 compatible)
---------------------------------------
NETBIOS.EXE The Netbios emulation program
(INT 5CH interface) allows you to
run Netbios application programs
based on the NETBIOS.EXE
interface. The run sequence is:
a. IPX shell driver
IPX.COM
NETBIOS.EXE ---> netbios emulation
... interface
b. DOS ODI driver
LSL.COM
MPX2PNP.COM ---> Accton MPX2 DOS ODI driver
IPXODI.COM
NETBIOS.EXE
...
RXMONSTK.COM RXMONSTK.COM is a Receive Monitor Utility for
Monitor Type Applications (Such as Lan Analyzer)
If the monitor type applications you are using seem to
stop receiving network packets when you install a new LAN
driver on your workstation, load the RXMONSTK.COM file.
Load the RXMONSTK.COM file after the LSL.COM driver but
before the LAN driver. The RXMONSTK.COM operates as a TSR
and requires 2684 bytes of memory. You can load only one
LAN driver when using the RxMonStk.
The run sequence is:
LSL.COM
RXMONSTK.COM
MPX2PNP.COM ---> Accton MPX2 DOS ODI driver
IPXODI.COM
...
Installation Procedure:
=======================
Before you start the installation process, make sure that
the adapter is properly installed and configured. Make sure
that your NetWare operating system is properly installed.
1. Run the following commands in the order given below and
press <Enter>:
lsl
MPX2PNP
ipxodi
netx
2. You can now log onto your network.
-- THE END --
.TOPIC:
Netware Client 32 Driver
NetWare* Client 32 for Windows* 95 and DOS/Windows 3.1x
======================================================================
Refer to the appropriate section for either Windows* 95 or
DOS/Windows 3.1x Client 32 installation.
General Installation of Client 32 with Windows 95 using Accton's 32 bit
LAN driver
-------------------------------------------------------------------------
Prerequisites:
a. Windows 95 operating system installed.
b. NetWare Client 32 for Windows 95 archive file and any patch files.
c. Access to the Windows 95 CD or CAB files, since Client 32
installation will ask for it.
1. If the Accton EN166X adapter is being installed for the first
time when Client 32 is being added, install the adapter hardware as
described in the Installation Guide and go to step 2. If the adapter is
already installed on the Windows 95 system, go to step 3.
2. When Windows 95 is restarting, it may display the message "Windows has
found new hardware and is installing software for it". Select the
option labeled "Do not install a driver (Windows will not prompt you
again)" then click OK.
3. Run the SETUP.EXE program for Client 32. It is located in the
\PRODUCT\WIN95\IBM_ENU subdirectory of the Client 32 software.
4. On the NetWare Client 32 Installation screen, make sure the "Upgrade
NDIS driver to ODI, if available" box is checked if you are replacing
the NDIS driver with ODI.
5. On the Recommended NetWare Client 32 properties screen, set the
appropriate settings for the version of NetWare you are using.
6. The Client 32 installation program will copy files. It may ask for the
source of the Windows 95 installation files. Click OK and then enter
the correct path to the files.
7. When Client 32 installation finishes, you must reboot in order
for the changes to take effect.
General Installation of Client 32 with DOS/Windows 3.1x
------------------------------------------------------------------------
1. From the Novell NetWare Client 32 software, run INSTALL.EXE.
2. Select the NetWare Client 32 products you want to install on
your workstation from the list:
[X] NetWare Client 32 for DOS
[X] NetWare Client 32 for Windows
[ ] NetWare TCP/IP protocol stack[ ] NetWare IP (TCP/IP Required)
[ ] Desktop SNMP
[ ] HOSTMIB for SNMP (SNMP Required)
[ ] NetWare TSA for SMS
Note - "NetWare Client 32 for DOS" and "NetWare Client 32 for
Windows" are usually selected by default.
3. From the Customize Support for Windows menu, specify if you want to
use multiple country codes or if you want to set the shared Windows
path. The default for both of these is NO.
4. From the Select LAN Driver Type menu, select "32-bit LAN drivers".
Copy ACC6X.LAN and ACC6X.LDI onto a disk.
In the Novell installation process, select "USER SPECIFIED 32 BIT DRIVER."
5. From the Insert the Driver Disk menu, insert the disk with the
acc6x.lan and acc6x.ldi files, and then specify the path to those
files.
6. From the Installation Configuration Summary, verify the default
settings for Client 32 are correct, or modify as necessary.
Modify AUTOEXEC.BAT and CONFIG.SYS [YES]
Client Directory: C:\NOVELL\CLIENT32
Windows Directory: C:\WINDOWS
LAN driver type: 32-bit LAN drivers
LAN driver: Accton EN166X MPX LAN Adapters
7. Novell NetWare will now copy the files to your workstations and
modify the configuration files to match your selected configuration.
Hints and Tips
--------------
1. If you are using multiple frame types, you will get the following
message when you load the driver:
"Do you want to load another frame type for a previously loaded
board? Y/N"
The way to avoid this is to uniquely identify the card in the STARTNET.BAT
LOAD C:\NOVELL\CLIENT32\ACC6X.LAN FRAME=ETHERNET_802.2
PORT=<PORT_NUM>
2. Check for a LASTDRIVE statement in the CONFIG.SYS file. You must have
LASTDRIVE=Z in config.sys when using Client 32.
3. Verify that you have FIRST NETWORK DRIVE = <SOME DRIVER LETTER LESS THAN z>
in the NET.CFG file under the NetWare DOS Requester section.
NOTE: NET.CFG is position sensitive, so be careful to indent lines
with TWO spaces or one tab as shown above in the example.
Sample Configurations
---------------------
Below are sample files from a Novell NetWare Client 32 workstation with an
Accton EN166X MPX adapter installed using the default
installation:
CONFIG.SYS
----------
DEVICE=C:\WINDOWS\HIMEM.SYS
BUFFERS=30,0
FILES=60
LASTDRIVE=Z
AUTOEXEC.BAT
------------
prompt $P$G
path=C:\WINDOWS;C:\DOS;C:\NOVELL\CLIENT32\
SET TEMP=C:\TEMP
@CALL C:\NOVELL\CLIENT32\STARTNET
STARTNET.BAT
------------
SET NWLANGUAGE=ENGLISH
C:\NOVELL\CLIENT32\NIOS.EXE
LOAD C:\NOVELL\CLIENT32\LSLC32.NLM
LOAD C:\NOVELL\CLIENT32\CMSM.NLM
LOAD C:\NOVELL\CLIENT32\ETHERTSM.NLM
LOAD C:\NOVELL\CLIENT32\ACC6X.LAN PORT=300 FRAME=ETHERNET_802.2
LOAD C:\NOVELL\CLIENT32\ACC6X.LAN PORT=300 FRAME=EHTERNET_802.3
LOAD C:\NOVELL\CLIENT32\IPX.NLM
LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM
NOTE: If you are loading multiple frame types, you will need to
specify UNIQUELY IDENTIFY the adapter on the load lines. See the
Hints and Tips section above for detailed information.
NET.CFG
-------
NetWare DOS Requester
FIRST NETWORK DRIVE F
NetWare PROTOCOL NDS BIND
Protocol IPX
IPX SOCKETS 40
*Third-party trademarks are the property of their respective owners.
-- THE END --
.TOPIC:
Netware Server 4.11 Green River
SOFTWARE INSTALLATION INSTRUCTIONS
FOR NOVELL NetWare VERSION 4.11 ODI SERVER DRIVER
=================================================
The driver is based on the latest version 3.3 of the ODI specification.
\NetWare\ACC6X.LAN Novell NetWare version 4.11 Server Driver
\NetWare\ACC6X.LDI Installation Information File for
Novell NetWare version 4.11 Server Driver
==============================
GENERAL INSTALLATION PROCEDURE
==============================
1. Install NetWare 4.11.
Complete the software installation procedures for the NetWare 4.11
server. See the Novell documentation for installing NetWare.
2. Update the server with files from the Support Disk for Accton EN166X.
NetWare 4.11 provides two different ways to load a new LAN driver.
One method is to copy the new file(s) onto the server and then
either load the driver by typing on the command line or edit
AUTOEXEC.NCF to load the driver. The other method is (1) to load
INSTALL.NLM and use it to select and load your new driver and
(2) to edit AUTOEXEC.NCF.
Manual Loading of Server Driver
===============================
1. Start the server. Load and bind the Accton server driver.
2. At the NetWare prompt (indicated by a colon), load the driver:
load D:\acc6x
bind ipx to acc6x net=X
D is the path to the server driver.
X is the NetWare Network number you choose.
3. Add the load and bind statements to your server's AUTOEXEC.NCF
file, so that the adapter driver loads automatically each time
the server starts.
Using INSTALL.NLM
=================
1. At the NetWare prompt, load the INSTALL.NLM program.
2. Select "LAN Driver Options (Configure/Load/...)" and [ENTER].
3. Press [INSERT] to specify other drivers to install.
4. Press [F3]. Enter the driver path, for example, "a:\netware"
5. Select the ACC6X.LAN driver in your selection list to start the
driver loading and binding procedure.
==============
Hints and Tips
==============
1. Installing multiple adapters:
If installing multiple adapters, each adapter must have a
different NET number and SLOT number. Also, it is a good idea to
name each adapter. Example:
load D:\acc6x slot=3 name=LAN_A
bind ipx to LAN_A net=222
load D:\acc6x slot=5 name=LAN_B
bind ipx to LAN_B net=333
2. Installing one adapter with multiple frame types:
When binding multiple frame types to one adapter, enter a LOAD and
BIND statement for each frame type. Each LOAD statement uses the same
SLOT number, but each BIND statement needs a unique network number.
NetWare 3.12 allows up to four different frame types, and the adapter
supports all four, as follows:
Ethernet_802.3
Ethernet_802.2
Ethernet_II
Ethernet_SNAP
.
==============
ERROR MESSAGES
==============
"The board cannot be found."
Possible cause: The adapter does not exist or driver does not
recognize the adapter.
Solution: Check that the Accton EN166X adapter is fully seated in the
correct slot.
"Board RAM failed the memory test."
Possible cause: The RAM buffer on the adapter failed.
Solution: Try a different Accton EN166X adapter.
"The board did not respond to the initialization command."
Possible cause: The driver recognized the adapter but the adapter
fails to respond.
Solution: Try a different Accton EN166X adapter.
"Adapter current mode is not supported or card not found."
Possible cause: The current adapter mode is not supported.
An example is NE1000 mode.
Solution: Run the SETUP utility on the support disk, and reset the
mode to NE2000.
"There is no cable connecting to adapter."
Possible cause: The adapter is not connected to the network cable,
or the adapter's transceiver has failed.
Solution: Check the cable connections and try again.
-- THE END --
.TOPIC:
Netware Server Driver
SOFTWARE INSTALLATION INSTRUCTIONS
FOR NOVELL NetWare VERSION 3.12 and 4.X (except 4.11)
ODI SERVER DRIVER
=====================================================
The driver is based on the latest version 3.3 of the ODI specification.
\NetWare\ACC6X.LAN Novell NetWare 3.12, 4.0, 4.1 Server Driver
\NetWare\ACC6X.LDI Installation Information File for
Novell NetWare 3.12, 4.0, 4.1 Server Driver
==============================
GENERAL INSTALLATION PROCEDURE
==============================
1. Install NetWare server.
Complete the software installation procedures for the NetWare
server. See the Novell documentation on how to install NetWare.
2. Copy the Accton driver and NetWare Loadable Modules from the Support
Disk for Accton EN166X.
While running DOS on the server computer, copy the Accton NetWare server
driver (ACC6X.LAN) and all the NetWare Loadable Modules from the
support disk to the DOS directory containing the NetWare server. For
example, if the support disk is in floppy drive A: and the server
is in the C:\NWSERVER directory (for NetWare 4.X except NetWare 4.11),
or is in the C:\SERVER.312 directory (for NetWare 3.12), execute
the following DOS commands:
For NetWare 3.12:
=================
copy a:\netware\acc6x.lan c:\server.312
copy a:\netware\312nlm\ethertsm.nlm c:\server.312
copy a:\netware\312nlm\msm31x.nlm c:\server.312
copy a:\netware\312nlm\nbi31x.nlm c:\server.312
In AUTOEXEC.NCF file, You must add the following three lines
before loading and binding the server driver (ACC6X.LAN).
load c:\server.312\nbi31x.nlm
load c:\server.312\msm31x.nlm
load c:\server.312\ethertsm.nlm
For NetWare 4.X (except NetWare 4.11):
======================================
copy a:\netware\acc6x.lan c:\nwserver
copy a:\netware\410nlm\ethertsm.nlm c:\nwserver
copy a:\netware\410nlm\msm.nlm c:\nwserver
copy a:\netware\410nlm\nbi.nlm c:\nwserver
In AUTOEXEC.NCF file, You must add the following three lines
before loading and binding the server driver (ACC6X.LAN).
load c:\nwserver\nbi.nlm
load c:\nwserver\msm.nlm
load c:\nwserver\ethertsm.nlm
If you can log onto the server, copy the files to the SYSTEM
subdirectory. If you do this, you won't need to specify a path on
the load line. If you copy the files to another subdirectory,
you'll need to specify the correct path.
Note: Be sure to obtain other patch files required for 3.12, 4.X
(except 4.11) available from Novell:
312PTx.EXE, 410PTx.EXE
("x" is the number indicating the latest
revision of the patch or archive file)
3. Start the server. Load and bind the Accton server driver.
4. At the NetWare prompt (indicated by a colon), run the driver
program:
load D:\acc6x
bind ipx to acc6x net=X
D is the path to the server driver.
X is the NetWare Network number you choose.
5. Add the load and bind statements to your server's AUTOEXEC.NCF
file, so that the adapter driver loads automatically each time the
server starts.
==============
Hints and Tips
==============
1. Installing multiple adapters:
If installing multiple adapters, each adapter must have a
different NET number and SLOT number. Also, it is a good idea to
name each adapter. Example:
load D:\acc6x slot=3 name=LAN_A
bind ipx to LAN_A net=222
load D:\acc6x slot=5 name=LAN_B
bind ipx to LAN_B net=333
2. Installing one adapter with multiple frame types:
When binding multiple frame types to one adapter, enter a LOAD and
BIND statement for each frame type. Each LOAD statement uses the
same SLOT number, but each BIND statement needs a unique network
number.
==============
ERROR MESSAGES
==============
"The board cannot be found."
Possible cause: The adapter does not exist or driver does not
recognize the adapter.
Solution: Check that the Accton EN166X adapter is fully seated in the
correct slot.
"Board RAM failed the memory test."
Possible cause: The RAM buffer on the adapter failed.
Solution: Try a different Accton EN166X adapter.
"The board did not respond to the initialization command."
Possible cause: The driver recognized the adapter but the adapter
fails to respond.
Solution: Try a different Accton EN166X adapter.
"Adapter current mode is not supported or card not found."
Possible cause: The current adapter mode is not supported.
An example is NE1000 mode.
Solution: Run the SETUP utility on the support disk, and reset the
mode to NE2000.
"There is no cable connected to the adapter."
Possible cause: The adapter is not connected to the network cable,
or the adapter's transceiver has failed.
Solution: Check the cable connections and try again.
-- THE END --
.TOPIC:
NDIS Driver
NDIS Driver Installation Overview
=================================
The drivers you need are in the directories MSLANMAN.DOS
and NDIS2. The NDIS drivers contained in these
subdirectories are used with 3Com 3+Open, Microsoft
OS/2 LAN Manager OEM distribution, Release 1.x or 2.x,
and other compatible OEM versions of LAN Manager.
The drivers named ETHNE conform to the Network Driver
Interface Specification (NDIS) defined by Microsoft/3Com.
Included in MSLANMAN.DOS and NDIS2 subdirectories
are the following files:
\MSLANMAN.DOS\DRIVERS\ETHERNET\Accton\
ETHNE.DOS The DOS NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\MSLANMAN.DOS\DRIVERS\NIF\
Accton.NIF Network Information File
\NDIS2\DOS
EN166XD.NIF Network Information File for LAN Server (DOS)
ETHNE.DOS The DOS NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
OEMSETUP.INF Network Information File for Windows for
Workgroups v3.1
\NDIS2\OS2
EN166XO.NIF Network Information File for LAN Server (OS/2)
ETHNE.OS2 The OS/2 NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\NDIS2
README.TXT This readme file
Verifying Installation
----------------------
Verify proper adapter installation by running
the diagnostic program in 1STEP.
Note that it only runs under DOS and will not run under
the OS/2 environment.
Sample PROTOCOL.INI Files and Parameters
----------------------------------------
[ACCNE_NIF]
; Default section of protocol.ini file for the Accton Adapter
drivername = ETHNE$
irq = 3
iobase = 0x300
; End of this sample file
There are several parameters included in the ACCNE_NIF
section of the PROTOCOL.INI file. However, the only parameter
that you should specify is the "drivername."
If you change other parameter settings, such as the IOBASE
or IRQ, make sure that it matches the hardware setting.
Otherwise, the adapter may fail.
If you don't specify these settings, Accton's NDIS driver
will automatically detect them.
irq Specifies the interrupt channel used by the adapter.
Acceptable values for this parameter are 2, 3, 4, 5,
10, 11, 12 and 15. However, some of the mentioned Accton
adapters do not support all the acceptable values.
iobase Specifies the iobase address used by the adapter.
This parameter is given in hexadecimal values.
Acceptable value for this parameter are 0x200, 0x220,
0x240, 0x260, 0x280, 0x2a0, 0x2c0, 0x2e0, 0x300, 0x320,
0x340, 0x360, 0x380, 0x3a0, 0x3c0, 0x3e0.
List of Additional Parameters in the PROTOCOL.INI file
for the NDIS Driver Configuration
------------------------------------------------------
Note that values for the following parameters are seldom
changed by the user. Most of the time the default
values are used.
Keyword Parameter
MaxMultiCast 1 .. 1000 Default 10
Maximum number of MultiCast Addresses.
This configures the size of the MultiCast
Address Table.
MaxRequests 6 .. 64 Default 8
Maximum number of outstanding General Requests.
This configures the size of the General Request
Queue.
MaxTransmits 6 .. 64 Default 12
Maximum number of outstanding TransmitChain commands.
This configures the size of the TransmitChain Request
Queue.
ReceiveChains 6 .. 96 Default 12
Maximum number of outstanding ReceiveChain commands.
This configures the size of the ReceiveChain Request
Queue.
ReceiveBuffers 6 .. 96 Default 12
Configures the number of the Receive buffers in the
Receive Buffer Pool.
TransmitBufSize 128 .. 1514 Default 1514
Configures the size (in bytes) of buffers in the
Transmit Buffer Pool.
Troubleshooting and Error Messages
----------------------------------
To check for problems, please run the Test Adapter option
from 1Step.
Error Message:
ERROR: Adapter card not found or I/O port error.
Possible Causes:
1. The adapter is not installed correctly in its slot.
2. I/O port failure due to incompatibility between
the computer and the card
Solution:
Run the 1Step program to determine reason for the error.
Error Message:
ETHNE-Error-01: Incorrect Media Setting or Bad Transceiver
Possible Causes:
1. The transceiver failure.
2. Cable breaks.
3. Loose cable connection.
Solution:
Run 1Step's diagnostic program to determine the cause
of the problem.
-- THE END --
.TOPIC:
LAN Manager
Accton Ethernet Adapter
NDIS DRIVER FOR LAN MANAGER INSTALLATION
========================================
The drivers named ETHNE contained in the
directory MSLANMAN.DOS conform to the
Network Driver Interface Specification (NDIS)
defined by Microsoft/3Com.
NDIS Driver Installation on LAN Manager v2.0
--------------------------------------------
1. Type Setup in the LAN Manager directory and press
Enter.
2. Choose "Import Network Drivers..." in the "Action"
field. Press <Enter> to continue.
3. Insert your Driver Diskette into either drive
A: or B:. Then press <Enter> to see the list
of Imported Network Drivers on screen.
4. Press the <Space bar> to select the appropriate
Network Adapter, i.e. "Accton EN166x Adapter Card"
for the MPX2 Ethernet Adapters. Then press <Enter>
to confirm your choice.
5. Follow screen instructions to complete the process,
until the Network Driver appears onscreen.
6. Identify your Network Adapter if asked. For example,
select "Accton EN166x Ethernet Card" to confirm any
MPX2 Ethernet Adapter.
7. Select the <Add driver> and the <Add protocol> options.
Then select <OK> to confirm your choices. The
Workstation's primary parameters should appear on screen.
8. Respond to all prompts issued on screen to complete the
process. Select <OK> to confirm a choice.
9. Save all selections. Choose "Save" from the "Action Menu"
10. Press <F3> to exit.
NDIS Driver Installation on LAN Manager v2.1
--------------------------------------------
1. Type lmsetup in the LAN Manager directory and
press <Enter>. The Microsoft LAN Manager
Setup screen should appear.
2. Choose "Network Drivers..." in the
"Configuration" field. Press <Enter> to
confirm your choice.
3. Choose <Add New Configs> and press <Enter>
to display a list of Network Adapter
Drivers.
4. Choose <Other Driver> and press <Enter>.
5. Insert the Driver Diskette into drive A:
or B: of your PC. Indicate the drive
location of the diskette and select
<OK> to proceed.
6. Select the appropriate Network Adapter
Driver from the list. For example,
select "Accton EN166x Ethernet adapter."
Select <OK> to confirm your choice.
7. Select an appropriate protocol. Use the
<Space bar> to highlight your choice.
8. Select <OK> to confirm your choice.
A Configuration Complete message should
appear on screen.
9. Save the configuration. Select <Save>.
10. Press <F3> to exit.
NDIS Driver Installation on LAN Manager v2.2
--------------------------------------------
1. Type setup in the LAN Manager directory and
press <Enter>. The Microsoft LAN Manager
Setup screen should appear.
2. Choose "Network Drivers" from the
"Configuration" field. Press <Enter> to
confirm your choice.
3. Choose <Add New Config> and press <Enter>
to display a list of Network Adapter
Drivers.
4. Choose <Other Driver> and press <Enter>.
5. Insert the Driver Diskette into drive A:
or B: of your PC. Indicate the drive
location of the diskette and select
<OK> to proceed.
6. Select the appropriate Network Adapter
Driver from the list. For example,
select "Accton EN166x Ethernet adapter."
Select <OK> to confirm your choice.
7. Select an appropriate protocol. Use the
<Space bar> to highlight your choice. If
you have chosen the TCP/IP protocol, you
will be prompted to key-in the IP address,
the subnet mask, and the default gateway
(router). By default, the workstation
number of NetBios session is set to 6.
Please consult Microsoft LAN Manager
Installation Manual for more details,
or check the online help.
8. Select <OK> to confirm your choice.
A Configuration Complete message should
appear onscreen.
9. Save the configuration. Select <Save>.
10. Press <F3> to exit.
If you are installing the LAN Manager for the first
time, you will be prompted to key-in the default user
name and domain of the workstation, as well as to answer
the questions concerning Windows environment and memory
management. Just follow the instructions on the screen.
Sample Configuration Files
--------------------------
LAN Manager 2.0
CONFIG.SYS File
LASTDRIVE=Z
BUFFERS = 35
FILES = 35
SHELL=C:\DOS50\COMMAND.COM C:\DOS50\e:1000 /p /E:1024
DEVICE=C:\HIMEM.SYS
DEVICE=C:\DOS50\SETVER.EXE
DOS=HIGH,UMB
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\Accton\ETHNE.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.DOS
PROTOCOL.INI File
[PROTOCOL MANAGER]
DRIVERNAME = PROTMAN$
[NETBEUI_XIF]
Drivername = netbeui$
BINDINGS = "ACCNE_NIF"
[ACCNE_NIF]
; PROTOCOL.INI for Accton EN166x ethernet adapter
drivername = ETHNE$
; irq = 3
; iobase = 0x300
; End of this sample file
AUTOEXEC.BAT File
@echo off
PROMPT $P$G
PATH=c:\PE2;C:\DOS50;C:\NC;
APPEND=C:\PE2;C:\DOS50;
REM === LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES
REM === LANMAN 2.0 ===
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
C:\LANMAN.DOS\DRIVERS\PROTMAN\NETBIND
NET START WORKSTATION
REM === LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES
REM === LANMAN 2.0 ===
LAN Manager 2.1 or LAN Manager 2.2
CONFIG.SYS File
LASTDRIVE=Z
BUFFERS = 35
FILES = 35
SHELL=C:\DOS50\COMMAND.COM C:\DOS50\e:1000 /p /E:1024
DEVICE=C:\HIMEM.SYS
DEVICE=C:\LANMAN.DOS\DRIVERS\DOSUTILS\EMM386.EXE NoEMS
DEVICE=C:\DOS50\SETVER.EXE
DOS=HIGH,UMB
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\Accton\ETHNE.DOS
PROTOCOL.INI File
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
PRIORITY = NETBEUI
[NETBEUI_XIF]
Drivername = netbeui$
SESSIONS = 6
NCBS = 12
BINDINGS = "ACCNE_NIF"
LANABASE = 0
[ACCNE_NIF]
; PROTOCOL.INI for Accton EN166x ethernet adapter
drivername = ETHNE$
; irq = 3
; iobase = 0x300
; End of this sample file
AUTOEXEC.BAT File
@echo off
PROMPT $P$G
PATH=c:\PE2;C:\DOS50;C:\NC;
APPEND=C:\PE2;C:\DOS50;
@REM === LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES
@REM === LANMAN 2.1 ===
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
NET START WORKSTATION
LOAD NETBEUI
@REM === LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES
@REM === LANMAN 2.1 ===
-- THE END --
.TOPIC:
LAN Server
Accton Ethernet Adapter
NDIS DRIVER FOR LAN SERVER INSTALLATION
=======================================
The drivers named ETHNE contained in the directory
NDIS2 conform to the Network Driver Interface
Specification (NDIS) defined by Microsoft/3Com.
DOS LAN Requester
-----------------
1. Insert the IBM LAN Support Program (LSP)
Version 1.36 Diskette into your floppy drive
(drive A: or B:).
2. Type the following at your DOS prompt
and press <Enter>:
A:>dxmaid
3. The screen will display the IBM logo. Press
<Enter> twice until the "Environment Information"
appears onscreen.
4. Responds to the screen prompts, specifying the
following values for each field:
Use the <Space Bar> to toggle between choices:
Configuration for this computer? Yes
Use existing configuration information? Yes
Do you have adapter option diskettes? Yes
Are you configuring for two adapters? No
Do you need 802.2 interface support? Yes
Type change as needed to drive and directory information below:
Source for LSP A:\
Target for new configuration C:\lsp
5. Make sure that the values given above are correct.
Press <Enter> to store your choices.
6. Insert the Driver Diskette in your source drive.
Specify the path and press <Enter> to proceed.
Examples:
A:\NDIS2\DOS
B:\NDIS2\DOS
7. Upon pressing <Enter> the necessary drivers
from the Driver Diskette are copies onto you
target directory in the hard disk.
8. Follow screen instructions to complete the
process. Simply pressing <Enter> for each
screen display will select the default options.
Press <Enter> three times, until you reach
the display prompting you to insert the LSP
diskette.
9. Insert the LSP diskette as prompted. Press
<Enter> to acknowledge completion of the action.
10. A screen showing the current configuration detected
will be displayed. It should show the Accton
EN166x series adapter and the protocols already
selected (i.e., "IBM IEEE 802.2" and
"IBM OS/2 NETBIOS").
11. Press <F4> to save the new configuration. This
completes the LSP installation.
Note:
You should have defined in your CONFIG.SYS a
maximum of 20 files, i.e. FILES=20, to run the
software properly. Change the FILES line using
the text editor if needed.
If installing LSP for the first time, you should
complete the installation by typing install and
following the instructions on screen.
12. Use a text editor to edit the CONFIG.SYS file.
Specify at least 20 files in the FILES= line.
Modify it to the following:
FILES=20
13. Save the configuration and reset your computer.
14. Insert the DOS LAN Requester Install Diskette 1
into your floppy drive.
15. Type the following and press <Enter>:
INSTALL <Enter>
16. The IBM logo will again appear on the screen.
Press <Enter> to move on to the next screen.
17. Follow screen instructions, pressing <Enter>
to move from screen-to-screen until you
are prompted to indicate the pathname of
the DOS LAN Requester directory.
TIP: After the IBM logo appears on the screen,
press <Enter> twice to reach this screen.
18. Specify the pathname for the DOS LAN Requester
directory (C:\DOSLAN is the default). Then
press <Enter> to continue.
19. The program will ask you for the services
that you require.
20. Highlight the appropriate option. Select
either "Send messages" or "Send, View, Edit,
and Log message" option.
TIP: Normally, the second option "Send, View, Edit
and Log message" is selected.
21. Specify the PC's ID and domain ID.
The domain ID is the domain server ID; it should
be the same for all workstations of the network.
22. Follow the screen prompts to complete installation.
OS/2 LAN Server 3.0
-------------------
1. Copy ETHNE.OS2 and EN166xO.NIF files from your
Driver diskette (\NDIS2\OS2) to c:\ibmcom\macs.
2. Click the OS/2 LAN Service icon.
3. Select "Installation and configuration." The IBM
logo should appear onscreen.
4. Click <OK>.
5. Select <Advance> and press <Enter>.
6. Select "Install or Configure this Workstation."
7. Select server type, adding a server or domain controller.
The "install or remove" selections should appear.
8. Select "Configure a component."
10. Click the "Configure" button.
11. Select "Configure workstation."
12. Select "Accton EN166x Ethernet adapter" when
prompted to identify you Network Adapter.
Then click the <Add> button.
13. Select "802.2" from the list and
click the <Add> button.
14. Select IBM NETBIOS from the list and
click the <Add> button
15. Select <OK> to confirm all selections.
16. Follow screen instructions to complete the process,
selecting <OK> to accept default selections.
17. Continue pressing <OK> until your screen
prompts you to backup old CONFIG.SYS and
AUTOEXEC.BAT and create a new CONFIG.SYS
and AUTOEXEC.BAT. Also select <OK> to
confirm this.
18. Installation is complete now. Reset your
PC by turning it off and on.
OS/2 LAN Server 4.0
-------------------
1. In OS2 desktop, click the MPTS (Multi-Protocol Transport Service)
icon. The IBM logo should appear on screen.
2. Click the <OK> button.
3. Click the <Configure> button.
4. Select the "LAN adapters and protocols" item, then click the
<Configure> button.
5. Click the <Other adapters...> button.
6. Insert the Accton EN166x Ethernet Adapter Driver Diskette into
a drive (A: or B:), then enter the driver path like
A:\NDIS2\OS2, (or B:\NDIS2\OS2, etc.)
and click the <OK> button
7. Select "Accton EN166x Ethernet adapter" from the Network Adapters
list when prompted to identify your Network Adapter.
Then click the <Add> button.
8. Select "IBM 802.2" from the Protocols list and click the <Add> button.
9. Select "IBM OS2 NETBIOS" from the Protocols list and click the
<Add> button
10. Select "IBM Netware Requester Support" from the Protocols list
and click the <Add> button if you need to log onto a NetWare server.
11. Select <OK> to confirm all selections.
12. Click the <Close> button in the Configure window.
13. Click the <Exit> button in the MPTS window.
14. Click the <Exit> button, then your screen will prompt you to backup
old CONFIG.SYS and AUTOEXEC.BAT and create a new CONFIG.SYS
and AUTOEXEC.BAT. Also select <OK> to confirm this.
15. Installation is complete now. Reset your PC by turning it off and on.
-- THE END --
.TOPIC:
Windows for Workgroups 3.11
NDIS DRIVER FOR WINDOWS FOR WORKGROUPS 3.11 INSTALLATION
========================================================
Content:
--------
A) Accton Support drivers for WFW 3.11
B) Install NDIS 2.0/ NDIS 3.0 driver to the WFW 3.11
C) Install ODI/ NDIS 3.0 driver to the WFW 3.11
A) Accton Support drivers for WFW 3.11
Accton support NDIS 2.0, NDIS 3.0 and DOS/ODI driver for Windows
for Workgroups 3.11, description of these 3 files are as follows:
Driver name Location Description
ACC311.SYS A:\WFW311 NDIS 3.0 driver in enhanced mode
ETHNE.DOS A:\NDIS2\DOS NDIS 2.0 driver in real mode
MPX2PNP.COM A:\DOS Accton's MPX2 DOS/ODI driver
B) Install NDIS 2.0/ NDIS 3.0 driver in the WFW 3.11
1. Run Windows by typing "WIN" at the DOS prompt.
2. Click the "Network" icon in the Main Program Group.
3. Click the "Network Setup" icon in the Network window.
4. Check drivers button, if it is hidden and can't be selected then
goto the next step. If it is visible and can be selected, goto step 8.
5. Click Networks button
6. Select "Install microsoft Windows Network" with no additional network.
7. Click the "OK" button
8. Select the "Drivers" item from the Network Setup dialog box.
9. Select the "Add Adapters" item from the Option dialog box.
10. If you are installing an Accton Adapter for the first time,
Select "Unlisted or Updated Network Adapter", then go to the next step.
The system will automatically search for the OEMSETUP.INF file which is
supported by the adapter maker (such as Accton).
If you have installed an Accton adapter before, just select the
"Accton EN166x MPX2 driver" from the drivers list table and go to
step 13.
11. Insert the Accton EN166x driver diskette in floppy drive A or B,
then type the destination drive and path name for your PC.
Make sure the full path of the directory (i.e. A:\)
is given. Then you will see the "Accton En166x MPX2 driver"
dialog box appear.
13. Use the setup button to change IO BASE, IRQ and driver type.
Accton EN166x MPX2 adapter uses 300, 3 as default IO BASE and
IRQ setting.
There are 4 driver types:
. Real mode and Enhanced mode NDIS
. Enhanced mode NDIS
. Real mode NDIS
. ODI driver
You can select one of these 4 drivers types depending on your
application. For workgroups environment only, you can select the
1'st driver type which combines real mode and enhanced mode NDIS.
14. Follow screen instructions to complete the process.
15. Restart your computer.
Following are some sample Configuration Files
---------------------------------------------
1. CONFIG.SYS File
FILES=30
BUFFERS=30
LASTDRIVE=Z
DEVICE=C:\WFW311\HIMEM.SYS
DEVICE=C:\WFW311\IFSHLP.SYS
STACKS=9,256
2. AUTOEXEC.BAT File
C:\WFW311\SMARTDRV.EXE
C:\WFW311\net start
PATH C:\WFW311;
SET TEMP=C:\WFW311\TEMP
3. PROTOCOL.INI File on Windows for Workgroups 3.11
[network.setup]
version=0x3110
netcard=ms$en166x,1,MS$EN166X,2
transport=ms$netbeui,NETBEUI
lana0=ms$en166x,1,ms$netbeui
[MS$EN166X]
DriverName=MS2000$
INTERRUPT=3
IOBASE=0x300
[EN166X]
adapters=MS$EN166X
[NETBEUI]
BINDINGS=MS$EN166X
LANABASE=0
SESSIONS=10
NCBS=12
4. SYSTEM.INI
[386Enh]
netcard=acc311.386
C) Install ODI/ NDIS 3.0 driver to the WFW 3.11
1. Run Windows by typing "WIN" from the DOS prompt.
2. Click the "Network" icon in the Main Program Group.
3. Click the "Network Setup" icon in the Network window.
4. Check the drivers button, if it is hidden and can't be selected then
go to the next step. If it is visible and can be selected, go to step 8.
5. Click the Networks button
6. Select "Install Microsoft Windows Network" with no additional network.
7. Click the "OK" button
8. Select the "Drivers" item from the Network Setup dialog box.
9. Select the "Add Adapters" item from the Option dialog box.
10. If you are installing an Accton Adapter for the first time,
Select "Unlisted or Updated Network Adapter", then go to the next step.
The system will automatically search for the OEMSETUP.INF file which is
supported by the adapter maker (such as Accton).
If you have installed an Accton adapter before, just select the
"Accton EN166x MPX2 driver" from the drivers list table and go to
step 13.
11. Insert Accton's EN166x driver diskette in floppy drive A or B,
then type the destination drive and path name for your PC.
Make sure the full path of the directory (i.e. A:\)
is given. Then you will see the "Accton En166x MPX2 driver"
dialog box appear.
13. Use the setup button to change the IO BASE, IRQ and driver type.
Accton's EN166x MPX2 adapter uses 300, 3 as default IO BASE and
IRQ settings.
There are 4 drivers type:
. Real mode and Enhanced mode NDIS
. Enhanced mode NDIS
. Real mode NDIS
. ODI driver
You must select ODI driver to let the NetWare ODI driver work in
WFW 3.11.
14. Follow screen instructions to complete the process.
15. Restart your computer.
Note: To connect to a Novell server from within Windows for Workgroups
make sure you are logged onto a NetWare server before starting
Windows. Also make sure that you have set up Windows for Workgroups
to use Novell NetWare.
Following are some sample Configuration Files
---------------------------------------------
1. CONFIG.SYS File
FILES=30
BUFFERS=30
LASTDRIVE=Z
DEVICE=C:\WFW311\HIMEM.SYS
DEVICE=C:\WFW311\IFSHLP.SYS
STACKS=9,256
2. AUTOEXEC.BAT File
SET TEMP=c:\windows\temp
PATH c:\windows;%PATH%
c:\windows\net start
lsl
MPX2PNP
c:\windows\odihlp.exe
ipxodi
netx
3. PROTOCOL.INI File on Windows for Workgroups 3.11
[network.setup]
version=0x3110
netcard=en166x,1,EN166X,4
transport=ms$netbeui,NETBEUI
lana0=en166x,1,ms$netbeui
[net.cfg]
PATH=C:\WINDOWS\net.cfg
[EN166X]
[Link Driver MPX2PNP]
[NETBEUI]
BINDINGS=MPX2PNP
LANABASE=0
SESSIONS=10
NCBS=12
4. SYSTEM.INI
[boot]
shell=progman.exe
network.drv=wfwnet.drv
.
.
[386Enh]
network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386
netheapsize=20
netmisc=ndis.386,msodisup.386
transport=netbeui.386
InDOSPolling=FALSE
.
.
[Network]
winnet=wfwnet/00025100
multinet=nonet
FileSharing=No
PrintSharing=No
LogonDisconnected=yes
EnableSharing=no
UserName=Accton
Workgroup=WORKGROUP
ComputerName=Accton
Comment=Accton
logonvalidated=no
[network drivers]
devdir=C:\WINDOWS
LoadRMDrivers=No
-- THE END --
.TOPIC:
Windows NT
NDIS3.0 DRIVER FOR WINDOWS NT INSTALLATION
==============================================
The driver named "ACCNT" conforms to the NDIS3 MiniPort Spec. It can support
Windows NT3.5x and NT4.0. This driver also supports Windows NT 3.1 but
you must replace NDIS.SYS with NT 3.5 DDK's NDIS.SYS.
(\DDK\SRC\NETWORK\NT31BIN\I386\FREE\NDIS.386)
File description:
ACCNT.SYS : NDIS3 MiniPort driver
README.TXT : Read me file
====================================================
Installing Driver in Microsoft Windows NT4.0
====================================================
Windows NT 4.0 has bundled the "Accton EN166x MPX2 PnP Ethernet Adapter"
driver in its OS, so you can install it directly from a list of pre-bundled
adapter drivers in the "Select Network Adapter" dialog box under the
"Network" icon. But the bundled driver will check the Ethernet MAC address
00 00 E8 header. If your adapter's Ethernet MAC address is not "00 00 E8",
please install the driver from the driver diskette.
1) Click the "Start" command button, select the "Settings" icon to display
an option list under it.
2) Click the "Control Panel" icon.
3) Double-click the "Network" icon.
4) Select the "Adapters" item, then click the "Add..." button in the
"Network" dialog box.
5) Click the "Have Disk..." button in the "Select Network Adapter" dialog
box.
6) Insert the Driver Diskette in your floppy drive. Enter the full pathname
A:\ of the driver installation information file (OEMSETNT.INF) in the
"Insert Disk" dialog box, then click the OK button.
7) Select "Accton EN166x MPX2 PnP Ethernet Adapter," then click the OK
button in the "Select OEM Option" dialog box.
8) When Accton EN166x MPX2 PnP Card Setup dialog box appears, you
can specify the "IRQ level" and "I/O Port Address" of the adapter plugged
in to your PC.
IRQ Level = 5
I/O Port Address = 0x300
9) To complete network installation, remember to bind the adapter to
the transport drivers by choosing the "Bindings" button from the
"Network" dialog box.
10) Click the "Close" button in the "Network" dialog box.
11) Remove the Driver Diskette from your floppy drive.
12) Restart your computer to initialize the network function.
====================================================
Installing the driver on Microsoft Windows NT3.5x
====================================================
1) In the Main group of NT, choose the Control Panel icon.
2) In the Control Panel window, choose the Network icon.
3) In the Network Settings dialog box, choose the Add Adapter button.
The Add Network Adapter dialog box appears.
4) In the list of network cards, select "<other> Requires disk from
manufacturer", and then press the <Enter> button.
5) Insert this driver disk in drive A, enter drive and pathname A:\
and then click on the OK button.
6) In the Select OEM Option dialog box, you will see Accton EN166x MPX2
PnP Ethernet Adapter in the menu. Click on the OK button to install it.
7) When the Accton EN166x MPX2 PnP Card Setup dialog box appears, you
can specify the "IRQ level" and "I/O Port Address" of the adapter plugged
in your PC. However, this NDIS 3.0 mini port driver automatically scans
the IO and IRQ for the EN166x MPX2 adapter, so the driver can work even
if you select a wrong IO port and IRQ.
For multiple card installation, you must specify the correct IO port and
IRQ.
8) After that, installation is completed. Accton's adapter becomes one
of those Installed Adapter Cards and the driver becomes one of the
Installed Network Software. You can see: "[0x]Accton EN166x MPX2 PnP
Ethernet Adapter" within the Installed Adapter Cards menu and "Accton
EN166x MPX2 PnP Ethernet Adapter Driver" within the Installed Network
Software menu.
9) Now, the SYSTEM has already copied ACCNT.SYS from A:\WINNT
directory to C:\WINNT\SYSTEM32\DRIVERS and the OEMSETNT.INF from
A:\ to C:\WINNT\SYSTEM32 but renamed it to another installation
information file. So the next time, if you want to add Accton's adapters
to your system, you do not need the floppy diskette again.
10) To complete network installation, remember to bind the adapter to the
transport drivers by choosing the "Bindings" button under the Network
Setting dialog box.
11) Restart your system to initialize network service.
-- THE END --
.TOPIC:
Windows 95
NDIS3.0 DRIVER FOR WINDOWS 95 INSTALLATION
==========================================
Microsoft has put the Accton EN166x driver in the Windows 95 system.
Please Set EN166x to "Plug and Play" mode with the 1Step program.
After Win95 starts up, it will recognize the Accton EN166x Adapter
automatically.
-- THE END --
.TOPIC:
Windows 98
NDIS DRIVER FOR WINDOWS 98 INSTALLATION
=========================================
Microsoft has put the Accton EN166x driver in the Windows 98 system.
Please Set EN166x to "Plug and Play" mode with the 1Step program.
After Win98 starts up, it will recognize the Accton EN166x Adapter
automatically.
-- THE END --
.TOPIC:
SCO Unix r3.2 v4
STREAM DRIVER ON SCO UNIX SERVER INSTALLATION
=============================================
Your Driver Diskette should contain the following files:
==================================================================
Files Contents
============================================================================
UNIX.TXT File about driver installation for the UNIX Server.
UNIXDRVR.TAR Accton device drivers packaged for UNIX (in tar format).
F2TAR.EXE Utility to transfer UNIXDRVR.TAR onto a formatted diskette.
----------------------------------------------------------------------------
INSTALLATION PROCEDURE
1. Prepare a formatted diskette on any DOS machine.
C>format a:
| |
| + Diskette drive
+ Dos prompt
Note: You must have a disk that does not have any bad sectors.
Verify this with the DOS command - CHKDSK
C>chkdsk a:
| |
| + Diskette drive
+ Dos prompt
2. Run F2TAR.EXE to generate an Installation Diskette for UNIX system.
a. After executing the "f2tar" command, the following message will be
shown on the screen:
"Target drive letter (press 'A' or 'B') : "
press 'A' for the first drive, 'B' for second drive.
b. Then "f2tar" will load the data file "unixdrvr.tar" into memory
and display the following messages:
"Reading file, please wait."
......
"Done."
c. Note if you are using the same drive for both Source Diskette and
UNIX Installation Diskette, "f2tar" will show the message:
"Remove the original diskette from drive A"
or
"Remove the original diskette from drive B"
d. When the message
"Insert a formatted diskette into drive A and press [ENTER] :"
or
"Insert a formatted diskette into drive B and press [ENTER] :"
is shown on the screen, put the formatted blank diskette into
drive A (or B) as indicated in the message. Press <Enter>
e. After transferring the files, the following messages will be shown.
"Generating UNIX Installation Diskette on drive ()"
"Press [Ctrl][C] to abort."
If you want to abort the operation, press <Ctrl> and <C>
at the same time.
Please wait for a few seconds, and the UNIX Installation Diskette
will be created. Note that the resulting diskette is in UNIX
tar format; it cannot be read by DOS.
3. Remove the UNIX Installation Diskette, log in to the UNIX system as root.
After the data file has been tranferred completely, you will see
"Please remove the diskette from drive A".
If you are using the same drive for both Source Diskette and UNIX
Installation Diskette, the messages below will be shown on the
screen too.
"Please insert the original diskette in drive A"
"Press [ENTER] to continue ..."
So put Source Diskette back in the drive as indicated by the message,
and press the <Enter> key.
Now the UNIX Installation Diskette is ready for use, please log
into UNIX system as supervisor (root).
(Note: Please make sure the current directory is "/" using the UNIX
command - pwd.)
4. Run the custom utility and select Install new package. It will prompt you
to insert the 16-BIT Ethernet LLI driver disk. After reading drive A, it
will show a message to inform you to use netconfig or mkdev <driver>
(this case- en16) to add drivers into your system.
If you use mkdev en16, you must use mkdev tcp and select en16 for
this LLI driver to complete configuration.
5. Use the program "1step" to configure Accton's 16-bit Ethernet adapter.
6. If you encounter any problems during installation, (i.e., an error
message appears on screen) call your dealer for assistance.
-- THE END --
.TOPIC:
SCO Unix r3.2 v5
SCO OpenServer MDI DRIVER INSTALLATION
======================================
Your Driver Diskette should contain the following files in the subdirectory
\SCOUNIX.5:
--------------------------------------------------------------
Files Contents
--------------------------------------------------------------
SCO5UNIX.TXT Text file about driver installation for the UNIX SCO5 Server
UNIXDRVR.114 EN166x ethernet device drivers packaged for UNIX
--------------------------------------------------------------
Introduction
-------------
This is the ISA Ethernet Adapter EN166x SCO Unix OpenServer MDI
driver R1.1.1. It is a custom installable MDI driver, configured
using netconfig.
The MDI driver requires the following hardware and software:
- Accton EN166x PnP ISA Ethernet Adapter
- SCO Unix OpenServer Release 5.0.0 or higher version.
>>> NOTE <<<
The EN166x adapter should not be programmed in the Plug-and-Play (PnP)
mode; otherwise, the adapter will be installed incorrectly because
the PnP feature is still not supported on the SCO OpenServer Release 5.
Installation Procedure
----------------------
1. Prepare a formatted diskette on any DOS machine. For example, type:
C>format a:
Note: Make sure your diskette is free from bad sectors.
Verify this using the DOS CHKDSK command.
2. Now log into the UNIX system as supervisor (root) and enter the
Maintenance mode.
(Note: Make sure that the current directory is "/"
using the UNIX command - pwd.)
Please follow the steps shown below to uncompress the package file:
> cd /tmp (and insert the package's floppy in the proper drive, i.e. a:)
> doscp a:/scounix.5/unixdrvr.114 ./en166xdriver
(then replace it with the prepared formatted diskette from step 1)
> #dd if=./en166xdriver of=/dev/rfd0135ds18
(Note: Use another device file name if you use a different floppy drive)
Now the package's installation diskette is ready for installing.
3. The following sections describe the configuration of the driver.
It is suggested that you perform these instructions in the
singler-user environment.
Run the custom utility and select the "Install new package"
option. It will prompt you to insert "Accton EN166x EtherNet Adapter Driver"
Floppy Volume 1.
After running the custom utility and the new package is installed,
you should use the "netconfig" command to add the driver into your
system as described in the step 4 below.
4. Run "netconfig". Add the desired chain. The Accton EN166x drivers are
called: actn0, actn1, actn2, actn3.
Remember the actn0 must be configured first, before any
other driver is configured.
5. When the chain has been configured, select 'q' from the
netconfig menu, and relink the kernel at the prompt.
6. To active the adapter, you must reboot. When the system
boots, you should see the following message among the
other configuration messages:
%actn0 0x0300-0x0319 3 - type=EN166x addr=00-00-e8-xx-xx-xx
with the appropriate I/O addresses, IRQ, Adapter Type and MAC address.
The display of the last three bytes of the MAC address depends on the adapter
currently plugged onto your system.
7. If you encounter any problems during installation
(i.e., an error message appears on screen), call your dealer for assistance.
-- THE END --
.TOPIC:
Packet Driver
PACKET DRIVER INSTALLATION
==========================
NWPD.COM is your adapter packet driver. The
following describes its command syntax and use.
NWPD Command Syntax
-------------------
NWPD [-d] [-n] [-w] [-u] [-h] <PD_INT_NO> [IRQ] [IO_BASE]
where:
[-d] The "-d" option does not start the Ethernet
adapter until this packet driver is called
first by higher layer programs
[-n] The Novell server uses NOVELL ISO-like packets,
while the Novell workstation uses the NOVELL 8137
packets. Use this option to convert NOVELL 8137
into NOVELL ISO-like packets, if necessary.
[-w] Steve Wallace added a hack to let the packet
drivers run under Windows. This is not to be
considered as the proper solution, which is to
write a TCP/IP package for Windows.
This hack is enabled only when you use the '-w' switch.
[-u] This option unloads the Packet Driver.
[-h] This option displays the on-line help.
<PD_INT_NO>
This specifies the software interrupt (IRQ)
where you'll load the packet driver. It must
be in the range 0x60 to 0x80.
The PC/TCP kernel, by default, is loaded at
interrupt 0x61 (so don't load the packet
driver there!)
[IRQ]
This specifies the hardware interrupt (IRQ)
[IO_BASE]
This specifies the I/O address.
Example 1
---------
Using Accton's EN166x adapter, the following command line
loads the Packet Driver at software interrupt 60h,
at I/O address 300 and hardware interrupt 3.
NWPD 0x60 3 0x300
Since the default I/O address for this adapter is 300 and the
default IRQ is 3, the above command may be simplified to:
NWPD 0x60
Note
----
Address parameters, such as the software interrupt and I/O address
are preceded by "0x". For example, "0x60" and "0x300".
Packet Driver Application: Using adapter on PC/TCP Environment
--------------------------------------------------------------
1. Load your Packet Driver.
2. Load the PC/TCP kernel ETHDRV.EXE. See following
example:
To load the PC/TCP kernel and allocate 8 packet buffers,
type the following:
ETHDRV -p 8 <Enter>
This will increase the number of packet buffers from
5 (default) to 8.
3. You are now ready to run any PC/TCP application, like
FTP's telnet.
Packet Driver Application: Communicating with NCSA Telnet
---------------------------------------------------------
1. Make sure that you have the correct version of NCSA
Telnet for the PC. You need version 2.3 or later to
support the packet driver interface.
2. Install the NCSA software onto your system. Refer
to the NCSA documentation for detailed instructions.
3. Load the Packet Driver (NWPD 0x60). Refer to the
corresponding section for details.
4. Get help or view the Packet Driver's syntax
by typing the following command:
NWPD -h <Enter>
5. Run the NCSA application that you need. To
do this, you need to know the host's
IP address. For example, ftp 192.72.24.202.
-- THE END --
.TOPIC:
LANtastic
LANTASTIC DRIVER INSTALLATION
=============================
Content:
--------
A) Install Accton drivers for LANtastic 5.0
B) Install Accton drivers for LANtastic 6.0
A) Install Accton drivers for LANtastic 5.0
========================================
Using NDIS driver:
------------------
For NDIS, Accton provides the "ETHNE.DOS" driver for the MPX2 product
series. You can use the "ETHNE.DOS" driver to replace AEXNDIS.DOS which
is the NDIS driver offered by ARTISOFT.
Example ----- CONFIG.SYS
DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
DEVICE=C:\LANTASTI\ETHNE.DOS -------> By Accton
Example ----- AUTOEXEC.BAT / STARTNET.BAT
C:\LANTASTI\AI-NDIS BIND_TO=ETHNE_NIF
C:\LANTASTI\AILANBIO
C:\LANTASTI\REDIR MachineName
Example ----- PROTOCOL.INI
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
[ETHNE_NIF]
DRIVERNAME = ETHNE$
Comments:
If you are using PROTMAN.DOS V1.x, you must use the NO_BIND option
on the AI-NDIS command line in STARTNET.BAT, and you must run
NETBIND.EXE V1.x before AILANBIO.EXE.
B) Install Accton NDIS2 drivers for LANtastic 6.0
==============================================
Using the NDIS driver:
----------------------
To install the Accton NDIS driver "ETHNE.DOS", you can use the LANtastic
6.0 install program, and select "NDIS support for network adapters",
then insert Accton's driver diskette, and type the path "A:\LANTASTI".
The install program will search for "ETHNE.DOS" and "PROTOCOL.INI", and copy
these two files to the target directory.
IF you have already installed LANtastic 6.0 and want to install Accton's
MPX2 adapter, just replace AEXNDIS.DOS with Accton's NDIS driver
"ETHNE.DOS" in CONFIG.SYS
"ETHNE.DOS" is an NDIS driver supported by Accton
"AEXNDIS.DOS" is an NDIS driver which is supported by ARTISOFT
Example ----- CONFIG.SYS
DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
DEVICE=C:\LANTASTI\ETHNE.DOS -------> By Accton
Example ----- AUTOEXEC.BAT / STARTNET.BAT
@echo ===== Begin LANtastic configuration =====
SET LAN_CFG=C:\LANTASTI
PATH C:\LANTASTI;%PATH%
SET LAN_DIR=C:\LANTASTI.NET
rem Please obtain the NETBEUI.EXE program from Microsoft
NETBEUI
AI-NDIS BIND_TO=AEXNDIS_NIF
AILANBIO @STARTNET.CFG
REDIR THOMAS @STARTNET.CFG
SERVER C:\LANTASTI.NET @STARTNET.CFG
NET LOGIN \\THOMAS
@echo ===== End LANtastic configuration =====
Example ----- Protocol.ini
[PROTMAN]
Priority=NETBEUI
DriverName = PROTMAN$
Dynamic = Yes
[NETBEUI_XIF]
DriverName = netbeui$
Sessions = 6
NCBS = 12
Bindings = ETHNE_NIF
LANABASE = 1
[ETHNE_NIF]
DriverName = ETHNE$
-- THE END --
.TOPIC:
DEC PATHWORKS
NDIS Driver for DEC PATHWORK Installation
=========================================
The drivers named ETHNE contained in the \NDIS2\DOS
subdirectory of your Driver Diskette conform to the
Network Driver Interface Specification (NDIS) defined
by Microsoft/3Com.
Installation Procedure
----------------------
1. Insert the DEC PATHWORKS Client Setup diskette #1
into your floppy drive (either A: or B:).
2. At the prompt, type the following and press <Enter>
to bring up the startup menu:
A:>NETSETUP <Enter>
3. You'll be asked if your keyboard type is LK250. Select
"NO" unless you are using an LK250 keyboard.
4. Next, you'll be prompted to choose a transport option.
Select the "DECNET transport option" and press <Enter>
to proceed.
5. Your system will prompt you to insert the DNET TRNSPRT diskette#1
into your floppy drive. Follow screen instructions.
6. Then you'll be prompted to specify a destination drive.
Type C: or D:
7. When asked if you are creating an initial workstation diskette,
select "NO."
8. Type in the node name and address (i.e., node number) in the
corresponding field. Then press <Enter>.
9. Type in the server node name and address (i.e., node number)
in the corresponding field. Then press <Enter>.
10. When asked to "Select the network adapter type:" choose
Ethernet.
11. When prompted to "Select the network adapter:" choose
"Other NDIS."
12. Indicate the subdirectory location of your NDIS
driver in the Accton Driver Diskette. For example,
type the following:
A:\MSLANMAN.DOS\DRIVERS\ETHERNET\Accton\ETHNE.DOS
13. When prompted, indicate the subdirectory location
of the PROTOCOL.INI file in the Accton Driver Diskette.
For example, type the following:
A:\MSLANMAN.DOS\DRIVERS\ETHERNET\Accton\
14. Select "WRITE KEY DISK" to save the settings that you have
chosen. When prompted to copy the ETHNE.DOS and PROTOCOL.INI
files, insert the Accton driver program diskette into your
floppy drive.
15. Follow screen instructions to complete the installation.
16. From the Configuration screen, press F10 to exit to C:\.
17. Edit the PROTOCOL.INI file from the DECNET subdirectory.
Remove the semicolon (;) from the statement
"NI_IRQ = 5" under the [DATALINK] section.
18. Make sure that the IRQ value in the new [ETHNE.DOS] section,
matches the NI_IRQ value in the [DATALINK] statement.
Sample Configuration Files
--------------------------
1. CONFIG.SYS File
shell=c:\command.com /P /E:526
device=c:\decnet\hiMEM.sys
device=C:\dos\EMM386.EXE ram 1024
dos=high, UMB
devicehigh=c:\decnet\protman.sys /I:D:\DECNET
devicehigh=c:\decnet\ethne.dos
rem device=c:\decnet\nddrv.sys
rem device=c:\decnet\npdrv.sys
FILES=50
BUFFERS=50
LASTDRIVE=v
STACKS=9,256
2. PROTOCOL.INI file for PATHWORKS v4.1
; PROTOCOL.INI file create by DNETOMO.V41 V4.1.060
; via DNETWIK.V41 V4.1.047
[protocol manager]
DRIVERNAME = PROTMAN$
[IPX4MAC]
DRIVER = IPX$MAC
BINDINGS = ETHNE.DOS
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
BINDINGS = ETHNE.DOS
;Specify IRQ level used by workstations network adapter
NI_IRQ = 3
[ETHNE.DOS]
; PROTOCOL.INI for Accton En166x adapter
drivername = ETHNE$
; irq = NI_IRQ = Adapter IRQ Setting
irq = 3
iobase = 0x300
; End of this sample file
3. AUTOEXEC.BAT
echo off
break on
cls
prompt $p$g
REM Insert any keyboard internationalization and character set information here.
if not exist \decnet\STARTNET.BAT goto nostartup
call \decnet\STARTNET
goto end
:nostartup
echo ** WARNING ** STARTNET.BAT file not found. Network functions not performed
-- THE END --
.TOPIC:
SUN PC-NFS
NDIS DRIVER FOR SUN PC-NFS Installation
=======================================
The drivers named ETHNE contained in the directory
\NDIS2\DOS conform to the Network Driver Interface
Specification (NDIS) defined by Microsoft/3Com.
NDIS Driver Installation on SUN PC-NFS
--------------------------------------
1. Edit the CONFIG.SYS file to include the following
command line, and reboot the PC:
Device=c:\dos\ansi.sys
2. Insert the PC-NFS Installation diskette into the
PC's floppy drive. Type the following at the DOS prompt and
press <Enter> to bring up the PC-NFS installation
screen:
INSTALL <Enter>
3. Follow the screen prompts to configure your screen
display. For example, press <M> to choose mono display,
or press <C> to choose color display, or press
<ESC> to cancel the installation.
4. When the "Install the Basic PC-NFS files" window
appears onscreen, select "Install Full PC-NFS" from
the choice list.
5. "Specify the target PC-NFS installation directory," by
typing the appropriate path in the field provided. For
example, C:\NFS. Then press <Enter> to continue.
6. Carefully read and respond to each prompt that
appears onscreen, indicating the suitable
selections for your system.
7. When you reach the prompt that reads "Configure
an Ethernet network connection," choose "Ethernet"
from the choice list. Then press <Enter> to confirm
your choice.
8. Choose the network adapter you will use. Select
"NDIS" from the list shown on screen. Then press
<Enter> to confirm your choice.
9. Follow screen instructions to complete the process. You
will be prompted to insert some PC-NFS distribution
diskettes. And during the process, files from
the diskettes will be copied onto your hard disk
drive.
10. When prompted to update your AUTOEXEC.BAT and
CONFIG.SYS files, press "Y."
11. Your system will prompt you when the installation
process is complete. It will display the following
message, "PC-NFS installation is complete."
12. The system will create two subdirectories
in the destination drive, namely, \LANMAN and \NFS.
13. Create the NETWORK.BAT, DRIVES.BAT and HOSTS files.
Specify the PC name, IP address, server name
and server IP address in these files.
See the section on Sample Configuration Files
for examples.
14. Copy the NETWORK.BAT, DRIVES.BAT and HOSTS files
into the \NFS directory of your server.
15. Copy the ETHNE.DOS file from the
\MSLANMAN.DOS\DRIVERS\ETHERNET\Accton\ of your Driver Diskette
to the newly created subdirectory (\LANMAN) on your
destination drive.
Note: The ETHNE.DOS file is also found in the \NDIS2\DOS
directory of your Driver Diskette.
16. Edit the CONFIG.SYS file using a text editor. Add
the following command line before the NFS_NDIS
driver specification:
DEVICE=C:\LANMAN\ETHNE.DOS
17. Edit the PROTOCOL.INI file in the \LANMAN directory,
replacing the following:
a. Replace the section name [your-mac-module]
with [EN166x]
b. Replace the command line "drivername = YOURMAC$" with
"drivername = ETHNE$"
c. Specify the correct IRQ and IOBASE value
(may be omitted) to match the adapter's
hardware configuration. For example:
IRQ = 3
IOBASE = 0x300
d. Replace the command line "bindings = YOUR-MAC-MODULE"
with "bindings = ETHNE$"
18. Reboot your computer. Then start the application
you need. For example:
a. Execute NFSCONF.EXE to configure the system,
such as mounting a virtual drive E:
b. Execute TELNET.EXE to do terminal emulation
Sample Configuration Files
--------------------------
1. NETWORK.BAT
REM stc* is a sample PC-NFS workstation name
REM accton3 is a sample PC-NFS server address
NET START RDR stc*
NET PCNFSD accton3
NET NAME stc*
2. DRIVES.BAT
REM specify connections to remote directory
NET USE l:accton3:/usr2/down
NET USE k:accton3:/mnt
3. HOSTS
REM specify gateway address
192.72.24.201 <gateway # updated>
REM specify workstation's IP address
192.72.24.102 stc
REM specify server's IP address
192.72.24.202 accton3
4. CONFIG.SYS
shell=c:\command.com /P /E:526
dos=high, UMB
rem ----pcnfs install
Device=c:\dos\ansi.sys
DEVICE=C:\NFS\PCNFS.SYS /m
DEVICE=C:\NFS\SOCKDRV.SYS
REM Specify PROTOCOL.INI directory
DEVICE=C:\LANMAN\PROTMAN.SYS /i:C:\LANMAN
REM Accton NDIS driver name
device=C:\LANMAN\ETHNE.DOS
DEVICE=C:\LANMAN\NFS-NDIS.SYS
FILES=50
BUFFERS=50
LASTDRIVE=v
STACKS=9,256
5. PROTOCOL.INI file at the \LANMAN directory
[protocol manager]
drivername = PROTMAN$
[ETHNE]
drivername = ethne$
irq = 3
iobase = 0x300
[NFS-NDIS]
drivername = NFSLINK1
bindings = ETHNE
6. AUTOEXEC.BAT
...
SET TZ=PST8
SET path=C:\;C:\NFS;C:\LANMAN
SET NFSDRIVE=D
REM Add the following line to bind NDIS driver
C:lanman\netbind
PRT *
REM Execute application you need, e.g. NFSRUN
NFSRUN
-- THE END --
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.