   NetWare Remote Boot 

   NetWare* Remote Boot Installation Notes for Intel's 
   EtherExpress(TM) PRO LAN Adapter
   ===================================================

   Location of Driver:     \NWCLIENT\EPROODI.COM
				    or
			   \NWCLIENT\IPX.COM 
			   

   Sample Configuration Files
   --------------------------
      AUTOEXEC.BAT (for ODI workstation):
	 prompt $p$g
	 set nwlanguage=english  ....... use with VLMs only
	 lsl
	 eproodi
	 ipxodi
	 netx   ........................ for NetWare 3.11 or 3.12 
	 vlm    ........................ for NetWare 3.12 or 4.0x

      AUTOEXEC.BAT (for IPX workstation)
	 prompt $p$g
	 ipx
	 netx

      CONFIG.SYS
	 files=20
	 buffers=20
	 lastdrive=Z ................... ONLY for use with ODI & VLMs

      NET.CFG
	 preferred server=<server_name> 
	 NetWare DOS Requester 
	    first network drive = F  ... for NetWare 4.0x

	 link driver EPROODI  ...... this section for ODI workstations 
	    port 300
	    frame ethernet_802.3
	    frame ethernet_802.2
	    protocol ipx 0 ethernet_802.3
	    protocol ipx e0 ethernet_802.2  

   General Installation
   --------------------
      Note: For NetWare 4.x remote boot installation see 
      Hints and Tips section for important information.

      1. The EtherExpress PRO adapter's boot ROM is ODI/802.2 based and 
	 therefore, requires the the IPX protocol and the RPL NLM to be 
	 loaded on each segment of the server that will have remote boot 
	 workstations.  
	 For example: 
	    LOAD EPRO PORT=xxx FRAME=ETHERNET_802.2 NAME=LAN1
	    BIND IPX TO LAN1 NET=xx
	    LOAD RPL
	    BIND RPL TO LAN1 
	 NetWare 3.11 server drivers default to 802.3 frame type so you 
	 may have to add all of the above lines.  See the README file on 
	 NetWare server installation for an example of multiple frame 
	 types on one adapter.  NetWare 3.12 and 4.0x default to 802.2,  
	 so you may only need to add other RPL lines.

      2. Configure the adapter so that it is set for ODI remote boot.  
	 This can be done the first time you plug the adapter in and turn
	 power on. Choose the FlashSet option and select the ODI remote 
	 boot option. If FlashSet is not active, use SoftSet2 to specify
	 ODI remote boot.
      
      
      Setting Up Single Boot Image
      ----------------------------
      
      1. A single boot image should be used if all your remote boot 
	 workstations use the EtherExpress PRO adapter, and all of them 
	 will use boot up files and DOS version.  Otherwise, refer to the 
	 instructions below for multiple boot images.

      2. If using the ODI driver, create a DOS bootable disk that contains 
	 these files:

	    COMMAND.COM
	    AUTOEXEC.BAT
	    CONFIG.SYS    ................ required if using VLMs
	    NET.CFG
	    LSL.COM
	    EPROODI.COM
	    IPXODI.COM
	    NETX.EXE      ................ for 3.11 or 3.12 workstations
	    VLM.EXE (and related files) .. for 3.12 or 4.0x workstations
      
	 If using the IPX driver create a DOS bootable disk that contains 
	 these files:

	    COMMAND.COM
	    AUTOEXEC.BAT
	    CONFIG.SYS    
	    NET.CFG
	    IPX.COM
	    NETX.EXE
	    
	 See the sample configurtion files above for details on contents 
	 of these files.  LSL, IPXODI, NETX and VLM (and related files) are
	 Novell files.  All but the VLMs can be found on the EtherExpress 
	 PRO/10 disk in the NWCLIENT directory with EPROODI and IPX driver.
	 Include any other drivers you plan to load on this boot disk.

      3. Log onto the network with supervisory rights and verify that 
	 these mappings exist:
	    SYS:LOGIN
	    SYS:SYSTEM
	 If they don't, you will need to create them.
	    MAP F:=SYS:LOGIN
	    MAP G:=SYS:SYSTEM

      4. Put the boot disk in drive A.  Change to the LOGIN directory and 
	 type:
	    G:DOSGEN  

	 NOTE: For DOSGEN to work correctly, you should run DOSGEN from 
	 the LOGIN directory not the SYSTEM directory.

	 DOSGEN creates a file called NET$DOS.SYS in the SYS:LOGIN 
	 directory. NET$DOS.SYS contains all the files from your boot disk. 
	 
      5. Change the attributes of NET$DOS.SYS to: Shareable, Read/Write.
     
	    FLAG NET$DOS.SYS SRW    (NetWare 3.11 and 3.12)
	    FLAG NET$DOS.SYS SHRW   (NetWare 4.01)


      Procedure for Setting up Multiple Boot Images
      ---------------------------------------------

      1. A multiple boot image file allows different workstations as
	 well as different brands of adapters to remote boot off the 
	 file server.  Each adapter can be given assigned different 
	 startup files.

      2. Create a DOS 5.0 or 6.0 bootable disk that contain the files as 
	 listed in step 2 under the single boot image section.

      3. The AUTOEXEC.BAT file should contain only one line:
	 xxxx.BAT

	 WHERE: xxxx is a name you assign to the remote boot workstation. 
	 Each remote boot workstation will have its own xxxx.BAT file.  
	 The xxxx.BAT file should contain the information as listed in 
	 the appropriate AUTOEXEC.BAT file under Sample configuration 
	 files above.

      4. Copy the xxxx.bat file to the LOGIN subdirectory on the server. 
	 You can execute other commands by including them in the xxxx.bat 
	 file.  

      5. Log onto the network as supervisor and verify that these mappings 
	 exist:
	    SYS:LOGIN
	    SYS:SYSTEM
	 If they don't, you will need to create them.
	    MAP F:=SYS:LOGIN  
	    MAP G:=SYS:SYSTEM 

      6. Put the boot disk in drive A.  Change to the LOGIN directory and 
	 type:
	    G:DOSGEN a: XXXX.sys
	 There MUST be a space between a: and XXXX.sys.

      7. Change the attributes of the new file to Shareable, Read/Write:
	    FLAG XXXX.SYS SRW    (NetWare 3.11 and 3.12)
	    FLAG XXXX.SYS SHRW   (NetWare 4.01)
     
      8. Change to the LOGIN directory and create an ASCII file called:
	    BOOTCONF.SYS
	 Each line in this file defines a unique remote-boot workstation.  
	 The format for this file is:

	    0xYYY,00AA00123456=XXXX.sys

	 where:

	 0xYYY is the network address of the remote-boot workstation (It
	 should start with 0x).  This is the NET=# that is specified on 
	 the BIND IPX line of the 802.2 segment.

	 00AA00123456 is the 12 digit Ethernet address of the EtherExpress
	 PRO adapter.  This address is printed on the board or can be 
	 displayed by running SoftSet2.

	 XXXX.sys is the name of the boot image for this workstation. You 
	 entered this name when you ran DOSGEN.

	 For additional information on setting up multiple boot images 
	 refer to your Novell documentation.


   Hints and Tips
   --------------
      
      1. NetWare 4.x servers: 
	 If you are using NetWare 4.x, and are experiencing problems 
	 remote booting to the server, replace your existing
	 RBOOT.RPL and RPL.NLM with the ones that are in the \NWRPL 
	 directory on the driver disk or available on our BBS.  
	 Among the symptoms that appear are problems reading the boot 
	 image on the server, or not seeing the rpl server.
	 The date and size of these files are:
	 RBOOT.RPL  04-23-93  7542 bytes
	 RPL.NLM    04-09-93  6322 bytes
	 
	 a. If RPL is already loaded, unload it from the server console.
	 b. From a workstation, login as ADMIN and flag \LOGIN\RBOOT.RPL 
	    and \SYSTEM\RPL.NLM as read-write.
	 c. From the driver disk or disk created from BBS download, 
	    copy RPL.NLM to the server's \SYSTEM directory and RBOOT.RPL
	    to the server's \LOGIN directory.
	 d. Flag both files as read only.   
	 e. From the server console, load RPL and bind it to the 
	    ethernet 802.2 frame type.
      
      2. Remote Boot Process: 
	 When you power on a remote-boot workstation, the ROM finds the 
	 server and looks for a BOOTCONF.SYS file.  If it finds this file 
	 AND it finds a line with its Ethernet address it executes the 
	 XXXX.sys file. If it does not find its Ethernet address (or a
	 BOOTCONF.SYS file), it looks for NET$DOS.SYS and executes 
	 that instead.

      3. Non 802.2 servers:
	 The Boot ROM is configured for a FRAME type of 802.2.  If you are 
	 using a different FRAME type (i.e. Ethernet Type II), the server 
	 must be configured to include both 802.2 and the other FRAME type.

	 You will also need to include a NET.CFG file in the boot image.  
	 This NET.CFG files must also include both FRAME types.  

      4. NetWare 2.2 servers:
	 To use an ODI based boot rom on a NetWare 2.2 server, you need to 
	 do the following:
	    a. the adapter in the file server must support Appletalk Phase II
	    b. load RPL.VAP
	    c. you may need to run RPLCFG.EXE to configure the frame type 
	       for RPL to use.

      5. Computer won't boot from network:
	 Make sure the computer will boot from the EXACT floppy disk used for
	 DOSGEN.  If the remote boot workstation does not have a floppy 
	 drive, try another computer with the SAME configuration.

	 If you are using a memory manager make sure you EXCLUDE the 
	 memory for the boot ROM.
	 
	 If a RPL counter appears while trying to boot, and it continues 
	 to increment, make sure the server has the correct frame types 
	 loaded, and ensure the cables are working properly.



   * Third-party trademarks are the property of their respective owners
