1. EBC573_LAN.zip Driver
2. e100ce4.txt File Contents

e100ce4.txt Driver File Contents (EBC573_LAN.zip)

Windows CE Network Interface Installation
12/18/2002

Summary
The configuration files provided with the Windows* CE driver enable support for single
or multiple network interfaces based on the 82559, 82559ER, 82551, 82551ER, or 82562 Fast Ethernet 
PCI Controller. This technical note provides information on installation and configuration. 
A specific example is shown for a 2-port scenario in a single system.

Single Network Interface Configuration
Use an ASCII text editor to read and modify the contents of the CONFIG.BIB and
PLATFORM.REG files. The network interface requires its own
reserved memory range, denoted in the CONFIG.BIB file. The size should match the
size of the default range (currently about 120KB) and must not conflict with any other
reserved ranges. The network interface also needs a Registry configuration in the
PLATFORM.REG file. The protocol information should be modified (e.g., different IP
address or gateway) to correspond to your application.
Modify the CE_PhysAddr Registry value to match the base address of the corresponding
memory range reserved above in the CONFIG.BIB file. The PCI slot no longer needs to be 
set via the registry.  Instead, the information is found via a PCI bus enumerator built into
the Windows CE operating system.  Bindings, routes, and linkages are now handled by the operating
system as well, eliminating the need to set the linkage and route by hand.  



Multiple Network Interface Configuration
Each network interface requires its own reserved memory range. These
additional memory ranges must be added to the CONFIG.BIB file. The size of each
range should match the size of the default, approximately 120KB. These memory ranges
must not overlap or conflict with any other reserved ranges. The only things that may need to be
modified are the subnet mask, default gateway, and IP address, in the case of static IP usage.

Modify the CE_PhysAddr Registry value for each of the new interfaces to match the
base address of the corresponding memory range reserved in the CONFIG.BIB file. 


Example Configuration for Two Network Interfaces

<CONFIG.BIB>
MEMORY

    ;Here is our packet buffer memory range (20000h for each adapter x 2 adapters)
    ;In platform.reg, map one adapter to 80050000 and one to 80070000
    EPKTBUF 80050000 00040000 RESERVED
    FRAMEBUF 800A0000 00020000 RESERVED
    PCMCIABUF 800D0000 00010000 RESERVED
    ; Debug Ethernet packet buffers
    NSCIRDA 801BC000 00020000 RESERVED
    EDBG 801DC000 00020000 RESERVED
    AUDIOBUF 801FC000 00002000 RESERVED
    LOADRBUF 801FFF00 00000100 RESERVED



<PLATFORM.REG>

IF CEPC_INTELFE_PCI
; Generic adapter configuration/description
[HKEY_LOCAL_MACHINE\Comm\E100CE]
    "DisplayName"="Intel(R) Fast Ethernet Controller"
    "Group"="NDIS"
    "ImagePath"="e100ce.dll"

;Create registry information for template (will be copied to ALL instances of
;adapters using the Intel Miniport Driver

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\E100CE]
;PCI Bus Enumeration Information
   "Class"=dword:02
   "SubClass"=dword:00
   "ProgIF"=dword:0
   "VendorID"=multi_sz:"8086","8086","8086"
   "DeviceID"=multi_sz:"1209","1229","2449"
   "Dll"="NDIS.dll"
   "Entry"="NdisPCIBusDeviceInit"
   "Transceiver"=dword:3
;Installable ISR Handler Information
   "IsrDll"="giisr.dll"
   "IsrHandler"="ISRHandler"
   "PortIsIO"=dword:0
   "PortOffset"=dword:0
   "PortSize"=dword:4
   "PortMask"=dword:20F0


; IP configuration for an adapter instance
; Settings for DHCP, if enabled
IF DHCP
[HKEY_LOCAL_MACHINE\Comm\E100CE1\Parms\TcpIp]
    "EnableDHCP"=dword:1
    "DefaultGateway"=""
    "UseZeroBroadcast"=dword:0
    "IpAddress"="0.0.0.0"
    "Subnetmask"="0.0.0.0"
ENDIF

; Settings for static IP configuration, if enabled
IF STATIC_IP
[HKEY_LOCAL_MACHINE\Comm\E100CE1\Parms\TcpIp]
    "EnableDHCP"=dword:0
    "DefaultGateway"="1.2.3.4"
    "UseZeroBroadcast"=dword:0
    "IpAddress"="192.168.168.98"
    "Subnetmask"="255.255.255.0"
ENDIF

; Specific configuration for a dual network interface instance

[HKEY_LOCAL_MACHINE\Comm\E100CE1\Parms]
    "BusNumber"=dword:0
    "BusType"=dword:5
    "BusTypeLocal"=dword:5
    ; Shared packet buffer storage, must match reserved memory range
    "CE_PhysAddr"=dword:80050000
    ; Other adapter-specific Registry parameters may be inserted here

[HKEY_LOCAL_MACHINE\Comm\E100CE2\Parms]
    "BusNumber"=dword:0
    "BusType"=dword:5
    "BusTypeLocal"=dword:5
    ; Shared packet buffer storage, must match reserved memory range
    "CE_PhysAddr"=dword:80070000
    ; Other adapter-specific Registry parameters may be inserted here

; Settings for DHCP, if enabled
IF DHCP
[HKEY_LOCAL_MACHINE\Comm\E100CE2\Parms\TcpIp]
    "EnableDHCP"=dword:1
    "DefaultGateway"=""
    "UseZeroBroadcast"=dword:0
    "IpAddress"="0.0.0.0"
    "Subnetmask"="0.0.0.0"
ENDIF
; Settings for static IP configuration, if enabled

IF STATIC_IP
[HKEY_LOCAL_MACHINE\Comm\E100CE2\Parms\TcpIp]
    "EnableDHCP"=dword:0
    "DefaultGateway"="1.2.3.4"
    "UseZeroBroadcast"=dword:0
    "IpAddress"="192.168.168.99"
    "Subnetmask"="255.255.255.0"
ENDIF

ENDIF



About Display Names

When the same Display Name (Intel(R) Fast Ethernet Controller) is used for multiple
network interfaces, no changes can be made once the Windows CE image is loaded. This
behavior is due to a limitation in the OS. Windows CE treats adapter settings with
identical Display Names as the same. When a change is made in the Network
Configuration (Control Panel) to one network interface, it affects all the others with the
same Display Name. When a static IP address is used in the Windows CE build, all
network interfaces with the same Display Name will list the same IP address. The
Registry settings will have the correct values. This limitation does not apply in a PC
development platform due to the ability to remove and re-insert a network adapter for the
changes to take effect.
__________________________________________________________________

DISCLAIMER

Information in this document is provided in connection with Intel products. No license,
express or implied, by estoppel or otherwise, to any intellectual property rights is granted
by this document. Except as provided in Intel's Terms and Conditions of Sale for such
products, Intel assumes no liability whatsoever, and Intel disclaims any express or
implied warranty, relating to sale and/or use of Intel products including liability or
warranties relating to fitness for a particular purpose, merchantability, or infringement of
any patent, copyright or other intellectual property right. Intel products are not intended
for use in medical, life saving, or life sustaining applications.

Intel assumes no responsibility for errors or omissions in this document or related
software, nor does Intel make any commitment to update the information contained
herein. The described software is supplied "as is" without warranty and may not be fully
functional.

Copyright (c) Intel Corporation, 2002. All rights reserved.
* Third-party brands and names are the property of their respective owners.