
	   EtherWORKS 3 Windows For Workgroups Installation file
	   =====================================================


Section 1..................................... Installing on WFW 3.11
Section 2..................................... Installing ODI(Novell) on WFW

				Section 1
				=========

  Previous to configuring WFW's please enter NICSETUP.EXE to configure the card
according to your PC's Operating environment. If you are using the NDIS3 driver
please configure your card for 32K or 64K MemoryMode's. 2K MemoryMode is not
supported with the NDIS3 driver. If 2K mode is chosen when utilizing the NDIS3
driver you will get a message that the network has responded incorrectly and
the following error will appear in c:\windows\ndislog.txt:

		EWRK3. Unsupported Configuration, 0x00000002

  If you are running an Extended Memory Manager(EMM) it is also necessary to 
edit your CONFIG.SYS file and add the eXclude(e.g. x=d000-d7ff) statement to 
the end of your EMM line. This is necessary so your EMM will not use the 
memory region that the EtherWORKS 3 card uses for its Network Buffer. For 
example if you were using the EtherWORKS 3 card in 32K mode starting at 
memory address d000 the line would look as follows:

	  device = c:\dos\emm386.exe RAM frame=E000 x=d000-d7ff

    Warning: (If using NDIS3) The current OEMSETUP.INF file sets 
	     PROTOCOL.INI so that during the time the NDIS3 driver is 
	     loaded (after NET START is performed) it will use 32K 
	     memory mode. Even though the card may be (permanently) 
	     configured for 2K mode (as shown by NICSETUP). For the 
	     NDIS3 driver a minimum of 32K must be excluded so as not 
	     to cause problems with your Extended Memory Manager.

For an EtherWORKS 3 card in 2K mode starting at memory address d000 it would 
alternatively look as follows:

	  device = c:\dos\emm386.exe RAM frame=E000 x=d000-d07f

 Note: For users who have *PREVIOUSLY* ADDed the EtherWORKS 3 card to 
       Windows for Workgroups and are trying to update their setup with 
       a newer EtherWORKS 3 OEMSETUP.INF file. First you need to enter 
       Windows for Workgroups and REMOVE the adapter. Then exit Windows 
       for Workgroups and delete the previously created OEMn.INF(where n 
       is a number) for the EtherWORKS 3 card that resides in your 
       \WINDOWS\SYSTEM directory. Type out the file(s) OEMn.INF individually 
       and delete any file that contains EtherWORKS 3 adapter information 
       before re-installing the new EtherWORKS 3 OEMSETUP.INF file found 
       on this distribution media. 

   If this is a new Windows for Workgroups V3.11 installation (or you are
replacing a previously installed Network Adapter other than an EtherWORKS 3 
card). Use the following procedure to add the card to your system: 

1) For a brand new install at the point when the NETWORK SETUP dialogue box 
   appears click on the following:

       ADVANCED >>
       NETWORKS
       Install Microsoft Windows Network
       OK

   Otherwise if you ALREADY have WFW's installed click on the NETWORK SETUP 
   icon in the NETWORK program group.
2) Click on the DRIVERS... button
3) If a Network Adapter has been previously installed click on the REMOVE 
   button to delete the current Network Adapter
4) Click on the ADD ADAPTER... button
5) Select Unlisted or Updated Network Adapter then click on OK.
6) Insert this distribution media into your floppy drive and enter the 
   path to where the appropriate OEMSETUP.INF file is:

     A:\      (if the adapter is being installed as an ISA device)
			    - or -
     A:\EISA  (if the adapter is being installed as an EISA device)

	       Note: The NDIS3 driver is not supported when the 
		     EtherWORKS 3 card is operating in EISA mode. 
		     The EtherWORKS 3 can run as a ISA device in
		     EISA machines with *NO* performance difference.

   Now click on the OK button of "Install Driver" dialogue box
   (Note: Do *NOT* include the OEMSETUP.INF filename as part of the path.)

7) Now click on the OK button of the "Unlisted or Updated Network Adapter"
   dialogue box to select "Digitaal EtherWORKS 3/TURBO Ethernet Adapter"

