Static IP - Unusual bug -

Hi
I have a very unusual situation.
I tried to have a static IP of 192.168.5.2 on my target ICOP Vortex86.
However I am unable to do it inspite of following most ideas suggested
atvarious google groups.

Finally This is what I did,
1. Booted target and in Network and Dial up connctions \ PCI-RTL81391,
assigned the IP 192.168.5.2 physically.
2. I tried Remote registry editing and found that
[HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TcpIp] has the following
entry

[HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TCPIP]
"DefaultGateway"=hex(7):\
30,2e,30,2e,30,2e,30,00,00,00,00
"Subnetmask"=hex(7):\
32,35,35,2e,32,35,35,2e,32,35,35,2e,30,00,00,00,00
"IpAddress"=hex(7):\
31,39,32,2e,31,36,38,2e,35,2e,32,00,00,00,00
"EnableDHCP"=dword:00000000
"AutoInterval"=dword:0000012c
"AutoMask"="255.255.0.0"
"AutoSubnet"="169.254.0.0"
"AutoIP"="169.254.131.160"
"AutoSeed"=dword:ffdee0c1
"PrevReqOptions"=hex:\
07,01,03,06,0f,2c,2e,2f
"T2"=dword:00000000
"T1"=dword:00000000
"Lease"=dword:00000000
"LeaseObtainedHigh"=dword:01c679f7
"LeaseObtainedLow"=dword:5402f200
"DhcpDefaultGateway"="0.0.0.0"
"DhcpServer"="255.255.255.255"
"DhcpSubnetMask"="255.255.0.0"
"DhcpIPAddress"="169.254.131.160"
"AutoCfg"=dword:00000001

3. I copied them verbatm in the new kernel image that I tried out. I
added the entries in project.reg file as suggested in various groups

The kernel image is built fine. However on loading it to target, there
is no static IP visible.
Also the target is not ping-able ???

Can anyone kindly suggest where I am going wrong?

-Ranjith

Piet
Wed May 17 04:22:19 CDT 2006

Please clarify. is it just a matter of adding registry settings? Or is
it a problem of IP settings? Did it work when you changed it manually?

Piet

ranjith
Wed May 17 04:58:14 CDT 2006

Hi,
When I go to Network and Dial up connctions \ PCI-RTL81391, and
assign the IP 192.168.5.2 physically, it is working fine. EVRYTHING is
fine.

However on rebooting all IP settings are lost.

-Ranjith

Paul
Wed May 17 11:18:26 CDT 2006

Those registry entries are invalid. DefaultGateway, SubnetMask, and
IpAddress should all be REG_SZ type entries, not hex.

Are you actually running a driver for the RTL8139 or are you using EBOOT and
VMini? If the latter, the IP address is set by the bootloader, not by the
Windows CE registry.

Paul T.

"ranjith" <ranjithgp@gmail.com> wrote in message
news:1147856351.271908.73290@g10g2000cwb.googlegroups.com...
> Hi
> I have a very unusual situation.
> I tried to have a static IP of 192.168.5.2 on my target ICOP Vortex86.
> However I am unable to do it inspite of following most ideas suggested
> atvarious google groups.
>
> Finally This is what I did,
> 1. Booted target and in Network and Dial up connctions \ PCI-RTL81391,
> assigned the IP 192.168.5.2 physically.
> 2. I tried Remote registry editing and found that
> [HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TcpIp] has the following
> entry
>
> [HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TCPIP]
> "DefaultGateway"=hex(7):\
> 30,2e,30,2e,30,2e,30,00,00,00,00
> "Subnetmask"=hex(7):\
> 32,35,35,2e,32,35,35,2e,32,35,35,2e,30,00,00,00,00
> "IpAddress"=hex(7):\
> 31,39,32,2e,31,36,38,2e,35,2e,32,00,00,00,00
> "EnableDHCP"=dword:00000000
> "AutoInterval"=dword:0000012c
> "AutoMask"="255.255.0.0"
> "AutoSubnet"="169.254.0.0"
> "AutoIP"="169.254.131.160"
> "AutoSeed"=dword:ffdee0c1
> "PrevReqOptions"=hex:\
> 07,01,03,06,0f,2c,2e,2f
> "T2"=dword:00000000
> "T1"=dword:00000000
> "Lease"=dword:00000000
> "LeaseObtainedHigh"=dword:01c679f7
> "LeaseObtainedLow"=dword:5402f200
> "DhcpDefaultGateway"="0.0.0.0"
> "DhcpServer"="255.255.255.255"
> "DhcpSubnetMask"="255.255.0.0"
> "DhcpIPAddress"="169.254.131.160"
> "AutoCfg"=dword:00000001
>
> 3. I copied them verbatm in the new kernel image that I tried out. I
> added the entries in project.reg file as suggested in various groups
>
> The kernel image is built fine. However on loading it to target, there
> is no static IP visible.
> Also the target is not ping-able ???
>
> Can anyone kindly suggest where I am going wrong?
>
> -Ranjith
>

