.TOPIC: Contents 1STEP Help Menu Netware Driver MPX Driver Technical Support Packet Driver NDIS Driver PC-NFS LAN Manager Remote BootROM LAN Server 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 ARROWS : Change parameter F3 : Config Software TAB : Move cursor forward F4 : Test Adapter SHIFT+TAB: Move cursor backward F6 : DOS Shell ALT+ : List parameters F10: Exit .TOPIC: Technical Support Accton Technology Corporation Technical Support For EN2212 PCMCIA Ethernet Adapters Accton provides free technical support to registered users. For more information, call the office that is closest to you. United States Phone: (510) 226-9800 7:00am to 5:00pm PST (800) 926-9288 FAX: (510) 226-9833 BBS: (510) 226-9832 14400-2400 baud Taiwan Phone: (886) 770-270 8:00am to 6:00pm FAX: (886) 770-267 BBS: (886) 770-654 14400-2400 baud Internet address: support@accton.com.tw -- THE END -- .TOPIC: MPX Driver Accton Technology Corporation MPX ODI Driver Installation For EN2212 PCMCIA Ethernet Adapters Copyright (C) 1994, 1995 by Accton Technology Corporation. All rights reserved. 1. To use the Accton MPX driver Accton MPX driver is a high performance NetWare 3.x ODI driver. It includes both workstation and server drivers: MPXPCM.COM : NetWare DOS/ODI workstation driver (A:\NETWARE\ODI\DOSODI\MPXPCM.COM) MPXPCM.LAN : NetWare DOS/ODI server driver (A:\NETWARE\ODI\SERVER\MPXPCM.LAN) To run MPXPCM.LAN as a server driver, you must modify STARTUP.NCF as follows: SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 4202 and use the LOAD & BIND command to start the server driver. Workstation driver MPXPCM.COM does not have any special requirement. You can run MPXPCM.COM in place of PCMMLID.COM. For example: LSL MPXPCM IPXODI NETX . . To achieve maximum performance, you must change server and workstation drivers to MPXPCM.LAN and MPXPCM.COM simultaneously. Otherwise, you get the same performance as that of NE2000-compatible drivers. Accton MPX driver supports NE2000 mode, and can process Ethernet_II, Ethernet 802.2, and Ethernet 802.3 frame types. -- THE END -- .TOPIC: Packet Driver Accton Technology Corporation Packet Driver Installation For EN2212 PCMCIA Ethernet Adapters Copyright (C) 1994, 1995 by Accton Technology Corporation. All rights reserved. To load the packet driver, type PCMPD 0X60. PCMPD syntax: PCMPD [-d] [-n] [-w] [-h] <PD_INT_NO> [IRQ] [IO_BASE] [MEM_BASE] where: [-d] The "-d" option does not start LAN card until this driver is called by the higher layer programs first. [-n] Your NOVELL server uses NOVELL ISO-like packets. Your NOVELL workstation uses NOVELL 8137 packets. You can use this option to convert NOVELL 8137 packets into NOVELL ISO-like packets. [-w] Steve Wallace added a hack to let the packet drivers run under Windows. This is not to be construed with the proper solution, which is to write a TCP/IP package for Windows. This hack is enabled only when you use the '-w' switch. [-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) where your card will be indicated whether the ring buffer is empty or not. [IO_BASE] This specifies the I/O address . [MEM_BASE] This specifies the shared RAM memory address. Example: The following command line loads the Accton PCMCIA Packet Driver at software interrupt 60h, I/O address 300, and hardware interrupt 5 (NE2000 MODE). PCMPD 0x60 5 0x300 or PCMPD 0x60 Note: The default I/O address is 300. Note: The default hardware interrupt is 5. Note: The placement of 0x prior to the parameters. After the Packet Driver is loaded, you can run the PC/TCP kernel ETHDRV.EXE. The PC is then ready for PC/TCP communications. To run PC/TCP applications, You need to load the PC/TCP Kernel ("ETHDRV.EXE"). a. Refer to the PC/TCP manual, Command Reference section, Chapter 2.3. b. The following example will load the Kernel and allocate 8 packet buffers. Increasing the number of packet buffers (from the default of 5) prevents packet dropping due to buffer shortage. ETHDRV -p 8 <Enter> c. At this point, you are ready to run PC/TCP applications (e.g. 'ftp', 'telnet'). example: ftp 192.72.24.202. 192.72.24.202 is the host address. For information regarding the "FTP's PC/TCP Network Software for DOS" packages, please contact: FTP Software, Inc. 26 Princess Street Wakefield, MA 01880 (617) 246-0900 How to Communicate with NCSA TelNet: 1. Make sure 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 on your system. Please refer to the NCSA documentation for detailed instructions. 3. Load Packet Driver (pcmpd 0x60): a. Refer to the "Packet Driver Syntax" section above. b. To view the hint screen, type pcmpd -h <Enter> c. The following example will load the packet driver using interrupt vector 60 (hex). The IO_BASE and IRQ will be read from the software configured adapter: pcmpd 0x60 <Enter> 4. At this point you are ready to run NCSA applications (e.g., 'ftp', 'telnet', etc.) for example : ftp 192.72.24.202. 192.72.24.202 is host address. For information regarding NCSA's products please contact: National Center for Supercomputing Applications 264 Computing Applications Building 605 E. Springfield Ave. Champaign, Ill. 61820 (217) 244-0638 telbug@ncsa.uiuc.edu -- THE END -- .TOPIC: Remote BootROM Accton's Ethernet Remote Boot ROM Device Copyright (C) 1994, 1995 by Accton Technology Corporation. All rights reserved. There will be two types of Ethernet Boot ROM supported by Accton Technology Corporation in the future. .TOPIC: NDIS Driver Accton Technology Corporation NDIS Driver Installation Overview For EN2212 PCMCIA Ethernet Adapters Copyright (C) 1994, 1995 by Accton Technology Corporation. All rights reserved. The drivers contained in directories \MSLANMAN.DOS and \NDIS are used with Accton PCMCIA Ethernet adapters. They are used with Com's 3+Open, Microsoft's OS/2 LAN Manager OEM, distribution packages Release 1.x or 2.x, and other compatible OEM versions of LAN Manager. The driver "ETHPCM.DOS" conforms to the Network Driver Interface Specification (NDIS) 2.0 defined by Microsoft/3Com. File Descriptions: \MSLANMAN.DOS\DRIVERS\ACCTON\ACCNE\ ETHPCM.DOS The DOS NDIS MAC driver PROTOCOL.INI A sample section of a PROTOCOL.INI file \MSLANMAN.DOS\DRIVERS\NIF\ ACCNE.NIF Network Information File \NDIS EN2212D.NIF Network Information File for LAN Server (DOS) EN2212O.NIF Network Information File for LAN Server (OS/2) README.TXT This file ETHPCM.DOS The DOS NDIS MAC driver ETHPCM.OS2 The OS/2 2.1 MAC driver OEMSETUP.INF Network Information File for Windows for Workgroups \NDIS\WFW\ README.TXT Installing Windows for Workgroups \NDIS\LANMAN\ README.TXT Installing MicroSoft's Lan Manager. \NDIS\LANSVR\ README.TXT Installing IBM's Lan Server \NDIS\BANYAN\ README.TXT Installing Banyan VINES \NDIS\PATHWAY\ README.TXT Installing Wollongong Pathway Access. \NDIS\PATHWORK\ README.TXT Installing DEC PATHWORKS \NDIS\PCNFS\ README.TXT Installing Sun PC-NFS 1. Installation Procedure The instruction to install the driver is summarized in the README.TXT file under each product's subdirectory. 2. Sample protocol.ini file and parameters [ACCNE_NIF] ; Default section of protocol.ini file for the Accton Adapter drivername = ETHPCM$ irq = 5 iobase = 0x300 ; End of this sample file Several parameters are included in the ACCNE_NIF section of the PROTOCOL.INI file. However, the only required parameter is the "drivername". The other parameters can use the default values. irq Specifies the interrupt channel used by the adapter. Acceptable values for this parameter are 2, 3, 4, 5, 10, 11, 12, and 15. iobase Specifies the iobase address used by the adapter. This parameter is given in hexadecimal values. Acceptable value for this parameter are 0x240, 0x280, 0x2C0, 0x300, 0x320, 0x340, 0x360. 3. Additional Parameters in the protocol.ini file for the Accton NDIS Driver Configuration: 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. ReceiveBuffers6 .. 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. ***** Note : Values for the preceding parameters are seldom changed by the user. Most of the time, the default values are used. ***** Trademarks: Microsoft OS/2 LAN Manager is a trademark of Microsoft Corporation. 3Com, 3+, 3+Open and EtherLink II are registered trademarks of 3Com Corporation. TROUBLE SHOOTING and ERROR MESSAGES Run Accton's "1Step" installation/diagnostic program to determine if the Network Adapter is working correctly. ERROR MESSAGES: ERROR: Adapter card not found or I/O port error. These are the possible reasons for this error: (1) The Adapter card is not installed correctly. (2) The failure is caused by more than one adapters trying to use the same set of I/O ports or IRQ number. (3) The Enabler ACCOPEN.EXE is not executed or it cannot enable the PCMCIA card because of resource conflicts with other PCMCIA cards. ERROR: Incorrect Media Setting or Bad Transceiver The following are the possible causes: (1) The transceiver is bad. (2) The cable is broken. (3) The cable is not attached. -- THE END -- .TOPIC: LAN Manager Accton EN2212 Ethernet PCMCIA Adapter NDIS Driver for LAN Manager Installation ========================================== Copyright (C) 1994, 1995 by Accton Technology Corporation. All rights reserved. The driver ETHPCM.DOS contained under directory \MSLANMAN.DOS is used with Accton Ethernet PCMCIA adapters in the LAN Manager environment. This driver conforms to the Network Driver Interface Specification (NDIS) 2.0 defined by Microsoft/3Com. 1. Installation Procedure for LAN Manager V2.0 -------------------------------------------------- a. Type "Setup" in the Lan Manager Directory. Press <Enter>. b. Press <Enter>. c. Select "Import Network Drivers..." in "Action". Press <Enter>. d. Type the source drive letter (A: or B:). e. Insert Driver Disk in the source drive. Press <Enter>. "Import Network Drivers" appears. f. Press the <SPACEBAR> to select Network Adapter Card, "Accton EN2212 Adapter Card". Press <Enter>. g. Press the <NO> button. h. Press <Enter> three times. "Network Driver" appears. i. Select "Accton EN2212 Ethernet Card" in the "Network Adapter Cards" menu. Press <Add driver>, <Add protocol>, and <OK>. "Workstation Primary parameters" appears. Press <OK>. k. Press <OK> three times. l. Select "Save" in "Action". m. Press <F3> to Exit. ******************************************************************************* 2. Installation Introduction for LAN Manager V2.1 -------------------------------------------------- a. Type "lmsetup" in the Lan Manager Directory. Press Enter. Microsoft LAN Manger Setup appears. b. Select "Network Drivers..." in "Configuration". Press Enter. c. Select <Add New Configs>. Press Enter. "Network Adapter Driver" appears. d. Select <Other Driver>. Press Enter. e. Insert the Driver Disk in the source drive. Type the drive letter (A: or B:). Push the <OK> button. f. In "Available Network Adapter Driver", select "Accton EN2212 Ethernet adapter". Push the <OK> button. g. Press the SPACEBAR to select the protocols. h. Push the <OK> button. "Configuration Complete" appears. i. Push the <Save> button. j. Press "F3" to exit. k. Press Enter. Sample configuration files: 3. Config.sys a. <V2.0> 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\ACCOPEN.EXE /int=3 /port=300 DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\ACCTON\ACCNE\ETHPCM.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.DOS b.<V2.1> 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\ACCOPEN.EXE /port=300 /int=5 DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\ACCTON\ACCNE\ETHPCM.DOS 4. Protocol.ini file for LAN Manager. a. V2.0 [PROTOCOL MANAGER] DRIVERNAME = PROTMAN$ [NETBEUI_XIF] Drivername = netbeui$ BINDINGS = "ACCNE_NIF" [ACCNE_NIF] ; PROTOCOL.INI for Accton EN2212 ethernet adapter drivername = ETHPCM$ irq = 5 iobase = 0x300 ; End of this sample file b. V2.1 [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 EN2212 ethernet adapter drivername = ETHPCM$ irq = 5 iobase = 0x300 ; End of this sample file 5. Autoexec.bat file for LAN Manager. a. V2.0 @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 ===== 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 ===== LANMAN 2.0 ==== b. V2.1 @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 === 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 === LANMAN 2.1 === -- THE END -- .TOPIC: LAN Server Accton EN2212 Ethernet PCMCIA Adapter NDIS Driver for LAN Server Installation ========================================= The driver ETHPCM.DOS contained in directory \NDIS is used for Accton Ethernet PCMCIA adapters in the LAN Server environment. This driver conforms to the Network Driver Interface Specification (NDIS) 2.0 defined by Microsoft/3Com. 1. DOS LAN REQUESTER ------------------------------ a. At the DOS prompt, insert the IBM LAN Support Program (LSP) Version 1.3x Diskette into the disk drive (A: or B: ). b. Type "dxmaid". The IBM logo appears. c. Press <Enter> twice. The Environment Information screen appears. d. Specify the values for the following fields on this screen. Use the <Space Bar> to toggle between selections. 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 the drive and directory fields: Source for LSP A:\ Target for new configuration C:\lsp e. Make sure the values are correct. Press <Enter> to store your choices. "Process Adapter Option Diskette" screen appears. g. Insert the Driver Diskette in the source drive and specify the path: A:\NDIS or B:\NDIS. Press <Enter>. g. The files are copied from the Driver Diskette to the target directory on the hard disk. g. Press <Enter> three times. h. Insert the LSP diskette and press <Enter>. The "Current Configuration" screen appears with the Accton EN2212 series adapter and protocols already selected ("IBM IEEE 802.2" and "IBM OS/2 NETBIOS"). i. Press F4. LSP is installed completely. j. Use a text editor to edit the config.sys file. Specify at least 20 files in the FILES= line, like this: FILES=20 Once you have saved the config.sys file, reboot the computer. k. Insert the DOS LAN Requester Install Diskette 1. l. Type: install. Press <Enter>. IBM logo appears. Press <Enter>. m. Press <Enter> two more times. The program prompts you for the pathname of the DOS LAN Requester directory. n. Specify the pathname for the DOS LAN Requester directory. (C:\DOSLAN is the default.) Press <Enter>. The program asks you which services you require. o. Highlight either the "Send messages" or "Send, View, Edit, and Log messages" option. (Normally, you select the second option.) Press <Enter> to confirm your selection. p. Specify the machine's ID and the domain ID. The domain ID must be the domain server ID and must be the same for all workstations on the network. q. Follow the prompts to complete the installation. ---THE END---- .TOPIC: Pathway Access Accton EN2212 Ethernet PCMCIA Adapter NDIS Driver for Wollongong Pathway Access Installation ======================================================== The driver ETHPCM.DOS contained in directory \NDIS is used with Accton Ethernet PCMCIA adapters in the Wollongong Pathway Access environment. This driver conforms to the Network Driver Interface Specification (NDIS) 2.0 defined by Microsoft/3Com. 1. INSTALLATION PROCEDURE a. NDIS driver Installation Procedure: 1. Insert your copy of Pathway Drivers diskette into drive A. Enter: C:\>A: 2. To install the software, enter: A:\> pwinstal C: where C: is the disk drive (you could also use D:, E:, and so on) that you intend to use for the installation of your Pathway software on a hard drive system. The PWINSTAL program automatically installs the driver software in a directory named \PATHWAY on the drive you specified. The installation is complete when you receive the following message: "The Pathway Drivers have been copied successfully. Refer to documentation to complete driver installation." 3. Insert the driver diskette in drive A and copy the NDIS driver to the subdirectory where you installed the Pathway software: A:\> Copy A:\NDIS\ETHPCM.DOS C:\PATHWAY 4. Edit the C:\CONFIG.SYS file to contain the following entries : DEVICE=C:\PATHWAY\ACCOPEN.EXE /int=5 /port=300 DEVICE=C:\PATHWAY\PWTCP.SYS DEVICE=C:\PATHWAY\PROTMAN.EXE/I:C:\PATHWAY DEVICE=C:\PATHWAY\ETHPCM.DOS At the same time copy accopen.exe from the driver diskette to the \PATHWAY directory. 5. Use a text editor to create a PROTOCOL.INI file in C:\PATHWAY with the following section: [EN2212] DriverName = ETHPCM$ 6. The startup batch file - autoexec.bat should have the following entries in the order shown : path=c:\pathway ndis [-d:#] pwbind where the -d option is used when accessing a specific module number within 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. b. Pathway Kernel Installation Procedure 1. Insert the Pathway Kernel diskette in drive A. Enter: C:\>A: 2. To install the software, enter: A:\> pwinstal C: where C: is the hard drive name (you could also use D:, E:, and so on) that you intend to use for the installation of your Pathway software. The PWINSTAL program automatically installs the driver software in a directory named \PATHWAY on the drive you specified. Diskette copying is complete when you see the following message: "Pathway Kernel files have been copied successfully. Reboot and refer to the documentation to complete kernel installation." 3. Remove the diskette from drive A: and reboot your PC by pressing <Ctrl>, <Alt>, and <Del> at the same time. 4. Change current directory to \PATHWAY. 5. Run the CUSTOM program to set or change the following parameters: . The Internet address . The subnet bits (if your network has subnetworks) . The gateway address (if you are communicating with hosts outside your local network) 6. Remove the diskette from drive A: and reboot your PC by pressing <Ctrl>, <Alt>, and <Del> at the same time. 7. Enter the following command to load the Kernel: C:\PATHWAY> PWTCP 8. Test your PC by using the PING program: C:\PATHWAY> PING hostname where hostname is the official name, alias, or Internet address of a host on your network that you expect to be able to communicate with. -- THE END -- .TOPIC: DEC PATHWORKS Accton EN2212 Ethernet PCMCIA Adapter NDIS Driver for DEC PATHWORKS Installation =========================================== The driver ETHPCM.DOS contained in directory \NDIS is used with Accton Ethernet PCMCIA adapters in the DEC Pathworks environment. This driver conforms to the Network Driver Interface Specification (NDIS) 2.0 defined by Microsoft/3Com. 1. INSTALLATION PROCEDURE: a. Insert the DEC PATHWORKS Client Setup diskette #1 in the diskette drive (A: or B:). b. Type Netsetup at the A: or B: prompt. c. Unless you have an LK250 keyboard, select "NO". d. Select the DECNET transport option and press <Enter>. e. Insert the DNET TRNSPRT diskette #1 in the diskette drive (A: or B:). f. Specify the target drive letter (C: or D:). g. At the prompt "Are you creating an initial workstation diskette?", select "NO". h. Type in the node name and address (i.e. node number). i. Type in the server node name and address (i.e. node number). j. Select "Ethernet" when prompted "Select the network adapter type:". k. Select "(Other NDIS)" when prompted "Select the network adapter:". l. Enter the full DRIVE:\PATH\FILENAME for NDIS driver: A:\ or B:\MSLANMAN.DOS\DRIVERS\ACCTON\ACCNE\ETHPCM.DOS Located in the Accton driver program diskette. m. Enter the DRIVE:\PATH for the protocol.ini file: A:\or B:\MSLANMAN.DOS\DRIVERS\ACCTON\ACCNE\ n. If they are all accurate, select "WRITE KEY DISK" to start installation. When prompted to copy files ETHPCM.DOS and protocol.ini, insert the Accton driver program diskette in the source drive (A: or B: dependent on path specified in step l. and m.) o. Follow the prompts until installation completes. p. At the Configuration screen, press F10 to exit to C:\. q. Using a text editor to edit protocol.ini in the DECNET sub-directory. Remove the semicolon (;) from the statement "NI_IRQ = 5" under [DATALINK], then check if the IRQ value in the new [ETHPCM.DOS] IRQ statement (maybe omitted) matches the NI_IRQ value in the [DATALINK] statement and Adapter IRQ value configured. Sample configuration files: 2. Config.sys 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\accopen.exe /int=5 /port=300 devicehigh=c:\decnet\protman.sys /I:D:\DECNET devicehigh=c:\decnet\ethpcm.dos rem device=c:\decnet\nddrv.sys rem device=c:\decnet\npdrv.sys FILES=50 BUFFERS=50 LASTDRIVE=v STACKS=9,256 3. Protocol.ini file for PATHWORKS v 4.1 ; PROTOCOL.INI file created by DNETOMO.V41 V4.1.060 ; via DNETWIK.V41 V4.1.047 [protocol manager] DRIVERNAME = PROTMAN$ [IPX4MAC] DRIVER = IPX$MAC BINDINGS = ETHPCM.DOS [DATALINK] DRIVERNAME = DLL$MAC LG_BUFFERS = 16 SM_BUFFERS = 6 OUTSTANDING = 32 HEURISTICS = 0 BINDINGS = ETHPCM.DOS ;Specify IRQ level used by the workstation network adapter NI_IRQ = 5 [ETHPCM.DOS] ; PROTOCOL.INI for ACCTON PCMCIA ethernet adapter drivername = ETHPCM$ ; irq = NI_IRQ = Adapter IRQ Setting irq = 5 iobase = 0x300 ; End of this sample file 4. 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 Accton Technology Corporation PC-NFS Software Interface Program Installation For EN2212 Ethernet PCMCIA Adapters Copyright (C) 1994, 1995 by Accton Technology Corporation. All rights reserved. Use the Accton EN2212 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 PCMPD.COM Accton Packet Driver for NE & WD serials cards INSTALLATION PROCEDURE: 1. Start the installation process by following the procedure described in the PC-NFS Manual for installing the Sun Microsystems PC-NFS program in your PC's hard disk. When asked to identify the type of network interface card, select "WD8003" from the list. Likewise, when asked for the interrupt level and the base I/O address, select: Interrupt Level (IRQ) 5 I/O Base Address 300h 2. Copy the following files to the \NFS directory on your hard disk: ACCOPEN.EXE PCNFSIF.SYS PCMPD.COM 3. Modify the config.sys file to include the following: DEVICE=C:\ANSI.SYS DEVICE=C:\NFS\ACCOEPN.EXE /int=5 /port=300 DEVICE=C:\NFS\PCNFS.SYS DEVICE=C:\NFS\SOCKDRV.SYS DEVICE=C:\NFS\PCNFSIF.SYS LASTDRIVE=V 4. Create or modify an existing autoexec.bat file to include the following: C:\NFS\PCMPD 98 SET PATH = C:\; C:\NFS SET TZ=CST6 SET NFSDRIVE=C PRT * NFSRUN For your system to work properly, make sure the C:\NFS\PCMPD 98 command line is placed before the NFSRUN command line. Allowable values for the software interrupt vector range from 96 to 128. The default software interrupt vector value is 98. 5. Reboot the PC and start the PC-NFS program. You may now run PC-NFS commands on your PC to communicate with other computers on the network that use the TCP/IP protocol. -- THE END -- .TOPIC: Windows for Workgroups Accton EN2212 Ethernet PCMCIA Adapter NDIS Driver for Windows for Workgroups Installation ===================================================== The driver ETHPCM.DOS contained in directory \NDIS is used with the Accton Ethernet PCMCIA adapter in the Windows for Workgroups environment. This driver conforms to the Network Driver Interface Specification (NDIS) 2.0 defined by Microsoft/3Com. 1. INSTALLATION PROCEDURE a. Select the "Control Panel" icon in Main group in Windows environment. b. Select the "Network" icon. c. Select "Adapters" in the "Option" dialog. d. push the <Add> button. e. Select "Unlisted or Updated Network Adapter". "Install driver" appears. f. Type in the drive and path name where the NDIS driver resides (e.g. A:\ndis or B:\ndis). g. Insert the Driver Diskette in the specified drive. h. Press <OK>. i. Press <close>. j. Press <OK> twice. k. Restart the computer. 2. Sample config.sys file FILES=30 buffers=30 STACKS=9,256 DEVICE=c:\windows\HIMEM.sys device=C:\WINDOWS\accopen.exe /port=300 /int=5 device=C:\WINDOWS\protman.dos /i:C:\WINDOWS device=C:\WINDOWS\ethpcm.dos device=C:\WINDOWS\workgrp.sys LASTDRIVE=y 3. Sample protocol.ini file for Windows for Workgroups [network.setup] version=0x3100 netcard=en2212d,1,EN2212D transport=ms$netbeui,MS$NETBEUI lana0=en2212d,1,ms$netbeui [protman] DriverName=PROTMAN$ PRIORITY=MS$NETBEUI [EN2212D] DriverName=ETHPCM$ [MS$NETBEUI] DriverName=netbeui$ SESSIONS=10 NCBS=32 BINDINGS=EN2212D LANABASE=0 4. Sample 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 EN2212 Ethernet PCMCIA Adapter NDIS Driver for Banyan VINES Installation ========================================= The driver ETHPCM.DOS contained in directory \NDIS is used with Accton Ethernet PCMCIA adapters in the Banyan VINES environment. This driver conforms to the Network Driver Interface Specification (NDIS) 2.0 defined by Microsoft/3Com. 1. Installation Procedure for Banyan VINES --------------------------------------------- a. Type Pcconfig. Press <Enter>. "Configuring A PC for the Network" appears. b. Select "1 - Network Card Setting". Press <Enter>. "The possible hardware configuration option are" appears. c. Select "NDIS Ethernet". Press <Enter>. d. Type in the desired interrupt number, and "EN2212" to the "PROTOCOL bindings =" prompt. e. Press 'F10' when done. Press <Esc> to exit. f. Select "2 - Login Environment Settings. " Press <Enter>. g. Select "1 - Select Default Communications Driver." Press <Enter>. h. Select "NDIS Ethernet". Press <Esc> to exit this menu. i. Press 'F10' when all done. "Please wait ...." appears. k. Modify the config.sys and protocol.ini files. See the examples below. l. Copy accopen.exe from the installation diskette to the \banyan directory. Sample configuration files: 2. Config.sys device=c:\banyan\accopen.exe /int=3 /port=300 device=c:\banyan\protman.dos/i:c:\banyan device=c:\banyan\ethpcm.dos 3. Protocol.ini file for LAN Manager. [protocol manager] DriverName = PROTMAN$ [EN2212] DriverName = ethpcm$ irq = 5 iobase = 0x300 -- THE END -- .TOPIC: Netware Driver Accton Technology Corporation Netware Driver Installation Overview For EN2212 PCMCIA Ethernet Adapters Copyright (C) 1994, 1995 by Accton Technology Corporation. All rights reserved. This README file is an explanation of the files contained in the \NETWARE subdirectory of this diskette. For more information, please refer to the "NOVELL NetWare ODI Shell for DOS" manual. LSL.COM: This file implements the Link Support Layer for DOS/ODI workstations and is the program that is generally loaded first after 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 what IPX.COM does for DOS workstations. It is loaded after the LAN driver. Other protocols can be loaded in place of it or along 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 Netbios emulation program (INT 5CH interface) allows you to run Netbios application programs based on the NETBIOS.EXE interface. The running sequence is: 1. IPX shell driver ACCOPEN.EXE /INT=5 /PORT=300 --> PCMCIA Enabler IPX.COM NETBIOS.EXE --> netbios emulation interface ... 2. DOS/ODI driver LSL.COM ACCOPEN.EXE /INT=5 /PORT=300 --> PCMCIA Enabler PCMMLID.COM --> Accton DOS/ODI driver IPXODI.COM NETBIOS.EXE ... If the DOS/ODI driver PCMMLID.COM executed successfully, it would display the adapter mode and configuration information. Otherwise you would see an error message and the cause of the failure. Note the PCMCIA Adapter must be enabled by ACCOPEN.EXE before issuing the PCMMLID.COM command. Here is the list of error messages the driver may display and the correction method: * "The board cannot be found." The adapter does not exist or the driver does not recognize the adapter. Correction: Insert an Accton PCMCIA adapter into the slot. Enable the Adapter by using the ACCOPEN.EXE enabler. * "Board RAM failed the memory test." The RAM buffer on the adapter failed. Correction: Insert a new adapter and run the driver again. * "The board did not respond to the initialization command." The driver recognized the adapter but the adapter failed to respond. Correction: Insert a new adapter and run the driver again. * "There is no cable connecting to the adapter." There is no cable connecting to the adapter or the transceiver within the adapter failed. Correction: Connect the cable to the adapter and run the driver again. Normally, you do not need a NET.CFG file because the established defaults are adequate for your network. One exception is when your workstation has more than one network adapters. In this case, for each adapter, there must exist a MLID section in the NET.CFG file. Note: ODI driver always parses your NET.CFG file first. The configuration in NET.CFG takes precedence over the parameter settings stored in the internal memory of the adapter. Below is a sample NET.CFG file: LINK DRIVER PCMMLID INT 5 PORT 300 : : You can consult "NetWare 386 Installation, Appendix E" for more information about NET.CFG. Novell has already changed the Ethernet default frame type to 802.2 starting with the release of NetWare v4.0. The move has to be made to enable it to better support future protocol and networking features. Some of these features are IPX with checksum, security enhancements, and protocol independence. Following this change, the default frame type of DOS/ODI driver is Ethernet 802.2 when there is no protocol binding in NET.CFG file. In this case, if your server is not NetWare v4.0, please make sure the Ethernet 802.2 frame type has been bound before logging in. -- THE END -- .TOPIC: PC-NFS Accton Technology Corporation PC-NFS Software Interface Program Installation For EN2212 PCMCIA Ethernet Adapters Copyright (C) 1994, 1995 by Accton Technology Corporation. All rights reserved. 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 PCMPD.COM Accton Packet Driver INSTALLATION PROCEDURE: 1. Start the installation process by following the procedure described in the PC-NFS Manual for installing the Sun Microsystems PC-NFS program in your PC's hard disk. When asked to identify the type of network interface card you are using, select "WD8003" from the list. Likewise, when asked for the interrupt level and the base I/O address, select: Interrupt Level (IRQ) 5 I/O Base Address 300h 2. Copy the following files to the \NFS directory of your hard disk: PCNFSIF.SYS PCMPD.COM 3. Modify the config.sys file to include the following entries: DEVICE=C:\ANSI.SYS DEVICE=C:\NFS\ACCOPEN.EXE /int=5 /port=300 DEVICE=C:\NFS\PCNFS.SYS DEVICE=C:\NFS\SOCKDRV.SYS DEVICE=C:\NFS\PCNFSIF.SYS LASTDRIVE=V 4. Create or modify the existing autoexec.bat file to include the following: C:\NFS\PCMPD 98 SET PATH = C:\; C:\NFS SET TZ=CST6 SET NFSDRIVE=C PRT * NFSRUN For your system to work properly, make sure that the C:\NFS\PCMPD 98 command line is placed before the NFSRUN command line. For more information on the PCMPD.COM program, refer to the README.TXT file of the Accton Packet Driver for NE & WD series adapters. Allowable values for the software interrupt vector range from 96 to 128. The default software interrupt vector value is 98. 5. Reboot the PC and start the PC-NFS program. You may now run PC-NFS commands on your PC to allow communication with other computers on the network that use the TCP/IP protocol. -- 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.