a:\readme.txt                                   04-APR-1996
		
		
			Version V2.00

      EtherWORKS 3 TURBO (DE203,DE204,DE205) Remote Boot Readme
      =========================================================

Congratulations on your purchase of the EtherWORKS 3 TURBO Remote
Boot ROM (DE20M-AR), supporting MOP and RPL protocols.

This README.TXT file contains:

	1. Contents of This Diskette
	2. Remote Boot ROM Configuration
	3. WINDOWS NT 3.51 Network Operating System
	4. LAN Manager Network Operating System 
	5. PATHWORKS V4.1x Network Operating System 
	6. PATHWORKS V5.x Network Operating System 
	7. IBM LAN Server Network Operating System
	

*****************************
* CONTENTS OF THIS DISKETTE *        
*****************************

The EtherWORKS 3 TURBO Remote Boot Setup diskette (included in the 
ROM kit) contains the following root files and directories:

	o  README.TXT-This file.

	o  RELEASE.NOT-Release note for the current version of the 
	   ROM kit. This file contains a list of known usage 
	   restrictions for the Remote Boot ROM.

	o  INSTALL.BAT-Batch file which calls the EZWORKS setup
	   utility.

	o  NICSETUP.BAT-Batch file which calls the EZWORKS setup
	   utility.

	o  SETUP.BAT-Batch file which calls the EZWORKS setup
	   utility.

	o  EWRK3_H.TSK-PATHWORKS 4.1x MOP task image file (uses 
	   hardware clock for the scheduler).

	o  EWRK3_S.TSK-PATHWORKS 4.1x MOP task image file (uses 
	   software clock for the scheduler).

	o  INSTALL directory-Contains the EZWORKS utility and
	   associated files.


*********************************
* REMOTE BOOT ROM CONFIGURATION *
*********************************

When you install a Remote Boot ROM (DE20M-AR) on an EtherWORKS 3 
TURBO adapter, the Remote Boot ROM enables your computer to perform 
a remote boot using either the MOP or RPL protocols.  (See the 
EtherWORKS 3 TURBO user's manual for instructions on how to install 
the ROM chip.)

To configure the DE20M-AR Remote Boot ROM, use the EZWORKS 
Installation utility. To access this utility:

	1. Insert the Remote Boot Setup diskette into drive A: 
	   on your computer.

	2. Enter the following command at the DOS prompt:

		     A:\> setup

	3. Follow the instructions to configure your Remote Boot 
	   ROM.


********************************************
* WINDOWS NT 3.51 Network Operating System *
********************************************

To prepare the Server for WINDOWS NT 3.51 ...

	1. Copy the driver (EWRK3.DOS) from the EtherWORKS 3 TURBO 
	   driver distribution diskette to the following:

	      \\winnt35\rpl\bblock\ndis

	2. Create a directory called EWRK3:

	      \\winnt35\rpl\bblock\netbeui.

	3. The newly created directory should look like following:

	      \\winnt35\rpl\bblock\netbeui\EWRK3.

	4. Copy the DOSBB.CNF and PROTOCOL.INI files under \EWRK3 
	   from another directory (any directory parallel to EWRK3 
	   will do).  For example:

	   \\winnt35\rpl\bblock\netbeui\XXXXX\dosbb.cnf    ==>
	   \\winnt35\rpl\bblock\netbeui\EWRK3\dosbb.cnf

	   \\winnt35\rpl\bblock\netbeui\XXXXX\protocol.ini ==>
	   \\winnt35\rpl\bblock\netbeui\EWRK3\protocol.ini

	5. Edit the newly created DOSBB.CNF file in the following:

	   \\winnt35\rpl\bblock\netbeui\EWRK3\dosbb.cnf

	   The first line is a comment. Change it to: 
	   
	   ; DOS on Digital EWRK3 Adapter

	   DAT BBLOCK\NETBEUI\XXXXX\PROTOCOL.INI ==>
	   DAT BBLOCK\NETBEUI\EWRK3\PROTOCOL.INI

	   DRV BBLOCK\NDIS\XXXXXX ~~~ ==>
	   DRV BBLOCK\NDIS\EWRK3.DOS ~~~

	6. Edit the newly created PROTOCOL.INI file in:

	   \\winnt35\rpl\bblock\netbeui\EWRK3\protocol.ini

	   In the PROTOCOL.INI file, there is a bracket title 
	   [netbeui_xif]. Search the file to find bindings = 
	   XXXXX_nif, then replace the XXXXX with EWRK3.

	7. Back up your files.

	8. Run the RPLCMD utility:

	      rplcmd    : enter
	      boot      : enter
	      add       : enter
	      bootname  : DOS
	      vendorname: 08002b or
		 0000f8
	      Bbcfile   : bblock\netbeui\EWRK3\dosbb.cnf
	      (all other parameters are optional)
	      Bootcomment = EWRK3
	      Window Size = 0

	9. Run the RPL Administrator utility to add the new EWRK3
	   workstation (see the Windows NT Installation Guide for 
	   setting up network adapters, profiles and workstations).

