Metzen

My wish: As a plugin for Windows PE / BartPE.

I think it's something like a $500 one time fee for the oem* files on the CD you want pre-activated, so it's within the realm of mere mortals. The catch? Those files are encrypted and during Windows Setup they are decrypted and look for a string in your computers BIOS within a specified location. Both sets of information are specified within the OEM* files. If it finds the information it's looking for in your BIOS your Windows automatically activates itself. If it does not, it makes you activate via the normal method.

I've seen the same thing with GHOST, etc. Which isn't surprising since this is "imaging" through and through. GUI mode setup IS platform discriminate based on your hardware. TEXTMODE setup is platform indiscriminate. TEXTMODE setup configures some basic hardware for GUI mode setup and if you try to change (enough) hardware AFTER recording the image at the GUI mode setup stage, it may not work. Naturally, it shouldn't have any problem with imaging to similar hardware. You will still need to image at TEXTMODE setup for XP. I do not believe Vista has this limitation, however (though we will see in the coming months...)

Just to let you all know, flexy found an easier/better way to do this. You would need to adapt it for WinPE but that is easy enough to do if you know what you are doing: EDIT Link to original post. EDIT I've found this method (included in this post) to NOT work.

Thanks Bern, Your the best!

To install it (manually), you must do the following: :Installing Microsoft Update... copy /Y Microsoft-Update\muweb.inf "%windir%\Downloaded Program Files" copy /Y Microsoft-Update\muweb.dll "%windir%\system32" regsvr32 /s muweb.dll And the ActiveX control will be installed.

if you're creating that shorcut, you can also browse to muweb.dll for the proper icon to go with it. Shark <{POST_SNAPBACK}> Download the MU activex control here: http://update.microsoft.com/microsoftupdat...b?1121269785890

Maybe someone can clue me in on this... Is there a way for WPI to automatically select, say "Workstation" to install all workstation apps? Or "Graphics" for all Graphics apps? I know this is similiar to the multi-defaults (Workstation Defaults, Graphic Defaults, Server Defaults, etc.) but is it possible to do that in WPI now?

That tickles me in a way that if Loretta tickled me in that way, I'd say, 'Oh yeah...that's nice...that's the spot.

Throw me a little bone man! email to me at trentent -at- voodoopc.com If you please

Any idea on an ETA? I want this feature very badly. Thanks bernr, this is much appreciated.

I had the same thing happen in VPC with my OPK SVR2003SP1. Running it on a machine worked normally though, try yours in a regular (not virtual) machine and see if it works normally.

No love?

Me as well please. Multiple defaults is a much needed feature for me.

START > Run MSconfig > Diagnostic Startup > Apply > Close > Reboot What's the score after doing that? You might have some programs/virus's running the background eating resources.

Here's the solution I found to enabling the software-based nForce 4 NIC: 1) Software the nForce machine completely off a CD or whatever medium you choose. The nForce NIC must be working once you are finished. 2) Open regedit, and click on the SYSTEM\ControlSet001 registry key. CTRL-F for find and type the following (without the quotes) "NVNET". You should come across a key in a similar location as this example one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 3) Export the registry key to NVNET1.REG 4) Search for (without the quotes) "NVIDIA Network Bus Enumerator". You should come across a key in a similar location as this example one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_10DE&DEV_0057&SUBSYS_289510F1&REV_A3\3&1070020&0&50 5) Export the root of the key. IE, remove the part after PCI so you are exporting HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_10DE&DEV_0057&SUBSYS_289510F1&REV_A3 to NVNET2.REG 6) Search for (without the quotes) "NVIDIA Network Bus Enumerator". You should come across a key in a similar location as this example one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{1A3E09BE-1E45-494B-9174-D7385B45BBF5} 7) Export the registry key to NVNET3.REG 8) Search for (without the quotes) "nvnetbus". You should come across a key in a similar location as this example one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\nvnetbus 9) Export the registry key to NVNET4.REG 10) Go into each file and do a find and replace on the following: HKEY_LOCAL_MACHINE\SYSTEM to HKEY_LOCAL_MACHINE\PE_SYSTEM 11) Load your setupreg.hiv file on your PE system and name it PE_SYSTEM. 12) Import each registry file into your PE_SYSTEM hive. 13) Unload the hive and rebuild the system. You should have a working NIC if your files are in the correct place (use DRVINST.EXE to install the files into your PE_Config_Set). NOTE: This will be specific to your motherboard. You will need to do this to each motherboard you want to add the nForce NIC to. I have only tried it on two different motherboards on two different WinPE images so I don't know if combining more than 1 set of registry keys will work.

