.TOPIC:
Contents
1STEP Help Menu Netware Driver
Technical Support Netware ODI Driver
MPX2 Driver Netware Server Driver
Remote BootROM Netware OS2/ODI Driver
NDIS Driver Windows for Workgroups 3.1
LAN Manager Windows for Workgroups 3.11
LAN Server Windows NT 3.1x
Windows NT 3.5
SCO UNIX Windows 95
UNIXWARE
SOLARIS UNIX LANtastic
Banyan VINES
Packet Driver Pathway Access
PC/TCP DEC PATHWORKS
NCSA SUN PC-NFS
Power Lan
[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: (035) 770-270 8:00am to 6:00pm
FAX: (035) 770-267
BBS: (035) 770-654 14400-2400 baud
Accton USA
Phone: (408) 452-8900 7:00am to 5:00pm Pacific Time
(800) 926-9288
FAX: (408) 452-8988
FastFax: (408) 452-8811
BBS: (408) 452-8828 14400-2400 baud
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 the Accton's new MPX2 DOS/ODI driver
It is found in your Driver Diskette
(\NETWARE\ODI\DOSODI\MPX2PNP.COM)
b. ACCTON.COM is your workstation driver for NetWare 3.11 DOS/ODI.
It is found in your Driver Diskette
(\NETWARE\ODI\DOSODI\ACCTON.COM)
c. ACCTON.LAN is your server driver for NetWare 3.11.
It is found in your Driver Diskette
(\NETWARE\ODI\3.11\ACCTON.LAN)
High performance MPX2 DOS/ODI driver
------------------------------------
MPX2PNP.COM is Accton's MPX2 DOS/ODI driver which can improve network
performance not only at Netware 3.11 but also Netware 4.xx.
To use MPX2PNP, it is not necessary to change server driver, just run
it at client site, then you can get big performance improvement.
LSL
MPX2PNP -----------> MPX2 workstation driver
IPXODI
NETX
Key points for high MPX performance
------------------------------------
This section describes steps to optimize its performance on NetWare 3.11
by Accton's old MPX driver.
1. Make sure to install an EN166x adapter in both
the workstation and the file server.
2. Install both the workstation and the file
server drivers respectively.
3. Before running the ACCTON.LAN server driver, modify
the STARTUP.NCF file to include the following
command line:
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 4202
4. Use the Load and bind command to start the server driver.
Loading the NetWare workstation driver
--------------------------------------
A sample command sequence for running the workstation driver
follows. From your prompt, type the following command sequence
and press <Enter>:
LSL
ACCTON -----------> MPX workstation driver
IPXODI
NETX
-- THE END --
.TOPIC:
Remote BootROM
Ethernet Remote Boot Rom for Netware Operation System
=====================================================
Accton adapters provide an empty socket for installing the optional
Boot ROM device. Once installed, the adapter is able to load DOS
from server. This is useful for using the adapter in a diskless
workstation. Two types of Boot ROMs available. They are as follows:
1. Ethernet Remote Reset Boot ROM (IPX Boot ROM)
- Supports the NetWare IPX workstation
2. Generic Boot ROM (RPL Boot ROM)
- Supports NetWare 3.x, 4.x and Microsoft LAN Manager 2.x
A: Using the Ethernet Remote Boot ROM (IPX Boot ROM)
=====================================================
The Ethernet Remote Reset Boot ROM is for NetWare applications.
1. Generate a DOS Image
To allow remote booting, you should first generate a DOS image.
See the corresponding section in your NetWare manuals for detailed
procedure.
2. Run RPLFIX.COM
This program is provided and developed by Novell to fix the bug
that causes boot failure when using MS-DOS 5.0 or DR DOS 6.0 or
their later versions. Users of MS-DOS 5.0 or DR DOS 6.0 MUST
run this program after generating the DOS image. Failure to do
so will result in boot failure.
3. Auto-detect adapter configuration
Once you power on the host PC, the Boot ROM will automatically
detect the configuration of the network adapter installed.
The parameters detected will vary according to the type of
network adapter. Corresponding values will be shown on screen.
See Figures 1 and 2 for sample screen displays. For related
information, see section on "List of Adapter Parameters
Automatically Detected by the Boot ROM".
4. Follow screen instructions to select the appropriate
Ethernet_Type if necessary.
See section on Ethernet Type Selection for more information.
Note: The program automatically detects the adapter's parameter
settings, including Frame type, RAM Test, RAM Size,
IRQ value, I/O base address, data width, Ethernet-ID.
Ethernet Type Selection
-----------------------
The Boot ROM device is compatible with both Ethernet_II and
IEEE 802.3 Ethernet.
1. Upon power on the program automatically detects the
adapter's configuration, and will display it on the screen.
2. When prompted to select a "frame type" choose an
appropriate one for your adapter if necessary.
For example, pressing "1" selects "Ethernet_II," while
pressing "2" selects "802.3"
Additional RPLODI.COM
_____________________
When you are building the DOS Image file, note that the logging in
sequence is different from booting from disk for IPX Boot ROM.
Run RPLODI after LSL.COM is loaded. The following procedures are
the same. They may be MPX2PNP, IPXODI and NETX. For Generic Boot ROM,
the booting sequences are the same.
B: Using the Generic Boot ROM (RPL Boot ROM)
=============================================
Accton's Generic Boot ROM can be used with the following programs:
* NetWare v3.x or later
* Microsoft's LAN Manager 2.1 or later
Each platform has its own software installation and setup routine.
The diskette that comes with the ROM kit has drivers for the different
network environments.
Generic Boot ROM Installation for NetWare v3.x
----------------------------------------------
1. Install the NetWare Server RPL software.
2. Prepare a blank diskette for the remote reset image.
3. Create the server image boot file.
4. Boot your workstation.
Installing the NetWare Server RPL Software
------------------------------------------
a. "Load" a server LAN driver and be sure to specify the
frame type that your workstation is going to use.
b. "Bind" IPX to each of the different frame types
(ETHERNET_802.2, ETHERNET_802.3, ETHERNET_II,
ETHERNET_SNAP) that you require.
c. "Load" RPL.NLM
d. "Bind" RPL to the LAN driver and appropriate frame type
(ETHERNET_802.2)
Preparing a blank diskette for the remote boot image
----------------------------------------------------
a. Label a blank diskette "Remote Image"
b. From your root directory, type format a: /s
c. Files needed on the remote image include the following:
* For an IPX workstation, you will need the
IPX.COM (generated using Accton's driver or NE2000),
and the NETX.COM files
* For the DOS ODI workstation with NetWare v3.x:
LSL.COM
MPX2PNP.COM (or NE2000.COM)
IPXODI.COM
NETX.COM (or EMSNETX.EXE)
NET.CFG
* For the DOSODI workstation with NetWare v4.x:
LSL.COM
MPX2PNP.COM (or NE2000.COM)
IPXODI.COM
VLM.COM
NET.CFG
* Other files necessary are:
AUTOEXEC.BAT (user defined)
CONFIG.SYS (user defined) and
other file you may deem necessary
All NetWare VLM files for workstation NET.CFG
Creating the server image boot file
-----------------------------------
Refer to the sections entitled "Customizing Remote Boot Files"
and "Creating the BOOTCONF.SYS Boot Files" in your NetWare
documentation for details. A brief procedure follows:
1. Log onto the network as "supervisor" for the NetWare
v3.x server; or as "admin" for the NetWare v4.x server.
2. Map to your network server. Type: MAP F:=SYS:LOGIN
3. Insert the Remote Reset Image diskette in the drive A
of the workstation.
4. Change to F: and type:
CD\LOGIN
5. Using DOSGEN create the file "NET$DOS.SYS":
F:\SYSTEM\DOSGEN
6. Flag the NET$DOS.SYS as sharable and run RPLFIX if you're
using MS-DOS 5.0 or the later versions.
--------------------------- END --------------------------------------------
Ethernet Remote Boot Rom for Lan Manager operation System
=========================================================
Remote Boot Installation for LAN Manager 2.1
--------------------------------------------
Remote Boot installation on LAN Manager 2.1 may be complex.
Also, be aware that the Accton Generic Boot ROM does not
provide remote boot capability on a Microsoft OS/2 system.
There are two ways to install the remote boot software
on the LAN Manager server. You can either use Accton's
configuration utility (on the Accton Driver diskette
or download it from Accton's BBS), or edit the RPL
files manually.
Generic Boot Installation for LAN Manager 2.1
Using Accton's Configuration Utility
----------------------------------------------
1. Refer to the Microsoft LAN Manager Administrator's Guide
Chapter 13: Booting Workstations Remotely for more
detailed information.
Follow the steps to setup the remote boot environment,
but do not use the RPLMGR.EXE program to create
the remote boot profile.
2. Select an OS/2 full screen, and change to the
RPL subdirectory. For example, C:\LANMAN\RPL
3. Copy the RPLCFG.CMD, RPL.ACC, RPLMGR.ACC and the ETHNE.DOS
from the \RPL\LANMAN subdirectory of the Accton Driver
diskette, or from Accton's BBS to C:\LANMAN\RPL.
4. Run RPLCFG to install the remote boot software.
5. Refer to the Chapter 13 of LAN Manager Administrator's Guide.
Follow the steps in "Managing Remote Boot".
Generic Boot Installation for LAN Manager 2.1
by Manually Editing the RPL File
---------------------------------------------
1. Refer to the Microsoft LAN Manager Administrator's Guide
Chapter 13: Booting Workstations Remotely. Follow the
steps to setup the remote boot environment, but do not
use the RPLMGR.EXE program to create a remote boot profile.
2. Select an OS/2 full screen. Make C:\LANMAN\RPL the default
directory.
3. Copy ETHNE.DOS to BBLOCK\NDIS
4. Create a subdirectory BBLOCK\NETBEUI\ETHNE
5. Create DOSBB.CNF and PROTOCOL.INI files in
BBLOCK\NETBEUI\ETHNE as shown below:
-----------------------------------------------------------
BBLOCK\NETBEUI\ETHNE\DOSBB.CNF:
; DOS on Accton Ethernet Adapter
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
DAT BBLOCK\NETBEUI\ETHNE\PROTOCOL.INI
DRV BBLOCK\RPLDISK.SYS ~ 4 M
EXE BBLOCK\RPLPRO1.COM ~ 2 ~
EXE BBLOCK\RPLBIND2.EXE ~ ~
EXE BBLOCK\PROTMAN.EXE ~ ~
EXE BBLOCK\RPLBIND1.EXE ~ ~
DRV BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~
EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
DRV BBLOCK\NDIS\ETHNE.DOS ~ ~ ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
BBLOCK\NETBEUI\ETHNE\PROTOCOL.INI:
[protman]
drivername = protman$
dynamic = yes
priority = netbeui
[netbeui]
drivername = netbeui$
bindings = ethne
names = 5
ncbs = 8
packets = 20
pipeline = 10
sessions = 4
stacksize = 512
lanabase = 0
[xnsnb]
DRIVERNAME = XNSNB$
BINDINGS = ethne
MAXPROCESSES = 12
FGTICKS = 2
BGTICKS = 2
MAXROUTES =
MAXSOCKETS =
MAXXMITDESCS =
NONGROUPS =
SHAREGROUPS =
LOGINLIBRARY =
COURIERLIBRARY =
NETBIOSGROUPS =
lanabase = 1
[xnstp]
DRIVERNAME = XNSTP$
LOAD = XNSTP[CB]
BINDINGS = ethne
MAXPROCESSES = 12
FGTICKS = 2
BGTICKS = 2
MAXROUTES =
MAXSOCKETS =
MAXXMITDESCS =
NONGROUPS =
SHAREGROUPS =
LOGINLIBRARY =
COURIERLIBRARY =
NETBIOSGROUPS =
lanabase = 1
[tcpip]
DRIVERNAME = TCPIP$
IPADDRESS0 = (TCPIP_ADDRESS)
SUBNETMASK0 = (TCPIP_SUBMASK)
DEFAULTGATEWAY0 = (TCPIP_GATEWAY)
NBSESSIONS = 6
LOAD = tcptsr[c],tinyrfc[c],emsbfr[cr]
UNLOAD = "unloadt /notsr[dc]"
bindings = ethne
lanabase = 1
[ethne]
drivername = ethne$
;iobase = 0x300
;irq = 0x3
---------------------------------------------------------------
6. Edit the RPL.MAP in the current directory.
a. Add the lines below the description of "boot block records"
yyyyyyyyyyyy BBLOCK\NETBEUI\ETHNE\DOSBB.CNF 2 6 A ~ DOS
~Accton~EtherPair 0000E8 ~ ,,, ~ RDOSA ~ ~ ~ ~ ~ ~
b. Insert the lines before the description of "profile and
workstation records added by rplmgr"
0000E8?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME)
S ~ ~ ~,,, ~ RDOSA ~ DEFAULT *~New~Accton~EtherPair~* ~ ~ ~
7. Edit the RPLMGR.INI in the current directory.
Insert the following section before the OS/2 description block.
[configuration]
name = DOS330A
os = DOS330
dirname = DOS
dirname2 = DOS330
bblink = RDOSA
fitfileshared = fits\dos330
fitfilepersonal = fits\dos330p
comment = DOS 3.30 Accton EtherPair
adapter = 0000E8??????
[configuration]
name = DOS401A
os = DOS401
dirname = DOS
dirname2 = DOS401
bblink = RDOSA
fitfileshared = fits\dos401
fitfilepersonal = fits\dos401p
comment = DOS 4.01 Accton EtherPair
adapter = 0000E8??????
[configuration]
name = DOS500A
os = DOS500
dirname = DOS
dirname2 = DOS500
bblink = RDOSA
fitfileshared = fits\dos500
fitfilepersonal = fits\dos500p
comment = DOS 5.00 Accton EtherPair
adapter = 0000E8??????
And append the following line to RPLMGR.INI
; 0000E8 = Accton (Ethernet)
8. Log onto the network as an administrator.
Stop the remote boot service. Run RPLINST.
Then restart remote boot service.
9. Refer to the Chapter 13 of LAN Manager
Administrator's Guide. Follow "Managing Remote Boot"
to generate a workstation profile.
--------------------------- END --------------------------------------------
Ethernet Remote Boot Rom for Lan Server 4.0 Operation System
============================================================
Content :
-------
A. Installation of DOS Remote IPL on the server.
B. Setting up DOS Remote IPL on the server
C. Setting up on the client
A. Installation of DOS remote IPL on the server
===============================================
1. Start OS/2.
2. Type "NET STOP SVR <ENTER>" at OS/2 command prompt
if the SERVER services are already enabled.
3. Click the "IBM LAN Services" icon from the desktop.
4. Click the "OS/2 LAN Services Installation/Configuration" icon.
5. Click OK button in the IBM logo window.
6. Click Tailored button in the Easy or Tailored
Installation/Configuration window.
7. Select "Install or configure this workstation" in the Installation
Tasks window, and then click OK button.
8. If the Installation Location window is displayed, verify that the
correct drive is displayed in the Drive field,
and then click OK button.
9. Select "Domain controller" in the Server Type window,
and then click OK button.
10.Click No button in the "Current MPTS Version Installed window.
(ie; if you have the current version of MPTS on your workstation,
you do not have to re-install this version.)
11.There displays a network adapter which is autodetected by the system,
use the mouse to deselect it, and then click OK button.
--------
12.In the LAPS Configuration window,
==> select the network adapter in the Network Adapters field
(such as Accton EtherCombo/Pair/Coax-16 Ethernet Adapter),
and then click Add button.
==> select the protocol in the Protocol field
(such as IBM IEEE 802.2, IBM OS/2 NETBIOS),
and then click Add button.
==> make sure the above network adapter and protocol appears in the
Current Configuration field, and then click OK button.
13.Select "Install and remove a component" in the Install and
Configuration window, and then click OK button.
==> select "DOS Remote IPL Service" in the Install and Remote window,
click Install button, and then click OK button.
14.Select "Configure a component" in the Install and Configuration
window, and then click OK button.
==> select "DOS Remote IPL Service", and then click Configure...
button in the Configuration window.
==> select the kind and version of DOS
(such as MS_DOS 6.0 or 6.2), click COPY button,
and then click OK button.
==> specify the number of MS DOS diskettes in the
Number of MS DOS Diskette window and then
click OK button.
==> specify the drive on which to install the remote IPL
subdirectory (\IBMLAN\RPL), and then click OK button.
==> specify the drive on which to install the remote IPL
user subdirectory (\IBMLAN\RPLUSER), and then click
OK button.
==> click OK button to close the Configuration window.
15.Select "Apply the Changes" in the Install and Configuration window,
and then click OK button.
==> Insert the diskettes as the instructions displayed in the Copy
Diskette window, click OK button to begin copy process.
16.Click OK button to backup some configuration files prior to their
modification (such as CONFIG.SYS).
17.Restart your computer.
B. Setting up DOS Remote IPL on the server
==========================================
1. Start OS/2.
2. At OS/2 command prompt, type "NET START SERVER" to start the
REQUESTER and SERVER services.
3. Log on with an administration ID.
==> click the "IBM LAN Services" icon from the desktop.
==> click "LAN Server Administration" icon.
==> type administrator's ID and password, click OK button to
log on to the server, and there displays three icons
(Local Workstation ****, DOMAIN, Shadowed Servers)
==> close all the windows to return to the desktop.
4. Type "NET STOP REMOTEBOOT <ENTER>" to stop the Remote IPL service
if it is started.
5. Type "GETRPL" at OS/2 command prompt to run GETRPL program. This
utility migrates DOS remote IPL requester profiles from previous
releases and sets up the access control profiles.
6. Edit the file "\IBMLAN\DOSLAN\NET\UMB_CFG.SYS".
DEVICE=A:\EMM386.EXE NOEMS X=D000-D3FF
---------
This is the Boot ROM address of
your client LAN adapter.
Note: Use parameter X to prevent EMM386 from using this address.
7. Please update the file "\IBMLAN\DOSLAN\NET\NET.EXE" from IBM's BBS.
File size is 307,825 bytes, and date is 11/25/94.
8. Click the "IBM LAN Services" icon from the desktop.
==> click the "LAN Server Administration" icon.
==> click the "Local workstation ****" icon.
==> click the "DOS Image Definitions" icon.
==> highlight the "STD3HUMB" icon.
==> pull down the "Selected" menu, and then
select the item "Make Image".
==> type the "Target server" name in the Make Image to Server
window, and then click OK button.
==> close the window.
==> click the "Remote IPL Requesters" icon.
==> select the "Remote IPL Requester Template" icon,
and while holding down right mouse button,
drag the icon to an open area in the window (there
displays the Remote IPL Requester - Create window).
==> make sure the "Enable DOS requester" is selected
in the status field.
type "RBOOT" in the MACHINE ID field,
type your client LAN adapter address in the Network
adapter address field (such as 0000E813B30A).
==> click the "Parameters" button located in the right
of the window.
select "R_Det_NDIS" in the Server record identifier
field.
select "STD3HUMB" in the Image ID field.
==> click Create button located in the bottom of the
window.
9. Close all the windows to return to the desktop.
10.Edit the file "\IBMLAN\RPL\DOSNDET.CNF".
==> modify the line "DRV DOS\MACETH.DOS~~~"
into "DRV DOS\ETHNE.DOS~~~".
---------
This is the driver for your client network
adapter, such as "ETHNE.DOS" for ACCTONE's
166x adapter.
11.Edit the file "\IBMLAN\RPL\DOS\ETHERNET\PROTOCOL.INI".
==> modify the following statements according to the setup of
your client network adapter.
[MACETH_MOD]
DriverName = MACTH$ ETHNE$ (LAN driver on the client)
IRQ = 3 IRQ on the client
RAMADDRESS = 0XC800 0XD000 (BOOT ROM address on the client)
IOBASE = 0X200 I/O address on the client
12.Copy the driver for your client network adapter into the
subdirectory "\IBMLAN\RPL\DOS".
For example: COPY A:\NDIS\ETHNE.DOS C:\IBMLAN\RPL\DOS <ENTER>
13.Edit the file "\IBMLAN\RPL\RPL.MAP".
==> modify the first twelve characters in the bottom line to twelve
question marks.
000012345678 RBOOT ~STD3HUMB TSLS4 DOMAIN~~~,,,
???????????? RBOOT ~STD3HUMB TSLS4 DOMAIN~~~,,,
------------
14.Type "NET START RIPL <ENTER>" at OS/2 command prompt.
C. Setting up on the client
===========================
1. Insert RPL BOOT ROM on your client network adapter.
2. Use the LAN's adapter setup program to enable BOOT ROM function.
(such as ACCTON's 1step program)
3. Format a blank diskette with the parameter "/s".
4. Start your client workstation with the above DOS system diskette.
(SW7125:Please do not install any hard disk on the workstation .
SW7145:don't care ).
-- THE END --
.TOPIC:
Netware Driver
NetWare DRIVER INSTALLATION OVERVIEW
====================================
This file describes the contents of the \NETWARE
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 the 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 running 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 Receive Monitor Utility for
Monitor Type Applications (Such as Lan Analyzer)
If the monitor type applications you are using seems 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 running sequence is:
LSL.COM
RXMONSTK.COM
MPX2PNP.COM ---> Accton MPX2 DOS ODI driver
IPXODI.COM
...
-- THE END --
.TOPIC:
Netware ODI Driver
NetWare DOS/ODI WORKSTATION DRIVER INSTALLATION
===============================================
This section describes the procedure to install
the NetWare v3.11 workstation driver for your adapter.
Requirements:
-------------
Accton Driver Diskette
Installation Procedure:
-----------------------
Before you start with the installation process, make sure that
the adapter is properly installed and configured. Make sure
the your NetWare operating system is properly installed.
1. Run the following command in the order given below and
press <Enter>:
lsl
MPX2PNP
ipxodi
netx
2. You can now log into your network.
-- THE END --
.TOPIC:
Netware Server Driver
NETWARE SERVER DRIVER INSTALLATION
==================================
Content:
A). NetWare ODI Server Driver Installation (NetWare v3.11)
B). NetWare ODI Server Driver Installation (NetWare 3.12 or 4.x)
A). NetWare ODI Server Driver Installation (NetWare v3.11)
======================================================
This section describes the procedure to install the
NetWare v3.11 server driver for your adapter.
Requirement:
------------
* Accton Driver Diskette (ACCTON.LAN is your server driver)
Installation Procedure:
-----------------------
Before you start with the installation process, make sure that
the Novell NetWare 386 v3.11 server is properly installed.
Similarly, your adapter should also be properly installed
in your workstation.
1. Copy the ACCTON.LAN file from the Accton Driver Diskette
into the NetWare 386 subdirectory of your server.
2. Run SERVER.EXE from your server. You will see a series
of NetWare messages onscreen.
3. When the NetWare 386 prompt appears (indicated by a colon),
load your server driver. Simply type:
: LOAD [d:]ACCTON <Enter>
(Command Syntax : LOAD [d:]<Driver Name>)
4. Follow the instructions to select the appropriate
adapter configuration, i.e. io_port, memory address,
memory length, interrupt. Allowable values for these
parameters will also be shown on-screen. When you
load the driver program, your screen will display the
following messages :
Loading module ACCTON.LAN
Supported I/O port values are : 300, 320, 340, 360, 380, 3a0, 3c0, 3e0,
200, 220, 240, 260, 280, 2a0, 2c0, 2e0.
I/O port : 300
(Enter appropriate I/O port and press <Enter>)
5. Bind IPX to the Accton LAN driver. At the NetWare server
prompt, type:
:BIND IPX ACCTON <Enter>
6. After pressing <Enter> the computer prompts you for
the Network Number. For details on how to assign this
number, please consult your NetWare 386 Installation
Manual.
If problems occur during the binding process, your
screen will prompt you with error messages. Please
refer to your NetWare 386 manual for details on these
messages. The LAN driver installation is completed
when you see the following message onscreen:
IPX LAN Protocol bound to Accton MPX Driver vx.xxRxx (yymmdd).
B). NetWare ODI Server Driver Installation (NetWare 3.12 or 4.x)
============================================================
Requirements:
-------------
Accton Driver Diskette (ACC41.LAN)
Installation Procedure:
-----------------------
1. Insert the Accton Driver Diskette into drive A
and check the contents of subdirectory \NETWARE\ODI\4.x
It should contain the following file :
ACC41.LANÄÄÄ Novell NetWare V4.x Server Driver
ACC41.LDIÄÄÄ Novell NetWare V4.x Server Driver Installation
Information File
2. At the NetWare prompt (indicated by the Server name),
run the INSTALL.NLM program by typing:
server name: LOAD INSTALL <Enter>
3. Select "Maintenance/Selective Install" and press <Enter>.
4. Select "LAN Driver Options (Configure/Load/...)"
and press <Enter>.
5. Press the <Ins> key to specify other drivers to install.
6. Press <F3> and specify the driver path (A:\NETWARE\ODI\4.x)
and press <Enter>.
7. The ACC41.LAN driver should appear in your choice list for
the 'Select a LAN Driver' field. Choose this driver to
start the driver loading and binding procedure. This
will allow you to load and bind all 4 frame types supported
by NetWare.
8. Next time you start up your system, simply follow steps
2 to 4 to complete the installation.
Installation notes:
-------------------
1. If user load server driver by manual.
a) At the NetWare prompt (indicated by a colon), run
the driver program, type the following line if using one adapter:
:LOAD [c:]ACC41 <Enter>
(Command Syntax : LOAD [d:]<Driver Name>)
or type the following line if using more adapters are used:
:LOAD [c:]ACC41 BOARD=board# Frame=frame_type
where board# starts 0 to 4, because number of adapters supported is 4
(You can reference the 4.x\autoexec.ncf example included in the floppy)
b) Bind IPX with LAN driver, at the Netware server prompt,
type :
:BIND IPX ACC41 <Enter>
After pressing <Enter> the computer prompts you for
the Network Number. For details on how to assign this
number, please consult your NetWare 386 Installation
Manual.
2. The architecture of Netware 4.x driver is different from that
of V3.11. You should load MSM.NLM and ETHERTSM.NLM modules
separately before loading ACC41.LAN.
When loading ACC41.LAN, it will check whether these two
modules have been loaded, if not, it will load them
automatically. So after ACC41.LAN is loaded, if you type '
MODULES' command under prompt, you will see that two extra
modules, namely, MSM.NLM and ETHERTSM.NLM are also loaded.
3. The default frame type for the ACC41.LAN binding is
Ethernet_802.2 and not Ethernet_802.3. This is the
difference between V3.11 and V4.x drivers.
The ACC41.LAN also supports the NetWare V3.11 environment.
However, it requires loading of some patch NLMs before loading it.
Under this circumstance, there are some unpredictable
faults. So we do not suggest this solution.
4. Remember to specify LASTDRIVE=Z in the CONFIG.SYS file.
5. Edit the NET.CFG if you want to change some parameters.
For example, if you're using a NetWare 3.11 workstation and
wants to log into a NetWare v4.x server. The default
frame type of NetWare 3.11 is Ethernet 802.3, while that of
NetWare v4.x is Ethernet 802.2. Before you can log into
the NetWare v4.x, make sure there is a protocol binding
for Ethernet 802.3 in the server's site.
This is normally included in the [MLID] section. A sample
NET.CFG file is given below:
LINK DRIVER MPX2PNP
INT 5
PORT 320
:
:
List of Error Messages
----------------------
Error message: "The board cannot be found."
Possible cause: The adapter does not exist or driver does
not recognize the adapter.
Solution: Plug Accton adapter into your PC bus slot.
Error message: "Board RAM failed the memory test."
Possible cause: The RAM buffer on the adapter failed.
Solution: Change a new adapter to run driver again.
Error message: "The board did not respond to the initialization command."
Possible cause: The driver recognized the adapter but the
adapter fail to respond.
Solution: Change a new adapter to run driver again.
Error message: "Adapter current mode is not supported or card not found."
Possible cause: The current adapter mode is not supported
such as NE1000 mode.
Solution: Run 1Step.exe reset adapter to NE2000.
Error message: "There is no cable connecting to adapter."
Possible cause: There is no cable connecting to adapter or
the transceiver within adapter is failed.
Solution: Connect the cable to adapter and run driver again.
-- THE END --
.TOPIC:
Netware OS2/ODI Driver
NETWARE OS/2 ODI DRIVER INSTALLATION
====================================
Requirements:
-------------
Before you start with the installation process make
sure you have the following:
a. Accton Driver Diskette
b. Novell NetWare OS/2 WORKSTATION SERVICES REQUESTER diskette.
c. Novell NetWare OS/2 WORKSTATION OS/2 Utility - 1
d. Novell NetWare OS/2 WORKSTATION OS/2 Utility - 2
e. Novell NetWare OS/2 WORKSTATION OS/2 Utility - 3
Installation Procedure
----------------------
You need this file to acquire network service after installing OS/2
Requester and Utilities.
OS2MLID.SYS ---- supported by Accton
1. The directory OS2ODI contains only an OS/2 driver,(OS2MLID.SYS). This
driver must be used with the OS/2 requester to establish
networking operations.
2. Make sure that the workstation on which you want to
install the Requester is a 286 or 386 machine that
will run OS/2 or Extended Edition OS/2. Please refer to
'Novell NetWare Requester for OS/2' documentation for
a detailed Requester and Utilities installation guide.
3. After installation, copy the OS2MLID.SYS file into the NETWARE
subdirectory of your hard disk.
4. Add or replace the OS2MLID.SYS file in the CONFIG.SYS file.
Make sure the it comes before the IPX.SYS command line.
The following shows the corresponding command sequence:
DEVICE=C:\NETWARE\LSL.SYS ; OS/2 Requester supported
DEVICE=C:\NETWARE\DDAEMON.SYS ; OS/2 Requester supported
DEVICE=C:\NETWARE\OS2MLID.SYS ; Accton supported
DEVICE=C:\NETWARE\IPX.SYS ; OS/2 Requester supported
5. Reboot your system to get service of network.
Installation note:
------------------
You can bind several frame types to the IPX protocol to support
various configurations. Include this in the Link Driver OS2MLID
section of the NET.CFG file. A sample is shown below:
Link Driver OS2MLID
frame Ethernet_802.3
frame Ethernet_802.2
frame Ethernet_II
frame Ethernet_snap
protocol IPX 00 Ethernet_802.3
-- THE END --
.TOPIC:
NDIS Driver
NDIS Driver Installation Overview
=================================
The driver you need are in the directories MSLANMAN.DOS,
MSLANMAN.OS2 and NDIS. 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, MSLANMAN.OS2, and NDIS 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
\MSLANMAN.OS2\DRIVERS\ETHERNET\ACCTON\
ETHNE.OS2 The OS/2 NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\MSLANMAN.OS2\DRIVERS\NIF\
ACCTON.NIF Network Information File
\NDIS\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
\NDIS\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
\NDIS
NDIS.TXT This readme file
OEMSETUP.INF Network Information File for Windows for
Workgroups v3.1
WFW.TXT The Installation guide for Windows for
Workgroups v3.1
LANMAN.TXT The Installation guide for LAN Manager
LANSVR.TXT The Installation guide for Lan Server
BANYAN.TXT The Installation guide for Banyan VINES
PATHWAY.TXT The Installation guide for Wollongong Pathway
Access.
PATHWORK.TXT The Installation guide for DEC PATHWORKS
PCNFS.TXT The Installation guide for Sun PC-NFS
Verifying Installation
----------------------
Verify for proper adapter installation by running
the diagnostic program using 1STEP.
Note that 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 and MSLANMAN.OS2 are conformed 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 appear onscreen.
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 onscreen.
8. Respond to all prompts issued onscreen 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 onscreen.
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 the 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
NDIS 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 from 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:\NDIS\DOS
B:\NDIS\DOS
7. Upon pressing <Enter> the necessary drives
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 the
minimum 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 further instructions on screen.
12. Use a text editor to edit the CONFIG.SYS file.
Specify at least 20 file 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, 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 screen prompts to complete the installation.
OS/2 LAN Server 3.0
-------------------
1. Copy ETHNE.OS2 and EN166xO.NIF files from your
Driver diskette (\NDIS) 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 Configuration 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
<Configure> button.
5. Click <Other adapters...> button.
6. Insert Accton EN166x Ethernet Adapter Driver Diskette into
a specified drive (A: or B:), then enter the driver path like
A:\NDIS\OS2, (or B:\NDIS\OS2, etc.)
and click <OK> button
7. Select "Accton EN166x Ethernet adapter" from Network Adapters
list when prompted to identify you 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 logon NETWARE server.
11. Select <OK> to confirm all selections.
12. Click <Close> button in the Configure window.
13. Click <Exit> button in the MPTS window.
14. Click <Exit> button, then your screen will 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.
15. Installation is complete now. Reset your PC by turning it off and on.
-- THE END --
.TOPIC:
Windows for Workgroups 3.1
NDIS DRIVER FOR WINDOWS FOR WORKGROUPS 3.1 INSTALLATION
=======================================================
The drivers named ETHNE contained in the directory
NDIS conform to the Network Driver Interface
Specification (NDIS) defined by Microsoft/3Com.
NDIS Driver Installation on Windows for Workgroups
--------------------------------------------------
1. Run Windows by typing WIN from the DOS prompt.
2. Click the "Control Panel" icon in the Main Program Group.
3. Click the "Network" icon from the Control Panel window.
4. Select "Adapters" item in the Option dialog box.
5. Click the <Add> button to select it.
6. Select "Unlisted or Updated Network Adapter" when the
Install driver field appears.
7. Type destination drive and path name in your PC.
Make sure the full path of the directory (i.e. A:\NDIS\DOS)
is given.
8. Insert the Accton Driver Diskette in your floppy drive
and press <Enter> to start the installation process.
9. Follow screen instructions to complete the process.
10. Restart your computer.
Sample Configuration Files
--------------------------
1. CONFIG.SYS File
FILES=30
buffers=30
STACKS=9,256
DEVICE=c:\windows\HIMEM.sys
device=C:\WINDOWS\protman.dos /i:C:\WINDOWS
device=C:\WINDOWS\ethne.dos
device=C:\WINDOWS\workgrp.sys
LASTDRIVE=y
2. PROTOCOL.INI File on Windows for Workgroups
[network.setup]
version=0x3100
netcard=en166xd,1,EN166XD
transport=ms$netbeui,MS$NETBEUI
lana0=en166xd,1,ms$netbeui
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI
[EN166XD]
DriverName=ETHNE$
[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=32
BINDINGS=EN166XD
LANABASE=0
3. AUTOEXEC.BAT File
C:\WINDOWS\net start
C:\WINDOWS\SMARTDRV.EXE
@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;
SET TEMP=C:\WINDOWS\TEMP
-- 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 following:
Driver name Location Description
ACC311.SYS A:\WFW311 NDIS 3.0 driver at enhanced mode
ETHNE.DOS A:\NDIS\DOS NDIS 2.0 driver at real mode
MPX2PNP.COM A:\DOS Accton's MPX2 DOS/ODI driver
B) Install NDIS 2.0/ 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 from the Network window.
4. Check drivers button, if it is hidden and can't be selected then
goto 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 "OK" button
8. Select "Drivers" item from the Network Setup dialog box.
9. Select "Add Adapters" item in the Option dialog box.
10. If you install Accton Adapter first time, Select "Unlisted or
Updated Network Adapter", then goto next step.
System will automatically search OEMSETUP.INF file which supported
by adapter maker (such as Accton),
.
If you have installed Accton adapter before, just select the
"Accton EN166x MPX2 driver" at drivers list table and goto step 13.
11. Insert Accton EN166x driver diskette at floppy drive A or B
then type destination drive and path name in your PC.
Make sure the full path of the directory (i.e. A:\WFW311)
is given. Then you will see the "Accton En166x MPX2 driver"
dialog box appear.
13. Using setup button to change IO BASE, IRQ and driver type.
Accton EN166x MPX2 adapter using 300, 3 as default IO BASE and
IRQ setting.
There are 4 drivers type:
. Real mode and Enhanced mode NDIS
. Enhanced mode NDIS
. Real mode NDIS
. ODI driver
You can select one of these 4 drivers type depend on your
application. For workgroups environment only, you can select
1'st driver type which combine real mode and enhanced mode NDIS.
14. Follow screen instructions to complete the process.
15. Restart your computer.
Following is 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 from the Network window.
4. Check drivers button, if it is hidden and can't be selected then
goto 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 "OK" button
8. Select "Drivers" item from the Network Setup dialog box.
9. Select "Add Adapters" item in the Option dialog box.
10. If you install Accton Adapter first time, Select "Unlisted or
Updated Network Adapter", then goto next step.
System will automatically search OEMSETUP.INF file which supported
by adapter maker (such as Accton),
.
If you have installed Accton adapter before, just select the
"Accton EN166x MPX2 driver" at drivers list table and goto step 13.
11. Insert Accton EN166x driver diskette at floppy drive A or B
then type destination drive and path name in your PC.
Make sure the full path of the directory (i.e. A:\WFW311)
is given. Then you will see the "Accton En166x MPX2 driver"
dialog box appear.
13. Using setup button to change IO BASE, IRQ and driver type.
Accton EN166x MPX2 adapter using 300, 3 as default IO BASE and
IRQ setting.
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 NetWare ODI driver work at
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 on to a NetWare server before starting
Windows. Also make sure that you have setup Windows for Workgroups
to use Novell NetWare.
Following is 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 3.1x
NDIS3.0 DRIVER FOR WINDOWS NT 3.1 INSTALLATION
==============================================
They are used with Microsoft Windows NT Release 3.11. The drivers named
ACC2000 conform to the Network Driver Interface Specification (NDIS) 3.0.
There are two files in this directory, one is the driver ACC2000.SYS and
the other is installation information file OEMSETUP.INF.
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
Installing driver on Microsoft Windows NT
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
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 <Enter> button.
5) Insert this driver disk in drive A, enter drive and pathname A:\NT31
and then choose the OK button.
6) In the Select OEM Option dialog box, you will see Accton EN166x
Adapter in the menu, use OK button to install it.
7) And then Accton EN166x Network Card Setup dialog box appear,
you must specify "IRQ level" and "I/O Port Address" of the adapter
plugged in your PC. Because netcard detection function does not
support in SETUP program, please make sure these setting matching
your adapter's configurations. Otherwise the network ability of
Windows NT can not work properly.
8) After that, installation is completed. Accton's adapter becomes one
of those Installed Adapter Cards and driver become one of those
Installed Network Software. You can see: "[0x]Accton EN166x Adapter"
within Installed Adapter Cards menu and "Accton EN166x Adapter Driver"
within Installed Network Software menu.
9) Now, the SETUP program have already copied ACC2000.SYS from A:\NT31
directory to C:\WINNT\SYSTEM32\DRIVERS and the OEMSETUP.INF form
A:\NT31 to C:\WINNT\SYSTEM32 but renamed it to other installation
information file. So next time, if you want to add Accton's adapters
to your system, you do not need floppy diskette again.
10) To complete network installation, remember binding the adapter to
transport drivers by choosing "Bindings" button under Network Setting
dialog box.
11) Restarting your system you will acquire network service.
-- THE END --
.TOPIC:
Windows NT 3.5
NDIS3.0 DRIVER FOR WINDOWS NT 3.5 INSTALLATION
==============================================
The drivers named "ACCNT" conform to the NDIS3 MiniPort Spec. It can
support Windows NT 3.5 and Windows 95 with different oemsetup.inf file.
This driver also support the Windows NT 3.1 but user must replace NDIS.SYS
by NT 3.5 DDK's NDIS.SYS (\DDK\SRC\NETWORK\NT31BIN\I386\FREE\NDIS.386)
File description:
ACCNT.SYS : NDIS3 MiniPort driver
OEMSETUP.INF : Accton NT3.5 drivers information file
NT35.TXT : Read me file
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
Installing driver on Microsoft Windows NT3.5
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
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 <Enter> button.
5) Insert this driver disk in drive A, enter drive and pathname A:\NT35
and then choose the OK button.
6) In the Select OEM Option dialog box, you will see Accton EN166x MPX2
PnP Adapter in the menu, use OK button to install it.
7) And then Accton EN166x MPX2 PnP Card Setup dialog box appear, you can
specify "IRQ level" and "I/O Port Address" of the adapter plugged in
your PC. However, this NDIS 3.0 mini port driver has support auto IO,
IRQ scan for EN166x MPX2 adapter, so driver can work even user select
a wrong IO port and IRQ.
For multiple cards installation, specify correct IO port and IRQ is
necessary.
8) After that, installation is completed. Accton's adapter becomes
one of those Installed Adapter Cards and driver become one of those
Installed Network Software. You can see: "[0x]Accton EN166x MPX2 PnP
Adapter" within Installed Adapter Cards menu and "Accton EN166x MPX2
PnP Adapter Driver" within Installed Network Software menu.
9) Now, the SYSTEM have already copied ACCNT.SYS from A:\NT35 directory
to C:\WINNT\SYSTEM32\DRIVERS and the OEMSETUP.INF form A:\NT35 to
C:\WINNT\SYSTEM32 but renamed it to other installation information
file. So next time, if you want to add Accton's adapters to your
system, you do not need floppy diskette again.
10) To complete network installation, remember binding the adapter to
transport drivers by choosing "Bindings" button under Network Setting
dialog box.
11) Restarting your system you will acquire network service.
-- THE END --
.TOPIC:
Windows 95
NDIS3.0 DRIVER FOR WINDOWS 95 INSTALLATION
==========================================
Microsoft had put Accton EN166x driver in Windows 95 system.
Please Set EN166x to "Plug and Play" mode by 1Step program,
after Win95 start up, it can recognize Accton EN166x Adapter
automatically.
-- THE END --
.TOPIC:
SCO UNIX
STREAM DRIVER ON SCO UNIX SERVER INSTALLATION
=============================================
Your Driver Diskette should contain the following files:
==================================================================
Files Contents
============================================================================
UNIX.TXT This 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, login to 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 to drive A"
"Press [ENTER] to continue ..."
So put Source Diskette back to the drive indicated by the message,
and press <Enter> key.
Now the UNIX Installation Diskette is ready for use, please login
to UNIX system as supervisor (root).
( Note: Please make sure the current directory is "/" using UNIX
command - pwd. )
4. Run custom utility and select Install new package. It will prompt you
to insert 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:
UNIXWARE
STREAMS DRIVER ON UNIXWARE
==========================
DISKETTE CONTENTS
Your Driver Diskette should contain the following files:
==================================================================
Files Contents
==================================================================
README.TXT This file; your installation guide
UNIXDRVR.Z ACCTON device drivers package for UNIXWARE
(in tar compress format)
-------------------------------------------------------------------
INSTALLATION PROCEDURE
There are two ways to do installation. One is to create an installable
diskette then install to UnixWare, the other is to install to the
default directory in UnixWare.
1. Create an installable floppy diskette.
1.1 Copy the tar compress file into UnixWare
# doscp a:/unixware/unixdrvr.z /tmp/driver.Z
# cd /tmp
1.2 Decompress the tar compress file
# uncompress driver
1.3 Prepare a floppy diskette, format a floppy diskette, then
make a file system.
If you use 1.44Mbyte floppy diskette:
# /usr/sbin/format -v /dev/rdsk/f03ht
# /sbin/mkfs -F s5 /dev/dsk/f03ht 2844:711 2 36
If you use 720Kbyte floppy diskette:
# /usr/sbin/format -v /dev/rdsk/f03dt
# /sbin/mkfs -F s5 /dev/dsk/f03dt 1422:355 2 18
1.4 Mount this file system
If you use 1.44Mbyte floppy diskette:
# mount /dev/dsk/f03ht /install
If you use 720Kbyte floppy diskette:
# mount /dev/dsk/f03dt /install
1.5 Change working directory to this file system and extract
required files to the floppy diskette
# cd /install
# tar xvf /tmp/driver
1.6 Unmount this file system, and this floppy is an installable
diskette.
# cd /
# umount /install
Now you can use console command or enter DeskTop environment
to install driver from this diskette. Following steps use
console command. Information about how to install diskette
in DeskTop environment, please consult your menu accompanied
with UnixWare Packages.
1.7 Install driver to UnixWare from this installable diskette.
If you use 720KByte diskette:
# pkgadd -d /dev/dsk/f03dt
The following messages display onscreen
Insert diskette into 3.5 inch 720 kbyte (Low Density).
Type [go] when ready
or [q] to quit: (default: go)
Press Enter and the following messages display onscreen
Installation in progress. Do not remove the diskette.
The following packages are available:
1. accdrv Ethernet Hardware Support
(i386)1
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Select 1 and press Enter, then it will prompt you to select desired
IRQ and I/O Base
2. install driver to UnixWare
2.1 Copy the tar compress file into UnixWare
# doscp a:/unixware/unixdrvr.z /tmp/accdrv.tar.Z
# cd /tmp
2.2 Decompress the tar compress file
# uncompress accdrv.tar.Z
2.3 Change working directory to /usr/spool/pkg and extract
required files to this directory
# cd /usr/spool/pkg
# tar xvf /tmp/accdrv.tar
2.4 Install driver to UnixWare from this directory
# pkgadd
The following messages display onscreen
The following packages are available:
1. accdrv Ethernet Hardware Support
(i386)1
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Select 1 and press Enter, then it will prompt you to select desired
IRQ and I/O Base
-- THE END --
.TOPIC:
SOLARIS UNIX
ISA Ethernet Adapter Solaris for X86 Driver Installation
========================================================
This is the SunSoft Solaris X86 Ethernet network driver installation
procedure for Accton's EN166X series products.
When Solaris X86 Unix was installed successfully then you can start network
installation:
1. Install Accton ISA Ethernet adapter in your PC.
2. Run 1Step or Setup program(from Accton Driver Program Diskette)
to configure and test the adapter.
(Record the IRQ and I/O address for later use)
3. Startup the system and log on to Solaris as Superuser(root).
4. Remove /etc/hostname.* and reboot the system if you had installed
network driver.
( if you used the SMC's 'smc' driver, you must have the file
/etc/hostname.smc0. For Accton 'actn' driver, the installation program
will create the file /etc/hostname.actn0.)
# rm /etc/hostname.*
# halt
5. Copy the install package file (acctar.16) from Accton's distributed
diskette or BBS to the SunSoft Solaris X86 unix system's /tmp directory.
# mount -F pcfs /dev/diskette /mnt
# cp /mnt/acctar.16 /tmp
# umount /mnt
6. At the prompt, execute the commands "dos2unix' and "uudecode" to
change the file data format, as follows:
# cd /tmp
# dos2unix acctar.16 acctar.uu
# uudecode acctar.uu
7. Extract the driver installation package files (Acc.tar).
# tar xvf Acc.tar
8. Copy the install package file directory (Accton166) and contents
to /var/spool/pkg.
# cp -r Accton166 /var/spool/pkg
9. Install the driver in the Solaris unix.
# pkgadd Accton166
The Console prompts you for the following:
Where should the device driver object be installed [/kernel/drv]? _
(Press Enter Key)
Should required driver configuration files be modified [y,n]? _
(Press "y" key)
Should /etc/hostname.actn0 be created with the current system name? _
(Please key in system Hostname )
Do you want to continue with the installation of this package [y,n,?]_
(Press "y" key)
The Console will inform you when driver installation is completed.
10. Edit /kernel/drv/actn.conf to change "ioaddr" and "intr" value
specified in step 2.
Warning: The values of IRQ and I/O address in actn.conf file
must match the values set in 1Step/Setup program.
Sample actn.conf is:
# Driver.conf file for the "Accton EN166"
#
# The ioaddr property is the base I/O port address.
# The second number in the "intr" specification is the IRQ.
# The second and third numbers of the "reg" specification are the
# physical address and the length in bytes of the device's
# memory-mapped address space.
# The optional multisize property specifies the number of multicast
# addresses to be supported by this device driver; default 16.
#
# See isa(4) for details about the format of this file.
name="actn" class="sysbus" ioaddr=0x300 intr=5,3 reg=0,0xc8000,0x4000;
| |---> IRQ 3
|---> I/O port address
11. Edit /etc/hosts to add my IP address and hostname.
Edit /etc/netmasks to add netmask.
ex. /etc/hosts
127.0.0.1 localhost loghost
<my IP address> <my hostname>
.. ..
12. Driver is installed successful, Reboot the system.
#halt
13. If you want to remove Accton166 package, first remove
/etc/hostname.actn0 and reboot the system.
After the system startup, remove the /etc/hostname.actn0
# rm /etc/hostname.actn0
# halt
Then, reboot the system and run "pkgrm Accton166"
# pkgrm Accton166
-- 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 packet,
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".
-- THE END --
.TOPIC:
PC/TCP
PACKET DRIVER INSTALLATION FOR FTP PC/TCP
=========================================
NWPD.COM is Accton's packet driver which can support FTP PC/TCP.
Following is the installation procedure:
1. Load your Packet Driver. example:
NWPD 0x60
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.
-- THE END --
.TOPIC:
NCSA
PACKET DRIVER INSTALLATION FOR NCSA
===================================
NWPD.COM is Accton's packet driver which can support NCSA Telnet.
Following is the installation procedure:
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 driver, Accton support "ETHNE.DOS" driver for MPX2 product
series. User can use "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 the STARTNET.BAT, and you must run
NETBIND.EXE V1.x before AILANBIO.EXE.
B) Install Accton NDIS2 drivers for LANtastic 6.0
==============================================
Using NDIS driver:
------------------
To install Accton NDIS driver "ETHNE.DOS", user can use LANtastic
6.0 install program, and select "NDIS support for network adapters"
then insert Accton's driver diskette, and type path "A:\LANTASTI".
Install program will search "ETHNE.DOS" and "PROTOCOL.INI" and copy
these two files to target directory.
IF user already install LANtastic 6.0 and want to install Accton's
MPX2 adapter, just replace AEXNDIS.DOS with Accton's NDIS driver
"ETHNE.DOS" at CONFIG.SYS
"ETHNE.DOS" is NDIS driver which supported by Accton
"AEXNDIS.DOS" is NDIS driver which 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$
-- End --
.TOPIC:
Banyan VINES
NDIS DRIVER FOR BANYAN VINES INSTALLATION
=========================================
The drivers named ETHNE contained in the directory
NDIS conform to the Network Driver Interface
Specification (NDIS) defined by Microsoft/3Com.
NDIS Driver Installation on Banyan VINES
----------------------------------------
1. Type Pcconfig and press <Enter> to display
the "Configuring A PC for the Network" window.
2. Select "1 - Network Card Setting," and press
<Enter>. Your screen will prompt you with the
possible hardware configuration options.
3. Choose the "NDIS Ethernet" option and
press <Enter>.
4. Type the appropriate interrupt number,
and the EN166x to the PROTOCOL bindings =.
5. Press <F10> when process is complete.
Or press <Esc> to exit this screen.
6. Select "2 - Login Environment Settings," and
press <Enter>.
7. Select "1 - Select Default Communications Driver,"
and press <Enter>.
8. Select "NDIS Ethernet," and press <Esc> to
exit this menu.
9. Press <F10> to save all choices.
10. Modify the CONFIG.SYS and the PROTOCOL.INI
files as in the following examples.
Sample Configuration Files
--------------------------
1. CONFIG.SYS
device=c:\banyan\protman.dos/i:c:\banyan
device=c:\banyan\ethne.dos
2. PROTOCOL.INI file for the LAN Manager
[protocol manager]
DriverName = PROTMAN$
[EN166x]
DriverName = ethne$
-- THE END --
.TOPIC:
Pathway Access
NDIS DRIVER FOR WOLLONGONG PATHWAY ACCESS INSTALLATION
======================================================
The drivers named ETHNE contained in the NDIS directory
NDIS conform to the Network Driver Interface Specification
(NDIS) defined by Microsoft/3Com.
NDIS Driver Installation on PATHWAY ACCESS
------------------------------------------
1. Insert your copy of the Pathway Drivers diskette
into drive A.
2. Install the Pathway Drivers into your PC hard disk
drive. Type the following, indicating the subdirectory
where you want to install the program. Then press
<Enter>.
A:\> pwinstal C:
The pwinstall program automatically installs the driver
software in a new directory named \PATHWAY in your
specified drive. Your system will prompt you with
the following message once the process is complete:
"The Pathway Drivers have been copied successfully.
Refer to the documentation to complete driver
installation."
3. Insert your Driver Diskette in drive A: and copy the
NDIS driver to the subdirectory where you want to
install the Pathway software. Do this by typing
the following command from DOS:
A:\> Copy A:\NDIS\DOS\ETHNE.DOS C:\PATHWAY
4. Edit the CONFIG.SYS file to contain the
following command lines:
DEVICE=C:\PATHWAY\PWTCP.SYS
DEVICE=C:\PATHWAY\PROTMAN.EXE/I:C:\PATHWAY
DEVICE=C:\PATHWAY\ETHNE.DOS
5. Edit your PROTOCOL.INI file in the C:\PATHWAY
subdirectory to include the following section:
[EN166x]
DriverName = ETHNE$
6. Edit your AUTOEXEC.BAT file to include the following
command lines:
path=c:\pathway
ndis [-d:#]
pwbind
where:
-d is an optional parameter used for accessing
a specific module number within the PROTOCOL.INI.
In your PROTOCOL.INI file, a line enclosed by
square brackets designates the beginning of a
new module. Each module is referred to by a
hexadecimal number. The first module is module
number one. The second module is module two, and so on.
-- THE END --
.TOPIC:
DEC PATHWORKS
NDIS Driver for DEC PATHWORK Installation
=========================================
The drivers named ETHNE contained in the \NDIS\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. Type 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." If you are using an LK250 keyboard choose "YES."
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
NDIS 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 from DOS and
press <Enter> to bring up the PC-NFS installation
screen:
INSTALL <Enter>
3. Follow 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 onscreen. 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 into 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 \NDIS\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 --
.TOPIC:
Power Lan
Power Lan driver Installation
=============================
To install Accton's EN166x adapter with Power Lan system, user
can use 3 different methods as following:
A) Install Power Lan driver with Accton's EN166x adapter
B) Install Accton's DOS/ODI drivers for Power Lan
C) Install Accton's Packet drivers for Power Lan
A) Install Power Lan Driver with Accton's EN166x adapter
=====================================================
To install Power Lan driver with Accton's EN166x adapter
1.) Use Power Lan install program, and select "NE2000" item.
2.) Change Iobase and IRQ setting by Accton's 1Step setup program
and using the same port at NXNE2000 command line parameter:
/lp:Iobase /li:IRQ
Example ----- PLSTART.BAT
if %PLTREE%. == . set PLTREE=C:\PL
REM
REM - - - - - - - - - - - - - - - - - - Start NETBIOS - - - - - - - - - - - -
REM
%PLTREE%\PROGRAMS\nxne2000 /ln:0 /ses:14 /nam:17 /lp:300 /li:3
REM
B) Install Accton's DOS/ODI driver for Power Lan
=============================================
To install Accton DOS/ODI driver at Power Lan system:
1.) Copy Accton's DOS/ODI driver "MPX2PNP.COM from A:\NETWARE\ODI\DOSODI
to C:\PL\PROGRAMS
2.) Copy Novell's driver "LSL.COM from A:\NETWARE to C:\PL\PROGRAMS
3.) Create NET.CFG file as following example at C:\PL\PROGRAMS
4.) Use Power Lan install program, and select "ODI" item,
then add "LSL.COM" and "MPX2PNP.COM" before NXODI.EXE
at C:\PL\ADMIN\SYS\PLSTART.BAT's "start NETBIOS" section
Example ----- PLSTART.BAT
if %PLTREE%. == . set PLTREE=C:\PL
REM
REM - - - - - - - - - - - - - - - - - - Start NETBIOS - - - - - - - - - - - -
REM
LSL
%PLTREE%\MPX2PNP ------> Accton's MPX2 DOS/ODI driver
%PLTREE%\PROGRAMS\nxodi /ln:0 /ses:14 /nam:17
REM
Example ----- NET.CFG
Link Driver MPX2PNP
Frame ETHERNET_II
Protocol IPX 8137 ETHERNET_II
Port 300
INT 3
C) Install Accton's Packet driver for Power Lan
=============================================
To install Accton packet driver at Power Lan system:
1.) Copy Accton's packet driver "NWPD.COM" from A:\PKTDRV to
C:\PL\PROGRAMS
2.) Use Power Lan install program, and select "NXPACKET" item,
then add Accton's packet driver "NWPD.COM" before NXPACKET.EXE
at C:\PL\ADMIN\SYS\PLSTART.BAT's "start NETBIOS" section
Example ----- PLSTART.BAT
if %PLTREE%. == . set PLTREE=C:\PL
REM
REM - - - - - - - - - - - - - - - - - - Start NETBIOS - - - - - - - - - - - -
REM
%PLTREE%\NWPD 0x60 ------> Accton's packet driver
%PLTREE%\PROGRAMS\nxpacket /ln:0 /ses:14 /nam:17 /li:0x60
-- 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.