Eagle710

I am trying to boot a 330MB WIM file on an HP Elitebook. It seems that when I boot this WIM file on any other laptop it works. Is there anything that could be preventing this WIM from loading from within BIOS?

The command doesnt work. It simply gives me a long list of all the options to use with the command. Is it because I placed the Dlls in the same folder as the exe?

I tried again and it didin't work. When I run winvnc4.exe -status it gives me the error message that the service doesn't exist.

everwicked, I am trying to get your instructions to work in WinPE 2.0. I will try again and let you know how it goes. How does the display quality come across the Remote and should I set a static IP?

I followed those instructions...... are those correct or am I missing something? Regedits perhaps?

I tried following everwicked's instructions but it wont work for me. I tried winvnc4 -start but a message about a the service not installed/exist came up. Am i missing something? I copied the Winvnc4.exe and the 3 other files to the same folder. This was not the System32 folder as indiciated above. Would this cause an issue? I am receiving a IP address via DHCP. Any ideas?

MrJinje, Perfect, that registry key managed to do the trick and everything worked great. Thanks, Eagle

Does anyone know how to edit the command line PATH variable to include commands with just by calling the .exe from anywhere in the directory structure? This is of course in WinPE 2?

So I have not determined what cause the driver to kick in after I unplug the USB key. However, I have found this little MS tool called Devcon.exe which is similar to Device Manager but using command line. I simply added the following command line into my winpeshl.ini to run at start and this allowed for the driver to activate. Devcon.exe, /rescan

After having injected the driver into the offline WinPE image and checking which drivers are running on the system using DriverView it seems as though the driver is not running. Only when I remove the USB key does the driver appear as installed/activiated in WinPE. Any ideas?

I actually tried this: If the name of the driver is net4.inf should i change the oem*.inf ? This didn't work when I tried to use it both within the startnet.cmd and just running via command line it still requires me to remove the USB key in order for the PCI device to obtain an device ID.

It seems like when I remove the USB the drvinst.exe process runs and once completed the driver is enabled and setup.... any ideas? Once removed the driver actually takes effect on the system.

I use BSExplorer for the start menu, taskbar but use XEPortable which is really handy and has a great file extension association feature.

Noise, I have injected the drivers on the offline WinPE image and then you recommend that I edit the startnet.cmd to drvload them again?

I tried injecting the driver however the driver doesn't take affect until I plug in and remove a USB key.

Is there a universal wireless driver package available?

I install a driver when WinPE is loaded using DRVLOAD however the drivers does not kick in until the USB key is physically unplugged. I noticied that once the key is remove the registry detects the PCI device which was the driver I installed. Any ideas?

Is there anyway to pretend that I have unplugged it thought via command line?

Is there anyway to make it seem(pretend) like a USB key has been unplugged from the system?

I'm looking at required services and files needed for Wireless. It seems like I need the following services: WLANSVC, NATIVEWIFIP, EAPHOST, NDISUIO and RPCSS (which is already included in the image). I have copied the necessary dll and sys files to the PE image. I have added the services to the regedit and enabled them to run automatically. How can I register dlls in WinPE?

Figured out that my Virus Scanner was preventing the system from copying what it considers system files. Killed all processed related to the Virus Scanner and was able to bypass this issue.

When I search to the source directory indicated above there are no files or folders at all.

I get the following error when attempting to create VistaPE using WinBuilder.... I have copied the Vista contents locally and pointed the builder to that folder as the source and have download the complete VistaPE packages. Any hints? FileCopy - Failed to copy [%BaseDir%\Temp\VistaPE-Core\BootWimSrc\windows\System32\csrss.exe] to: [%BaseDir%\Target\VistaPE-Core\windows\System32\csrss.exe]

I would really like to use PE Network Manager for my Windows PE 2.1 image. Anyway this could be possible? I havent found a stand alone application to use the utility. Any advice/hints would be greatly apperciated. Thanks.

What are the downsides to not prepping the WIM? I have finished and don't want to get re-create it unless I absolutely need to. Still doesn't answer my question of why I cannot add a driver afterwards...prepping it should still allow me to add a driver.