(C)Copyright 2003-2005 Marvell(R).
All rights reserved..
===========================================================================


dlk530.txt created 23-Feb-2005

Readme File for dlk530.dos v8.11.1.3 NDIS2 Driver supporting the
D-Link DGE-530T Gigabit Ethernet Adapter


This file contains
 1  Overview
 2  Required Files
 3  Installation
 4  Operation on dual port controllers
 5  Driver Parameters
 6  Sample Installation/Configuration

===========================================================================



1  Overview
===========

The driver dlk530.dos is the NDIS2 driver for the Microsoft Network Client
for DOS for the D-Link DGE-530T Gigabit Ethernet Adapter.
***


2  Required Files
=================

    DLK530.DOS          the driver
    OEMSETUP.INF        installation skript
    PROTOCOL.INI        SAMPLE configuration file

    Microsoft Network Client 3.0 for MS-DOS
***


3  Installation
===============

When installing the Microsoft Network Client for DOS follow these steps
to install dlk530.dos:

1.  Start the installation of the Microsoft Network Client.
2.  When you are prompted to select a network adapter, select
    "Network adapter not shown on list below ...".
3.  Enter the path where the files dlk530.dos and
    oemsetup.inf are located.
4.  Select "D-Link DGE-530T Gigabit Ethernet Adapter".
5.  Answer the questions in the following dialogs to best fit your needs.
6.  When prompted if the listed options are correct, you should select
    "Change Network Configuration".
7.  Add the protocols that are needed for your network and configure them
    to best fit your needs.
8.  Return from the dialog and confirm that the listed options are
    correct.
9.  Finish the installation of the Microsoft Network Client.
10. If you have more than one network adapter you might want to change
    the bus number and device number in the protocol.ini as described
    in the next section.
***



4  Operation on dual port controllers
=====================================

The driver will run on that port that first came up with a link when the
driver is loaded. It does not switch if the current port loses its link
and the other comes up.
If none of the ports has a link at the time the driver is loaded, it will
setup port A in case a cable is plugged in after loading the driver.
***



5  Driver Parameters
====================

After the installation of the driver, the file protocol.ini in your
Microsoft Network Client installation directory contains the following
lines:

[DLINK$dlk530]
    DriverName = dlk530$

When you have more than one adapter supported by the driver in your system
you might want to specify which adapter should be used. There are two ways
to specify the adapter.

Bus and device number (optional)

    BUSNUM = <busnum>
    DEVNUM = <devnum>

    With these parameters you can specify the network adapter the
    driver should bind on.
    The bus and device numbers are assigned by the BIOS at boot time.

Connection type (optional)

    CONTYPE = <contype>

    This parameter can be used to force link speed and duplex mode.
    Using other values than AUTO turns off auto-negotiation and is not
    recommended.
    Possible values are:

    AUTO
    _100FD
    _100HD
    _10FD
    _10HD

Check link mode (optional)

    CHECKLINK = 1

    When this parameter has been specified the driver uses the first
    supported adapter in the system with a valid link. This parameter
    will be ignored when BUSNUM and DEVNUM are used.

Number of receive and transmit buffers (optional)

    MAXRECEIVES
    MAXTRANSMITS

    Possible values: 1..4, but the sum of receive and transmit buffers
    cannot be greater than 5.

    These parameters specify how many transmit and receive buffers the
    driver shall use. Using more buffers might improve the performance
    but the driver will consume more memory.

Designated port (optional)

    HWPORT = A

    Possible values: A, B, L(default)

    On controllers with two ports, the driver will use the port that is
    selected (Port A or B) or it will use the port that has a link.
    On controllers with only one port, this parameter will be ignored and
    defaults to 'A'.
    If the parameter CHECKLINK is selected at the same time, the parameter
    PORT is automatically reset to 'L'.

Adjust internal behavior (optional)

    FIX = <bitmask>

    A bitmask to change some internal behavior of the driver. May be
    entered as a number (e.g. 3) or as a bitstring (e.g. "011").

    - Bit 0 ("FIX=1") avoids crashes caused by a stack overflow
      problem (observed only with MtTool 3.0). Use only if you
      experience crashes or system stops.

    - Bit 1 ("FIX=2") will let the driver queue packets internally.
      MS network client 3.11 with IPX (nwlink) may otherwise stop
      working if out of send buffers.

    Bit values can be combined by simply using their sum (e.g. "FIX=3").
***


6  Sample Installation/Configuration
====================================

Below you find a sample protocol.ini and system.ini from the Microsoft
Client Installation directory:

Sample system.ini:

   [network]
   filesharing=no
   printsharing=no
   autologon=yes
   computername=MyComputer
   lanroot=C:\NET
   username=Me
   workgroup=MyWorkgroup
   reconnect=yes
   dospophotkey=N
   lmlogon=0
   logondomain=MyWorkgroup
   preferredredir=basic
   autostart=basic
   maxconnections=8

   [network drivers]
   netcard=dlk530.dos
   transport=tcpdrv.dos,nemm.dos
   devdir=C:\NET
   LoadRMDrivers=yes

   [386enh]
   TimerCriticalSection=5000
   UniqueDosPSP=TRUE
   PSPIncrement=2

   [Password Lists]
   *Shares=C:\NET\Shares.PWL


Sample protocol.ini:

   [network.setup]
   version=0x3110
   netcard=DLINK$dlk530,1,DLINK$dlk530,1
   transport=tcpip,TCPIP
   lana0=DLINK$dlk530,1,tcpip

   [TCPIP]
   NBSessions=6
   SubNetMask0=255 255 0 0
   IPAddress0=10 9 1 41
   DisableDHCP=1
   DriverName=TCPIP$
   BINDINGS=DLINK$dlk530
   LANABASE=0

   [protman]
   DriverName=PROTMAN$
   PRIORITY=MS$NDISHLP

   [DLINK$dlk530]
   DriverName=dlk530$
   CHECKLINK=1

*** End of Readme file ***