To prepare the Client for WINDOWS NT 3.51 ...

    Use the EZWORKS Installation utility on the EtherWORKS 3 TURBO
    Remote Boot ROM diskette to select the following settings for 
    the client:

	   Remote Boot Function = Enable
	   Remote Boot Protocol = RPL/19H

    When the selections are complete, reboot the client PC to
    perform remote boot from the server.


****************************************
* LAN Manager Network Operating System *
****************************************

To prepare the Server for LAN Manager ...

	1. Set the default directory to the RPL directory 
	   (\LANMAN\RPL) containing the RPL.MAP file.

	2. Insert the EtherWORKS 3 TURBO driver distribution disk-
	   ette into drive A: on your computer, then copy the latest 
	   NDIS2 driver to the server. For example:

	      >COPY A:\NDIS2\DOS\EWRK3.DOS BBLOCK\NDIS\

	3. Create a subdirectory to contain PROTOCOL.INI and Boot 
	   Block Config Files (*.CNF), for example, 
	   BBLOCK\NETBEUI\EWRK3. This subdirectory contains 
	   PROTOCOL.INI and DOSBB.CNF files.

	   The following is an example of a DOSBB.CNF file:

	      ; DOS on Digital EtherWORKS 3 TURBO Adapter
	      RPL BBLOCK\RPLBOOT.SYS
	      LDR BBLOCK\RPLSTART.COM ~
	      DAT BBLOCK\NETBEUI\EWRK3\PROTOCOL.INI
	      DRV BBLOCK\RPLDISK.SYS ~ ~ ~
	      EXE BBLOCK\RPLPRO1.COM ~ 2 ~
	      EXE BBLOCK\I13.COM ~ ~ ~
	      EXE BBLOCK\RPLBIND2.EXE ~ ~
	      EXE BBLOCK\PROTMAN.EXE ~ ~
	      EXE BBLOCK\RPLBIND1.EXE ~ ~
	      ;DRV BBLOCK\IPXNDIS.DOS ~ ~ ~
	      EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
			     EXE BBLOCK\PW\DLLNDIS.EXE ~ 1 ~
			     EXE BBLOCK\PW\RPLENV.EXE ~ ~ ~
	      DRV BBLOCK\NDIS\EWRK3.DOS ~ ~ ~
		     DRV BBLOCK\PROTMAN.DOS/I:C:\LANMAN.DOS ~ M

	   The PROTOCOL.INI and NDIS2 driver EWRK3.DOS directories
	   are described in the above DOSBB.CNF example. Refer 
	   to the NDIS2 README.TXT file found on the driver distri-
	   bution diskette to create the PROTOCOL.INI file.

	4. For LAN Manager 2.2 or later, run the RPL Manager utility 
	   to create a new workstation record that contains your new 
	   EWRK3 adapter.

	   For LAN Manager versions prior to 2.2, add a boot block 
	   and workstation record in RPL.MAP.

	   Add a Boot Block Record in RPL.MAP. For example:

	yyyyyyyyyyyy BBLOCK\NETBEUI\EWRK3\DOSBB.CNF 2 6 A ~
	DOS~Digital~DECpc~EWRK3 08002B ~ ,,, ~ RDOSPCI ~ ~ ~ ~ ~ ~

	   In the above example, BBLOCK\NETBEUI\EWRK3\DOSBB.CNF 
	   is referred to as RDOSPCI.

	   Add a Workstation Record in RPL.MAP to specify the work-
	   station adapter ID and its corresponding Boot Block 
	   Record.

	08002B01005D 2B01005D N fits\dos600 (RPL_SERVER_NAME) S ~ ~ ~
	,,, ~ RDOSPCI ~ WINDOW *~New~Digital~EtherWORKS~* ~ ~ ~

	   In the above example, the workstation adapter ID is
	   08002B01005D; its corresponding Boot Block Record is 
	   referred to as RDOSPCI.

	   For more information, see the LAN Manager RPL Functional
	   Specification.

