The Windows for Workgroups 3.11 Driver
======================================
                                               LSS 5.0(0), August 1996
                                               -----------------------

Summary
-------

This  file  discusses  the manual  configuration  of  the  MDGWFWG.386 
driver.


Section 1) Manual Installation
------------------------------

You can adjust the settings for each adapter managed by the driver  by 
editing  the  PROTOCOL.INI  file  in  the  \WINDOWS  directory. In the 
[network.setup] section there will be one or  more  "netcard="  lines. 
Each  line has four parameters, the third of which will be of the form 
MDG$MDG???,  where  ???  identifies  the  type  of  adapter,  possibly 
followed  by a number to make them unique. Elsewhere in the file there 
will be a separate section  named  exactly  the  same  as  this  third 
parameter  on  the  "netcard="  line.  In each section there will be a 
series of lines, one for each parameter  that  has  been  set  in  the 
"Setup..." and "Advanced..." dialogs above. These are:

   IOADDRESS      (ISA bus only, should be a hex. number,  of the form
                   0x????)
   IRQNUMBER      (ISA bus only, should be a decimal number)
   DMACHANNEL     (ISA bus only, should be a decimal number)
   MAXFRAMESIZE   (should be a decimal number)
   ALTERNATE      (0 means no, 1 means yes)
   NETWORKADDRESS (must be a 12 digit hexadecimal number in quotes)

You  can  change  these  parameters  with  a text editor,  although we 
recommend  using  the  Windows  Setup program to do this.  It  may  be 
useful  to  know  where  the  parameters  are, to  confirm the setup.

Note  that  there  is also a MDGWFWG section in the PROTOCOL.INI file, 
with a single line in it  looking  like  "Adapters=<sec1>,<sec2>,...", 
where  there will be one or more section names exactly the same as the 
sections discussed above. Do NOT put any parameters in this section  - 
this  is  for  NDIS3  specific  parameters  which configure the driver 
itself as supposed  to  the  various  card  instances.  There  are  no 
parameters available for this section.

You   may  want to check that  Windows  knows  about  the  MDGWFWG.386 
file.  Look in the \WINDOWS\SYSTEM.INI file, in the [386Enh]  section, 
for the "netcard3=" line.  This specifies the name of an NDIS3 netcard 
driver  and  should  be  MDGWFWG.386,  with  the  file  itself  in the 
\WINDOWS\SYSTEM directory.  (The "netcard=" line is for NDIS2 drivers, 
not NDIS3 drivers.)

Extra Configuration:
--------------------

The following advanced  configuration  options  can  only  be  set  by 
editing the PROTOCOL.INI.

    TESTANDXIDENABLED  (0 means no, 1 means yes)
    FORCEOPEN          (0 means no, 1 means yes)
    TXSLOTS            (should be a decimal number)
    RXSLOTS            (should be a decimal number)
    FORCE16BITPIO      (0 means no, 1 means yes)
    SLOTNUMBER         (should be a decimal number)

1) TestAndXIDEnabled (TEXTANDXIDENABLED):

   Certain  connectivity  products  require that an NDIS driver handle 
   LLC  TEST  and  XID  frame.  Setting  this  option   enables   such 
   processing.  Only  set  this  option  if  it  is  required  in your 
   internetwork.

2) ForceOpen (FORCEOPEN):

   Normally a token ring adapter will only insert into a ring  if  the 
   ring  is  in  a good state. However an adapter can be configured to 
   insert into the ring even if the ring is in a  bad  state.  Setting 
   this  option  causes  such  a  forced open to be used.  This option 
   should NOT normally be used.

3) Number of receive/transmit and receive slots (TXSLOTS/RXSLOTS):

   These two options allow you to alter the amount of memory  that  is 
   allocated  for  buffering frames being received or transmitted. The 
   buffers used are on the host PC, and take up memory resources  that 
   cannot  be  paged  in a virtual memory environment. Each receive or 
   transmit slot requires "Maximum frame size" bytes of memory. It  is 
   unwise  to  allocate a total of more than 65535 bytes of memory for 
   buffering. The default of 4 transmit and 4 receive slots  has  been 
   found to be optimal for a 486 class workstation.

4) Force 16bit PIO (FORCE16BITPIO):

   Normally  when  PIO  is chosen as the transfer method  MDGWFWG will 
   attempt to use 32bit programmed I/O on adapters that  support  this 
   mode.  One  some old or out of specification PCs you may experience 
   problems with 32bit PIO. If this is the case you may force the  use 
   of 16bit PIO by setting this option to yes.

5) PCI Device ID (SLOTNUMBER):

   PCI adapters may be referred to by a logical device ID. This is not 
   always  the  same  as the physical slot number in the PC. If you do 
   not know the logical device ID of your PCI adapter do not specify a 
   device ID and MDGWFWG will find the Madge Smart PCI adapter when it 
   starts.


                    ****** End of WFWG.TXT ******