Here's the solution I found to enabling the software-based nForce 4 NIC: 1) Software the nForce machine completely off a CD or whatever medium you choose. The nForce NIC must be working once you are finished. 2) Open regedit, and click on the SYSTEM\ControlSet001 registry key. CTRL-F for find and type the following (without the quotes) "NVNET". You should come across a key in a similar location as this example one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 3) Export the registry key to NVNET1.REG 4) Search for (without the quotes) "NVIDIA Network Bus Enumerator". You should come across a key in a similar location as this example one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_10DE&DEV_0057&SUBSYS_289510F1&REV_A3\3&1070020&0&50 5) Export the root of the key. IE, remove the part after PCI so you are exporting HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_10DE&DEV_0057&SUBSYS_289510F1&REV_A3 to NVNET2.REG 6) Search for (without the quotes) "NVIDIA Network Bus Enumerator". You should come across a key in a similar location as this example one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{1A3E09BE-1E45-494B-9174-D7385B45BBF5} 7) Export the registry key to NVNET3.REG 8) Search for (without the quotes) "nvnetbus". You should come across a key in a similar location as this example one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\nvnetbus 9) Export the registry key to NVNET4.REG 10) Go into each file and do a find and replace on the following: HKEY_LOCAL_MACHINE\SYSTEM to HKEY_LOCAL_MACHINE\PE_SYSTEM 11) Load your setupreg.hiv file on your PE system and name it PE_SYSTEM. 12) Import each registry file into your PE_SYSTEM hive. 13) Unload the hive and rebuild the system. You should have a working NIC if your files are in the correct place (use DRVINST.EXE to install the files into your PE_Config_Set). NOTE: This will be specific to your motherboard. You will need to do this to each motherboard you want to add the nForce NIC to. I have only tried it on two different motherboards on two different WinPE images so I don't know if combining more than 1 set of registry keys will work.

no love?

Please PM it to me please or add it to a post below! There is a utility I require it for and I can't find this file for Windows 98 SE anywhere!

Using PXE-Linux, though, Window's PXE has the same problem. 2003 SP1 Nvidia...

I loose connectivity immediantly after the text-mode "hash" setup. The computer errors out with a blue-screen saying "network drivers are either incorrect or missing" or some such.

which is the typical error when the registry is corrupt in Windows. I thought of the Recovery Console but it only installs on the first partition and BOOTSECT.DAT seems to load minint from the first partition only. <{POST_SNAPBACK}> That's because the "SYSTEM" registry in WinPE is setupreg.hiv in the \winpe\system32 folder.

I believe the problem happens because the nForce NIC is done (mostly?) in software. If you software the machine by hand you'll find to enable the network driver for the nForce NIC you must first install the "NVIDIA Network Bus Enumerator" then, once WinPE loads, factory -winpe will find your ethernet drivers and install for you auto-magically. THIS WILL STILL NOT ALLOW YOU TO RIS AND ONLY WORK VIA A CD/HDD METHOD. To install the "NVIDIA Network Bus Enumerator" you must go on a machine that is fully softwared and trace the registry keys needed for "NVIDIA Network Bus Enumerator". They should only be in the SYSTEM portion of the registry, searching for "NVNETBus (IIRC)" will come up with all the keys (or nearly all the keys). If you're missing any I'll see if I can find my registry keys tomorrow that I used to get this working. Fortunately for us, it appears the "NVIDIA Network Bus Enumerator" uses the same HWID/registry keys across a broad range of hardware. I've tested it on a dual-proc iWill nForce 3 SFF system and the ASUS A8N-SLI Deluxe and the same registry keys worked to getting networking installed on both systems. Again, this will not allow RIS to operate fully, but will allow for CD-boot. With the new "in-RAM" CD-boot method MS is using for WinPE 2005, this method will allow for RIS to work (only in the sense that RIS is only used to download and launch a CD-based image from RAM first).

Edit the WinPE SYSTEM registry file (C:\winpe\i386\system32\setupreg.hiv). Edit the hive as PESYSTEM Edit HKLM\PESYSTEM\ControlSet001\Control\Session Manager\KnownDLLs and delete all entries except for "DLLDirectory" This should resolve that problem.

If you did it correctly with the unattend.txt, you need to use signed drivers.