74 replies to this topic

[MedEvil]

Just to inform that network script of NIKZZZZ (member of forum.ru-board.com) worked for me perfectly!

Yes, net.script from NIKZZZZ works, but it cheats!
The needed inf files are not created, but included.

[Oleg_II]

Yes, net.script from NIKZZZZ works, but it cheats!
The needed inf files are not created, but included.

Sorry, don't get you My network works, I can browse the Web and I don't care if needed INFs are created or included

PS Just tried network in my hotel where I had to enter IP, gateway and DNS - works!

[pscEx]

... and I don't care if needed INFs are created or included

Maybe Jaclaz can tell more about that.
But I think it is not legal to distribute 'part of software', in this case *.inf files.
Therefore such a script cannot be inside the official WinBuilder delivery.

Peter

[Oleg_II]

Well, I can agree that distributing not free software or its parts is bad. But INF files are just regestry settings in INF files format written in TXT files. You will have to write this regestry settings anyway if you want it working.

And it is not a bad idea to extract all these files from the script in a separate folder - if somebody wants this script working (and it works! he/she will need to provide these files (download from net or take from owned software).

[Holger]

Would be good if anybody would read the 1st page of this topic completely.
However, I respect the work of Bart...
The only complete way would to use WinPE2.0 from WAIK cause it comes with "netcfg", etc.
Wondering what "net.script" uses to detect devices and install network components...

However, I will do it my way - licensefree
...

[Oleg_II]

Holger
Waiting for your solution

But anyway: in order to use WinBuilder to work someone needs to provide XP or W2k3 CD. Look in Download section - there are quite a few scripts for commercial software too. Why couldn't someone who wants networking provide a few files that are downloadable from net for free?

It would be greate if somebody creates free alternatives just for WinBuilder. But untill then...

[MedEvil]

Well the main problem besides legal issues, is of course the language thing.
The net.script from NIKZZZZ is from a russian build, i guess. It should work on all machines, but most will see just a lot of garbage in their services.msc

I think we should at least 'upgrade' to english, so that more people can read the entries.

[Oleg_II]

I use English source. I didn't find much Russian in his script except the title.

[MedEvil]

I use English source. I didn't find much Russian in his script except the title.

Start services.msc and admire the rows of questionmarks!

[Oleg_II]

MedEvil

Start services.msc and admire the rows of questionmarks!

Very strange I can't find this file neither in my build nor in running PE... Are you sure you saw these rows of questionmarks after running this script? I noticed only one during WinBuilder runs - it's a title for the script. Maybe you confusing with some other script (there are a few Russians placing scripts on this board

[thunn]

Medevil was referring to the MMC services snapin file, the Russian descriptions are from the 3 inf files embedded in the script, I believe you can put Eng BartPE .infs...
I've just read this thread which includes some usefull info on enabling basic networking on XPE or PE. I've barrowed data from both current net scripts, thx. to Alexei and HighwayStar for there fine efforts.

[Oleg_II]

You were right. I found netmscli.inf and nettcpip.inf files have lines in Russian.

I still don't care because I'm not going to read description of services. But in order everything is perfect it would be great to make it readable

[Oleg_II]

Just a small suggestion:)

If somebody can provide me with English versions of these files (netmscli.inf and nettcpip.inf) and if they even exist of cause:

1. I can compare two files and look for different settings that make it working.

2. I can just copy-past English strings instead Russian ones and see if it works this way.

[Oleg_II]

OK. That was very stupid of me The files are from original XP source.

I compared the content and found quite a few differences except those lines in Russian. Maybe it's the reason the files are not taken from the source but were included into the script?

Unfortunatelly I can't test it right now cause the hotel I'm living tonight doesn't have LAN connection.

[thunn]

The infs can come from a localized BartPE...
I've spent quite a bit of time sorting all this out as I would like for this community to have a reliable networking script. I invite you to provide some feeback on a script which is working well in my tests. DL here

tests used livexp on m$ VPC
Please test with bartpe and startnet by Holger, I use factory and netcfg from the Srv2k3 Opk and all works very well. More details later, enjoy!

[Oleg_II]

thunn
Good work

I compared the files again - they differ only in strings Russian-English but the rest is the same. Should work.

From the first look, you add a bit more files and regestry settings then NIKZZZZ.
Maybe I'm wrong but in your script networking auto-starts? He makes it for user to choose when to start networking.
NIKZZZZ doesn't use FACTORY.EXE - would it be usefull for PPPoE and Dial-Up connections?

[thunn]

thunn
From the first look, you add a bit more files and regestry settings then NIKZZZZ.

As a matter a fact (and I hope you're reading the correct script) My script contains no registry entries at all. They're not required as the .infs update the registry with the correct information at runtime. Lets have a look at a section of NETTCPIP.INF...

; Install Tcpip service

[Install.AddService.TCPIP]

	DisplayName	 = %MS_TCPIP.TCPIP.ServiceDescription%

	ServiceType	 = 1;SERVICE_KERNEL_DRIVER

	StartType	   = 1;SERVICE_SYSTEM_START

	ErrorControl	= 1;SERVICE_ERROR_NORMAL

	ServiceBinary   = %12%\tcpip.sys

	Dependencies	= IPSec

	LoadOrderGroup  = PNP_TDI

	AddReg		  =Registry.Service.TCPIP

	Description	 = %MS_TCPIP.TCPIP.ServiceDescription%

..

[Registry.Service.TCPIP]

	HKR,Parameters\Winsock,"UseDelayedAcceptance",%FLG_ADDREG_TYPE_DWORD%,0x0000

	HKLM,"System\CurrentControlSet\Control\ServiceProvider\Order","ExcludedProviders",%FLG_ADDREG_SZ_NO_CLOBBER%,""

	HKLM,"System\CurrentControlSet\Control\ServiceProvider\Order","ProviderOrder",%FLG_ADDREG_MULTI_SZ_APPEND%,"Tcpip"



	HKR,Performance,Close,,"CloseTcpIpPerformanceData"

	HKR,Performance,Collect,,"CollectTcpIpPerformanceData"

	HKR,Performance,Library,,"Perfctrs.dll"

	HKR,Performance,Open,,"OpenTcpIpPerformanceData"



	HKR,ServiceProvider,Class,%FLG_ADDREG_TYPE_DWORD%,8

	HKR,ServiceProvider,DnsPriority,%FLG_ADDREG_TYPE_DWORD%,2000

	HKR,ServiceProvider,HostsPriority,%FLG_ADDREG_TYPE_DWORD%,500

	HKR,ServiceProvider,LocalPriority,%FLG_ADDREG_TYPE_DWORD%,499

	HKR,ServiceProvider,ProviderPath,%FLG_ADDREG_TYPE_EXPAND_SZ%,"%%SystemRoot%%\System32\wsock32.dll"

	HKR,ServiceProvider,NetbtPriority,%FLG_ADDREG_TYPE_DWORD%,2001

	HKR,ServiceProvider,Name,,"TCP/IP"



	HKR,Parameters,DataBasePath,%FLG_ADDREG_TYPE_EXPAND_SZ%,"%%SystemRoot%%\System32\drivers\etc"

	HKR,Parameters,NameServer,%FLG_ADDREG_SZ_NO_CLOBBER%,""

	HKR,Parameters,ForwardBroadcasts,%FLG_ADDREG_DWORD_NO_CLOBBER%,0

	HKR,Parameters,IPEnableRouter,%FLG_ADDREG_TYPE_DWORD%,0



	HKR,Parameters\Winsock,"UseDelayedAcceptance",%FLG_ADDREG_TYPE_DWORD%,0x0000

While the other scripts provide required files and may work (esspecially if run together) the registry entries are not all needed. Some hardware may require a few entries...If so, I'll be testing and updating. Works well with Realtek NIC and VPC though.

Windows Embedded installs everything for networking including reg entries in advance to the XPE runtime image. I know there've been ideas here about trying to do that, but PE is not an Embedded OS. It's a good idea though.

And about starup...
In the download is the Core script plus a sepparate startup script. You may use them as you like. The core contains no autostart, only registers a few .dlls. Like I said, be my guest and try the core with other startup options. Please try all features of networking, I was very carefull about the file sellection, no issues yet.

[Oleg_II]

thunn
I'll have a closer look at the scripts tonight. And I've got a good connection also today so I'll try to test your scripts.

About Embedded - interesting info. I'd like to have PPPoE and Dial-Up connections too (need to enter user names and passwords).

[TheHive]

The infs can come from a localized BartPE...
I've spent quite a bit of time sorting all this out as I would like for this community to have a reliable networking script. I invite you to provide some feeback on a script which is working well in my tests. DL here

Please test with bartpe and startnet by Holger, I use factory and netcfg from the Srv2k3 Opk and all works very well. More details later, enjoy!

I was testing the two scripts within the zip.
Selected a working BartPE. At this point you could link to where they can find BartPE.

I received this error when booting in NativeEx


The next screen said it didnt recognize the network card. This should be expected since we dont have a Qemu Network Card Driver working. Ill try it in Vmware since I put the Network Drivers for that card.


Same errors using VMware.
In LiveXP I get errors in the log about not being able to copy some files.
 Log.zip   58.78KB   233 downloads

[thunn]

-NativeEX is an even smaller subset of files than LiveXP...I'll add the one file, no problem.

-You must add the VMware net drivers...did you?

-Thx for the log...one line needed fixing, but it won't break the script.

-I tested and received no errors...will test again. and post revision.

[TheHive]

-NativeEX is an even smaller subset of files than LiveXP...I'll add the one file, no problem.

Its faster to build. Its more stable at the moment. I borrowed the Vmware drivers from LiveXP when testing to use the Network Card of Vmware on nativeEx

-You must add the VMware net drivers...did you?

Yes!

-I tested and received no errors...will test again. and post revision.

Once its working can you revise it to where it can be disabled by default and let the script have the ability to let the user add a shortcut to Penetconfig in the Desktop, Quicklaunch, or StartMenu.

[thunn]

I assume you mean autostart...

Either don't use my penetcfg script OR:

open startnet.ini and edit this-

[General]
AutoStartNet = Yes

btw...
It works fine. Run a test in VPC.
Can you verify that the VMware drivers work fine? (try using HwPnP.exe)

also
I may not use PEnetcfg for the 'final' release for licensing reasons, so have fun with this one.

I'm going to PM you an alternate version for a test in VMware.

[TheHive]

I assume you mean autostart...

Either don't use my penetcfg script OR:

open startnet.ini and edit this-

[General]
AutoStartNet = Yes

btw...
It works fine. Run a test in VPC.
Can you verify that the VMware drivers work fine? (try using HwPnP.exe)

also
I may not use PEnetcfg for the 'final' release for licensing reasons, so have fun with this one.

I'm going to PM you an alternate version for a test in VMware.

Holget just released his script PENetwork-PreBeta. It works with the Vmware Script Network Drivers. Right out the box. Tested on nativeEx Project using Winbuilder53 beta 14.
http://www.boot-land...?...

[thunn]

Holget's script looks very nice. It will be fun to test.
The .inf patching is an actractive feature...

If I understand correctly (from PM) the script worked...it was the lack of RAM/virt mem that caused programs not to run and net not to start. For normal testing I use 512MB on my VMs. 256...not always enough. But, cutting RAM is a test in itself. So...nevermind.
With a free solution in development I'll just use this script for the Opk net tools from MS. I believe certain NICs require registry entries to be present, others don't. attached has registry entries some of which can be removed.

--edit--
*this script was a fast patchjob to get me up and running, I'm posting a more comprehensive well researched update under Development.

Attached Files

•  NetworkCore_regd_B.script   46.28KB   297 downloads

[paraglider]

Note snetcfg was replaced by bindview in w2003 / Vista DDKs. Thats why you can't find the source any more.