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 - Supports the NetWare IPX workstation 2. Generic Boot ROM - Supports NetWare 3.x, 4.x and Microsoft LAN Manager V2.1 and LAN Server V2.1 Using the Ethernet Remote Boot ROM -------------------------------------------- The Ethernet Remote Reset Boot ROM is for NetWare applications. 1. Generate a DOS Image To allow remote booting, you should first generate a DOS image. See the corresponding section in your NetWare manuals for detailed procedure. 2. Run RPLFIX.COM This program is provided and developed by Novell to fix the bug that causes boot failure when using MS-DOS 5.0 or DR DOS 6.0. Users of MS-DOS 5.0 or DR DOS 6.0 MUST run this program after generating the DOS image. Failure to do so will result in boot failure. 3. Auto-detect adapter configuration Once you power on the host PC, the Boot ROM will automatically detect the configuration of the network adapter installed. The parameters detected will vary according to the type of network adapter. Corresponding values will be shown on screen. See Figures 1 and 2 for sample screen displays. For related information, see section on "List of Adapter Parameters Automatically Detected by the Boot ROM". 4. Follow screen instructions to select the appropriate Ethernet_Type if necessary. See section on Ethernet Type Selection for more information. Note: The program automatically detects the adapter's parameter settings, including Frame type, RAM Test, RAM Size, IRQ value, I/O base address, data width, Ethernet-ID Ethernet Type Selection ----------------------- The Boot ROM device is compatible with both Ethernet_II and IEEE 802.3 Ethernet. 1. Upon power on the program automatically detects the adapter's configuration, and will display it on the screen. 2. When prompted to select a "frame type" choose an appropriate one for your adapter if necessary. For example, pressing "1" selects "Ethernet_II," while pressing "2" selects "802.3" Using the Generic Boot ROM ---------------------------------------------- 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 NWMLID.COM (or NE2000.COM) IPXODI.COM NETX.COM (or EMSNETX.EXE) NET.CFG * For the DOSODI workstation with NetWare v4.x: LSL.COM NWMLID.COM (or NE2000.COM) VLM.COM * Other files necessary are: AUTOEXEC.BAT (user defined) CONFIG.SYS (user defined) and other file you may deem necessary All NetWare VLM files for workstation NET.CFG Creating the server image boot file ----------------------------------- Refer to the sections entitled "Customizing Remote Boot Files" and "Creating the BOOTCONF.SYS Boot Files" in your NetWare documentation for details. A brief procedure follows: 1. Log onto the network as "supervisor" for the NetWare v3.x server; or as "admin" for the NetWare v4.x server. 2. Map to your network server. Type: MAP F:=SYS:LOGIN 3. Insert the Remote Reset Image diskette in the drive A of the workstation. 4. Change to F: and type: CD\LOGIN 5. Using DOSGEN create the file "NET$DOS.SYS": F:\SYSTEM\DOSGEN 6. Flag the NET$DOS.SYS as sharable and run RPLFIX if you're using MS-DOS 5.0. Remote Boot Installation for LAN Manager 2.1 -------------------------------------------- Remote Boot installation on LAN Manager 2.1 may be complex. Also, be aware that the 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 UK000.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\UK000.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 = uk000$ ;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 ~EtherPair 0000E8 ~ ,,, ~ RDOSA ~ ~ ~ ~ ~ ~ b. Insert the lines before the description of "profile and workstation records added by rplmgr" 0000E8?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME) S ~ ~ ~,,, ~ RDOSA ~ DEFAULT *~New~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 = 0000E8?????? [configuration] name = DOS401A os = DOS401 dirname = DOS dirname2 = DOS401 bblink = RDOSA fitfileshared = fits\dos401 fitfilepersonal = fits\dos401p comment = DOS 4.01 EtherPair adapter = 0000E8?????? [configuration] name = DOS500A os = DOS500 dirname = DOS dirname2 = DOS500 bblink = RDOSA fitfileshared = fits\dos500 fitfilepersonal = fits\dos500p comment = DOS 5.00 EtherPair adapter = 0000E8?????? And append the following line to RPLMGR.INI ; 0000E8 = (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 UK000.DOS driver into the \IBMLAN\RPL\DOS subdirectory of your server. 2. Modify the PROTOCOL.INI file. Change bindings to include UK000.DOS; change DriverName to UK000.DOS. 3. Activate the LAN Requester program for creating the DOS image file. From DOS, type the following and press . 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 worksattion and allow remote booting. All trademarks or brand names mentioned are properties of their respective owners. ===End=== rvices 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 worksattion and allow remote booting. All trademarks or brand names mentioned are properties of their respective owners. ===End===