.TOPIC: Contents 1STEP Help Menu Netware Driver MPX2 Driver Netware ODI Driver Remote BootROM Netware OS2/ODI Driver NDIS Driver Windows for Workgroups 3.1 LAN Manager Windows for Workgroups 3.11 LAN Server Windows NT 3.5x SCO UNIX r3.2 v4 Windows 95 Banyan VINES Packet Driver Pathway Access PC/TCP DEC PATHWORKS NCSA SUN PC-NFS Power Lan LANtastic [TAB]: Forward [SHIFT+TAB]: Backward [C]: Contents [E]: Exit .TOPIC: 1STEP Help Menu [ 1Step Help Menu ] < Function Key> Software Installation F1 : Help F2 : Install Driver F3 : Update Driver F6 : Dos Shell F10: Exit < Control Key > ALT : Menu ARROWS : Change parameter TAB : Move cursor forward SHIFT+TAB: Move cursor backward ALT : List parameters ESC : Exit -- THE END -- .TOPIC: MPX2 Driver Digital Equipment Corporation MPX2 DRIVER INSTALLATION ============================= File Description ---------------- a. DE305.COM is the Digital's new MPX2 DOS/ODI driver It is found in your Driver Diskette (\NOVELL\DOSODI\DE305.COM) High performance MPX2 DOS/ODI driver ------------------------------------ DE305.COM is Digital's MPX2 DOS/ODI driver which can improve network performance not only at Netware 3.11 but also Netware 4.xx. To use DE305, it is not necessary to change server driver, just run it at client site, then you can get big performance improvement. LSL DE305 -----------> MPX2 workstation driver IPXODI NETX -- THE END -- .TOPIC: Remote BootROM Digital Equipment Corporation ETHERNET REMOTE BOOT ROM DEVICE =============================== This adapter provides an empty socket for installing the optional Boot ROM device. Once installed, the adapter is able to load DOS from server. This is useful for using the adapter in a diskless workstation. Two types of Boot ROMs available. They are as follows: 1. Ethernet Remote Reset Boot ROM (Model No. SW7140) - Supports the NetWare IPX workstation 2. Generic Boot ROM (Model No. SW7145) - Supports NetWare 3.x, 4.x and Microsoft LAN Manager V2.1 and LAN Server V2.1 Using the Ethernet Remote Boot ROM (SW7140) -------------------------------------------- The Ethernet Remote Reset Boot ROM is for NetWare applications. 1. Generate a DOS Image To allow remote booting, you should first generate a DOS image. See the corresponding section in your NetWare manuals for detailed procedure. 2. Run RPLFIX.COM This program is provided and developed by Novell to fix the bug that causes boot failure when using MS-DOS 5.0 or DR DOS 6.0. Users of MS-DOS 5.0 or DR DOS 6.0 MUST run this program after generating the DOS image. Failure to do so will result in boot failure. 3. Auto-detect adapter configuration Once you power on the host PC, the Boot ROM will automatically detect the configuration of the network adapter installed. The parameters detected will vary according to the type of network adapter. Corresponding values will be shown on screen. For related information, see section on "List of Adapter Parameters Automatically Detected by the Boot ROM". 4. Follow screen instructions to select the appropriate Ethernet_Type if necessary. See section on Ethernet Type Selection for more information. Note: The program automatically detects the adapter's parameter settings, including Frame type, RAM Test, RAM Size, IRQ value, I/O base address, data width, Ethernet-ID Ethernet Type Selection ----------------------- The Boot ROM device is compatible with both Ethernet_II and IEEE 802.3 Ethernet. 1. Upon power on the program automatically detects the adapter's configuration, and will display it on the screen. 2. When prompted to select a "frame type" choose an appropriate one for your adapter if necessary. For example, pressing "1" selects "Ethernet_II," while pressing "2" selects "802.3" Using the Generic Boot ROM (Model No. SW7145) ---------------------------------------------- This 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 vendor's driver or NE2000), and the NETX.COM files * For the DOS ODI workstation with NetWare v3.x: LSL.COM DE305.COM (or NE2000.COM) IPXODI.COM NETX.COM (or EMSNETX.EXE) NET.CFG * For the DOSODI workstation with NetWare v4.x: LSL.COM DE305.COM (or NE2000.COM) IPXODI.COM VLM.EXE * 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 This Generic Boot ROM does not provide remote boot capability on a Microsoft OS/2 system. There are one ways to install the remote boot software on the LAN Manager server. 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 DE305.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 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\DE305.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 = de305$ ;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 ~Digital~EtherPair 08002B ~ ,,, ~ RDOSA ~ ~ ~ ~ ~ ~ b. Insert the lines before the description of "profile and workstation records added by rplmgr" 08002B?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME) S ~ ~ ~,,, ~ RDOSA ~ DEFAULT *~New~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 EtherPair adapter = 08002B?????? [configuration] name = DOS401A os = DOS401 dirname = DOS dirname2 = DOS401 bblink = RDOSA fitfileshared = fits\dos401 fitfilepersonal = fits\dos401p comment = DOS 4.01 EtherPair adapter = 08002B?????? [configuration] name = DOS500A os = DOS500 dirname = DOS dirname2 = DOS500 bblink = RDOSA fitfileshared = fits\dos500 fitfilepersonal = fits\dos500p comment = DOS 5.00 EtherPair adapter = 08002B?????? And append the following line to RPLMGR.INI ; 08002B = (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. Remote Boot ROM Installation for LAN Server V2.1 or later versions ------------------------------------------------ This section describes the procedure to install the Generic Boot ROM program. Before starting with the installation process, make sure that the LAN Server program is installed. 1. Insert the Driver Diskette into your floppy drive and copy the DE305.DOS driver into the \IBMLAN\RPL\DOS subdirectory of your server. 2. Modify the PROTOCOL.INI file. Change bindings to include DE305.DOS; change DriverName to DE305.DOS. 3. Activate the LAN Requester program for creating the DOS image file. From DOS, type the following and press <Enter>. NET 4. Bring up the Manage Image screen. From the main menu, choose the Definition item and IPL image option. 5. Choose Create to bring the Create image profile. 6. Input Image ID name and Description to add a new Image ID into the Manage Image field. 7. Go back to the main screen, choose the Definition item and the Machine parameters option to bring up the Manage Machine parameters screen. 8. Choose Create, Show Machine Type option. Then select the Remote IPL workstation from the list onscreen. 9. Create a Remote IPX Requester Deft -- assign a machine ID, input network number, remote IPL server, server record identifier and image ID if necessary. 10. Follow screen instructions to change diskettes and copy files. 11. Choose the Action item and the Network devices option to run the remote boot ROM install service. A list of available services will be shown onscreen. 12. Select Server to display the Manage Network Services screen. 13. Choose Remote Boot to activate the Remote Boot function. This completes your installation. You can now power on your workstation and allow remote booting. -- THE END -- .TOPIC: Netware Driver Digital Equipment Corporation NETWARE DRIVER INSTALLATION OVERVIEW ==================================== This file describes the contents of the \NETWARE subdirectory. For more detailed information about NetWare installation, please refer to the "NOVELL NetWare ODI Shell for DOS" manual. List Of Files You Need ---------------------- ------------------------------------------------------ Filename Description ------------------------------------------------------ LSL.COM This file implements the Link Support Layer for DOS ODI workstations and is the program that is generally loaded first when booting. The Link Support Layer file enables the workstation to communicate over several protocols. IPXODI.COM This is Novell's protocol stack for DOS ODI workstations. It performs the same functions as the IPX.COM, which is used for DOS workstations. However it is optional and is loaded after the LAN driver. Other protocols can be loaded in its place or with it. This is one of the key features of the ODI environment. NETX.COM NetWare Network program. -------------------------------------- If you use You Need -------------------------------------- Conventional memory NETx.COM Expanded memory EMSNETx.EXE (LIM 4.0 EMS Compatible) Extended memory XMSNETx.EXE (XMS 2.0 compatible) --------------------------------------- NETBIOS.EXE The Netbios emulation program (INT 5CH interface) allows you to run Netbios application programs based on the NETBIOS.EXE interface. The running sequence is: a. IPX shell driver IPX.COM NETBIOS.EXE ---> netbios emulation ... interface b. DOS ODI driver LSL.COM DE305.COM ---> Digital MPX2 DOS ODI driver IPXODI.COM NETBIOS.EXE ... RXMONSTK.COM RXMONSTK.COM is Receive Monitor Utility for Monitor Type Applications (Such as Lan Analyzer) If the monitor type applications you are using seems to stop receiving network packets when you install a new LAN driver on your workstation, load the RXMONSTK.COM file. Load the RXMONSTK.COM file after the LSL.COM driver but before the LAN driver. The RXMONSTK.COM operates as a TSR and requires 2684 bytes of memory. You can load only one LAN driver when using the RxMonStk. The running sequence is: LSL.COM RXMONSTK.COM DE305.COM ---> Digital MPX2 DOS ODI driver IPXODI.COM ... -- THE END -- .TOPIC: Netware ODI Driver Digital Equipment Corporation NetWare ODI Driver Installation =============================== Content: A). NetWare DOS ODI Workstation Driver Installation for Novell 3.1x and Novell 4.x B). Novell NetWare V3.1x Server Driver Installation C). Novell NetWare V4.x Server Driver Installation A). NetWare DOS ODI Workstation Driver Installation for Novell 3.1x and Novell 4.x =================================================================== ========================================================== NOTE: The DE305.LAN DO support Novell 3.1x and Novell 4.x ========================================================== The driver DE305.COM is used for the Novell 3.1x and 4.x network environments. This section describes its installation. Once fully installed a workstation running this driver can log into a server running either NetWare v3.1x or v4.x. Requirements ------------ Make sure you have the following: 1. Driver Diskette 2. Novell DOS ODI Workstation Services Diskette Make a backup copy of your Driver Diskette and use the backup as your working diskette. Installation Procedure ---------------------- 1. Make sure that your network adapter is proper installed and the adapter proper configured to the appropriate hardware settings. 2. Run the following commands in the order given below, indicating the directory location or path for each command. Then press <Enter> after each line to continue. lsl <Enter> de305 <Enter> ipxodi <Enter> Note ---- DE305 is the Digital adapter's workstation driver for the Novell 3.1x and 4.x environments. If problems occur during the loading operation error messages will be shown onscreen to indicate unsuccessful loading of the driver. Installation Notes ------------------ 1. The NET.CFG file is automatically read when driver installation is successful. It contains the adapter's hardware and software configuration. 2. This file is especially needed when there are more than one network adapters installed inside the host PC. In this situation, make sure that each adapter's NET.CFG file has an MLID section. 3. The ODI driver parses the NET.CFG file first and recognizes the parameter settings in this file as the adapter's default, even though it conflicts with the setting stored in the EEPROM. In this situation, the adapter will fail to initialize. Sample NET.CFG File ------------------- LINK DRIVER DE305 INT 5 PORT 320 . . . See your NetWare 386 Installation Manual for more information about the NET.CFG file. 4. With the release of NetWare 4.x, Novell has changed the setting of the default Ethernet frame type to Ethernet 802.2. This is to allow better protocol support. In addition, additional features were added, including IPX with checksum, security enhancement and protocol independence. When using NetWare 4.x, make sure that the frame type is bound before logging into the server. List of Error Messages ---------------------- This section lists error messages detected when the driver installation fails. Error Message: "The board cannot be found." Possible Cause: The adapter does not exist, or driver does not recognize the adapter. Solution: Make sure that the adapter is properly plugged onto the host PC's slot. Error Message: "Board RAM failed the memory test." Possible Cause: Adapter's RAM buffer failure. Solution: Replace your network adapter. Call your dealer for assistance. Reinstall the adapter, including the driver. Error Message: "The board did not respond to the initialization command." Possible Cause: The driver recognizes the adapter, but the adapter fails to respond. Solution: Replace your network adapter. Call your dealer for assistance. Reinstall the adapter, including the driver. Error Message: "Adapter current mode is not supported or card not found." Possible Cause: The current adapter mode is to NE1000. Solution: Run the SETUP program and set adapter mode to NE2000. Error Message: "There is no cable connecting to adapter." Possible Cause: There is no cable connected to the adapter; or adapter's on-board transceiver failure. Solution: Check cable connections and run the driver again. B). Novell NetWare V3.1x Server Driver Installation =================================================== 1. Things You Need ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Before you start with the installation process make sure you have the following : a) Hardware Driver Disk b) Novell NetWare Version 3.11 System Diskette 2. How To Install O.S. Driver ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ a) Insert the Acc-10 Hardware Driver Disk into drive A and check the contents of subdirectory \NOVELL\SRVODI It should contain the following file : DE305.LAN ÄÄÄ Novell NetWare V3.11 Server Driver b) Copy the contents of the Novell NetWare 386 Version 3.11 System Diskette into your NetWare 386 server station hard disk. Please refer to your Novell NetWare 386 Installation Manual for details. c) Copy the DE305.LAN file from the Hardware Driver Disk into the NetWare server station hard disk. d) Run SERVER.EXE on the server station. Several NetWare messages will be shown on-screen. e) At the NetWare prompt (indicated by a colon), run the driver program, type the following line if using one adapter: : LOAD [d:]DE305 Frame=frame_type <Enter> or type the following line if more adapters are used: : LOAD [d:]DE305 BOARD=board# Frame=frame_type where board# starts 0 to 4, because number of adapters supported is 4 (You can reference the autoexec.ncf example included in the floppy) LOAD DE305 BOARD=0 FRAME=Ethernet_802.3 BIND IPX DE305 LOAD DE305 BOARD=0 FRAME=Ethernet_802.2 BIND IPX DE305 LOAD DE305 BOARD=0 FRAME=Ethernet_SNAP BIND IPX DE305 LOAD DE305 BOARD=0 FRAME=Ethernet_II BIND IPX DE305 f) Bind IPX with LAN driver, at the Netware server prompt, type : :BIND IPX DE305 <Enter> After pressing <Enter> the computer prompts you for the Network Number. For details on how to assign this number, please consult your NetWare 386 Installation Manual. 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 on-screen : IPX LAN Protocol bound to NE Mode vx.xxRxx (yymmdd). C). Novell NetWare V4.x Server Driver Installation ================================================== Requirements ------------ Make sure you have the following: 1. Driver Diskette 2. Novell DOS ODI Workstation Services Diskette Installation Procedure ---------------------- 1. Insert the Driver Diskette that comes with the package into drive A: and check the contents of the subdirectory \NOVELL\SRVODI It should have the following files: DE305.LAN ----> your Novell NetWare v4.x Server Driver DE305.LDI ----> your Novell NetWare v4.x Server Driver configuration file 2. At the NetWare prompt (indicated by the Server name), run the INSTALL.NLM program by typing: server name: LOAD INSTALL <Enter> 3. Follow screen instruction to complete the process. Respond to prompts displayed on the screen. Select the following items in the order given below. Press <Enter> to confirm each choice: Maintenance/Selective Install <Enter> LAN Driver Options (Configure/Load/...) <Enter> 4. Press the <Ins> key to insert other drivers you wish to install. 5. Press <F3> to display the driver loading path as follows: A:\NOVELL\SRVODI <Enter> 6. The DE305.LAN will appear as an item under the "Select a LAN Driver" menu. Choose the correct board number and Select it to load the driver and start the binding process. This will allow you to load and bind all 4 frame types supported by NetWare. 7. Next time you reboot your NetWare 4.x server, do so by following steps 2 to 4 above. Notes about the Novell v4.x and the v3.1x drivers -------------------------------------------------- 1. The NetWare v4.x and v3.11 drivers have different architectures. When using NetWare v4.x, you should load the MSM.NLM and ETHERTSM.NLM modules before loading server driver DE305.LAN. 2. DE305.LAN is your server driver for NetWare v4.x. When loading DE305.LAN, it will check whether or not these two modules (MSM.NLM and ETHERTSM.NLM) have been loaded. If not, it will load them automatically. 3. After the DE305.LAN is loaded, type the "MODULES" command to view and confirm that the additional modules, MSM.NLM and ETHERTSM.NLM loaded. 4. The default frame type DE305.LAN binding for NetWare v4.x is Ethernet_802.2 and not Ethernet_802.3. -- THE END -- .TOPIC: Netware OS2/ODI Driver Digital Equipment Corporation NETWARE OS/2 ODI DRIVER INSTALLATION ==================================== Requirements: ------------- Before you start with the installation process make sure you have the following: a. Digital 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. DE305.SYS ---- supported by Digital 1. The directory OS2ODI contains only an OS/2 driver,(DE305.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 DE305.SYS file into the NETWARE subdirectory of your hard disk. 4. Add or replace the DE305.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\DE305.SYS ; Digital 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 DE305 section of the NET.CFG file. A sample is shown below: Link Driver DE305 frame Ethernet_802.3 frame Ethernet_802.2 frame Ethernet_II frame Ethernet_snap protocol IPX 00 Ethernet_802.3 -- THE END -- .TOPIC: NDIS Driver DE305 DIGITAL EtherWORKS ISA Adapter NDIS Driver Installation Overview ==================================== The driver you need are in the directories MSLANMAN.DOS, MSLANMAN.OS2 and NDIS2. The NDIS drivers contained in these subdirectories are used with 3Com 3+Open, Microsoft OS/2 LAN Manager OEM distribution, Release 1.x or 2.x, and other compatible OEM versions of LAN Manager. The drivers named DE305 conform to the Network Driver Interface Specification (NDIS) defined by Microsoft/3Com. Included in MSLANMAN.DOS, MSLANMAN.OS2, and NDIS2 subdirectories are the following files: \MSLANMAN.DOS\DRIVERS\ETHERNET\DE305\ DE305.DOS The DOS NDIS MAC driver PROTOCOL.INI A sample section of PROTOCOL.INI file \MSLANMAN.DOS\DRIVERS\NIF\ DE305.NIF Network Information File \MSLANMAN.OS2\DRIVERS\ETHERNET\DE305\ DE305.OS2 The OS/2 NDIS MAC driver PROTOCOL.INI A sample section of PROTOCOL.INI file \MSLANMAN.OS2\DRIVERS\NIF\ DE305.NIF Network Information File \NDIS2\DOS DE305.NIF Network Information File for LAN Server (DOS) DE305.DOS The DOS NDIS MAC driver PROTOCOL.INI A sample section of PROTOCOL.INI file \NDIS2\OS2 DE305.NIF Network Information File for LAN Server (OS/2) DE305.OS2 The OS/2 NDIS MAC driver PROTOCOL.INI A sample section of PROTOCOL.INI file \NDIS2 README.TXT This readme file BANYAN.TXT The Installation guide for Banyan VINES LANMAN.TXT The Installation guide for LAN Manager LANSRV.TXT The Installation guide for Lan Server LANTASTI.TXT The Installation guide for LANTASTIC PATHWAY.TXT The Installation guide for Wollongong Pathway Access. PATHWRKS.TXT The Installation guide for DEC PATHWORKS PCNFS.TXT The Installation guide for Sun PC-NFS WFW.TXT The Installation guide for Windows for Workgroups v3.1 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 ---------------------------------------- [NDIS2_NIF] ; Default section of protocol.ini file for the Digital Adapter drivername = DE305$ irq = 3 iobase = 0x300 ; End of this sample file There are several parameters included in the NDIS2_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, Digital's NDIS driver will automatically detect them. irq Specifies the interrupt channel used by the adapter. Acceptable values for this parameter are 2/9, 3, 4, 5, 10, 11, 12 ,and 15. However, some of the mentioned Digital adapters do not support all the acceptable values. iobase Specifies the iobase address used by the adapter. This parameter is given in hexadecimal values. Acceptable value for this parameter are 0x200, 0x220, 0x240, 0x260, 0x280, 0x2a0, 0x2c0, 0x2e0, 0x300, 0x320, 0x340, 0x360, 0x380, 0x3a0, 0x3c0, 0x3e0. List of Additional Parameters in the PROTOCOL.INI file for the NDIS Driver Configuration ------------------------------------------------------ Note that values for the following parameters are seldom changed by the user. Most of the time the default values are used. Keyword Parameter MaxMultiCast 1 .. 1000 Default 10 Maximum number of MultiCast Addresses. This configures the size of the MultiCast Address Table. MaxRequests 6 .. 64 Default 8 Maximum number of outstanding General Requests. This configures the size of the General Request Queue. MaxTransmits 6 .. 64 Default 12 Maximum number of outstanding TransmitChain commands. This configures the size of the TransmitChain Request Queue. ReceiveChains 6 .. 96 Default 12 Maximum number of outstanding ReceiveChain commands. This configures the size of the ReceiveChain Request Queue. ReceiveBuffers 6 .. 96 Default 12 Configures the number of the Receive buffers in the Receive Buffer Pool. TransmitBufSize 128 .. 1514 Default 1514 Configures the size (in bytes) of buffers in the Transmit Buffer Pool. Troubleshooting and Error Messages ---------------------------------- To check for problems, please run the Test Adapter option from 1Step. Error Message: ERROR: Adapter card not found or I/O port error. Possible Causes: 1. The adapter is not installed correctly in its slot. 2. I/O port failure due to incompatibility between the computer and the card Solution: Run the 1Step program to determine reason for the error. Error Message: DE305-Error-01: Incorrect Media Setting or Bad Transceiver Possible Causes: 1. The transceiver failure. 2. Cable breaks. 3. Loose cable connection. Solution: Run 1Step's diagnostic program to determine the cause of the problem. -- THE END -- .TOPIC: LAN Manager DE305 DIGITAL EtherWORKS ISA Adapter NDIS DRIVER FOR LAN MANAGER INSTALLATION ========================================= The drivers named DE305 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. "DE305 DIGITAL EtherWORKS ISA Adapter" for the MPX2 Ethernet Adapters. Then press <Enter> to confirm your choice. 5. Follow screen instructions to complete the process, until the Network Driver appears onscreen. 6. Identify your Network Adapter if asked. For example, select "DE305 DIGITAL EtherWORKS ISA Adapter" to confirm any MPX2 Ethernet Adapter. 7. Select the <Add driver> and the <Add protocol> options. Then select <OK> to confirm your choices. The Workstation's primary parameters should appear onscreen. 8. Respond to all prompts issued onscreen to complete the process. Select <OK> to confirm a choice. 9. Save all selections. Choose "Save" from the "Action Menu" 10. Press <F3> to exit. NDIS Driver Installation on LAN Manager v2.1 -------------------------------------------- 1. Type lmsetup in the LAN Manager directory and press <Enter>. The Microsoft LAN Manager Setup screen should appear. 2. Choose "Network Drivers..." in the "Configuration" field. Press <Enter> to confirm your choice. 3. Choose <Add New Configs> and press <Enter> to display a list of Network Adapter Drivers. 4. Choose <Other Driver> and press <Enter>. 5. Insert the Driver Diskette into drive A: or B: of your PC. Indicate the drive location of the diskette and select <OK> to proceed. 6. Select the appropriate Network Adapter Driver from the list. For example, select "DE305 DIGITAL EtherWORKS ISA Adapter." Select <OK> to confirm your choice. 7. Select an appropriate protocol. Use the <Space bar> to highlight your choice. 8. Select <OK> to confirm your choice. A Configuration Complete message should appear onscreen. 9. Save the configuration. Select <Save>. 10. Press <F3> to exit. NDIS Driver Installation on LAN Manager v2.2 -------------------------------------------- 1. Type setup in the LAN Manager directory and press <Enter>. The Microsoft LAN Manager Setup screen should appear. 2. Choose "Network Drivers" from the "Configuration" field. Press <Enter> to confirm your choice. 3. Choose <Add New Config> and press <Enter> to display a list of Network Adapter Drivers. 4. Choose <Other Driver> and press <Enter>. 5. Insert the Driver Diskette into drive A: or B: of your PC. Indicate the drive location of the diskette and select <OK> to proceed. 6. Select the appropriate Network Adapter Driver from the list. For example, select "DE305 DIGITAL EtherWORKS ISA Adapter." Select <OK> to confirm your choice. 7. Select an appropriate protocol. Use the <Space bar> to highlight your choice. If you have chosen the TCP/IP protocol, you will be prompted to key-in the IP address, the subnet mask, and the default gateway (router). By the default, the workstation number of NetBios session is set to 6. Please consult Microsoft LAN Manager Installation Manual for more details, or check the online help. 8. Select <OK> to confirm your choice. A Configuration Complete message should appear onscreen. 9. Save the configuration. Select <Save>. 10. Press <F3> to exit. If you are installing the LAN Manager for the first time, you will be prompted to key-in the default user name and domain of the workstation, as well as to answer the questions concerning Windows environment and memory management. Just follow the instructions on the screen. Sample Configuration Files -------------------------- LAN Manager 2.0 CONFIG.SYS File LASTDRIVE=Z BUFFERS = 35 FILES = 35 SHELL=C:\DOS50\COMMAND.COM C:\DOS50\e:1000 /p /E:1024 DEVICE=C:\HIMEM.SYS DEVICE=C:\DOS50\SETVER.EXE DOS=HIGH,UMB DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\DE305\DE305.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.DOS PROTOCOL.INI File [PROTOCOL MANAGER] DRIVERNAME = PROTMAN$ [NETBEUI_XIF] Drivername = netbeui$ BINDINGS = "DE305_NIF" [DE305_NIF] ; PROTOCOL.INI for DE305 DIGITAL EtherWORKS ISA Adapter drivername = DE305$ ; irq = 3 ; iobase = 0x300 ; End of this sample file AUTOEXEC.BAT File @echo off PROMPT $P$G PATH=c:\PE2;C:\DOS50;C:\NC; APPEND=C:\PE2;C:\DOS50; REM ====== LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES REM ===== LANMAN 2.0 ==== SET PATH=C:\LANMAN.DOS\NETPROG;%PATH% C:\LANMAN.DOS\DRIVERS\PROTMAN\NETBIND NET START WORKSTATION REM ====== LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES REM ===== LANMAN 2.0 ==== LAN Manager 2.1 or LAN Manager 2.2 CONFIG.SYS File LASTDRIVE=Z BUFFERS = 35 FILES = 35 SHELL=C:\DOS50\COMMAND.COM C:\DOS50\e:1000 /p /E:1024 DEVICE=C:\HIMEM.SYS DEVICE=C:\LANMAN.DOS\DRIVERS\DOSUTILS\EMM386.EXE NoEMS DEVICE=C:\DOS50\SETVER.EXE DOS=HIGH,UMB DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\DE305\DE305.DOS PROTOCOL.INI File [PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES PRIORITY = NETBEUI [NETBEUI_XIF] Drivername = netbeui$ SESSIONS = 6 NCBS = 12 BINDINGS = "DE305_NIF" LANABASE = 0 [DE305_NIF] ; PROTOCOL.INI for DE305 DIGITAL EtherWORKS ISA Adapter drivername = DE305$ ; irq = 3 ; iobase = 0x300 ; End of this sample file AUTOEXEC.BAT File @echo off PROMPT $P$G PATH=c:\PE2;C:\DOS50;C:\NC; APPEND=C:\PE2;C:\DOS50; @REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES @REM=== LANMAN 2.1 === SET PATH=C:\LANMAN.DOS\NETPROG;%PATH% NET START WORKSTATION LOAD NETBEUI @REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES @REM === LANMAN 2.1 === -- THE END -- .TOPIC: LAN Server DE305 DIGITAL EtherWORKS ISA Adapter NDIS DRIVER FOR LAN SERVER INSTALLATION ======================================= The drivers named DE305 contained in the directory NDIS conform to the Network Driver Interface Specification (NDIS) defined by Microsoft/3Com. DOS LAN Requester ----------------- 1. Insert the IBM LAN Support Program (LSP) Version 1.36 Diskette into your floppy drive (drive A: or B:). 2. Type the following from your DOS prompt and press <Enter>: A:>dxmaid 3. The screen will display the IBM logo. Press <Enter> twice until the "Environment Information" appears onscreen. 4. Responds to the screen prompts, specifying the following values for each field: Use the <Space Bar> to toggle between choices: Configuration for this computer? Yes Use existing configuration information? Yes Do you have adapter option diskettes? Yes Are you configuring for two adapters? No Do you need 802.2 interface support? Yes Type change as needed to drive and directory information below: Source for LSP A:\ Target for new configuration C:\lsp 5. Make sure that the values given above are correct. Press <Enter> to store your choices. 6. Insert the Driver Diskette in your source drive. Specify the path and press <Enter> to proceed. Examples: A:\NDIS2\DOS B:\NDIS2\DOS 7. Upon pressing <Enter> the necessary drives from the Driver Diskette are copies onto you target directory in the hard disk. 8. Follow screen instructions to complete the process. Simply pressing <Enter> for each screen display will select the default options. Press <Enter> three times, until you reach the display prompting you to insert the LSP diskette. 9. Insert the LSP diskette as prompted. Press <Enter> to acknowledge completion of the action. 10. A screen showing the current configuration detected will be displayed. It should show the Digital series adapter and the protocols already selected (i.e., "IBM IEEE 802.2" and "IBM OS/2 NETBIOS"). 11. Press <F4>. to save the new configuration. This completes the LSP installation. Note: You should have defined in your CONFIG.SYS the minimum of 20 files, i.e. FILES=20, to run the software properly. Change the FILES line using the text editor if needed. If installing LSP for the first time, you should complete the installation by typing install and following the further instructions on screen. 12. Use a text editor to edit the CONFIG.SYS file. Specify at least 20 file in the FILES= line. Modify it to the following: FILES=20 13. Save the configuration and reset your computer. 14. Insert the DOS LAN Requester Install Diskette 1 into your floppy drive. 15. Type the following and press <Enter>: INSTALL <Enter> 16. The IBM logo will again appear on the screen. Press <Enter> to move on to the next screen. 17. Follow screen instructions, pressing <Enter> to move from screen-to-screen until you are prompted to indicate the pathname of the DOS LAN Requester directory. TIP: After the IBM logo appears on the screen, press <Enter> twice to reach this screen. 18. Specify the pathname for the DOS LAN Requester directory (C:\DOSLAN is the default). Then press <Enter> to continue. 19. The program will ask you for the services that you require. 20. Highlight the appropriate option. Select either "Send messages" or "Send, View, Edit, and Log message" option. TIP: Normally, second option "Send, View, Edit and Log message" is selected. 21. Specify the PC's ID and domain ID. The domain ID is the domain server ID; it should be the same for all workstations of the network. 22. Follow screen prompts to complete the installation. OS/2 LAN Server 3.0 ------------------- 1. Copy DE305.OS2 and DE305.NIF files from your Driver diskette (\NDIS2) 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 "DE305 DIGITAL EtherWORKS ISA adapter" when prompted to identify you Network Adapter. Then click the <Add> button. 13. Select "802.2" from the list and click the <Add> button. 14. Select IBM NETBIOS from the list and click the <Add> button 15. Select <OK> to confirm all selections. 16. Follow screen instructions to complete the process, selecting <OK> to accept default selections. 17. Continue pressing <OK> until your screen prompts you to backup old CONFIG.SYS and AUTOEXEC.BAT and create a new CONFIG.SYS and AUTOEXEC.BAT. Also select <OK> to confirm this. 18. Installation is complete now. Reset your PC by turning it off and on. OS/2 LAN Server 4.0 ------------------- 1. In OS2 desktop, click the MPTS(Multi-Protocol Transport Service) icon. The IBM logo should appear on screen. 2. Click the <OK> button. 3. Click the <Configure> button. 4. Select the "LAN adapters and protocols" item, then click <Configure> button. 5. Click <Other adapters...> button. 6. Insert Digital Ethernet Adapter Driver Diskette into a specified drive (A: or B:), then enter the driver path like A:\NDIS2\OS2, (or B:\NDIS2\OS2, etc.) and click <OK> button 7. Select "DE305 DIGITAL EtherWORKS ISA Adapter" from Network Adapters list when prompted to identify you Network Adapter. Then click the <Add> button. 8. Select "IBM 802.2" from the Protocols list and click the <Add> button. 9. Select "IBM OS2 NETBIOS" from the Protocols list and click the <Add> button 10. Select "IBM Netware Requester Support" from the Protocols list and click the <Add> button if you need to logon NETWARE server. 11. Select <OK> to confirm all selections. 12. Click <Close> button in the Configure window. 13. Click <Exit> button in the MPTS window. 14. Click <Exit> button, then your screen will prompts you to backup old CONFIG.SYS and AUTOEXEC.BAT and create a new CONFIG.SYS and AUTOEXEC.BAT. Also select <OK> to confirm this. 15. Installation is complete now. Reset your PC by turning it off and on. -- THE END -- .TOPIC: Windows for Workgroups 3.1 DE305 DIGITAL EtherWORKS ISA Adapter NDIS DRIVER FOR WINDOWS FOR WORKGROUPS 3.1 INSTALLATION ======================================================= The drivers named DE305 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:\NDIS2\DOS) is given. 8. Insert the Digital 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\de305.dos device=C:\WINDOWS\workgrp.sys LASTDRIVE=y 2. PROTOCOL.INI File on Windows for Workgroups [network.setup] version=0x3100 netcard=ndis2d,1,NDIS2D transport=ms$netbeui,MS$NETBEUI lana0=ndis2d,1,ms$netbeui [protman] DriverName=PROTMAN$ PRIORITY=MS$NETBEUI [NDIS2D] DriverName=DE305$ [MS$NETBEUI] DriverName=netbeui$ SESSIONS=10 NCBS=32 BINDINGS=NDIS2D LANABASE=0 3. AUTOEXEC.BAT File C:\WINDOWS\net start C:\WINDOWS\SMARTDRV.EXE @ECHO OFF PROMPT $p$g PATH C:\WINDOWS; SET TEMP=C:\WINDOWS\TEMP -- THE END -- .TOPIC: Windows for Workgroups 3.11 Digital Equipment Corporation NDIS DRIVER FOR WINDOWS FOR WORKGROUPS 3.11 INSTALLATION ======================================================== Content: -------- A) Install NDIS 2.0/ NDIS 3.0 driver to the WFW 3.11 B) Install ODI/ NDIS 3.0 driver to the WFW 3.11 A) Install NDIS 2.0/ NDIS 3.0 driver to the WFW 3.11 1. Run Windows by typing "WIN" from the DOS prompt. 2. Click the "Network" icon in the Main Program Group. 3. Click the "Network Setup" icon from the Network window. 4. Check drivers button, if it is hidden and can't be selected then goto next step. If it is visible and can be selected, goto step 8. 5. Click Networks button 6. Select "Install microsoft Windows Network" with no additional network. 7. Click "OK" button 8. Select "Drivers" item from the Network Setup dialog box. 9. Select "Add Adapters" item in the Option dialog box. 10. If you install Digital Adapter first time, Select "Unlisted or Updated Network Adapter", then goto next step. System will automatically search OEMSETUP.INF file which supported by adapter maker (such as Digital), . If you have installed Digital adapter before, just select the "DE305 DIGITAL EtherWORKS ISA driver" at drivers list table and goto step 13. NOTE: OEMSETUP.INF file in Digital driver diskette A:\ 11. Insert DE305 DIGITAL EtherWORKS ISA driver diskette at floppy drive A or B then type destination drive and path name in your PC. Make sure the full path of the directory (i.e. A:\) is given. Then you will see the "DE305 DIGITAL EtherWORKS ISA driver" dialog box appear. 13. Using setup button to change IO BASE, IRQ and driver type. DE305 DIGITAL EtherWORKS ISA adapter using 300, 11 as default IO BASE and IRQ setting. There are 4 drivers type: . Real mode and Enhanced mode NDIS . Enhanced mode NDIS . Real mode NDIS . ODI driver You can select one of these 4 drivers type depend on your application. For workgroups environment only, you can select 1'st driver type which combine real mode and enhanced mode NDIS. 14. Follow screen instructions to complete the process. 15. Restart your computer. Following is some sample Configuration Files -------------------------------------------- 1. CONFIG.SYS File FILES=30 BUFFERS=30 LASTDRIVE=Z DEVICE=C:\WFW311\HIMEM.SYS DEVICE=C:\WFW311\IFSHLP.SYS STACKS=9,256 2. AUTOEXEC.BAT File C:\WFW311\SMARTDRV.EXE C:\WFW311\net start PATH C:\WFW311; SET TEMP=C:\WFW311\TEMP 3. PROTOCOL.INI File on Windows for Workgroups 3.11 [network.setup] version=0x3110 netcard=ms$de305,1,MS$DE305,2 transport=ms$netbeui,NETBEUI lana0=ms$de305,1,ms$netbeui [MS$DE305] DriverName=MS2000$ INTERRUPT=11 IOBASE=0x300 [DE305] adapters=MS$DE305 [NETBEUI] BINDINGS=MS$DE305 LANABASE=0 SESSIONS=10 NCBS=12 4. SYSTEM.INI [386Enh] netcard=de305.386 B) Install ODI/ NDIS 3.0 driver to the WFW 3.11 1. Run Windows by typing "WIN" from the DOS prompt. 2. Click the "Network" icon in the Main Program Group. 3. Click the "Network Setup" icon from the Network window. 4. Check drivers button, if it is hidden and can't be selected then goto next step. If it is visible and can be selected, goto step 8. 5. Click Networks button 6. Select "Install microsoft Windows Network" with no additional network. 7. Click "OK" button 8. Select "Drivers" item from the Network Setup dialog box. 9. Select "Add Adapters" item in the Option dialog box. 10. If you install Digital Adapter first time, Select "Unlisted or Updated Network Adapter", then goto next step. System will automatically search OEMSETUP.INF file which supported by adapter maker (such as Digital), . If you have installed Digital adapter before, just select the "DE305 DIGITAL EtherWORKS ISA driver" at drivers list table and goto step 13. NOTE: OEMSETUP.INF file in Digital driver diskette A:\ 11. Insert DE305 DIGITAL EtherWORKS ISA driver diskette at floppy drive A or B then type destination drive and path name in your PC. Make sure the full path of the directory (i.e. A:\) is given. Then you will see the "DE305 DIGITAL EtherWORKS ISA driver" dialog box appear. 13. Using setup button to change IO BASE, IRQ and driver type. DE305 DIGITAL EtherWORKS ISA adapter using 300, 11 as default IO BASE and IRQ setting. There are 4 drivers type: . Real mode and Enhanced mode NDIS . Enhanced mode NDIS . Real mode NDIS . ODI driver You must select ODI driver to let NetWare ODI driver work at WFW 3.11. 14. Follow screen instructions to complete the process. 15. Restart your computer. Note: To connect to a Novell server from within Windows for Workgroups make sure you are logged on to a NetWare server before starting Windows. Also make sure that you have setup Windows for Workgroups to use Novell NetWare. Following is some sample Configuration Files -------------------------------------------- 1. CONFIG.SYS File FILES=30 BUFFERS=30 LASTDRIVE=Z DEVICE=C:\WFW311\HIMEM.SYS DEVICE=C:\WFW311\IFSHLP.SYS STACKS=9,256 2. AUTOEXEC.BAT File SET TEMP=c:\windows\temp PATH c:\windows;%PATH% c:\windows\net start lsl de305 c:\windows\odihlp.exe ipxodi netx 3. PROTOCOL.INI File on Windows for Workgroups 3.11 [network.setup] version=0x3110 netcard=de305,1,DE305,3 transport=ms$netbeui,NETBEUI lana0=de305,1,ms$netbeui [net.cfg] PATH=C:\WINDOWS\net.cfg [DE305] [Link Driver DE305] [NETBEUI] BINDINGS=DE305 LANABASE=0 SESSIONS=10 NCBS=12 4. SYSTEM.INI [boot] shell=progman.exe network.drv=wfwnet.drv . . [386Enh] network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386 netheapsize=20 netmisc=ndis.386,ndis2sup.386 transport=netbeui.386 InDOSPolling=FALSE . . [Network] winnet=wfwnet/00025100 multinet=nonet FileSharing=No PrintSharing=No LogonDisconnected=yes EnableSharing=no UserName=Digital Workgroup=WORKGROUP ComputerName=Digital Comment=Digital logonvalidated=no [network drivers] devdir=C:\WINDOWS LoadRMDrivers=No -- THE END -- .TOPIC: Windows NT 3.5x Digital Equipment Corporation NDIS 3.1 MiniPort driver installation guide for Windows NT 3.5x =============================================================== The drivers named "DE305" conform to the NDIS31 MiniPort Spec. It can support Windows NT3.5, NT3.51, NT4.0 and Windows 95 with different oemsetnt.inf file. This driver also support the Windows NT 3.1 but user must replace NDIS.SYS by NT 3.5 DDK's NDIS.SYS (\DDK\SRC\NETWORK\NT31BIN\I386\FREE\NDIS.386) File description: DE305.SYS : NDIS31 MiniPort driver OEMSETNT.INF : NT3.5x drivers information file (A:\) README.TXT : Readme file NOTE: OEMSETNT.INF file in Digital driver diskette A:\ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Installing driver on Microsoft Windows NT3.5x, NT4.0 ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1) In the Main group of NT, choose the Control Panel icon. 2) In the Control Panel window, choose the Network icon. 3) In the Network Settings dialog box, choose the Add Adapter button. The Add Network Adapter dialog box appears. 4) In the list of network cards, select "<other> Requires disk from manufacturer", and then press <Enter> button. 5) Insert this driver disk in drive A, enter drive and pathname A:\ and then choose the OK button. 6) In the Select OEM Option dialog box, you will see DE305 DIGITAL EtherWORKS ISA Adapter in the menu, use OK button to install it. 7) And then DE305 DIGITAL EtherWORKS ISA Card Setup dialog box appear, you can specify "IRQ level" and "I/O Port Address" of the adapter plugged in your PC. However, this NDIS 3.1 mini port driver has support auto IO, IRQ scan for DE305 DIGITAL adapter, so driver can work even user select a wrong IO port and IRQ. For multiple cards installation, specify correct IO port and IRQ is necessary. 8) After that, installation is completed. Digital's adapter becomes one of those Installed Adapter Cards and driver become one of those Installed Network Software. You can see: "[0x]DE305 DIGITAL EtherWORKS ISA Adapter" within Installed Adapter Cards menu and "DE305 DIGITAL EtherWORKS ISA Adapter Driver" within Installed Network Software menu. 9) Now, the SYSTEM have already copied DE305.SYS from A:\WINNT\INTEL351 directory to C:\WINNT\SYSTEM32\DRIVERS and the OEMSETNT.INF form A:\ to C:\WINNT\SYSTEM32 but renamed it to other installation information file. So next time, if you want to add Digital's adapters to your system, you do not need floppy diskette again. 10) To complete network installation, remember binding the adapter to transport drivers by choosing "Bindings" button under Network Setting dialog box. 11) Restarting your system you will acquire network service. -- THE END -- .TOPIC: Windows 95 DE305 DIGITAL EtherWORKS ISA Adapter WIN95 driver Installation Note ==================================== File description: DE305.SYS : NDIS31 MiniPort driver DE305.DOS : NDIS2 driver DE305.INF : WIN95 drivers information file(in A:\) README.TXT : Read me file NOTE: DE305.INF file in Digital driver diskette A:\ For user who want to use NDIS31 MiniPort driver, please following the sequences below: 1. From "Control Pannel" select "Network" icon. 2. Select "Adapter" icon 3. Select "Add" icon 4. Select "Have Disk" icon 5. Insert driver diskette and input the path "A:\" 6. Select "DE305 DIGITAL EtherWORKS ISA Adapter" 7. System will copy NDIS31 driver DE305.SYS and NDIS2 driver DE305.DOS from driver diskette. For other files which is necessary for Network function, please input the correct path for system to copy those files. (Microsoft suggest user copy all the Windows 95 installation files to the same hard disk with directory C:\WIN95) 8. If you want to share your files or printer, you can click "File and Print Sharing" to allow the other user to access your files. 9. Specify the correct iobase and irq. It must match with your adapter's configuration, otherwise network function can't work properly. 10.After copy all the files, network installation is complete. System will ask user to restart the computer, just press "YES" to reboot the PC. If you want to share your files or printer, don't restart here You can select "Network Function" from "Control Pannel", and click "File and Print Sharing" before you restart the computer. -- THE END -- .TOPIC: SCO UNIX r3.2 v4 Digital Equipment Corporation DE305 DIGITAL EtherWORKS ISA Adapter SCO UNIX LLI STREAM DRIVER INSTALLATION ======================================== Your Driver Diskette should contain the following files in the subdirectory \SCO: --------------------------------------------------------------------------- Files Contents --------------------------------------------------------------------------- README.TXT Text file about driver installation for the UNIX Server DE305.TAR PCI ethernet device drivers packaged for UNIX (in tar format) --------------------------------------------------------------------------- Introduction ------------- This file is the SCO Unix LLI driver of DE305 EtherWORKS whose version is v1.0.0. It is a custom installable LLI driver, configured using netconfig. The LLI driver requires the following software: - DEC's DE305 EtherWORKS ISA adapter - ODT 2.0 or higher version, SCO Unix r3.2v or higher version (Unix SCO5 excluded). Installation Procedure ---------------------- 1. Prepare a formatted diskette on any DOS machine. For example, type: C>format a: Note: Make sure your diskette is free from bad sectors. Verify this using the DOS SCANDISK or CHKDSK command. 2. Now login to UNIX system as supervisor (root). (Note: Make sure that the current directory is "/" using UNIX command - pwd.) Please follow the following steps to uncompress the package file: > cd /tmp > mkdir tmp > cd tmp (then inserting the Package Diskette) > doscp a:\sco\DE305.TAR ./unixdrvr.tar.Z > uncompress unixdrvr.tar (then inserting the prepared formatted diskette) > #dd if=unixdrvr.tar of=/dev/rfd0135ds18 (Note: Use another device file name if you use different floppy drive) Now the package installation diskette is ready for installing. 3. The following sections describe the configuration of the driver. It is suggested that you should perform these instructions in the singler-user environment. Run custom utility and select the "Install new package" option. It will prompt you to insert "DE305 DIGITAL EtherWORKS ISA Adapter driver" Floppy Volume 1. 4. After reading drive A, it will show a message prompting you to use "netconfig" to add drivers into your system. 5. Run "netconfig". Add the desired chain. The DE305 EtherWORKS adapter drivers are called: u5l0, u5l1, u5l2 and u5l3. Rember the u5l0 must be configured first, before any other driver is configured. 6. When the chain has been configured, select 'q' from the netconfig menu and relink the kernel at the prompt. 7. To active the adapter, you must reboot. When the system boots, you should see the following message among the other configuration messages: *u5l0 0x0300-031f 3 - type=Ethernet id=08-00-2b-xx-xx-xx with the appropriate I/O addresses, IRQ, Adapter-type with its detected media-type and the 8 octets of its IEEE address. 8. If you encounter any problems during installation, (i.e., an error message appears on screen) call your dealer for assistance. -- THE END -- .TOPIC: Packet Driver Digital Equipment Corporation PACKET DRIVER INSTALLATION ============================= DE305.COM is your adapter packet driver. The following describes its command syntax and use. DE305 Command Syntax -------------------- DE305 [-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 Digital's adapter, the following command line loads the Packet Driver at software interrupt 60h, at I/O address 300 and hardware interrupt 3. DE305 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: DE305 0x60 Note ---- Address parameters, such as the software interrupt and I/O address are preceded by "0x". For example, "0x60" and "0x300". -- THE END -- .TOPIC: PC/TCP Digital Equipment Corporation PACKET DRIVER INSTALLATION FOR FTP PC/TCP ========================================= DE305.COM is Digital's packet driver which can support FTP PC/TCP. Following is the installation procedure: 1. Load your Packet Driver. example: DE305 0x60 2. Load the PC/TCP kernel ETHDRV.EXE. See following example: To load the PC/TCP kernel and allocate 8 packet buffers, type the following: ETHDRV -p 8 <Enter> This will increase the number of packet buffers from 5 (default) to 8. 3. You are now ready to run any PC/TCP application, like FTP's telnet. -- THE END -- .TOPIC: NCSA Digital Equipment Corporation PACKET DRIVER INSTALLATION FOR NCSA =================================== DE305.COM is Digital's packet driver which can support NCSA Telnet. Following is the installation procedure: 1. Make sure that you have the correct version of NCSA Telnet for the PC. You need version 2.3 or later to support the packet driver interface. 2. Install the NCSA software onto your system. Refer to the NCSA documentation for detailed instructions. 3. Load the Packet Driver (DE305 0x60). Refer to the corresponding section for details. 4. Get help or view the Packet Driver's syntax by typing the following command: de305 -h <Enter> 5. Run the NCSA application that you need. To do this, you need to know the host's IP address. For example, ftp 192.72.24.202. -- THE END -- .TOPIC: Banyan VINES DE305 DIGITAL EtherWORKS ISA Adapter NDIS DRIVER FOR BANYAN VINES INSTALLATION ========================================= The drivers named DE305 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 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\de305.dos 2. PROTOCOL.INI file for the LAN Manager [protocol manager] DriverName = PROTMAN$ [DIGITAL] DriverName = de305$ -- THE END -- .TOPIC: Pathway Access DE305 DIGITAL EtherWORKS ISA Adapter NDIS DRIVER FOR WOLLONGONG AND PATHWAY ACCESS INSTALLATION ========================================================== The drivers named DE305 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:\NDIS2\DOS\DE305.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\DE305.DOS 5. Edit your PROTOCOL.INI file in the C:\PATHWAY subdirectory to include the following section: [DIGITAL] DriverName = DE305$ 6. Edit your AUTOEXEC.BAT file to include the following command lines: path=c:\pathway ndis [-d:#] pwbind where: -d is an optional parameter used for accessing a specific module number within the PROTOCOL.INI. In your PROTOCOL.INI file, a line enclosed by square brackets designates the beginning of a new module. Each module is referred to by a hexadecimal number. The first module is module number one. The second module is module two, and so on. -- THE END -- .TOPIC: DEC PATHWORKS DE305 DIGITAL EtherWORKS ISA Adapter NDIS Driver for DEC PATHWORK Installation ========================================= The drivers named DE305 contained in the \NDIS2\DOS subdirectory of your Driver Diskette conform to the Network Driver Interface Specification (NDIS) defined by Microsoft/3Com. Installation Procedure ---------------------- 1. Insert the DEC PATHWORKS Client Setup diskette #1 into your floppy drive (either A: or B:). 2. 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 Digital Driver Diskette. For example, type the following: A:\MSLANMAN.DOS\DRIVERS\ETHERNET\DE305\DE305.DOS 13. When prompted, indicate the subdirectory location of the PROTOCOL.INI file in the Digital Driver Diskette. For example, type the following: A:\MSLANMAN.DOS\DRIVERS\ETHERNET\DE305\ 14. Select "WRITE KEY DISK" to save the settings that you have chosen. When prompted to copy the DE305.DOS and PROTOCOL.INI files, insert the Digital driver program diskette into your floppy drive. 15. Follow screen instructions to complete the installation. 16. From the Configuration screen, press F10 to exit to C:\. 17. Edit the PROTOCOL.INI file from the DECNET subdirectory. Remove the semicolon (;) from the statement "NI_IRQ = 5" under the [DATALINK] section. 18. Make sure that the IRQ value in the new [DE305.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\de305.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 = DE305.DOS [DATALINK] DRIVERNAME = DLL$MAC LG_BUFFERS = 16 SM_BUFFERS = 6 OUTSTANDING = 32 HEURISTICS = 0 BINDINGS = DE305.DOS ;Specify IRQ level used by workstations network adapter NI_IRQ = 3 [DE305.DOS] ; PROTOCOL.INI for DE305 DIGITAL EtherWORKS ISA Adapter drivername = DE305$ ; irq = NI_IRQ = Adapter IRQ Setting irq = 3 iobase = 0x300 ; End of this sample file 3. AUTOEXEC.BAT echo off break on cls prompt $p$g REM Insert any keyboard internationalization and character set information here. if not exist \decnet\STARTNET.BAT goto nostartup call \decnet\STARTNET goto end :nostartup echo ** WARNING ** STARTNET.BAT file not found. Network functions not performed -- THE END -- .TOPIC: SUN PC-NFS DE305 DIGITAL EtherWORKS ISA Adapter NDIS DRIVER FOR SUN PC-NFS Installation ======================================= The drivers named DE305 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 DE305.DOS file from the \MSLANMAN.DOS\DRIVERS\ETHERNET\DE305\ of your Driver Diskette to the newly created subdirectory (\LANMAN) on your destination drive. Note: The DE305.DOS file is also found in the \NDIS2\DOS directory of your Driver Diskette. 16. Edit the CONFIG.SYS file using a text editor. Add the following command line before the NFS_NDIS driver specification: DEVICE=C:\LANMAN\DE305.DOS 17. Edit the PROTOCOL.INI file in the \LANMAN directory, replacing the following: a. Replace the section name [your-mac-module] with [ETHNE] b. Replace the command line "drivername = YOURMAC$" with "drivername = DE305$" c. Specify the correct IRQ and IOBASE value (may be omitted) to match the adapter's hardware configuration. For example: IRQ = 3 IOBASE = 0x300 d. Replace the command line "bindings = YOUR-MAC-MODULE" with "bindings = ETHNE$" 18. Reboot your computer. Then start the application you need. For example: a. Execute NFSCONF.EXE to configure the system, such as mounting a virtual drive E: b. Execute TELNET.EXE to do terminal emulation Sample Configuration Files -------------------------- 1. NETWORK.BAT REM stc* is a sample PC-NFS workstation name REM nfsuser is a sample PC-NFS server address NET START RDR stc* NET PCNFSD nfsuser NET NAME stc* 2. DRIVES.BAT REM specify connections to remote directory NET USE l:nfsuser:/usr2/down NET USE k:nfsuser:/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 nfsuser 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 Digital NDIS driver name device=C:\LANMAN\DE305.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 = de305$ 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: LANtastic Digital Equipment Corporation LANtastic driver Installation ============================= Content: -------- A) Install Digital drivers for LANtastic 5.0 B) Install Digital drivers for LANtastic 6.0 A) Install Digital drivers for LANtastic 5.0 ========================================= Using NDIS driver: ------------------ For NDIS driver, Digital support "DE305.DOS" driver for MPX2 product series. User can use "DE305.DOS" driver to replace AEXNDIS.DOS which is the NDIS driver offered by ARTISOFT. Example ----- CONFIG.SYS DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI DEVICE=C:\LANTASTI\DE305.DOS -------> By Digital Example ----- AUTOEXEC.BAT / STARTNET.BAT C:\LANTASTI\AI-NDIS BIND_TO=ETHNE_NIF C:\LANTASTI\AILANBIO C:\LANTASTI\REDIR MachineName Example ----- PROTOCOL.INI [PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES [ETHNE_NIF] DRIVERNAME = DE305$ Comments: If you are using PROTMAN.DOS V1.x, you must use the NO_BIND option on the AI-NDIS command line in the STARTNET.BAT, and you must run NETBIND.EXE V1.x before AILANBIO.EXE. B) Install Digital NDIS2 drivers for LANtastic 6.0 =============================================== Using NDIS driver: ------------------ To install Digital NDIS driver "DE305.DOS", user can use LANtastic 6.0 install program, and select "NDIS support for network adapters" then insert Digital's driver diskette, and type path "A:\LANTASTI". Install program will search "DE305.DOS" and "PROTOCOL.INI" and copy these two files to target directory. IF user already install LANtastic 6.0 and want to install Digital's MPX2 adapter, just replace AEXNDIS.DOS with Digital's NDIS driver "DE305.DOS" at CONFIG.SYS "DE305.DOS" is NDIS driver which supported by Digital "AEXNDIS.DOS" is NDIS driver which supported by ARTISOFT Example ----- CONFIG.SYS DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI DEVICE=C:\LANTASTI\DE305.DOS -------> By Digital Example ----- AUTOEXEC.BAT / STARTNET.BAT @echo ===== Begin LANtastic configuration ===== SET LAN_CFG=C:\LANTASTI PATH C:\LANTASTI;%PATH% SET LAN_DIR=C:\LANTASTI.NET rem Please obtain the NETBEUI.EXE program from Microsoft NETBEUI AI-NDIS BIND_TO=AEXNDIS_NIF AILANBIO @STARTNET.CFG REDIR THOMAS @STARTNET.CFG SERVER C:\LANTASTI.NET @STARTNET.CFG NET LOGIN \\THOMAS @echo ===== End LANtastic configuration ===== Example ----- Protocol.ini [PROTMAN] Priority=NETBEUI DriverName = PROTMAN$ Dynamic = Yes [NETBEUI_XIF] DriverName = netbeui$ Sessions = 6 NCBS = 12 Bindings = ETHNE_NIF LANABASE = 1 [ETHNE_NIF] DriverName = DE305$ -- End -- .TOPIC: Power Lan Digital Equipment Corporation Power Lan driver Installation ============================= To install Digital's adapter with Power Lan system, user can use 3 different methods as following: A) Install Power Lan driver with Digital's adapter B) Install Digital's DOS/ODI drivers for Power Lan C) Install Digital's Packet drivers for Power Lan A) Install Power Lan Driver with Digital's adapter =============================================== To install Power Lan driver with Digital's adapter 1.) Use Power Lan install program, and select "NE2000" item. 2.) Change Iobase and IRQ setting by Digital's 1Step setup program and using the same port at NXNE2000 command line parameter: /lp:Iobase /li:IRQ Example ----- PLSTART.BAT if %PLTREE%. == . set PLTREE=C:\PL REM REM - - - - - - - - - - - - - - - - - - Start NETBIOS - - - - - - - - - - - - REM %PLTREE%\PROGRAMS\nxne2000 /ln:0 /ses:14 /nam:17 /lp:300 /li:3 REM B) Install Digital's DOS/ODI driver for Power Lan ============================================= To install Digital's DOS/ODI driver at Power Lan system: 1.) Copy Digital's DOS/ODI driver "DE305.COM" from A:\NOVELL\DOSODI to C:\PL\PROGRAMS 2.) Copy Novell's driver "LSL.COM" from A:\NOVELL\DOSODI to C:\PL\PROGRAMS 3.) Create NET.CFG file as following example at C:\PL\PROGRAMS 4.) Use Power Lan install program, and select "ODI" item, then add "LSL.COM" and "DE305.COM" before NXODI.EXE at C:\PL\ADMIN\SYS\PLSTART.BAT's "start NETBIOS" section Example ----- PLSTART.BAT if %PLTREE%. == . set PLTREE=C:\PL REM REM - - - - - - - - - - - - - - - - - - Start NETBIOS - - - - - - - - - - - - REM LSL %PLTREE%\DE305 ------> Digital's MPX2 DOS/ODI driver %PLTREE%\PROGRAMS\nxodi /ln:0 /ses:14 /nam:17 REM Example ----- NET.CFG Link Driver DE305 Frame ETHERNET_II Protocol IPX 8137 ETHERNET_II Port 300 INT 3 C) Install Digital's Packet driver for Power Lan ============================================= To install Digital packet driver at Power Lan system: 1.) Copy Digital's packet driver "DE305.COM" from A:\PKTDRV to C:\PL\PROGRAMS 2.) Use Power Lan install program, and select "NXPACKET" item, then add Digital's packet driver "DE305.COM" before NXPACKET.EXE at C:\PL\ADMIN\SYS\PLSTART.BAT's "start NETBIOS" section Example ----- PLSTART.BAT if %PLTREE%. == . set PLTREE=C:\PL REM REM - - - - - - - - - - - - - - - - - - Start NETBIOS - - - - - - - - - - - - REM %PLTREE%\DE305 0x60 ------> Digital's packet driver %PLTREE%\PROGRAMS\nxpacket /ln:0 /ses:14 /nam:17 /li:0x60 -- THE END --Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.