3 replies to this topic

[hoody]

Dear all,

I know quite a few posts discussed this issue. I found two solutions.

1. Using peimg.
http://www.boot-land...3169#entry21613

When I tried this method, I got following error message.

The image directory specified is not a valid windows PE images

PEIMG failed complete the operation with status code 0x8007002

2. Using drvload.exe

I tried in Vista PE. I got following error message:

Drvload: unable to load x:\drivers (Error 0x8007000x)

Please help.

Thanks.

[allanf]

Dear all,

I know quite a few posts discussed this issue. I found two solutions.

1. Using peimg.
http://www.boot-land...3169#entry21613

When I tried this method, I got following error message.

The image directory specified is not a valid windows PE images

PEIMG failed complete the operation with status code 0x8007002

Interesting... Where does the peimg come from?

peimg will only work on pe images (hence the name), and somehow detects whether the image is based on winpe.wim or a full Vista install.wim. So, is your project a regular VistaPE which is basically a pe image with install-image bits added?

Wondering if the latest peimg is perhaps more sensitve...

Regards

[hoody]

Interesting... Where does the peimg come from?

peimg will only work on pe images (hence the name), and somehow detects whether the image is based on winpe.wim or a full Vista install.wim. So, is your project a regular VistaPE which is basically a pe image with install-image bits added?

Wondering if the latest peimg is perhaps more sensitve...

Regards

Thanks. I tried your trick and it gives the same error message. The file of WIN AKI I downloaded from MS is 6001.18000.080118-1840-kb3aik_en.iso. I am not sure if this is the latest version. The PEimg is from this package.

Here is the steps I tried. I use vistape v12 beta to build the ISO.

1. Open vistaPE-Core in UltraISO.
2. Extract boot.wim into c:\.
3. Rename boot.wim to winpe.wim.
4. Mount boot.wim to a folder.
imagex.exe /mountrw "c:\winpe.wim" 1 c:\mount
5. Merge driver
peimg.exe /inf=c:\drivers c:\mount\windows

It still gives me the same error message. In fact, I am a little bit surprised that you think the wim file name will affect the result. This file will be mounted or extracted. So I guess this file should not affect it. Anyway, I also tried change file name to Vista install.wim, same error message.

I googled and found this article.
http://www.msfn.org/...php/t92626.html

This gentlman installed Windows 2003 SP1 OPK and solve the problem. I found MS has Windows XP SP2 OPK so I tried to download it. However, it needs some partnership. I can not download it.

Thanks.
3. Using following command to mount

[allanf]

Here is the steps I tried. I use vistape v12 beta to build the ISO.

1. Open vistaPE-Core in UltraISO.
2. Extract boot.wim into c:\.
3. Rename boot.wim to winpe.wim.
4. Mount boot.wim to a folder.
imagex.exe /mountrw "c:\winpe.wim" 1 c:\mount
5. Merge driver
peimg.exe /inf=c:\drivers c:\mount\windows

It still gives me the same error message. In fact, I am a little bit surprised that you think the wim file name will affect the result. This file will be mounted or extracted. So I guess this file should not affect it. Anyway, I also tried change file name to Vista install.wim, same error message.

Hi hoody,

It's not the name that I was worried about. I don't know how, but peimg determines whether or not a mounted image directory (or just a plain directory like VistaPE's TargetDir) is a 'PE' image. I tried peimg to install drivers to a mounted install.wim, and no go! There must be a flag somewhere.

Anyway, that was what I thought your error message was all about - "not a valid windows PE image". Maybe not.

The peimg comand to install multiple drivers is:

peimg.exe /inf=c:\drivers\*.inf c:\mount\windows

One of the main differences between Vist's boot.wim and WAIK's winpe.wim is that the boot.wim has been prepped (peimg /prep), so it cannot be further optimized for size, and some of the peimg functions will not work - like /install, /import, /list (for packages). However /inf would still work after prepping.

Regards