Re: NIC fails in RELEASE build CE 5.0

And you did remove VMINI in the release build, right? The Ethernet
controller can't serve two masters, so, if your OAL code is trying to
operate it for VMINI/KITL and you also are trying to run the right driver on
top of it, it won't work.

Paul T.

"AllanL" <allan AT ByteWiseSG D0T com> wrote in message
news:%23HSF3nnnHHA.3512@xxxxxxxxxxxxxxxxxxxxxxx
I have a CEPC-GEODE PC/104 board with an NE2000 ISA NIC. When I use the
VMINI driver in a debug build it works fine. In the release build, DHCP
fails. Searching, it seems that similar problems are form not removing the
vmini driver and KITL formthe build. I have done this--at least I think I
have.

Static IP also doesn't work--the board won't respond to a ping.

Here is what I have done in the build:

IMGNOKITL=1 (UN-check box - Build Options)
KERNELNOSHAREETH=1
BSP_NOSHAREETH=1
BSP_NIC_NE2000_ISA=1

I also have:

BSP_NOPCIBUS=1
BSP_NOPCMCIA=1 (These are also in the debug build)


In the DEBUG Build, none of these are set.
In the registry, I hav left the default settings, with the exception of
setting port (0x2c0) and IRQ (5) as follows:
[HKEY_LOCAL_MACHINE\Comm\NE2000]
"DisplayName"=LOC_DISPLAYNAME_COMM_NE2000
"Group"="NDIS"
"ImagePath"="ne2000.dll"

[HKEY_LOCAL_MACHINE\Comm\NE2000\Linkage]
"Route"=multi_sz:"NE20001"

[HKEY_LOCAL_MACHINE\Comm\NE20001]
"DisplayName"=LOC_DISPLAYNAME_COMM_NE20001
"Group"="NDIS"
"ImagePath"="ne2000.dll"

[HKEY_LOCAL_MACHINE\Comm\NE20001\Parms]
"BusNumber"=dword:0
"BusType"=dword:1
"InterruptNumber"=dword:05
"IoBaseAddress"=dword:2C0
"Transceiver"=dword:3
"CardType"=dword:0

[HKEY_LOCAL_MACHINE\Comm\NE20001\Parms\TcpIp]
"EnableDHCP"=dword:1
"DefaultGateway"=""
"UseZeroBroadcast"=dword:0
"IpAddress"="0.0.0.0"
"Subnetmask"="0.0.0.0"

The CE board sends a "DHCP Discover message", and it gets an Offer message
from the DHCP server, but the message is ignored--I never see a DHCP
Request--instead it sends several more "DHCP Discover" messages.

I enabled serialDebug, but kept :
KERNELNOSHAREETH=1
BSP_NOSHAREETH=1
I get debug message through the serial port and I can see that the NIC is
initialized and DHCP loads and tries to DHCP, but never sees the replys
from the DHCP server (They are sent)

It looks like the board cannot receive any data.

I am really stuck on this one!

thx



.

Relevant Pages

  • Re: NIC fails in RELEASE build CE 5.0
    ... VMINI driver in a debug build it works fine. ... IMGNOKITL=1 (UN-check box - Build Options) ... The CE board sends a "DHCP Discover message", ...
    (microsoft.public.windowsce.platbuilder)
  • Re: DHCP differences between VMini and NDIS
    ... We're seeing some differences between DHCP operation on our some ... VMini mode but not when running NDIS. ... is loaded like a regular network driver but it did no hardware ... (l'indirizzo di reply di questo messaggio non è ...
    (microsoft.public.windowsce.platbuilder)
  • Re: NIC fails in RELEASE build CE 5.0
    ... There's a "how to use vmini" document in the VMINI directory. ... that you don't have the VMINI entries in the registry. ... VMINI driver in a debug build it works fine. ... The CE board sends a "DHCP Discover message", ...
    (microsoft.public.windowsce.platbuilder)
  • DHCP_REQUEST_WLAN
    ... Does anyone know why DHCP is using DHCP_REQUEST_WLAN with my miniport? ... VMINI, but the process for getting an address via DHCP seems to be ... driver is different from VMINI, considering I've matched as closely as ...
    (microsoft.public.windowsce.platbuilder)
  • Re: 1720 and comcast
    ... logging buffer 10000 debug ... Verify that the "outside" interface connected to the cable modem is ... Enable DHCP debugging ...
    (comp.dcom.sys.cisco)