To prepare the Client for LAN Manager ...

    Use the EZWORKS Installation utility on the EtherWORKS 3 TURBO
    Remote Boot ROM diskette to select the following settings for 
    the client:

	   Remote Boot Function = Enable
	   Remote Boot Protocol = RPL or RPL/19H

    (Selecting RPL will hook INT 18H, ROM BASIC while RPL/19H will
    hook INT 19H, Bootstrap Loader.  For LAN Manager version 2.2 and
    later, always choose RPL/19H.)

    After the selection is completed, power up the client PC to
    perform remote boot from the server.


********************************************        
* PATHWORKS V4.1x Network Operating System *
********************************************

To prepare the Server for PATHWORKS V4.1x ...

    Before the first client is configured, have your PATHWORKS 
    system manager install the EtherWORKS 3 TURBO remote boot 
    task image files on the server as follows:

	1. Insert the Remote Boot Setup diskette into the disk 
	   drive of a PC connected to PATHWORKS network operating 
	   system (NOS).

	2. Copy the PATHWORKS task image files from the Remote Boot
	   Setup diskette to the Personal Computing Systems Archi-
	   tecture (PCSA), version V4.1 or later, default file area 
	   on the server using the Network Files Transfer (NFT) 
	   program:

    NFT> COPY/BLOCK
    FILE(S)?: A:\EWRK3_?.TSK
    TO?: hostname"SYSTEM password"::SYS$COMMON:[PCSA.LOAD_FILE.V41]

	   The /BLOCK switch is required to preserve the file 
	   format during the copy process.

	3. Run NETSETUP to prepare the server for client boot 
	   requests.  Set NETSETUP to Advanced mode, select the 
	   Configure a Remote Boot Client option, then configure 
	   the client as usual. Repeat this process for each remote 
	   boot client.

	4. Log into the server and set the Network Control Program
	   (NCP) database entry for each new client name to point 
	   to the EtherWORKS 3 TURBO remote boot task image 
	   file. The following example shows a client configured 
	   to use the hardware clock for the scheduler.  Replace 
	   EWRK3_H.TSK with EWRK3_S.TSK for the software clock.

	NCP> DEFINE NODE client_name -
	_NCP> LOAD FILE SYS$COMMON:[PCSA.LOAD_FILE.V41]EWRK3_H.TSK
	NCP> SET NODE client_name ALL

	   The installation is complete when the database has been
	   updated for all new nodes. For more information, refer 
	   to the PATHWORKS for DOS Client Installation and Config-
	   uration Guide for the VMS Server manual.

To prepare the Client for PATHWORKS V4.1x ...

    Use the EZWORKS Installation utility on the EtherWORKS 3 TURBO
    Remote Boot ROM diskette to select the following settings for 
    the client:

	   Remote Boot Function = Enable
	   Remote Boot Protocol = MOP

    When the selections are complete, reboot the client PC to 
    perform remote boot from the server.


*******************************************
* PATHWORKS V5.x Network Operating System *
*******************************************

To prepare the Server for PATHWORKS V5.x

	1. Find the file RPL.MAP that is located in the 
	   \\lanmanager.rpl directory.

	2. Edit the file and add lines to enable your system to 
	   receive the EWRK3 adapter's remote boot.

	   Find the Boot Block Record fields and add the following 
	   lines to the last few lines of Boot Block record field:

yyyyyyyyyyyy BBLOCK\NETBEUI\EWRK3\DOSBB.CNF 2 6 A ~ DOS~Digital~DECpc~EWRK3
08002b ~ '''~ RDOSPCI_1 ~~~~~~
yyyyyyyyyyyy BBLOCK\NETBEUI\EWRK3\DOSBB.CNF 2 6 A ~ DOS~Digital~DECpc~EWRK3
0000F8 ~ '''~ RDOSPCI_1 ~~~~~~

	3. Copy the driver (EWRK3.DOS) from the EtherWORKS 3 TURBO
	   driver distribution diskette to:

	      \\lanmanger.rpl\bblock\ndis

	4. Create a directory called EWRK3:

	      \\lanmanger.rpl\bblock\netbeui.

	   The new directory should look like the following:

	      \\lanmanger.rpl\\bblock\netbeui\EWRK3.

	5. Copy the DOSBB.CNF and PROTOCOL.INI files under \EWRK3 
	   from another directory (any directory parallel to EWRK3 
	   will do).  For example:

	   \\lanmanger.rpl\bblock\netbeui\XXXXX\dosbb.cnf    ==>
	   \\lanmanger.rpl\bblock\netbeui\EWRK3\dosbb.cnf

	   \\lanmanger.rpl\bblock\netbeui\XXXXX\protocol.ini ==>
	   \\lanmanger.rpl\bblock\netbeui\EWRK3\protocol.ini

	6. Edit the newly created DOSBB.CNF file in the following:

	   \\lanmanger.rpl\bblock\netbeui\EWRK3\dosbb.cnf

	   The first line is a comment. Change it to: 
	   
	   ; DOS on Digital EWRK3 Adapter

	   DAT BBLOCK\NETBEUI\XXXXX\PROTOCOL.INI ==>
	   DAT BBLOCK\NETBEUI\EWRK3\PROTOCOL.INI

	   DRV BBLOCK\NDIS\XXXXX.DOS ~~~ ==>
	   DRV BBLOCK\NDIS\EWRK3.DOS ~~~

	7. Edit your new PROTOCOL.INI file in the following:

	   \\lanmanger.rpl\bblock\netbeui\EWRK3\protocol.ini

	   In the PROTOCOL.INI file, there is a bracket title 
	   [netbeui_xif]. Search the file to find bindings = 
	   XXXXX_nif, then replace the XXXXX with EWRK3.

	8. Run the RPL Manager utility to create a new workstation
	   record that contains the EWRK3 adapter. This is the same
	   as adding a workstation record in the workstation fields 
	   of the RPL.MAP file.

