1. DM9102A_CE30MIPS_v101.zip Driver
2. README.TXT File Contents

README.TXT Driver File Contents (DM9102A_CE30MIPS_v101.zip)

        Davicom DM9102A NDIS CE Miniport Device Driver Note
               for MIPS 4300 Edition (Dec. 4, 2000)


    The Davicom DM9102A NDIS CE miniport device driver is used to be the
network component of the Microsoft CE Operating System enables hardware
containing Davicom's fast ethernet controller 'DM9102A'.
    This file describes the procedures of the driver installation. Note that
this is not written for end-users.

CONTENTS:

    README.TXT      -   This file
    DM9PCI.DLL      -   NDIS CE miniport device driver
    Config.bib      -   CE file  (See note 1)
    Platform.bib    -   CE file
    Platform.reg    -   CE file


INSTALLATION:

    1. Place the driver (DM9PCI.DLL) in Windows CE Release Directory(_FLATRELEASEDIR).

    2. In Platform.bib, insert the following line in this file:
          dm9pci.dll       $(_FLATRELEASEDIR)\dm9pci.dll              NK  SH

    3. In Platform.reg, add the following registry value for the driver in this file:

         [HKEY_LOCAL_MACHINE\Comm\DM9PCI]
             "DisplayName"="DM9102 Fast Ethernet Adapter"
             "Group"="NDIS"
             "ImagePath"="dm9pci.dll"

         [HKEY_LOCAL_MACHINE\Comm\DM9PCI\Linkage]
             "Route"=multi_sz:"DM9PCI1"

         [HKEY_LOCAL_MACHINE\Comm\DM9PCI1]
             "DisplayName"="DM9102 Fast Ethernet Adapter"
             "Group"="NDIS"
             "ImagePath"="dm9pci.dll"

         [HKEY_LOCAL_MACHINE\Comm\DM9PCI1\Parms]
             "BusNumber"=dword:0
             "BusType"=dword:5
             "ConnectionType"=dword:0
             "XmitBuffer"=dword:5
             "RecvBuffer"=dword:23

         [HKEY_LOCAL_MACHINE\Comm\DM9PCI1\Parms\TcpIp]
             "EnableDHCP"=dword:0
             "DefaultGateway"="172.22.5.62"
             "UseZeroBroadcast"=dword:0
             "IpAddress"="172.22.5.60"
             "Subnetmask"="255.255.255.0"
             "DNS"="202.14.101.253"
             "WINS"="202.14.101.252"

         [HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage]
             "Bind"="dm9pci1"

        Note:
            1. The parameter "BufferPhysicalAddress" is the starting address as the
                value in Config.bib.
            2. "XmitBuffer" and "RecvBuffer" stand for the quantity of transmitting buffers
                and receiving buffers.
            3. This driver can search the hardware device automatically.
            4. The value '0' of "ConnectionType" means Auto-negotiation.

            5. The total physical memory occupied can be calculated by this:
                   TX  : the quantity of the transmit buffer
                   RX  : the quantity of the receive buffer

                   Size = (TX + RX) * 1584 + 192

               Note:
                    The Physical Buffer Address need not to be assigned in new ITE's PDK.


TCP/IP CONFIGURATION:

    There are two methods to configure TCP/IP under Windows CE environment.
    1. DHCP:
        TCP/IP protocol drivers obtain IP address by DHCP method. So the setting
        in TCP/IP block should be as bellow:

         [HKEY_LOCAL_MACHINE\Comm\DM9PCI1\Parms\TcpIp]
            "EnableDHCP"=dword:1

    2. Force mode:
        Under this method, TCP/IP retrieve IP address and other information from
        the registry in the firmware, i.e.

         [HKEY_LOCAL_MACHINE\Comm\DM9PCI1\Parms\TcpIp]
             "EnableDHCP"=dword:0
             "DefaultGateway"="172.22.5.62"
             "UseZeroBroadcast"=dword:0
             "IpAddress"="172.22.5.60"          <---- IP address
             "Subnetmask"="255.255.255.0"       <---- Subnet mask
             "DNS"="202.14.101.253"             <---- Domain Name Server address
             "WINS"="202.14.101.252"            <---- WINS server address, if needed


Note:
    1. According to ITE's PDK, the functions of the dynamical memory allocation
       have been provided. So the file 'Config.bib' does not need to be changed
       any more. So this file is removed in this package.


----------------------------------------------------------------------------------
All trademarks or brand names mentioned are trademarks and registered trademarks
of their respective companies.