8) At this point a "Networks Driver" dialogue box will appear showing the:

     "Digital EtherWORKS 3/TURBO Ethernet Adapter [NDIS2/NDIS3]"

   as the currently selected driver. Click on SETUP... to configure the card 
   according to your PC's Operating environment. 

9) You need to make 2 selections at this point:

      a) Base I/O Port (hex): This MUST match what the card is currently
			      configured for via NICSETUP. 0x300 is the
			      default setting for EtherWORKS 3 cards. 

      b) Driver Type:         NDIS3-> Real Mode and Enhanced Mode NDIS Driver
			      NDIS2-> Real Mode NDIS Driver
			      ODI  -> ODI Driver (Novell)

  (Note: Do *NOT* select the Enhanced Mode NDIS driver as a Driver Type. If 
	this is selected the [EWRK3] section of your PROTOCOL.INI file(in 
	the \WINDOWS directory) will not be built correctly and the network 
	will not start. The following shows how the [EWRK3] section should 
	appear(The IOAddress parameter MUST match what the EtherWORKS 3 
	card is configured for in your PROTOCOL.INI file:))

			     [EWRK3]
			     DriverName=EWRK3$
			     IOAddress=0x300
			     Adapters=EWRK3

    Click on OK after you have completed your selections.

10) Click on ADD PROTOCOL... if you need to add any Network Protocol's

11) Click on CLOSE then on OK to complete the setup portion of the EtherWORKS 3
    Turbo's installation. 

12) Depending upon your installation you will be asked a series of questions. 
    At some point an "Install Driver" dialogue box will ask you to to insert 
    the "Digital EtherWORKS 3 TURBO" diskette. Please insert this Distribution 
    Media into your diskette drive and click on "OK" so that the EtherWORKS 3
    driver(s) are copied from your diskette to your hard drive.

				Section 2
				=========

Using the ODI Client driver for WFW 3.11
****************************************
If you have already installed some other driver (such as ndis2), remove
it using netsetup.  Also, remove the Microsoft Windows Network.  After 
re-booting, examine the files config.sys, autoexec.bat, 
windows\protocol.ini, windows\win.ini, and windows\system.ini 
to make certain that all references to your previous driver have been 
removed.  There have been cases observed where WFW does not remove all
that it should and this can cause problems in your odi client installation.

WFW assumes that you will have an odi client RUNNING before you initiate
windows.  Set up an odi subdirectory with your client software, your
client driver, and a net.cfg file, as you would for any ordinary odi
client installation.

Edit autoexec.bat to add the following lines at the top of the file.

	lsl
	ewrk3.com
	ipxodi
	netx            (or vlm)

Start your Novell Client software and enter windows. 

    Click on NETWORK SETUP.
    Click on NETWORKS.
	Install Microsoft Windows Network
	Choose additional network: other, 
	    then locate Novell Netware 3.x (or 4.x) and click on it.
	Click on OK.

	Choose the type of Novell Netware drivers
	(IPXODI.COM and LSL.COM)

    Click on DRIVERS.
	Click on ADD ADAPTER.
	Choose unlisted or updated network adapter.
	Click on OK.
	Enter path to new oemsetup file.
	"Digital EtherWORKS 3" should appear.
	Click on OK.
	Menu should show ODI/NDIS3.
	Click on CLOSE

    Click on OK.

    Enter network name when prompted.
    You will be prompted for Novell files from WINUP9 - WINUP9.EXE can
	be obtained from Novell's CompuServe forum.
    You will be prompted for files from the WFWG 3.11 installation kit.
    You will be told that various initialization files are being updated.
    Click on RESTART SYSTEM.

    (NOTE: Some earlier manufactured versions of the WFW V3.11 install 
	   diskettes may not contain all the Novell files asked for when 
	   inserting disks 7 and/or 8. In these cases you may need a more 
	   recently produced version of the WFW V3.11 kit. Alternatively 
	   the files can be obtained on Novell's CompuServe Forum).

Your system should re-boot and attach to your server.  At this point,
it is best to log on to your Netware server before starting windows 
- this will allow all Netware mapped drives to AUTOMATICALLY appear in 
your WFW filemanager, otherwise, if you log on later, you would have to 
add them manually.

Start WFW and open the filemanager.  You should see your Netware drive(s).
