confused_ka

January 11, 2013

Hello,

I am using Windows PE 4.0 with built in powershell to deploy Windows Server 2008 R2. Basicly I am booting Windows PE 4.0 with all the neccessary drivers into the RAM Disk and from there on I get the unattended files and sources for Windows 2008 Server R2 and I will start the install process withhin the PE.

With Windows PE 3.1 I had 0 problems but now with PE 4.0 after the end of the Installation during the PE Part I get the following Error message "Installation cannot continue because a required driver could not be installed". Ofc I browsed thru the panther logs and found out it was the areca mass storage driver.

The logs are showing me this:

2013-01-11 15:15:49, Info [0x0a0024] UI progress task ProgressInfo\CBSServicing : EndProgress

2013-01-11 15:15:49, Info [0x0602a4] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package path is [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf]

2013-01-11 15:15:49, Info [0x0602b2] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package is [critical]

2013-01-11 15:15:49, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf]

2013-01-11 15:15:49, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x9]

2013-01-11 15:15:49, Info IBS AddDriverPackageIntoDriverStore:System root is [C:\Windows]

2013-01-11 15:15:49, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\]

2013-01-11 15:16:11, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf] into driver store. Error code is [0x80070032]

2013-01-11 15:16:11, Error [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf]. Driver package is [Critical]. Error code is [0x32][gle=0x00000032]

2013-01-11 15:16:11, Error [0x0602ab] IBS CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x32][gle=0x00000032]

2013-01-11 15:16:11, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows installation cannot continue because a required driver could not be installed.]

The driver itself works fine within the PE. Windows PE 4.0 can access the harddisks and the driver gets initialized properly. The same driver works with PE 3.1 and the unattended installation. I also tried to switch the driver with another version but still same error.

Anybody know what those error codes are standing for? Error code is [0x80070032] or Error code is [0x32][gle=0x00000032].

Regards,

Phil

March 28, 2012

Thank you for the info. Looks good!

March 27, 2012

Hi,

is there a way that after the unattended setup, I can automaticly download and install unattended all missing updates? Like trigger it via a command line tool?

At the moment I am slipstreaming them offline with dism. So they get applied during the offlince servicing phase. However when I applied the latest RDP hotfix, my unattended setup stopped during the offline servicing phase cause it couldnt apply a package (the hotfix I suppose, did not tell me any readable name in the panther logs).

February 11, 2009

The multiple BCD is a cool thing, but did any of you guys managed to add LOCALBOOT as a default entry?

I dont know how to set it to localboot so when there is no user interaction and the timeout is done, it should boot to local instead of booting a windows PE image....(like the first one in order...)

anyone knows a solution?

February 11, 2009

Hi,

i am using BCD for my PXE Environment in order to have 2 multiboot windows pe 2.1 (32 and 64 bit).

Everything works besides that I dont know how I add localboot as default boot to the BCD...

When the timer runs down it boots the Windows PE...

my Configuration looks like this

bcdedit -store c:\BCD -enum all

Windows Boot Manager
--------------------
identifier              {bootmgr}
description             W.H.A.T. BootManager
default                 {default}
displayorder            {625f9b00-ec81-11dd-b5f9-0019b9464270}
                        {77c871b0-ebc3-11dd-b5f9-0019b9464270}
timeout                 10

Windows Boot Loader
-------------------
identifier              {625f9b00-ec81-11dd-b5f9-0019b9464270}
device                  ramdisk=[boot]\Boot\boot32.wim,{ramdiskoptions}
description             Windows PE 2.1 (x86)
osdevice                ramdisk=[boot]\Boot\boot32.wim,{ramdiskoptions}
systemroot              \Windows
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {77c871b0-ebc3-11dd-b5f9-0019b9464270}
device                  ramdisk=[boot]\boot\boot.wim,{ramdiskoptions}
description             Windows PE 2.1 (x64)
osdevice                ramdisk=[boot]\boot\boot.wim,{ramdiskoptions}
systemroot              \Windows
detecthal               Yes
winpe                   Yes

Setup Ramdisk Options
---------------------
identifier              {ramdiskoptions}
description             32 Bit PE 2.1 OBEN, 64 Bit PE 2.1 UNTEN
ramdisksdidevice        boot
ramdisksdipath          \boot\boot.sdi

