wschulze

@WreX: Thanks for the hint. I have verified that the driver works OK with WinPE 2.x by mounting the WinPE 2.x Registry hive on the technician machine, and making the driver entries manually. So, the driver is the correct one. Of course, I may have screwed up the INF file ... @leen2: Thanks for your detailed information. The manual method I use is basically described in this post: http://www.msfn.org/board/How-to-edit-WinP...ne-t112872.html The INF file is not decorated for multiple target platforms, and the driver has no associated hardware - you may think of it as something like a RAM disk driver. Also, this driver does not replace any existing WinPE 2.x in-box driver.

This is from http://technet.microsoft.com/en-us/library/cc507857.aspx: Many applications couldn’t run within Windows PE 1.0 because they required temporary storage space, and Windows PE was often launched from nonwriteable media such as a CD. Windows PE 2.0 now supports most applications that need to write temporary files by providing 32 MB of scratch space in the computer’s RAM. Any time an application attempts to write temporary files, no matter which folder, Windows PE redirects the changes to the scratch space in memory to simulate the presence of a hard disk. Naturally, all changes are lost when you restart the computer. And this is from me: WinPE 2005 does not allow write access to its system drive X:, even when booted as a RAM disk image. In order to write files in WinPE 2005, you will need to integrate another RAM disk driver that provides writeable space, or write to some other available media (a partition on the hard disk, a USB attached device, a network drive, etc.). WinPE 2.0 appears to allow write access to its system drive X:, but this is not unlimited. Although it seems that you can add, delete and modify files at will, WinPE does this by way of a "write filter", and stores all added and modified data in a scratch space. This works completely transparent as long as you do not exceed the scratch space limit. So, deleting existing files on drive X: does not free space, but in fact consumes space.

Hello, I am trying to add a non-PnP driver to an offline WinPE 2.x image. The driver works OK when I add it manually (mount WinPE 2.x image, copy sys file, load WinPE registry hive, add driver Registry entries, unmount WinPE 2.x image). Looking for a more comfortable way, I tried adding the driver via "peimg /inf", which appeared to work - peimg reported no error, and the driver files were copied to the WinPE 2.x image. However, the driver was not loaded when booting the WinPE 2.x image. Does anybody know if it is possible to add Non-PnP drivers via "peimg /inf" to a WinPE 2.x image? If not, is there any other comfortable way of adding Non-PnP drivers to an offline WinPE 2.x image? Thanks for any information.