ipconfig

  • Thread starter Thread starter Larry Waibel
  • Start date Start date
L

Larry Waibel

I've been working through "Windows XP Embedded Step by Step" by James Beau
Cseri and am at the exercises to setup a telnet server, etc. I'm trying to
access the target from a computer that's on the domain and telnet doesn't
connect. So I wanted to get the IP address of the target and tried running
'ipconfig /all' on it. All it does is print out a program header but doesn't
report anything about the IP address, etc. Any ideas what else I need to do?
What other information does anyone need in order to be able to help me?
Thanks!
 
I know I'm replying to myself but I discovered additional details that I hope
will help someone help me :-) I'm doing this on my Dell Latitude D800 notebook
which has a Broadcom 570x Gigabit Integrated Controller for a network adapter
and the 'tap' didn't install it. It's not in the components list in TD. How do
I install this device? Thanks!
 
Hi Larry,

You will either need to make your component from driver package that support your hardware and add it to your image.
Or you can add any network driver component just to bring you other dependencies that you will need.
And then you can manually copy driver files to their folders (windows\inf, windows\system32, wndows\system32\drivers) depending on
file extensions.

Following thread is a little advanced but it will allow you to support range of different hardware by one image and by simple driver
components that you will create.
Read trough all posts it might help you on the longer run:
http://groups-beta.google.com/group...6794b5ed5ff/a6b590cb38cbd984#a6b590cb38cbd984

Regards,
Slobodan
 
I'm new to all this so I assumed I could import the .inf and end up with a component
..sld. I tried that but got an essentially empty .sld. I tried using the 'econvert'
and here's what I get:

EConvert Version 2.00.0807.0.

Converting c:\drivers\network\onboard\b57xp32.inf started at 01/25/2005 11:17.
Info:INF Importer is creating look up tables. This will take a few minutes. Plea
se wait...
Info:More than one component has the same Concordance ID [NORTEL NETWORKS E-MOBI
LITY 802.11B WIRELESS LAN PCI CARD:PCI\VEN_126C&DEV_1F1F].
Info:More than one component has the same Concordance ID [SYMBOL LA-41X3 SPECTRU
M24 WIRELESS LAN PCI CARD:PCI\VEN_1562&DEV_0001].
Info:More than one component has the same Concordance ID [ERICSSON DSSS WIRELESS
LAN PCI CARD:PCI\VEN_5401&DEV_0101].
Info:More than one component has the same Concordance ID [3COM 3CRWE737A AIRCONN
ECT WIRELESS LAN PC CARD:PCMCIA\3COM-3CRWE737A_AIRCONNECT_WIRELESS_LAN_PC_CARD-3
0DD].
Info:More than one component has the same Concordance ID [INTEL(R) PRO/WIRELESS
2011 LAN PCI CARD:PCI\VEN_8086&DEV_1042].
Info:More than one component has the same Concordance ID [NORTEL NETWORKS E-MOBI
LITY 802.11B WIRELESS LAN PC CARD:PCMCIA\NORTEL_NETWORKS-EMOBILITY_802.11_WIRELE
SS_LAN_PC_CARD-A907].
Info:More than one component has the same Concordance ID [INTEL(R) PRO/WIRELESS
2011 LAN PC CARD:PCMCIA\INTEL-PRO/WIRELESS_2011_LAN_PC_CARD-E11D].
Info:More than one component has the same Concordance ID [SYMBOL LA-41X1 SPECTRU
M24 WIRELESS LAN PC CARD:PCMCIA\SYMBOL_TECHNOLOGIES-LA4111_SPECTRUM24_WIRELESS_L
AN_PC_CARD-077D].
Info:More than one component has the same Concordance ID [3COM 3CRWE777A AIRCONN
ECT WIRELESS LAN PCI CARD:PCI\VEN_10B7&DEV_1F1F].
Info:More than one component has the same Concordance ID [ERICSSON DSSS WIRELESS
LAN PC CARD:PCMCIA\ERICSSON-ERICSSON_DSSS_WIRELESS_LAN_PC_CARD-F68B].
Info:c:\drivers\network\onboard\b57xp32.inf: type PNP device INF
Warning:c:\drivers\network\onboard\b57xp32.inf: [Broadcom] is missing.
Conversion succeeded, elapsed time 0119 seconds.
Output file saved as: b57xp32.inf.sld.


From: "Slobodan Brcin \(eMVP\)" <[email protected]>
Subject: Re: ipconfig
Date: Tue, 25 Jan 2005 18:54:38 +0100
Newsgroups: microsoft.public.windowsxp.embedded

Hi Larry,

You will either need to make your component from driver package that support your
Click to expand...
hardware and add it to your image.
 
I guess I should have mentioned that the .sld is still essentially empty so I still
don't have a driver for the Broadcom network card and can't figure out how to go about
getting one.
 
Larry Waibel пишет:
I guess I should have mentioned that the .sld is still essentially empty so I still
don't have a driver for the Broadcom network card and can't figure out how to go about
getting one.
Click to expand...
I guess you have some problems with your .inf file. When I tried to
follow the same route with the Intel PRO/100 card, I hoped to just
import .inf in component designer but never succeed. By searchng this NG
on the keyword PRO/100 I have found that I am not alone :)
The manufacturer section in it was not just [Intel], but [Intel.x86] or
something like this.
So I used custom import with the right manufacturer name and voila - it
worked :)
You can do it this way, or listen to what Slobodan says - just put some
generic network driver in your .sld to bring up the dependencies, and
after compilation copy your .inf, .sys, .dll etc file in appropriate
directories.

