Quote
-Is there a way to enable file sharing in pe?
-Is there a way to change your pc name?
-Is there a way to change your pc name?
By default in winpe, you can access network resources and you have a computer name, but other computers cannot access your resources. The fix is relatively simple.
In win2k and XP (and higher), the network stuff is installed during setup by netcfgx.dll i believe. For the XP and server 2003 OPK MS included a tool called NETCFG.EXE. This tool let's you do what the dll already did, this time with interaction.
To use netcfg just search google or type netcfg /?
Quote
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
E:\Documents and Settings\Administrator>F:\WXOPK_EN\TOOLS\X86\NETCFG.EXE /?
netcfg [-v] [-winpe] [-l <full-path-to-component-INF>] -c <p|s|c> -i <comp-id>
where,
-winpe installs tcpip, netbios and msclient for windows preinstall envrionmen
t
-l provides the location of INF
-c provides the class of the component to be installed
p == Protocol, s == Service, c == Client
-i provides the component ID
The arguments must be passed in the order shown.
Examples:
netcfg -l c:\oemdir\foo.inf -c p -i foo
...installs protocol 'foo' using c:\oemdir\foo.inf
netcfg -c s -i MS_Server
...installs service 'MS_Server'
OR
netcfg [-v] -winpe
Examples:
netcfg -v -winpe
...Installs tcpip, netbios and msclient for windows preinstall environment
OR
netcfg [-v] -q <comp-id>
Example:
netcfg -q MS_IPX
...displays if component 'MS_IPX' is installed
OR
netcfg [-v] -u <comp-id>
Example:
netcfg -u MS_IPX
...uninstalls component 'MS_IPX'
OR
netcfg [-v] -s <a|n>
where,
-s provides the type of components to show
a == adapters, n == net components
Examples:
netcfg -s n
...shows all installed net components
OR
netcfg [-v] -b <comp-id>
Examples:
netcfg -b ms_tcpip
...shows binding paths containing 'ms_tcpip'
General Notes:
-v turns on the verbose mode
-? Displays this help
E:\Documents and Settings\Administrator>
© Copyright 1985-2001 Microsoft Corp.
E:\Documents and Settings\Administrator>F:\WXOPK_EN\TOOLS\X86\NETCFG.EXE /?
netcfg [-v] [-winpe] [-l <full-path-to-component-INF>] -c <p|s|c> -i <comp-id>
where,
-winpe installs tcpip, netbios and msclient for windows preinstall envrionmen
t
-l provides the location of INF
-c provides the class of the component to be installed
p == Protocol, s == Service, c == Client
-i provides the component ID
The arguments must be passed in the order shown.
Examples:
netcfg -l c:\oemdir\foo.inf -c p -i foo
...installs protocol 'foo' using c:\oemdir\foo.inf
netcfg -c s -i MS_Server
...installs service 'MS_Server'
OR
netcfg [-v] -winpe
Examples:
netcfg -v -winpe
...Installs tcpip, netbios and msclient for windows preinstall environment
OR
netcfg [-v] -q <comp-id>
Example:
netcfg -q MS_IPX
...displays if component 'MS_IPX' is installed
OR
netcfg [-v] -u <comp-id>
Example:
netcfg -u MS_IPX
...uninstalls component 'MS_IPX'
OR
netcfg [-v] -s <a|n>
where,
-s provides the type of components to show
a == adapters, n == net components
Examples:
netcfg -s n
...shows all installed net components
OR
netcfg [-v] -b <comp-id>
Examples:
netcfg -b ms_tcpip
...shows binding paths containing 'ms_tcpip'
General Notes:
-v turns on the verbose mode
-? Displays this help
E:\Documents and Settings\Administrator>
For question #2:
WinPE and longhorn sets the initial computer name in setupreg.hiv. You can load this hive in regedit to change the computername, make sure you unload the hive when done!
Just go to this key in regedit with the hive loaded:
????\ControlSet001\Control\ComputerName\ComputerName
On the right hand site you'll see the default, change it to what you want the computer name to be.
Another cool thing you can do in setupreg.hiv is change the OS Type to server 2003. If you do this, when you boot winpe you'll see the server 2003 or "whistler advanced server" boot screen. Other than that i don't think it has any benefits.
Just go to ????\ControlSet001\Control\ProductOptions, on the right hand side change WinNT to what you want.
I think i had to change that in winpe or something because windows protected it.
-gosh



Help
Back to top









