[PanFriedPossum]

Hey all.

I apologise ahead of time if this question has been already addressed somewhere, but I have not been able to find it. I'm trying to create a WinPE boot CD with network support which I can use for several server models. I am using WinPE 1.2 as the base, and am confused about Winbom.ini and Startnet.cmd. The included documentation with WinPE is confusing as hell and is only making things worse. What I need to know is this: When WinPE boots up from the CD, it runs Startnet.cmd and then stops at a command prompt when Startnet.cmd is completed. The default Startnet.cmd contains the Factory -minint command which gets Factory.exe to locate the Winbom.ini file, create a computername for the Windows PE session if the name is not specified in the Winbom.ini, use Plug and Play to detect and install the network card drivers, and process the Winbom.ini file. In the Winbom.ini file documentation however, I am told to that if I run Factory.exe with any option other than -winpe then the Winpe.net section gets ignored and then the server's network connection will fail since an IP address will not get assigned.

What am I missing here?

Thanks much folks.


-PanFriedPossum

[LiquidSage]

grab a plug in called StartServices2. Shared folder are hidden though, as they are system shares ($). There are also plugins for RemotelyAnywhere & TWD-Industries RemoteAnything. You will need more than the standard winlogon to have the resources to run a server in WinPE... You should also get plugins for WSH HTA and VB support.
Get/use the The Truth's NetConfig tool to easily set comp name ,ip etc. This link should provide you with enough to work with for extras.

[PanFriedPossum]

I'm not sure that explained my problem correctly...in order for my 'client' box to connect to the network it needs to get the proper NIC driver loaded and to get an IP right?...I'm confused about what sequence of entries I need in Startnet.cmd and Winbom.ini so that I can do that...

-PanFriedPossum

[prathapml]

Please say whether you are using the actual WinPE environment from MS, or its clone (bart's PE builder).

[PanFriedPossum]

I'm using the actual WinPE 1.2 from MS.

[likuidkewl]

So what exactly are you looking to do? Is this just a question or is this an actual problem that you need to add your nic drivers to your winbom.ini? Because WinPE loads alot of drivers at the start. Have you booted your client with a custom CD? If so what is the outcome?

[LiquidSage]

im pretty sure ms winpe uses DHCP by default. Do you need a static ip? Is your nic being detected? or both?

maybe this will help...from a saved commentary....

Quote

Host Guest_BillL_MS:
Q: When trying to assign a fixed ip with netsh I fail because the network interface has a GUID instead of a name….

Host Guest_BillL_MS:
A: There should be a white paper on this coming out soon, if not already. Basically, To specify static IP addresses for runtimes three things must be done. First, components need to be added to the runtime to support TCP/IP networking and the netsh utility. Second, a script must be created that will use the netsh utility to set the address. Third, a component must be created to add an entry to the Registry’s Runonce key that will call the script. The components required for netsh are the following: CMD - Windows Command Processor, Network Command Shell, Network Command Shell Interface Context, IP Router Monitor Library

[LiquidSage]

Quote

Host Guest_BillL_MS:
Q: dibbe : Bill - But in the netsh script do you still have to specifiy GUID?...

Host Guest_BillL_MS:
A: You will need to create a component that RunOnce, and set a reg key that will call the script. See if this shed some light for the third step… Start Component Designer, and Add Component. Give the component a Name. Select Registry Data. Right click and select Add, Registry Data. Set Key Name to: System\FBA\RunOnce, Set Type to REG_SZ (this means the key value will be a string). Set Value Name to some name of your choosing such as static_ip. Set Value to the path and file name of the script that you want to run. Use the %% syntax to define system folders when specifying the path. For example: %11%\set_static_ip.cmd designates a file named set_static_ip.cmd in the System32 folder.


A: When you are done, import the component into database, and add that to your configuration. After building your runtime image you will need to copy the script file to the folder you designated in the Runonce key. Create the necessary script and then copy it using Windows Explorer. An example:

netsh interface ip set address name="Local Area Connection" source=static addr=192.168.1.10 255.255.255.0 192.168.1.1 1

netsh interface ip set dns name="Local Area Connection" static 192.168.1.2 primary

netsh interface ip add dns name="Local Area Connection" 192.168.1.3 index=2

netsh interface ip add dns name="Local Area Connection" 192.168.1.4 index=3

…etc.

Note that if you are using a language other than English you will need to change “Local Area Connection” to the appropriate connection name.

[PanFriedPossum]

Thanks all for the replies. Clarification of the actual problem is that I am confused about the syntax of winbom.ini and startnet.cmd. I need to run factory with the -minint option in startnet.cmd in order to process winbom.ini where my NIC drivers will be specified. That I get. What I don't get is the fact that according to the documentation, if I run factory.exe with any option other than -winpe, then the winpe.net subsection of winbom.ini gets completely ignored and therefore my NIC never gets an IP becaule I never get to tell winbom.ini that the client machine's NIC is on DHCP.

Am I missing something really obvious here??

[likuidkewl]

PanFriedPossum, on Jan 30 2004, 09:22 PM, said:

Thanks all for the replies.  Clarification of the actual problem is that I am confused about the syntax of winbom.ini and startnet.cmd.  I need to run factory with the -minint option in startnet.cmd in order to process winbom.ini where my NIC drivers will be specified.  That I get.  What I don't get is the fact that according to the documentation, if I run factory.exe with any option other than -winpe, then the winpe.net subsection of winbom.ini gets completely ignored and therefore my NIC never gets an IP becaule I never get to tell winbom.ini that the client machine's NIC is on DHCP.

Am I missing something really obvious here??

Have you gone to the MS OEM website and looked through the news groups for Xp or what ever *preinstallation you are trying to accomplish? I find tons of information there.

[likuidkewl]

Please see http://oem.microsoft.com/worldwide/512502.asp. However, in step 2 (step 4 in the example), place the INF for the Network Interface Card in the C:\Winpe.tmp\i386\INF directory and the driver file(s) in the C:\Winpe.tmp\i386\System32\Drivers directory.

From the OPK cd trouble shooting.

[PanFriedPossum]

Hey all.

Thanks to those who gave their suggestions. I gave up on using the MS WinPE and switched to Bart's excellent piece of work...everything's cool now. WAAAAYYY easier to use...Kudos to the man!