To prepare the Client for PATHWORKS V5.x ...

    Use the EZWORKS Installation utility on the EtherWORKS 3 TURBO
    Remote Boot ROM diskette to select the following settings for 
    the client:

	   Remote Boot Function = Enable
	   Remote Boot Protocol = RPL/19H

    When the selections are complete, reboot the client PC to
    perform remote boot from the server.


*******************************************
* IBM LAN Server Network Operating System *
*******************************************

To prepare the Server for DOS RPL ...

	1. Set the default directory to the RPL directory 
	   (\IBMLAN\RPL) containing RPL.MAP.

	2. Copy the latest NDIS driver to the server. For example:

	      >COPY A:\NDIS2\DOS\EWRK3.DOS C:\IBMLAN\DOSLAN\LSP\DOS

	3. Create a subdirectory to contain the PROTOCOL.INI file. 
	   For example:

		     C:\IBMLAN\RPL\DOS\EWRK3
		     C:\IBMLAN\RPL contains DOSEWRK3.CNF.

	   The following is an example of DOEWRK3.CNF:

	; DOS on Digital EtherWORKS 3 TURBO Adapter
	; NDIS LAN Support Program Drivers
	BASE 7C0H
	RPL DOS\RPLBOOT.SYS
	LDR DOS\RPLLOADR.COM ~
	DAT DOS\EWRK3\PROTOCOL.INI
	DAT C:\IBMLAN\DOSLAN\LSP\DXM.MSG
	EXE C:\IBMLAN\DOSLAN\LSP\NETBIND.COM ~ ~ ~
	;**NETBIOS and IEEE 802.2*******************************************
	;DRV C:\IBMLAN\DOSLAN\LSP\DXMT0MOD.SYS PBA=0~S=12~ST=12~C=14~O=N ~ ~
	;DRV C:\IBMLAN\DOSLAN\LSP\DXME0MOD.SYS ~ 10 ~
	;**NETBIOS and IEEE 802.2*******************************************
	;**NETBIOS**********************************************************
	DRV C:\IBMLAN\DOSLAN\LSP\DXMJ0MOD.SYS ~ 17 ~
	;**NETBIOS**********************************************************
	DRV C:\IBMLAN\DOSLAN\LSP\DXMA0MOD.SYS 001 ~ ~
	DRV C:\IBMLAN\DOSLAN\LSP\DOS\EWRK3.DOS ~ ~ ~
	DRV C:\IBMLAN\DOSLAN\LSP\PROTMAN.DOS /I: ~ ~

	   The directories of PROTOCOL.INI and NDIS2 Driver 
	   EWRK3.DOS are described in the previous DOSEWRK3.CNF 
	   example. Refer to the NDIS2 README.TXT file to create 
	   the PROTOCOL.INI file.

	4. Add a Boot Block Record in RPL.MAP. For example:

	      yyyyyyyyyyyy dosEWRK3.cnf  3 10 N IBMLAN$
	      DOS~DEC~EWRK3        ~ ~ ,,, Z R_EWRK3 ~ ~

	   In the previous example, DOSEWRK3.CNF is referred to as
	   R_EWRK3.

	5. Add a Workstation Record in RPL.MAP to specify the work-
	   station adapter ID and its corresponding Boot Block 
	   Record.

	      08002B92FBFA EWRK3DOS ~ STD3HHMA PCISVR1 PCIDM ~ ~ ~
	      ,,, Z R_EWRK3 ~ ~ ~

	   In the previous example, the workstation adapter ID is
	   08002B92FBFA; the Boot Block Record is referred to as
	   R_EWRK3.

