Battery driver missing in VM

[haubmi]

Hi,

i was doing this:

1. slipstreamed SP3 into XP Pro with nLite (tried it in VMWare -> ok)

2. integrated KB923789, KB942763, KB950759, KB950760, KB950762, KB951376, KB951698, KB951748 with nLite (tried it in VMWare -> ok)

3. integrated IE7 with nLite

When i install step 3 in VMWare i get an error saying that the battery driver could not be installed.

The hardware assistand does not find it.

(batt.dll is missing in Windows\System32, i copied it there and told the assistant to also search in Windows\System32, then the driver was found and installed

but this is no solution becaus i want to have a unattended setup)

Why does nLite corrupt the installation of the battery driver?

What is the workaround?

Second Problem is:

If i run c't offline update on an installation from step 3. It installs KB950759 again (was allready installed in step 2).

Why does that happen?

What are the impacts if i integrate KB950759 again in a step 4.?

Thanks in advance

Michael

[TranceEnergy]

I get this as well if i do NOT patch SFC , OR if i do NOT copy with security catalog files for hotfixes. It is a known problem.

[Guest]

Which version of KB950759 do you integrate and when? You should be using the IE7 version and integrate it after IE7 in nLite. Your battery problem is a symptom of a known catalog file issue.

[TranceEnergy]

5eraph that last update in your ryanvm forum thread does update an old file, some single .dll file. Valid imho.

[haubmi]

Hi 5eraph,

i used: windowsxp-kb950759-x86-deu_77cda2a8778d23eed4cb91d2c67de77d4f5209d7.exe

which was wget by c't offline update.

I integrated KB950759 after slipstreaming of SP3.

(As wsu agent "WindowsUpdateAgent30-x86.exe" used by c't offline update, installed it, in a separate test.)

After integrating IE7 and setting up the VM with this iso, wsu agent (startet by c't offline update) installed it again.

What is the "IE7 version" you talking about?

Thank you for the link "known catalog file issue". I'did a quick scan, but found nothig that could help me

or name the cause of my problem. Please forgive my ignorance, but the link is about an update pack from you.

Could you be so kind and give me a bit more technical background about what could be causing this issue.

Thanks

Michael

Edited August 15, 2008 by haubmi

[haubmi]

I get this as well if i do NOT patch SFC , OR if i do NOT copy with security catalog files for hotfixes. It is a known problem.

Hi, thank you TranceEnergy.

How do you patch SFC with nLite?

How do you tell nLite to copy with security catalog files for hotfixes?

Can i do that in my step by step procedure?

I thougt my last step should be to do any patches...

Thanks

Michael

[Guest]

There are other links in the post I sent you to that explain the problem. Here is a more direct link:

http://www.ryanvm.net/forum/viewtopic.php?p=18296#18296

To put that into context, consider that IE7 includes newer versions of the files that KB950759 for IE6 is updating. So here's what is happening the way you've been doing it:

1. You integrate KB950759 for IE6.
   
2. You integrate IE7, overwriting KB950759 for IE6.
   
3. You integrate KB950759 for IE7, overwriting the same files a third time.
   

Windows gives you the battery error because there is a problem with three different catalog files protecting different versions of the same set of files during setup.

Here is the file you should be using. It supersedes KB950759 and should be integrated after Internet Explorer 7:

IE7-WindowsXP-KB953838-x86-(locale).exe

Edited August 16, 2008 by 5eraph

[Zorba the Geek]

I am currently developing addons for XP that remove Windows applications like Outlook Express and they all have the missing battery driver problem if I remove entries from syssetup.inf and patch syssetup.dll.  Rather than identify the root cause of the problem I do a workaround that involves copying the batt.dll file from the i386 folder to System32.  Here are the relevant entries OE_Rem.inf:

[OErem]
CopyFiles = Battery.File

[SourceDisksNames.x86]
1="Setup Files","WIN51",,"i386"

[SourceDisksFiles]
batt.dll = 1

[DestinationDirs]
DelINFs = 17
Battery.File = 11
Cleanup = 10

[Battery.File]
batt.dll

As far as I can tell these addons do not have a problem with multiple cat files for one updated file.