Jump to content

Recommended Posts

Posted (edited)

Hi all,

Does PkgMgr.exe work from *inside* WinPE?

Here's what I'm trying to do:

1) Create baseline image

2) Sysprep/Capture

3) Boot WinPE image (which includes various tools - imagex, pkgmgr etc)

4) Format hard disk

5) Imagex /apply WIM

6) Copy drivers to C:\OEM\Mouse, C:\OEM\Video etc

6) Use PkgMgr to inject drivers.

Stages 1-5 seems to work fine.

Stage 6 crashes and burns :wacko:

I *think* I have the XML and commands correct:

XML snippet:


<settings pass="offlineServicing">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<DriverPaths>
<PathAndCredentials wcm:keyValue="1">
<Path>c:\oem</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>

PkgMmgr command:


pkgmgr /o"c:\;c:\windows" /n:c:\unattend.xml /l:"c:\log2.txt"

And the resulting log file:


2007-01-31 10:02:54, Info CBS Pkgmgr: called with: "pkgmgr /o:"c:\;c:\windows" /n:c:\unattend.xml /l:"c:\log2.txt""
2007-01-31 10:02:54, Info CSI 00000001@2007/1/31:18:02:54.564 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x73a7f745 @0xb02dbf @0xafd892 @0xafe27e @0x77273833 @0x7734a9bd)
2007-01-31 10:02:54, Error CSI 00000002@2007/1/31:18:02:54.564 (F) d:\vistartm\base\xml\udom_builder.cpp(932): Error c000a083 [Error,Facility=(system),Code=41091 (0xa083)] originated in function CMicrodomXmlWalker::XmlError expression: (null)
[gle=0x80004005]
2007-01-31 10:02:54, Info CBS Pkgmgr: return code: 0x5b9

I've very probably got something misconfigured, but I'm scratching my head....!

All pointers/suggestions welcome.

Cheers,

Mike

Edited by mdolan

Posted

Another day, another try... and success!

For those of you who encounter this problem, the solution is:

DO NOT CUT AND PASTE FROM THE WAIK HELP FILE.

For some reason it dumped some invisible junk in the XML file. Not viewable from notepad, but enough to cause the package manager to cough blood and die. It would be slightly nicer if the error messages were a *little* more informative ;-)

So either retype by hand, find a known working sample (in very plain text!), or use the SIM.

Cheers,

Mike

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...