.TOPIC:
Contents
1STEP Help Menu Netware Driver
MPX Driver Netware ODI Driver
Technical Support NDIS Driver
Packet Driver LAN Manager
PC-NFS LAN Server
Remote BootROM Windows for Workgroups
Banyan VINES
Pathway Access
DEC PATHWORKS
SUN PC-NFS
[TAB]: Forward [SHIFT+TAB]: Backward [C]: Contents [E]: Exit
.TOPIC:
1STEP Help Menu
[ 1Step Help Menu ]
< Function Key> < Control Key >
F1 : Help ALT : Menu
F2 : AutoConfig Hardware TAB : Move cursor forward
F3 : Config Software ARROWS : Change parameter
F4 : Test Adapter SHIFT+TAB: Move cursor backward
F5 : Update Driver ALT+ : List parameters
F6 : Dos Shell
F10: Exit
[ 1Step Command Set ]
Syntax: 1STEP ?
Description: Displays available 1STEP commands
Syntax: 1STEP/A
Description: Autoconfigures the adapter
Syntax: 1STEP <filename.1st>
Description: Loads the specified configuration file
(*.1st) into the adapter's EEPROM to configure
the adapter's hardware settings
Syntax: 1STEP /D:<path>
Description: Specifies which IO_BASE you want to use
(i.e., for single card only). Allowable
values include 300, 320, 340, 360, 200, 220, 240, 260
Syntax: 1STEP/S <filename.1st>
Description: Loads the specified configuration file
(*.1st) into the adapter's EEPROM to configure
both hardware and software settings. For NetWare
applications, a batch file to run the software
driver is automatically created
Syntax: 1STEP /I: IOBASE
Description: Loads the specified IO_BASE address.
.TOPIC:
Technical Support
Accton Technology Corporation
Ethernet Adapter
==============================
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@mis.accton.com.tw
-- THE END --
.TOPIC:
MPX Driver
Accton Technology Corporation
About MPX
==============================
Key points for high MPX performance
------------------------------------
Accton's MPX Ethernet adapters are
performance-tuned for heavy network loads, like
transferring large files. This section describes
steps to optimize its performance on NetWare.
1. Make sure to install an Accton's adapter in both
the workstation and the file server.
2. Install both the workstation and the file
server drivers respectively.
a. ACCTON.COM is your workstation driver for NetWare DOS/ODI.
It is found in your Driver Diskette
(\NETWARE\ODI\DOSODI\ACCTON.COM)
b. ACCTON.LAN is your server driver for NetWare 3.x.
It is found in your Driver Diskette
(\NETWARE\ODI\3.1x\ACCTON.LAN)
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
All trademarks or brand names mentioned are properties
of their respective owners.
-- THE END --
.TOPIC:
Packet Driver
Accton Technology Corporation
PACKET DRIVER INSTALLATION
==============================
Copyright (c) 1993, 1994 by Accton Technology
Corporation. All rights reserved.
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 adapter, the following command line
loads the Packet Driver at software interrupt 60h,
at I/O address 300 and hardware interrupt 3.
NWPD 0x60 3 0x300
Since the default I/O address for this adapter is 300 and the
default IRQ is 3, the above command may be simplified to:
NWPD 0x60
Note
----
Address parameters, such as the software interrupt and I/O address
are preceded by "0x". For example, "0x60" and "0x300".
Packet Driver Application: Using adapter on PC/TCP Environment
--------------------------------------------------------------
1. Load your Packet Driver.
2. Load the PC/TCP kernel ETHDRV.EXE. See following
example:
To load the PC/TCP kernel and allocate 8 packet buffers,
type the following:
ETHDRV -p 8 <Enter>
This will increase the number of packet buffers from
5 (default) to 8.
3. You are now ready to run any PC/TCP application, like
FTP's telnet.
Packet Driver Application: Communicating with NCSA Telnet
---------------------------------------------------------
1. Make sure that you have the correct version of NCSA
Telnet for the PC. You need version 2.3 or later to
support the packet driver interface.
2. Install the NCSA software onto your system. Refer
to the NCSA documentation for detailed instructions.
3. Load the Packet Driver (NWPD 0x60). Refer to the
corresponding section for details.
4. Get help or view the Packet Driver's syntax
by typing the following command:
nwpd -h <Enter>
5. Run the NCSA application that you need. To
do this, you need to know the host's
IP address. For example, ftp 192.72.24.202.
All trademarks or brand names mentioned are properties
of their respective owners.
-- THE END --
.TOPIC:
Remote BootROM
Accton's ETHERNET REMOTE BOOT ROM DEVICE
========================================
Copyright (c) 1993, 1994 by Accton Technology
Corporation. All rights reserved.
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. One types
of Boot ROMs available.
1. Generic Boot ROM (Model No. SW7129)
- Supports NetWare 3.x, 4.x and Microsoft
LAN Manager 2.x
Using the Generic Boot ROM (Model No. SW7129)
----------------------------------------------
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. Copy Novell's RPL.NLM to the server directory SYS:SYSTEM.
b. Copy Novell's RBOOT.RPL to the server directory SYS:LOGIN.
c. "Load" a server LAN driver and be sure to specify the
frame type that your workstation is going to use.
d. "Bind" IPX to each of the different frame types
(ETHERNET_802.2, ETHERNET_802.3, ETHERNET_II,
ETHERNET_SNAP) that you require.
e. "Load" RPL.NLM
f. "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.EXE files
* For the DOS ODI workstation with NetWare v3.x:
LSL.COM
NWMLID.COM (or NE2000.COM)
IPXODI.COM
NETX.EXE (or EMSNETX.EXE)
NET.CFG
* For the DOSODI workstation with NetWare v4.x:
LSL.COM
NWMLID.COM (or NE2000.COM)
IPXODI.COM
VLM.COM
* 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.
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.
All trademarks or brand names mentioned are properties of
their respective owners.
-- THE END --
.TOPIC:
NDIS Driver
Accton Technology Corporation
NDIS Driver Installation Overview
=================================
Copyright (c) 1993, 1994 by Accton Technology Corporation.
All rights reserved.
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\ETHNE\ACCNE\
ETHNE.DOS The DOS NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\MSLANMAN.DOS\DRIVERS\NIF\
ACCNE.NIF Network Information File
\MSLANMAN.OS2\DRIVERS\ETHNE\ACCTNE\
ETHNE.OS2 The OS/2 NDIS MAC driver
PROTOCOL.INI A sample section of PROTOCOL.INI file
\MSLANMAN.OS2\DRIVERS\NIF\
ACCNE.NIF Network Information File
\NDIS
EN1657O.NIF Network Information File for LAN Server (OS/2)
EN1657D.NIF Network Information File for LAN Server (DOS)
NDIS.TXT This readme file
ETHNE.OS2 The OS/2 NDIS MAC driver
ETHNE.DOS The DOS NDIS MAC driver
OEMSETUP.INF Network Information File for Windows for
Workgroups v3.1
\NDIS\WFW\
README.TXT The Installation guide for
Windows for Workgroups v3.1
\NDIS\LANMAN\
README.TXT The Installation guide for LAN Manager
\NDIS\LANSVR\
README.TXT The Installation guide for Lan Server
\NDIS\BANYAN\
README.TXT The Installation guide for Banyan VINES
\NDIS\PATHWAY\
README.TXT The Installation guide for Wollongong Pathway
Access.
\NDIS\PATHWORK\
README.TXT The Installation guide for DEC PATHWORKS
\NDIS\PCNFS\
README.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, 0x300, 0x320, 0x340, 0x360.
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:
ERROR: 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.
All trademarks or brand names mentioned are properties
of their respective companies.
-- 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. "NE2000 Compatible Adapter Card"
for the MPX 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 "NE2000 Compatible Adapter Card" to confirm any
MPX 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 "NE2000 Compatible Adapter Card"
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 "NE2000 Compatible Adapter Card"
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\ETHNE\ACCNE\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 NE2000 Compatible 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\ETHNE\ACCNE\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 NE2000 Compatible Adapter Card
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 ===
All trademarks or brand names mentioned are properties
of their respective companies.
-- THE END --
.TOPIC:
LAN Server
Accton Technology Corporation
NDIS DRIVER FOR LAN Server INSTALLATION
=======================================
Copyright (c) 1993, 1994 by Accton Technology Corporation.
All rights reserved.
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.30 (or 1.31) 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
B:\NDIS
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 NE2000
Compatible Ethernet 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
---------------
1. Copy ETHNE.OS2 and EN1657O.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 "NE2000 Compatible 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.
-- THE END --
.TOPIC:
Pathway Access
Accton Technology Corporation
NDIS DRIVER FOR WOLLONGONG PATHWAY ACCESS INSTALLATION
======================================================
Copyright (c) 1993, 1994 by Accton Technology Corporation.
All rights reserved.
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\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:
[EN1657]
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.
All trademarks or brand names mentioned are properties of their
respective owners.
-- THE END --
.TOPIC:
DEC PATHWORKS
Accton Technology Corporation
NDIS Driver for DEC PATHWORK Installation
=========================================
The drivers named ETHNE contained in the \NDIS
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\ETHNE\ACCNE\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\ETHNE\ACCNE\
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
drive 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 ETHERCoax/Pair-NE(2) 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
All trademarks or brand names mentioned are properties of their respective
companies.
-- THE END --
.TOPIC:
SUN PC-NFS
Accton Technology Corporation
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\ETHNE\ACCNE 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
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 [EN1657]
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 = EN1657$"
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:
Windows for Workgroups
Accton Technology Corporation
NDIS DRIVER FOR WINDOWS FOR WORKGROUPS 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)
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=EN1657d,1,EN1657D
transport=ms$netbeui,MS$NETBEUI
lana0=EN1657d,1,ms$netbeui
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI
[EN1657D]
DriverName=ETHNE$
[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=32
BINDINGS=EN1657D
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:
Banyan VINES
Accton Ethernet Adapter
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 EN1657 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$
[EN1657]
DriverName = ETHNE$
All trademarks or brand names mentioned are
properties of their respective companies.
-- THE END --
.TOPIC:
Netware Driver
Accton Technology Corporation
NetWare DRIVER INSTALLATION OVERVIEW
====================================
Copyright (c) 1993, 1994 by Accton Technology
Corporation. All rights reserved.
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
NWMLID.COM ---> Accton DOS ODI driver
IPXODI.COM
NETBIOS.EXE
...
------------------------------------------------------------
All trademarks or brand names mentioned are properties
of their respective owners.
...
-- THE END --
.TOPIC:
Netware ODI Driver
Accton Technology Corporation
NetWare DOS ODI Driver Installation
===================================
NetWare DOS 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 (NW311.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 NW311.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:]NW311 <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 NW311.LAN
Supported I/O port values are : 300, 320, 340, 360,
200, 220, 240, 260
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 NW311 <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).
NetWare DOS ODI Workstation Driver Installation (NetWare v3.11)
---------------------------------------------------------------
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
ipxodi
nwmlid
netx
2. You can now log into your network.
Note:
For better performance on NetWare, you can opt to use Accton's
MPX ODI drivers. Install ACCTON.LAN as the server driver, and
install ACCTON.COM as the workstation driver. For more information
see the MPX.TXT file.
NetWare DOS ODI Driver Installation (NetWare 4.0x)
==================================================
Requirements:
-------------
Accton Driver Diskette (ACC40.LAN)
Installation Procedure:
-----------------------
1. Insert the Accton Driver Diskette into drive A
and check the contents of subdirectory \NETWARE\ODI\4.00
It should contain the following file :
ACC40.LAN ------> Novell NetWare V4.0 Server Driver
ACC40.LDI ------> Novell NetWare V4.0 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.00)
and press <Enter>.
7. The ACC40.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. The architecture of V.40 driver is different from that
of V3.11. You should load MSM.NLM and ETHERTSM.NLM modules
separately before loading ACC40.LAN.
When loading ACC40.LAN, it will check whether these two
modules have been loaded, if not, it will load them
automatically. So after ACC40.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.
2. The default frame type for the ACC40.LAN binding is
Ethernet_802.2 and not Ethernet_802.3. This is the
difference between V3.11 and V4.0 drivers.
The ACC40.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.
3. Remember to specify LASTDRIVE=Z in the CONFIG.SYS file.
4. Edit the NET.CFG if you want to change some parameters.
For example, if you're using a NetWare 3.1x workstation and
wants to log into a NetWare v4.0x server. The default
frame type of NetWare 3.1x is Ethernet 802.3, while that of
NetWare v4.0 is Ethernet 802.2. Before you can log into
the NetWare v4.0, make sure there is a protocol binding
for Ethernet 802.3 in the server's NET.CFG file.
This is normally included in the [MLID] section. A sample
NET.CFG file is given below:
LINK DRIVER NWMLID
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.
Driver Installation for Novell NetWare OS/2 ODI
===============================================
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
All trademarks and brand names mentioned belong to their
respective owners.
-- THE END --
Driver Installation for Novell NetWare 386 V3.11
------------------------------------------------
This section describes the driver installation on
the Novell NetWAre 386 V3.11 environment.
1. Make sure that the original NetWare diskettes
have been duplicated for backup purpose.
If you have already duplicated the diskettes,
skip this step. Please refer to Novell NetWare
Installation Manuals for detailed description
of the backup process.
2. Insert the Driver Diskette into drive A:, and
check the contents of the subdirectory
\NETWARE\IPX. There should be 2 NetWare 3.11
driver programs in the subdirectory:
EP0100.LAN ----- Workstation Configuration File
EP0100SH.OBJ ----- Workstation Driver
3. Copy the EP0100.LAN and EP0100SH.OBJ files
into the NetWare diskette labeled LAN_DRV_003.
4. Insert the NetWare diskette WSGEN into
drive A:. Execute the WSGEN.EXE program
and specify a new path to LAN_DRV_003. From
the menu shown on your screen, choose the
target network adapter by selecting,
"ACCTON Ethernet Series v3.xx (yymmdd)"
from the choice list. This will allow the
WSGEN program to generate the NetWare
workstation execution program IPX.COM automatically.
IPX.COM File
------------
1. To simplify the installation procedure of the shell
driver, a ready IPX.COM is included. It can be
used for all settings of the NE2000 compatible mode.
2. Re-generate the IPX.COM or use DCONFIG to re-configure
IPX.COM, if necessary.
Function Enhancement
--------------------
The following items are functions enhanced by the
IPX driver.
1. Software Auto-configuration
The drivers automatically detect adapter configuration.
2. Transmission Line Auto-detection
The driver automatically detects the type of transmission
you use, when loaded into memory.
All trademarks or brand names mentioned are properties
of their respective owners.
-- THE END --
.TOPIC:
PC-NFS
Accton Technology Corporation
PC-NFS Software Interface Program Installation
==============================================
Using any Accton Ethernet LAN Adapter and the Accton
PC-NFS Software Interface Program, you can run the
Sun MicroSystems PC-NFS on your PC.
The following files will be used in this installation:
Files Contents
--------------------------------------------------------------
PCNFSIF.SYS PC-NFS Software Interface Program
NWPD.COM Accton packet driver
Installation
------------
1. Install the Sun Microsystems PC-NFS program in your
PC's hard disk. Refer to the PC-NFS Manual for more
details. Upon completing the installation process
an \NFS subdirectory is created in your
hard disk drive.
2. When prompted to identify the netowrk interface card
that your are using, select "WD8003" from the list.
3. Likewise, when asked for the interrupt and I/O base
address select the following respectively:
interrupt level (IRQ) 3
I/O Base Address 300h
4. Copy the following files in the \NFS directory
of your hard disk:
PCNFSIF.SYS
NWPD.COM
5. Modify the CONFIG.SYS file to include the following
command lines:
DEVICE=C:\ANSI.SYS
DEVICE=C:\NFS\PCNFS.SYS
DEVICE=C:\NFS\SOCKDRV.SYS
DEVICE=C:\NFS\PCNFSIF.SYS
LASTDRIVE=V
6. Create or modify an existing AUTOEXEC.BAT file
to include the following:
C:\NFS\NWPD 98
SET PATH = C:\; C:\NFS
SET TZ=CST6
SET NFSDRIVE=C
PRT *
REM execute the application you need
NFSRUN
Important notes about the AUTOEXEC.BAT:
---------------------------------------
a. For proper system operation, make sure that the
C:\NFS\NWPD 98 command line comes before
the NFSRUN command.
b. For more information about the NWPD.COM command,
please check the *.txt file in the PKTDRV
subdirectory of your driver diskette.
c. Allowable values for the software interrupt vector
range from 96 to 128. The default is 98.
7. Reboot the PC and start the PC-NFS program.
You may now run the PC-NFS commands on your PC
to allow communication with other computers on the
network that use the TCP/IP protocol.
-- THE END --
Trademarks
----------
All trademarks or brand names mentioned are properties
of their respective companies.
-- 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.