ranjith
Thu May 18 04:17:48 CDT 2006

Hello,
1. I do agree that the hex entries are not the format expected...
However I ottk them using remote registry editor from the target itself
(After I manually entered the IP)

2. Also here are the entry as recommended in a documentation from the
manufacturer ICOP itself,
[HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TcpIp]
"EnableDHCP"=dword:0
"DefaultGateway"=multi_sz:"192.168.0.1"
"UseZeroBroadcast"=dword:0
"IpAddress"=multi_sz:"192.168.0.236"
"Subnetmask"=multi_sz:"255.255.128.0"
I tried these also, but when these are used, there is no display, no
keyboard no ouse and no IP on the target (when I tried to ping the
target)

Any suggestions?

Steve
Thu May 18 11:24:20 CDT 2006

Is KITL enabled when you enable the NDIS driver? Is KITL using that same
NIC? If the answer to both question is yes then that's the problem. You
can't have both. If you need app level networking when KITL is in use then
you can use VMINI/VBridge for that. You should bracket the NDIS driver
registry settings in the .REG file with:

;; Don't include the NDIS driver unless this is a non-kitl build
IF IMGNOKITL
[ NDIS registry settings go here ...]
ENDIF

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

ranjith
Fri May 19 00:41:08 CDT 2006

Hello,
I am new to Windows CE.
This is how we do it.
1. Use a cross cable to connect the target and development machine.
Development machine uses IP 192.168.5.1 and target (we wish to assign)
IP 192.168.5.2 ... PB is configured to commmunicate at port 5000.
(working fine) This is how we transfer the image to target.
2. I have not understood what needs to be done, as per your advice
above ???
"f you need app level networking when KITL ...." Can you please
clarify what change I should make for app level networking configured
on target automatically ??

Thank you

Ranjith

Silver
Fri May 19 03:03:54 CDT 2006

Background to your problem is important so you need to understand the
communication requirements of a) an OS and b) a debugger.

Steve (I think) wants you to read the section in the help about VMINI.
(BTW: I've never met Steve, but I have a really good magic 8-ball that
told me. (http://www.thepcmanwebsite.com/media/magic_8ball/))

Lookup KITL too while you are in the help pages.


The layer 1 is not the issue. If you only have one physical Ethernet
connection then CE debug services must share it with other CE services,
like your application. Applications that need to use Ethernet need to
communicate somehow, and if this is a shared interface over KITL it is
called "VMINI". (Virtual MINIport). VMINI uses KITL. If you have a
native NDIS driver trying to use the same hardware as KITL then you are
going to be in trouble.

My advice is disable KITL and use RETAILMSG to debug your
application/situation. At least figure out the question you really want
to ask.

The bootloader downloads the OS image to your device and has *nothing*
to do with the OS, hence your answer (1) below does not really mean
anything.

So - lookup VMINI and KITL in the Platform Builder help system.
- Decide what your hardware has
- Is it VMINI or separate NICs?
- Populate the registry settings correctly
- Does the problem still exist?

If it still exists;
- Describe your hardware setup
- Describe your software setup (Imagine I was explaining it to you
without you ever having seen my hardware/software)
- Attend Steve's training
course(s)(http://www.embeddedfusion.com/Training.htm)


Regards,
Silver
--

ranjith wrote:
> Hello,
> I am new to Windows CE.
> This is how we do it.
> 1. Use a cross cable to connect the target and development machine.
> Development machine uses IP 192.168.5.1 and target (we wish to assign)
> IP 192.168.5.2 ... PB is configured to commmunicate at port 5000.
> (working fine) This is how we transfer the image to target.
> 2. I have not understood what needs to be done, as per your advice
> above ???
> "f you need app level networking when KITL ...." Can you please
> clarify what change I should make for app level networking configured
> on target automatically ??
>
> Thank you
>
> Ranjith
>