The following boot ROM is an optional part you may purchase separately for installing the remote boot ROM function for the ET32/P PCI Ethernet adapters. BOOT/32-RPL : * RPL remote boot ROM for remote boot from . Netware 3.11, 3.12, 4.x server . Artisoft's LANtastic 6.0 server . IBM LAN Server 3.0 . IBM LAN Server 4.0 . Windows NT 3.5 Server The following sections describe the installations as below: A. BOOT/32-RPL RPL boot ROM for Netware remote boot function B. BOOT/32-RPL RPL boot ROM for LANtastic softwares. C. BOOT/32-RPL RPL boot ROM for IBM LAN Server 3.0 RIPL service D. BOOT/32-RPL RPL boot ROM for IBM LAN Server 4.0 RIPL service E. BOOT/32-RPL RPL BOOT ROM FOR WINDOWS NT 3.5 SERVER A. RPL BOOT ROM FOR NETWARE REMOTE BOOT FUNCTION ============================================= SET UP REMOTE BOOT SERVICE ON SERVER 1. At Netware 3.11 (or higher) server, proceed the following steps to setup the RPL function on the server. In the following steps, we use et32nw.lan as example: :load et32nw frame=ethernet_802.2 Loading module et32nw.lan :load rpl.nlm :bind rpl to et32nw Several boards are using et32nw driver 1. ..... 2. ..... 3. ..... Frame type ETHERNET_802.2 Select board to bind : 3 ------------------------------------------------------- |Note: Select the board with frame type ETHERNET_802.2. | ------------------------------------------------------- :bind IPX to et32nw Several boards are using et32nw driver 1. ..... 2. ..... 3. ..... Frame type ETHERNET_802.2 Select board to bind : 3 ------------------------------------------------------- |Note: Select the board with frame type ETHERNET_802.2. | ------------------------------------------------------- 2. Run Netware DOSGEN procedure to generate NET$DOS.SYS on server. Refer to the Netware documentation for details. Note: a. It is not necessary to run RPLFIX utility to patch the NET$DOS.SYS for MS-DOS ver 5.0 and ver 6.0 any more. b. This RPL approach can accept IPX or ODI loading procedure in the bootable source disk for DOSGEN. c. Make sure the client software in the bootable source disk can match the frame type used on the server. If your are using ODI driver, you may specify the frame type in NET.CFG and place it in the source disk. 3. If your server is Netware 3.12 or 4.x, you may skip this step. Otherwise, copy RBOOT.RPL to the \LOGIN directory on the server. 4. Now, server is available to provide RPL remote boot service for any workstation equipped with remote boot ROM. 5. Install the boot ROM into your adapter in workstation. Align the notch of the boot ROM in the same direction of the notch of the boot ROM socket on the adapter. Enable the boot ROM function by running the SETUP program. 6. If your workstation is equipped with hard disk and has active partition. You MUST use DISPAR utility to set the active partition to inactive. Do not insert any diskette in the floppy disk drive. 7. Now, the workstation is available to remote boot from server. B. BOOT/32-RPL RPL BOOT ROM FOR LANTASTIC REMOTE BOOT FUNCTION =========================================================== 1. Insert the BOOT/32-RPL into the boot ROM socket on the Ethernet adapter as instruction in each installation guide. 2. BOOT/32-RPL will auto-configure the adapter by itself. 3. BOOT/32-RPL can work with boot type of Find/Found on LANtastic. 4. Prepare a bootable diskette for the workstation with the following command: FORMAT A:/4/S This MUST be a 360K bootable disk. If the computer has only a 3.5" disk drive then download the CHGSIZE.ZIP from the Artisoft BBS @1-520-884-8648. This will allow you to format a 720K disk to single sided 360K. [If you have a 1.44Mb 3.5" disk drive, format the disk to 720K and then run CHGSIZE.EXE.] Note: You may need to use one previous version of DOS, such as DOS5, to fit all necessary files into this 360K disktette. 5. Copy the following files to the bootable floppy disk create in last step: COPY AILANBIO.EXE A:\ COPY REDIR.EXE A:\ COPY NET.EXE A:\ COPY PROTMAN.DOS A:\ COPY PROTMAN.EXE A:\ COPY AI-NDIS.EXE A:\ COPY \ARTISOFT\DOS\ET32ND.DOS A:\ 6. Create the following AUTOEXEC.BAT, CONFIG.SYS and PROROCOL.INI files on the bootable floppy: AUTOEXEC.BAT ------------ @ECHO OFF AI-NDIS BIND_TO=ET32_NIF <-- AI-LANBIOS driver for the remote AILANBIO boot station. REDIR # BUFFERS=2 SIZE=2048 NET LOGIN \\SERVERNAME NET USE C: \\SERVERNAME\C-DRIVE PATH=C:\DOS;C:\LANTASTI;C:\ PROMPT $P$G C: CONFIG.SYS ---------- BUFFERS=32 FILES=100 LASTDRIVE=Z FCBS=16,8 DEVICE=PROTMAN.DOS /I:A:\ DEVICE=ET32ND.DOS PROTOCOL.INI ------------ [PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES ;PROTOCOL.INI for ET32 [ET32_NIF] DRIVERNAME = ET32ND$ 7. Execute NET_MGR program at Lantastic server. The program will build a boot image on the server by using the bootable diskette mentioned above. Please refer to Chapter 14 in "Complete Guide to LANtastic" Network Operating System DOS version. The chapter describes the detail of how to set up remote booting and NET_MGR. 8. Please refer to the description of command "NET UNLINK" in the LANtastic manual. This is usually used to allow workstations to use their A: or B: drive locally after remote booting and it also can resolve the problem of insufficient system memory after remote booting on a diskless workstation. C. BOOT/32-RPL RPL BOOT ROM FOR IBM LAN SERVER 3.0 RIPL SERVICE ============================================================ 1. Find an IBM LAN Server 3.0 client and proceed the following steps to setup the Remote IPL service on LAN Server. 2. Logon server as administrator. 3. Stop Remote IRP service on server. Type NET STOP REMOTEBOOT at an OS/2 command prompt. 4. Create a sub-directory \IBMLAN\RPL\DOS\ET32ND. 5. Copy \NDIS\ET32ND.DOS in this driver diskette to \IBMLAN\RPL\DOS\ET32ND. 6. Edit \IBMLAN\RPL\RPL.MAP: - Add the following line below ";server record for DOS" yyyyyyyyyyyy et32nd.cnf 3 10 N IBMLAN$ DOS~ET32ND~Ethernet ~ ~ ,,, Z R_ET32ND 7. Create et32nd.cnf in directory \IBMLAN\RPL\DOS as below: ; DOS Boot Block Configuration (P32PND Ethernet) ; NDIS LAN Support Program Drivers BASE 7C0H RPL DOS\RPLBOOT.SYS LDR DOS\RPLLOADR.COM ~ DAT DOS\LT2.MSG DAT C:\IBMLAN\DOSLAN\LSP\DXM.MSG DAT DOS\ET32ND\PROTOCOL.INI EXE C:\IBMLAN\DOSLAN\LSP\NETBIND.COM ~ ~ ~ DRV C:\IBMLAN\DOSLAN\LSP\DXMJ0MOD.SYS ~ 14 ~ DRV C:\IBMLAN\DOSLAN\LSP\DXMA0MOD.SYS 001 ~ ~ DRV DOS\ET32ND\ET32ND.DOS ~ ~ ~ DRV C:\IBMLAN\DOSLAN\LSP\PROTMAN.DOS /I: ~ ~ 8. Create PROTOCOL.INI in directory \IBMLAN\RPL\DOS\ET32ND. [PROTMAN_MOD] DriverName = PROTMAN$ [NETBEUI] Drivername = netbeui$ Bindings = et32nd [et32nd] DriverName = et32ND$ 9. Type NET command at OS/2 full screen and proceed the following steps: a. Select "Definition" in the LAN Requester Main Panel. b. Select "Machine parameters". c. Select "--New--". d. Select "Actions" from the action bar. e. Select "Create" from the Actions pull-down. f. Select "Remote IPL workstation", and then select "Enter". g. Complete the following definition panel, and then select "Enter": Machine ID workstation name Description ET32ND Network adapter number (address) 0040F6?????? Remote IPL Server remote IPL server Server record identifier R_ET32ND h. Type the image ID you want to use to start the workstation, or select "F4=List" to select an image ID from a list. Note: You also may create your own DOS Image profile by the following procedure: In LAN Requester Main Panel, select "Definitions" select "IPL images" 10. Restart Remote IPL service, type NET START REMOTEBOOT. Please refer to Chapter 13 of LAN Server Manual "Network Administrator Reference Volume 3: Network Administrator Tasks" for more information. D. REMOTE BOOT FROM LAN SERVER 4.0 =============================== 1. Install the BOOT/32-RPL onto the ET32/P PCI Ethernet adapter installed in the workstation which is going to remote boot from a LAN server 4.0. 2. Install the remote boot service on your LAN server for the remote boot workstations as the following steps. The LAN server is assumed that has been installed with a network adapter and MPTS properly. 3. Check <MPTS> icon and <LAPS Configuration> for the installed LAN adapter and protocol support of your LAN server 4.0. Make sure the LAN adapter supports IBM IEEE 802.2 protocol, since all remote boot workstations with RPL BOOT ROM are using IEEE 802.2 to communicate with server. 4. Start [Install OS/2 LAN Server 4.0] and select [Tailored] option. 5. Follow the on-screen instructions for : - select [Domain controller] - do not re-install MPTS - select [Install or remove a component] 6. Select [Server] and [DOS Remote IPL Service] from <Install and Remove> dialog. Press [OK]. 7. Select [Configure a component]. Press [OK]. 8. Select [Sever]. Press [Configure] to enter configurations for Server. 9. Select [DOS Remote IPL Service] and press [OK]. Answer the following prompts: - the available DOS version for the remote workstation - the drive for storing Remote IPL Subdirectory 10. Select [LAN Service Adapters] and press [OK] to: - configure the installed adapters for the LAN service - copy DOS files from hard driver or floppy disk driver 11. Now, the LAN Server product installation is complete. 12. Retuen to OS/2 prompt window, copy a new version of NET.EXE to \IBMLAN\DOSLAN\NET\NET.EXE. Please note that the new version of NET.EXE can be obtained from any available IBM Technical support facility. 13. Shut down your computer and restart it. 14. On the OS/2 prompt window, type the following command: >LOGON USERID /P:Password 15. Complete to execute \IBMLAN\NETPROG\GETRPL command from OS/2 prompt. 16. Click <IBM LAN Services> icon and start <LAN Server Administration>. 17. Select <Local Workstation XXXXXX> and start <DOS Image Definitions>. "XXXXXX" - the name of your server 18. There are four DOS Image icons. Select one , but not start it. Click right button of your mouse. Select "Make Image to XXXXXX". Then, select a target server from the list. 19. Return to <Local Workstation XXXXXX> icon view and start <Remote IPL Requesters> icon. 20. Start <Remote IPL Requester Template> to create identity on server for each workstation which is going to remote boot from the server. The information required for each workstation are: [Identity] - requester type : DOS or OS/2 - Machine ID - Network adapter address [Parameters] - Server record identifier : DOS IBM ETHERNET NDIS - Image ID : STD3HUMB 21. Execute the following edit program from OS/2 prompt: >EPM \IBMLAN\RPL\DOSNDET.CNF Important: replace the following line DRV DOS\MACETH.DOS with DRV DOS\ET32ND.DOS This action is necessary in order to configure a proper adapter driver for the remote workstation. 22. Copy ET32ND.DOS from the adapter driver diskette \NDIS.DOS to \IBMLAN\RPL\DOS. 23. Use EPM program to edit \IBMLAN\RPL\DOS\ETHERNET\PROTOCOL.INI. It is suggested to use Search/Replace function of EPM program to replace all "MACETH" instances in PROTOOL.INI file with "ET32ND". Delete all lines except "Drivername = ET32ND$ line in [ET32ND_MOD] section as follows: [ET32ND_MOD] Drivername = ET32ND$ 24. Now, you may start RPL remote boot service for the workstations installed with the ET32/P PCI Ethernet adapter. Under OS/2 prompt, run the command below: >NET START RIPL <Enter> E. BOOT/32-RPL RPL BOOT ROM FOR WINDOWS NT SERVER ============================================== This document provides a supplemental information for user to install the Remoteboot function with the Microsoft Windows NT Server V3.5. There are still other Microsoft documentation that one should refer to during this installation, since they give more sufficient information officially from Microsoft, such as the Chapter 8 of \SUPPORT\BOOK\INSTALL.HLP file in the NT Server 3.5 CD-ROM. This document is based on the following assumptions: 1. The Microsoft Windows NT Server V 3.5 has been properly installed with the Remoteboot service started and a NIC adapter in place. 2. A workstation with the ET32/P Ethernet adapter and the BOOT/32-RPL ROM is inserted and enabled in the adapter. 3. The Windows NT Server is installed in the C:\WINNT directory and the workstation is going to Remote Boot in the MS-D0S 6.22 from the Server. Steps to prepare NT Server for Remoteboot request from a station using ET32/P Ethernet adapter as an example): 1. One easy way is to use NE2000 sample as a template. Just copy all the files from C:\WINNT\RPL\BBLOCK\NETBEUI\NE2000 directory to a new directory called C:\WINNT\RPL\BBLOCK\NETBEUI\ET32NIC. 2. Edit the C:\WINNT\RPL\BBLOCK\NETBEUI\ET32NIC\PROTOCOL.INI file as follows: a. Keep the section name "ms2000_nif" for the new ET32/P adapter driver. b. Change the driver name ms2000$ under [ms2000_nif] section to [ms2000_nif] drivername = ET32ND$ No other keywords are required. 3. Edit the C:\WINNT\RPL\BBLOCK\NETBEUI\ET32NIC\DOSBB.CNF file to contain the following line. (The previous PROTOCOL.INI line should be deleted.) DAT BBLOCK\NETBEUI\ET32NIC\PROTOCOL.INI 4. Prepare an MS-DOS 6.22 boot image diskette which contain all the necessary files to be boot in by the remote boot workstation. The IO.SYS and MSDOS.SYS files, on this diskette, should have RO and Hidden attributes removed. 5. Copy all the files from this boot image diskette to the C:\WINNT\RPL\RPLFILES\BINFILESS\DOS622 directory. 6. Edit the CONFIG.SYS and AUTOEXEC.BAT files in the C:\WINNT\RPL\RPLFILES\CONFIGS\DOS622 directory to reflect your workstation configurations. 7. Open the <MS-DOS prompt> and enter <RPLCMD>. 8. Enter the <Vendor Add> commands and provide the following information: VendorName: 0040F6 VendorComment: ET32NIC 9. Enter the <Boot Add> commands and provide the following information: BootName: DOS622 VendorName: 0040F6 BbcFile: BBLOCK\NETBEUI\ET32NIC\DOSBB.CNF WindowSize: 0x0 10. Enter the <Config Add> commands and provide the following information: ConfigName: DOS622K BootName: DOS622 DirName: DOS DirName2: DOS622 DirName3: DirName4: FitShared: fits\dos622.FIT FitPersonal: fits\dos622p.FIT ConfigComment: DOS 622 for ET32-NIC 11. Enter the <Profile Add> commands and provide the following information: ProfileName: ET32-NIC ConfigName: DOS622K BootName: DOS622 FitShared: fits\dos622.FIT FitPersonal: fits\dos622p.FIT ProfileComment: DOS 622 for ET32-NIC 12. Quit the <RPLCMD> program and exit the <MS-DOS prompt>. Run <Remoteboot Manager> from the <Network Administration> program group. 13. Switch to the Workstation with the ET32/P adapter. At this time you should see a line like "RPL-ROM-FFC: xxx" is keeping on counting in the Workstation's screen. From the <Remoteboot Manager> Window on the Windows NT Server, you should be able to see a line containing 0040F6XXXXXX. If not, just press the F3 key or select the [View] [Refresh] to get the Workstation’s node ID on screen. If, by any chance, you can not get this far, then you should go back to previous steps and double check anything wrong and do not go any further. 14. From the screen of the <Remoteboot Manager> click and select the 0040F6XXXXXX line. Then select the menu items <Remoteboot Convert Adapters>, a <Convert Adapters> dialog box should appear at this time for your input. This operation is necessary for all RPL NIC adapters, since they all need to be regisetered in the Remoteboot Manager. 15. Select the <DOS 622 for ET32-NIC> profile in the <Wksta In Profile> list box item. Complete other inputs of this dialog box as you are prompted to. And press the [Add] button when finish. 16. Your Workstation, at this time, should start booting the MS-DOS V6.22 from Server. You may also need to provide the password, as you setup in the previous step, for this Remoteboot operation to take place. 17. For the installation of extra Workstations with exactly the same NIC adapters, just repeat the steps 15-17. And for the installation of extra Workstation with different NIC adapters you should repeat from step 1. ----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.