Battery Driver Prompt During GUI Setup

[InTheWayBoy]

Okay, so this is a little funky...I'm setting up an RIS server, and have used the correct tools setup a new image using an XP Pro SP2 disc. I then created a new install image using a new unattended file, in which I edited to suit my needs. Everythings gravy...just like the many times I've done this before.

However, I am having a slight problem during the GUI Setup section...it gets to 39 minutes and then prompts me with the Windows Logo error for the Battery! I've never seen this before...I've seen it with other hardware, but not for the battery!

It's safe to say that I'm sure I goofed something, but I really haven't done any configuring other than the unattended setup...I'm sure the CD on it's own works great, and I've used the same disc for previous RIS images with nothing like this.

I really just want to know where to look...any log files, or were is the actual battery driver that is causing me grief. I'm sure it would be in the I386 dir, but what files relate to this?

[InTheWayBoy]

Here's the error I'm getting:

Windows Logo Prompt - Battery

I click yes and everything is fine...but it doesn't seem to go any further until then, defeating the unattended purpose...thanx in advance!!!

[peter_hob]

On one hand glad I am not the only one, but on the other hand as curious as you to a cause and solution.

[InTheWayBoy]

How are you installing WinXP? From CD or over network? Maybe we can figure this out on our own

[tuxman]

I have had the same problem and have been installing via CD rom

On desktops not Laptops

tuxman

[erik_demon]

Odd indeed,

maybe a stupid question, but did you guys removed the battery drivers with Nlite?

[zorro1]

i have the same problème, since update with April hotfix

[InTheWayBoy]

No nlite for me...that's what is so odd...

[nowarez]

I have also the same problems. None nLite. But I have change files that I got from XPize uAE 1.1.exe

[InTheWayBoy]

Hmmm...never heard of that program...at least not yet

I'm gonna reload the CD onto the server later this afternoon...going fishing now!

[RyanVM]

I've had that problem in the past, but it just kind of went away on its own

Setting DriverSigningPolicy to Ignore in winnt.sif would be a cheap workaround, but it should work in the meantime.

[InTheWayBoy]

RyanVM, that's exactly what I was gonna post! Didn't get to reload the RIS image so I just edited the sif file and added that, among other extra settings. No problem...still would like to know what causes it of course.

[Nepali]

what will be the winnt.sif file looks like

just to ignore driver signing

[InTheWayBoy]

I guess it would be something like this:

[Data]
MSDOSInitiated="0"
UnattendedInstall="Yes"

[Unattended]
DriverSigningPolicy="Ignore"
NonDriverSigningPolicy="Ignore"

I think that would be it, if that's all you want to do. Normally mine is like this:

[Data]
MSDOSInitiated="0"
UnattendedInstall="Yes"
AutoPartition="0"
AutomaticUpdates="Yes"

[Unattended]
DUDisable="Yes"
UnattendMode="FullUnattended"
UnattendSwitch="Yes"
OemPreinstall="Yes"
FileSystem="*"
Repartition="No"
TargetPath="\WINDOWS"
OemSkipEula="Yes"
WaitForReboot="No"
DriverSigningPolicy="Ignore"
NonDriverSigningPolicy="Ignore"

[UserData]
ProductKey=""
FullName="NAME"
OrgName="COMPANY"
ComputerName="TEMP"

[GuiUnattended]
OemSkipWelcome="1"
OemSkipRegional="1"
TimeZone="035"
AdminPassword="*"

[Display]
AutoConfirm="1"
BitsPerPel="32"
XResolution="800"
YResolution="600"
VRefresh="75"

[Networking]
InstallDefaultComponents="Yes"

[Components]
msmsgs="Off"
msnexplr="Off"
indexsrv_system="Off"
fax="Off"
OEAccess="Off"

[WindowsFirewall]
Profiles="WindowsFirewall.TurnOffFirewall"

[WindowsFirewall.TurnOffFirewall]
Mode="0"