The question is how do I add an GENERIC localboot entry as default? I only have the choice to make a default vista/2008 boot or {ntdlr} for xp/2003

but we have all kinds of servers (2003 and 2008) so I need a generic localboot entry...

Anyone an idea?

January 23, 2009

Hi,

I am looking for a guide to pxe boot 32 or 64 bit Windows pe 2.1. I am using pxelinux for multiboot but due to the hardcoded pxeboot.0 I dont get how to add another Windows PE 2.1 bootimage into it. Since it hardlinks to boot.wim etc...

Is there a way to dual boot Windows 2.1 PE (32 or 64 Bit)?

Regards,

Philipp

December 4, 2008

Hi,

looking for a tool which erases the first megabyte (size variable) of a hardisk with zeros.

Kinda what DD can do under Linux. Is there a free one for xp/vista x64?

Regards,

Phil

September 17, 2008

or asking in another way, is it possible to slipstream dot.net 3.5 sp1 offline to my install.wim?

I heard about the pkgmgr.exe and the /iu switch. But I did not figured out yet how to slipstream the .net 3.5 sp1 as an official package or feature.

Any ideas are appreciated

Regards,

Phil

September 17, 2008

Hi

I am trieng to install dot.net 3.5 sp1 unattended in audituser pass with a sync command. For some reason it doesnt get applied however the audit passes are applied. I simply did it with a cmd /c c:\Install\dotfx35.exe /q sync command. Is there an error log where I can look what went wrong?

Regards,

Philipp

June 26, 2008

If you completely disable the raid function you don't need to install mass storage device (msd) drivers. If raid function is disabled you need to install the drivers in the sata_ide directory which you can find if you extract the official nVIDIA nForce driver package found on their website. You can't / don't need to install these drivers using the txtsetup.oem method, use OemPnPDriversPath in [unattended] in WINNT.SIF!
Depending on the exact chipset you have, you might cannot use every driver out there compatible with your chipset. Can you tell me the Hardware-ID of your sATA- or pATA-Controller? It look like PCI\VEN_10DE&DEV_0036 and can be found in the device manager below the "ide ata/atapi controller" or below "scsi- and raid-controller". If i know that ID i can tell you which driver version will be the best (stability and performace).

Hi,

thanks for you advise but I checked on the chipset of the Mainboard and its an Nvidia MCP78B. I have only found SATA Raid Drivers with this package, not standalone SATA drivers.

I dont think the nforce drivers are that uptodate since the mainboard chipset drivers are from 3/2008.

I get the error during the textmode setup when you can press f6 to add new SATA drivers. If I use teh same drivers via floppy i dont get the bluescreen at all. I have also put the drivers to the "OemPnPDriversPath" written in the unattend.ini, still no success.

Seems kinda strange...

Regards,

Philipp

June 25, 2008

Hello

I am trieng to embedd a mass storage driver for a windows server 2003 (64 bit) unattend installation.

I am using the txtsetup.oem method.

I have embedded alot of mass storage drivers in this way and never had any problems, but this one seems strange.

Here is my txtsetup.oem

[Disks]
d1 = "NVIDIA RAID DRIVER (SCSI) disk 1",\disk1,\

[Defaults]
;scsi = RAIDCLASS

[scsi]
RAIDCLASS = "NVIDIA RAID Driver (required)"
BUSDRV = "NVIDIA nForce Storage Controller (required)"

[Files.scsi.RAIDCLASS]
driver  = d1,nvrd64.sys,RAIDCLASS
inf     = d1,nvrd64.inf
catalog = d1,nvraid.cat
dll     = d1,nvraidco.dll
dll     = d1,NvRCoENU.dll


[Files.scsi.BUSDRV]
driver = d1,nvgts64.sys,BUSDRV
inf    = d1, nvrd64.inf
catalog = d1, nvraid.cat
dll    = d1,nvraidco.dll
dll     = d1,NvRCoENU.dll

[Config.RAIDCLASS]

[Config.BUSDRV]
value = parameters\PnpInterface,5,REG_DWORD,1