To prepare the Server for OS/2 RPL ...

	1. Set the default directory to the RPL directory 
	   (\IBMLAN\RPL) containing RPL.MAP.

	2. Copy the latest NDIS driver to the server. For example:

	      >COPY A:\NDIS2\DOS\EWRK3.DOS C:\IBMLAN\DOSLAN\LSP\DOS
	      >COPY A:\NDIS2\OS2\EWRK3.OS2 C:\IBMLAN\RPL\IBMCOM\MACS

	3. Create a subdirectory to contain PROTOCOL.INI. For 
	   example:

		      C:\IBMLAN\RPL\DOS\EWRK3

	4. Edit C:\IBMLAN\RPL\NDISDD.PRO, then append the following
	   line:

		     EWRK3.DOS   EWRK3

	5. Create a subdirectory to contain PROTOCOL.INI and 
	   CONFIG.NET files. For example:

		     C:\IBMLAN\RPL\IBMCOM\EWRK3

	   Edit C:\IBMLAN\RPL\IBMCOM\EWRK3\CONFIG.NET, then change
	   DEVICE=Z:\IBMCOM\MACS\?????.OS2 to 
	   DEVICE=Z:\IBMCOM\MACS\EWRK3.OS2.

	   Edit C:\IBMLAN\RPL\IBMCOM\EWRK3\PROTOCOL.INI, then insert 
	   the following line into the IBMLXCFG module:

		     EWRK3_nif = EWRK3.nif

	6. Manually create the FIT file for EWRK3, 
	   C:\IBMLAN\RPL\FITS\EWRK3OS2.FIT 
	   or use the LAN Server Administration LAN Service.

	7. Manually create the configuration file for EWRK3,
	   C:\IBMLAN\RPL\MACHINES\EWRK3OS2\CONFIG.SYS,
	   or use the LAN Server Administration LAN Service.

	8. Create a CNF file for EWRK3, C:\IBMLAN\RPL\OS2EWRK3.CNF. 
	   For example:

	      ; OS/2 Boot Block Configuration (EWRK3 adapter)
	      ;
	      RPL DOS\RPLBOOT.SYS
	      DAT DOS\MFSD20.SYS
	      ORG 1000H
	      LDR OS2.21\OS2LDR ~ OS2LDR UFSD.SYS MFSD20.SYS
	      DAT DOS\UFSD.SYS
	      DAT DOS\EWRK3\PROTOCOL.INI
	      DAT C:\IBMLAN\DOSLAN\LSP\DXM.MSG
	      EXE C:\IBMLAN\DOSLAN\LSP\NETBIND.COM ~ ~ ~
	      DRV C:\IBMLAN\DOSLAN\LSP\DXMJ0MOD.SYS ~ 17 ~
	      DRV C:\IBMLAN\DOSLAN\LSP\DXMA0MOD.SYS 001 ~ ~
	      DRV C:\IBMLAN\DOSLAN\LSP\DOS\EWRK3.DOS ~ ~ ~
	      DRV C:\IBMLAN\DOSLAN\LSP\PROTMAN.DOS /I: ~ ~

	9. Add a Boot Block Record in RPL.MAP. For example:

	      yyyyyyyyyyyy os2EWRK3.cnf  3 10 N ~
	      OS2~2.1~DEC~EWRK3~Adapter~ ~ ,,, ~ R_21_EWRK3 ~ ~

	   In the previous example, OS2EWRK3.CNF is referred as
	   R_21_EWRK3.

	10.Add a Workstation Record in RPL.MAP to specify the work-
	   station adapter ID and its corresponding Boot Block 
	   Record.

	      08002B92FBFA EWRK3OS2 ~ FITS\EWRK3OS2
	      LAN40 Z ~ ~ ~ ,,, ~ R_21_EWRK3 ~ ~ ~

	   In the previous example, the workstation adapter ID is
	   08002B92FBFA; the Boot Block Record is referred to as
	   R_EWRK3.

	For more information, refer to the Network Administrator
	Reference Volume 3: Network Administrator Tasks, or the LAN
	Manager RPL Functional Specification.

To prepare the Client ...

    Use the ROM Setup program, on the Remote Boot Setup diskette, 
    to select the following settings for the client:

	   Remote Boot Function = Enable
	   Remote Boot Protocol = RPL or RPL/19H

    (The RPL will hook INT 18H ROM BASIC and the RPL/19H will hook
    INT 19H Bootstrap Loader.)

    When the selections are complete, reboot the client PC to 
    perform remote boot from the server.
