Hi guys!

Today I did a new XP installation disc (included the latest MS patches etc). Naturally I also added the Xpize. When I tested the new ISO (before burning) in VMware I get a "Hardware installation Error" (See attached picture for details).

After this I reversed my steps and did just the ISO installation of the XPize on XPP SP2 disc. The error was still present:( I've tried it with a couple other XP installation disks and I got the same error in all cases.

I've tried google, to see if anyone has the same experience, but I didn't found anything, so I've decided to ask you guys for advice what to do.

I really love Xpize and would really like to find a way how to fix this.

Here are the things I used:

XP Professional SP2 (Build 2600.xxx)

XPize 4.7b 2 Full

VMWare Workstation 5.5.2 build 29772

I've just tested this "new ISO" on VMWare 6.0.2 build 59824 and the error is still present. So it's indeed XPize's fault

Have you tried it without XPize before you confidently place the blame there?

Ofcourse I did. That was the first thing that I did.

Removed. Pointless suggestions. I was able to duplicate the problem. So, I'm going to take my foot out of my mouth.

Edited December 28, 200718 yr by mmarable

I've taken a vanilla XP source, slipstreamed SP2 to start with. You're screen shot has the XPize setup screen, so I'm working from the belief that you used XPize to patch the binaries in i386.

I did that as well, and although it did not generate the error during setup, at first login I got a "Device installer error" message: "Windows could not load the installer for Battery. Contact your hardware vendor for assistance."

Taking a look at the SetupAPI log, this error jumped out at me:

#E364 An unsigned or incorrectly signed file "D:\i386\NOTEPAD.EX_" for driver "Battery" blocked....

The exact wording of the error I recieved at first login shows up several times in SetupAPI, each time it followed this error:

#E144 Loading module "C:\Windows\System32\Batt.dll" failed. Error 126: The specified module could not be found.

Thing is, Batt.dll was being used to install a device called "Batteries", while the error message is reporting the device being names "Battery"

Looks like there may be a problem. I'm going to try it on VirtualPC next.

Installing in VirtualPC I don't get error messages thrown, but the same messages show up in SetupAPI.log.

Edited December 28, 200718 yr by mmarable

Today I just found an old copy of Xpize 4.6 (XPize46Full.exe) on my PC and I did another Xpize ISO installation using the same base XP cd as I did before. I then installed it in vmware and this time it's without the battery error. So it seems that xpize 4.7 (XPize47b2Full.exe) has a bug in it.

What machine are you guys creating these discs on? What OS?

I'm doing all my work on FSC Lifebook E8020 with Windows XP PRO SP2 + all hotfixes/patches that MSBSA finds + xpize 4.6.