Igor

P.S.
Search rules! :)
 
On my system there are a .cat, .inf, .pnf, and .sys files for the driver all in (and only
in) \drivers\network\onboard. Do I put them all in the same place on the target and are
you suggesting I manually copy them after I've copied the XPe image files? Could I
create a component that depends on the 'any network driver component' that I choose and
then somehow (repository?) cause them to be copied as part of the build image?

Or you can add any network driver component just to bring you other dependencies that you will need.
And then you can manually copy driver files to their folders (windows\inf,
Click to expand...
windows\system32, wndows\system32\drivers) depending on
 
Not sure what 'custom import with the right manufacturer name' means? How
would I do that with my .inf?
 
Larry,

When you open CD INF Import, switch off from Automatic import to Custom.

(I don't think the Custom Import option is available for econvert.exe)
 
Larry,

You copy:
INF file to \windows\inf folder
PNF file to \windows\inf folder (but you don't really need this file)
CAT file to \windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} folder (you may need this file only if you wan
to have the driver signed)
SYS file to \windows\system32\drivers

Yes, you will have to create a Repository and associate your component with it. When you add files to you component make sure that
go to the directories mentioned above on the target (although, use symbolic variable names %%).
 
Larry,

PNF file actualy should not be used since it will be created by PnP during the driver installation.
Do I put them all in the same place on the target and are you suggesting
I manually copy them after I've copied the XPe image files?
Click to expand...
Yes but only for test purposes to see that it is working.
Could I create a component that depends on the 'any network driver component' that
Click to expand...
Of course you can. But you should not depend on other drivers, you should create component that inherit same device class as it
would be created by CD if you used it to import inf file.

Most likely you will need to make dependency to component "Ndis"
And to use prototype component "Device: Net"

Regards,
Slobodan
 
Thanks, I found that. But it assumes I know a lot more about .inf files than
I do :-) No idea what to do in the Add for section names, etc. Can't find
much information about these parsing options in the online help or books that
I have.
 
Thanks! If I can't figure out how to get the .inf import to work, this is what I'd need
to know to get the files in the right places.

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: ipconfig
Date: Wed, 26 Jan 2005 12:22:33 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

You copy:
INF file to \windows\inf folder
PNF file to \windows\inf folder (but you don't really need this file)
CAT file to \windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
Click to expand...
folder (you may need this file only if you wan
to have the driver signed)
SYS file to \windows\system32\drivers

Yes, you will have to create a Repository and associate your component with it. When you
Click to expand...
add files to you component make sure that
 
How do I 'use a prototype component'?

From: "Slobodan Brcin \(eMVP\)" <[email protected]>
Subject: Re: ipconfig
Date: Wed, 26 Jan 2005 21:42:17 +0100
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

PNF file actualy should not be used since it will be created by PnP during the driver installation.

Yes but only for test purposes to see that it is working.

Of course you can. But you should not depend on other drivers, you should create component that inherit same device class as it
would be created by CD if you used it to import inf file.

Most likely you will need to make dependency to component "Ndis"
And to use prototype component "Device: Net"

Regards,
Slobodan
Click to expand...
 
Larry,
How do I 'use a prototype component'?
Click to expand...

You have few ways:
1. Add it as you would any other component in TD.
2. From CD select your component and you will see option named "Prototype:" you have browse button beside that you can use to search
and pick for prototype that you want to use.
3. Or in CD you can add it in "Component or Group Dependency".

All these will give same result, with slight differences regarding new SP2 generic components (if you use them).

Regards,
Slobodan
 
THANKS! I got enough from there to glean what I needed for the custom Manufacturer
section and was then able to get the imported .inf to create a valid .sld, setup the
repository for it, add the component, and get the network working! Couldn't have done it
without you :-) However, I really do think there's a bug in the CDM import handling of
.inf files. The .inf has (... indicates lines I didn't show because I don't think
they're relevant) the entries below. I was only able to import by specifying a custom
Manufacturer of 'Broadcom.NTx86.5.1'. Otherwise, it always reported that it couldn't
find 'Broadcom'.

[Manufacturer]
%BRCM% = Broadcom, NTx86.5.1
...
[Broadcom.NTx86.5.1]
...
[Strings]
BRCM = "Broadcom"
...

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: ipconfig
Date: Wed, 26 Jan 2005 16:56:32 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

This should help you get going:
http://msdn.microsoft.com/library/en-us/install/hh/install/create-inf_f88cf176-2886-45a4-
b93a-a12a572ebb16.xml.asp
Click to expand...
 
Larry,

For some reasons the XPe INF importer is not as smart as the PnP INF parser.
There are some known (and probably yet unknown) issues with it including the one you outlined below.

Well.. all we can do for now is to file a bug to Microsoft:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx

--
Regards,
KM, BSquare Corp.

THANKS! I got enough from there to glean what I needed for the custom Manufacturer
section and was then able to get the imported .inf to create a valid .sld, setup the
repository for it, add the component, and get the network working! Couldn't have done it
without you :-) However, I really do think there's a bug in the CDM import handling of
inf files. The .inf has (... indicates lines I didn't show because I don't think
they're relevant) the entries below. I was only able to import by specifying a custom
Manufacturer of 'Broadcom.NTx86.5.1'. Otherwise, it always reported that it couldn't
find 'Broadcom'.

[Manufacturer]
%BRCM% = Broadcom, NTx86.5.1
...
[Broadcom.NTx86.5.1]
...
[Strings]
BRCM = "Broadcom"
...
Click to expand...
 
Back
Top