[HardwareIds.scsi.RAIDCLASS]
id = "SCSI\NVIDIA__Raid_Disk________","nvrd64"
id = "SCSI\__NVIDIA_______Raid_Disk","nvrd64"
id = "SCSI\NVIDIA__Raid_Disk_20_____","nvrd64"
id = "SCSI\__NVIDIA____Raid_Disk_20","nvrd64"
id = "*_NVRAIDBUS","nvrd64"
id = "*NVRAIDBUS","nvrd64"
id = "*NVRAID20","nvrd64"

[HardwareIds.scsi.BUSDRV]
id = "PCI\VEN_10DE&DEV_0036", "nvgts64"
id = "PCI\VEN_10DE&DEV_003E", "nvgts64"
id = "PCI\VEN_10DE&DEV_0054", "nvgts64"
id = "PCI\VEN_10DE&DEV_0055", "nvgts64"
id = "PCI\VEN_10DE&DEV_0266", "nvgts64"
id = "PCI\VEN_10DE&DEV_0267", "nvgts64"
id = "PCI\VEN_10DE&DEV_037E", "nvgts64"
id = "PCI\VEN_10DE&DEV_037F", "nvgts64"
id = "PCI\VEN_10DE&DEV_036F", "nvgts64"
id = "PCI\VEN_10DE&DEV_03F6", "nvgts64"
id = "PCI\VEN_10DE&DEV_03F7", "nvgts64"
id = "PCI\VEN_10DE&DEV_03E7", "nvgts64"
id = "PCI\VEN_10DE&DEV_044C", "nvgts64"
id = "PCI\VEN_10DE&DEV_0558", "nvgts64"
id = "PCI\VEN_10DE&DEV_0559", "nvgts64"
id = "PCI\VEN_10DE&DEV_055A", "nvgts64"
id = "PCI\VEN_10DE&DEV_07F8", "nvgts64"
id = "PCI\VEN_10DE&DEV_07F9", "nvgts64"
id = "PCI\VEN_10DE&DEV_07FA", "nvgts64"
id = "PCI\VEN_10DE&DEV_07FB", "nvgts64"
id = "PCI\VEN_10DE&DEV_0AD9", "nvgts64"
id = "PCI\VEN_10DE&DEV_0AD8", "nvgts64"
id = "PCI\VEN_10DE&DEV_0ABD", "nvgts64"
id = "PCI\VEN_10DE&DEV_0ABC", "nvgts64"

And the here is the unattend.txt (well the most relevant parts):

...
OEMPreinstall=Yes
...
[MassStorageDrivers]
"NVIDIA RAID Driver (required)" = OEM
"NVIDIA nForce Storage Controller (required)" = OEM

[OEMBootFiles]
nvgts64.sys
disk1
nvide.nvu
nvraid.cat
nvraidco.dll
NvRCoEnu.dll
nvrd64.inf
nvrd64.sys
txtsetup.oem

...

The problem that I am getting is that driver works when I enable the NVRAID in the Bios. If I use the NVraid just as a Storage Controller without raid Function (BUS DRV) I get a Bluescreen (Stop 0x07b).

If I disable the raid and use the disk method with F6 during the setup with exact the same files like the one in my unattend installation I dont get a bluescreen.

Do I get this right?:

[scsi]

RAIDCLASS = "NVIDIA RAID Driver (required)" --> the driver for the raid, when its enabled via bios

BUSDRV = "NVIDIA nForce Storage Controller (required)" --> the driver for just a storage controller if I disable the raid function

So my theory is that for some reason if i leave the raid disabled windows setup does not care and still takes the raid driver instead of the second one.

Leaving the Raid enabled isnt a solution for me, well for my boss

The mainboard is an FSC D2721h with on board NVRAID.

Thank you for your help in advance.

Regards,

Philipp

Sign In

confused_ka

Posts

Joined

Last visited

Donations

Country

Content Type

Profiles

Forums

Events

Posts posted by confused_ka

Problem deploying Windows Server 2008 R2 with Windows PE 4.0

Automatic Update Installation

Automatic Update Installation

Multi Boot and TFTP32

bcdedit questions

Dual PXE/TFTP boot Windows PE 2.1 (32 and 64bit)

Looking for a HD Tool to erase the first megabyte of a hardsik

Installing dotnet 3.5 unattended problems

Installing dotnet 3.5 unattended problems

mass storade(nvraid) integration via txtsetup.oem/unattend.txt

mass storade(nvraid) integration via txtsetup.oem/unattend.txt

Activity

Browse