Shutdown by power switch with MinLogon

[Mike Warren]

Slobodan,

pciide did not initialized for some reason :-(

This board has SATA as well as IDE. I will try playing with the
BIOS settings to see if that makes a difference.

The system boots fine if I just replace the ACPI HAL with Standard
PC. Perhaps I should uninstall SP2 and go back to SP1 to see if the
problem still exists.

You might want to send us setupapi.log that was made during the FBA.

I tried to attach it but the server said it was too big so I have uploaded it to

http://www.cairnscarsound.com.au/temp/setupapi.log

Also info that was not written to setupapi.log during second boot can
be read from remote debugger if you tell windows to send diag to
debugger.
http://msdn.microsoft.com/library/d..._66a07114-953e-49aa-bebf-f9b4ca60a6dd.xml.asp

Ok. I'll see if I can do that shortly.

This all sound too strange. (Ability to pass FBA, and then in second
boot XPe wont work)

This is a worry if it is confusing to you and Konstantin. I'm often confused

-Mike

 

[KM]

Mike,

Can you try adding intelide.sys to you image? (and remove pceide.sys)
E.g., by adding "Intel(r) 82092AA PCI IDE Controller" component.


KM

 

[Mike Warren]

Konstantin,

System Bus Extender is not there.
pciide.sys or pciidex

Mike, do you have a PCI IDE Controller component? Most likely you do
since you were able to pass FBA at least once. If you got "Standard Dual Channel PCI IDE
Controller" you will get
both pciide.sys and pciidex.sys.

Yes, I have Standard Dual Channel PCI IDE Controller. This image is one
built from the list Slobodan gave earlier in this thread. All I added was
MinLogon, Command Shell and NTFS, then resolved all dependencies.

If you still have similar platform running XP Pro, check what System
Bus Extender is runinng there: pciide.sys or else?

The XPPro machine has both files.

Earlier today I tried building an image by including all the components listed
in Device Manager with a fresh install of XPPro. This included a lot of Intel
drivers including "Intel(R) 82801EB UltraATA Storage Controllers - 24C1"
but that image failed (7B) on first boot.

The fresh XPPro install uses "ACPI Uniprocessor PC" and I haven't installed
any drivers other than those that were installed automatically during Windows
installation.

I also just tried my test HDD on another target just in case I had a faulty
motherboard but got the same error on second boot.

-Mike

 

[Slobodan Brcin \(eMVP\)]

Mike,

Do you have SMBIOS driver component in your image. (This is the only component that you need to fill registry entries)
For all other Intel chipset drivers please copy inf, sys and dll files to their folders. (use same files that are installed on your
XPP with same board, or extract and copy all Intel files from setup)

This is a worry if it is confusing to you and Konstantin. I'm often confused

It is confusing in a way that I have never experienced similar symptoms. And I have seen too many different problems so far.

Regards,
Slobodan

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

This is a very long shot but try going to MB manufacturer site and look for BIOS updates.

Regards,
Slobodan

 

[Mike Warren]

Konstantin,

Can you try adding intelide.sys to you image? (and remove pceide.sys)
E.g., by adding "Intel(r) 82092AA PCI IDE Controller" component.

I removed "Standard Dual Channel PCI IDE Controller" and added
"Intel(r) 82092AA PCI IDE Controller" and got 7B on first boot.

-Mike

 

[Mike Warren]

Slobodan,

Do you have SMBIOS driver component in your image. (This is the only
component that you need to fill registry entries)

Do you mean Microsoft System Managment BIOS Driver? If so, I have
added that and Microsoft System Managment BIOS Driver Installer. It
made no difference

For all other Intel chipset drivers please copy inf, sys and dll
files to their folders. (use same files that are installed on your
XPP with same board, or extract and copy all Intel files from setup)

Do you think I should do this now?

I don't understand why I can't get an image that works purely from the
components supplied with XPe since I can with a standard install of
XP Pro.

-Mike

 

[Slobodan Brcin \(eMVP\)]

Mike,

Do you mean Microsoft System Managment BIOS Driver? If so, I have
added that and Microsoft System Managment BIOS Driver Installer. It
made no difference

I ment about the one from intel driver package. (But Iy should not make a difference)

Do you think I should do this now?

It can't hurt and it might help you.

I don't understand why I can't get an image that works purely from the
components supplied with XPe since I can with a standard install of
XP Pro.

This is the part that I do not understand either. It should work :-(

Redirect setupapi logging to remote debugger, increase message level reporting, and see what will be reported during the boot

Regards,
Slobodan

 

[KM]

Mike,

Well.. That was only a guess of mine following some errors from your setupapi.log.
One more thing I forgot to mention. You may want to try to add intelppm.sys for experimenting purposes. This is SP2 library only.

I still think the issue may be related to SP2. When we are out of ideas a last hope could be building an SP1 image.

Konstantin

 

[Mike Warren]

Hi Slobodan,

This is the part that I do not understand either. It should work :-(

Ok. I just removed all traces of XPe SP2 and reinstalled SP1. I did not
install any QFEs. I then built an image based on the list you supplied
earlier and it booted fine (first and second).

I have started to add other components and have noticed that I can't
get the USB keyboard and USB mouse to work and the power button
doesn't work either.

I've been at this for the last 19 hours straight and I'm getting tired. I'll
go home and get some sleep and continue in the morning.

Redirect setupapi logging to remote debugger, increase message level
reporting, and see what will be reported during the boot

I don't understand how to do this. I did some Google searches and looked
through the Windbg help but couldn't find any relevant information. Maybe I'm
just too tired. Another job for tomorrow morning.

Thank you Slobodan and Konstantin for your help with this problem.

Regards
-Mike

 

[KM]

Mike,

I don't understand how to do this. I did some Google searches and looked
through the Windbg help but couldn't find any relevant information. Maybe I'm
just too tired. Another job for tomorrow morning.

Just for future use, take a look at this simple application http://www.sourcequest.com/download/suplog-1_01-install.exe.
A while ago I found it pretty useful. Some good description of it you can find here: http://www.sourcequest.com/download/suplog.htm.
This is Source Quest project and therefore sources also available.

Basically, the app will allow you to set up necessary SetupAPI logging and debugging parameters without messing around with
registry. This may just save you some time.

Konstantin

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

Like I said look at the link:
http://msdn.microsoft.com/library/d..._66a07114-953e-49aa-bebf-f9b4ca60a6dd.xml.asp

For full log info set this value from TD.
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\LogLevel REG_DWORD 0x8000FFFF

But this will produce too many log output so you might want to reduce this logging level a big.

I have started to add other components and have noticed that I can't
get the USB keyboard and USB mouse to work and the power button
doesn't work either.

"USB Human Interface Device"
"HID Keyboard device"
"HID-compliant mouse"

Power button with minlogon is another issue and you should read my old post on this subject how to solve this trough your program.
(New minlogon versions might solve the problem, have no idea)

Regards,
Slobodan

 

[Mike Warren]

Hi Konstantin,

Just for future use, take a look at this simple application
http://www.sourcequest.com/download/suplog-1_01-install.exe. A while ago I found it pretty useful.
Some good description of it you
can find here: http://www.sourcequest.com/download/suplog.htm. This
is Source Quest project and therefore sources also available.
Basically, the app will allow you to set up necessary SetupAPI
logging and debugging parameters without messing around with
registry. This may just save you some time.

Thanks, I'll look into this.

-Mike

 

[Mike Warren]

Hi Slobodan,

Like I said look at the link:
http://msdn.microsoft.com/library/d..._66a07114-953e-49aa-bebf-f9b4ca60a6dd.xml.asp

For full log info set this value from TD.
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\LogLevel
REG_DWORD 0x8000FFFF

But this will produce too many log output so you might want to reduce
this logging level a big.

I'll look at this and the link Konstantin supplied today.

"USB Human Interface Device"
"HID Keyboard device"
"HID-compliant mouse"

These are already added. I had no problems getting them to work with SP2

Power button with minlogon is another issue and you should read my
old post on this subject how to solve this trough your program. (New
minlogon versions might solve the problem, have no idea)

I should point out that reverting to SP1 does not solve my problem. I particularly
wanted to use the firewall from SP2. The point of the exercise was to prove that
I wasn't going nuts and I had built a successful image for this hardware.

-Mike

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

Have you tried to install XPP SP2 on this computer?

Regards,
Slobodan

 

[KM]

Mike,

FBALog.txt and SetupAPI.log again?

These are already added. I had no problems getting them to work with SP2


I should point out that reverting to SP1 does not solve my problem. I particularly
wanted to use the firewall from SP2. The point of the exercise was to prove that
I wasn't going nuts and I had built a successful image for this hardware.

This makes perfect sense. Also, you are getting more and more data about the problem and your analysis can be more accurate now.

So, did I get it right:
1) You have XP Pro SP1 with ACPI HAL running on the hardware fine.
2) You have XPe SP1 with ACPI HAL running on the hardware fine.
3) You have XPe SP2 with ACPI HAL that shows 7B BSOD on first or second boot.
4) You have XPe SP2 with Standard PC HAL running on the hardware fine.

If so, and you got XPe SP1 and SP2 images with minimum components (see Slobodan's list mentioned earlier) you can do diff on the
configurations to see if any differences in the component lists.

Then you can do a diff on images (2,3) to see what MS binaries got changed in SP2 that broke the build. It could be something from
critical boot components.

In case there is no binary differences (which I doubt) you can also compare registry.

This is routine work but may help you to narrow down the problem.

As soon as you know the differences you can analyze SetupAPI.log with more knowledge on what to be looking for.

Konstantin

 

[Mike Warren]

Slobodan,

Have you tried to install XPP SP2 on this computer?

Yes. Yesterday I took a new, unformatted machine and installed XP Pro
SP2 onto it. I did not use any other drivers and everything on the machine
works fine. I still have that machine here as a reference.

I then built a XPe image by using every component listed in device manager
on the XPP SP2 machine. There were a couple of components I couldn't
find such as Intel Celeron 2.66 processor and DVD-ROM drive. I then
added WinLogon and Explorer Shell and resolved all dependencies.
This image failed to boot (7B).

-Mike

 

[Slobodan Brcin \(eMVP\)]

Hi Mike,

Unfortunately for you, only thing that you can do is to test different things.

Try something like following.
1. Make winlogon based XPe image.
2. Copy on target HDD your working XPP SP2.
3. Copy XPe files that are not found in XPP. (Copy without overwrite)
4. Replace config folder (this contain registry files).
5. Let target machine boot.

If this pass you will know that you either:
1. Missing some critical driver file. (Strange but....)
2. Some file in XPe SP2 is not same as the ones in SP2. (This can be easily checked.)

Regards,
Slobodan

 

[Mike Warren]

Hi Kostantin,

FBALog.txt and SetupAPI.log again?

I would rather spend my time making SP2 work, but if you think it is important
I will go down this path. I don't have 2 dev machines and it is time consuming
to remove SP2 and reinstall SP1 so I haven't gone back to SP2 yet.

So, did I get it right:
1) You have XP Pro SP1 with ACPI HAL running on the hardware fine. Yes

2) You have XPe SP1 with ACPI HAL running on the hardware fine.

Previously, yes. I haven't built a complete image since going back to XPe SP1.
I still have the Keyboard and mouse issue which stops me from testing the image
properly. I am unable to connect PS/2 keyboard due to hardware (the plug is
blocked).

3) You have XPe SP2 with ACPI HAL that shows 7B BSOD on first or
second boot. Yes.

4) You have XPe SP2 with Standard PC HAL running on
the hardware fine.

Yes, except for the power button problem.

and 5) I have XP Pro SP2 running ACPI Uniprocessor HAL fine.

If so, and you got XPe SP1 and SP2 images with minimum components
(see Slobodan's list mentioned earlier) you can do diff on the
configurations to see if any differences in the component lists.

I loaded the base SLX file I had created for SP2 into SP1 and the components
I had to change due to version changes were:

ACPI Multi Processor PC
FAT
Mount Manager
PnP (Kernel Mode)
Standard Dual Channel PCI IDE Controller
Standard IDE/ESDI Hard Disk Controller

There are lots of changes when dependencies are auto resolved.

-Mike

 

[KM]

Mike,

I would rather spend my time making SP2 work, but if you think it is important
I will go down this path. I don't have 2 dev machines and it is time consuming
to remove SP2 and reinstall SP1 so I haven't gone back to SP2 yet.

I totaly understand. It is definitely up to you (your time lines) what spend time on.
I don't see the important of getting those simple components to work with SP1 image.

....>

I loaded the base SLX file I had created for SP2 into SP1 and the components
I had to change due to version changes were:

ACPI Multi Processor PC
FAT
Mount Manager
PnP (Kernel Mode)
Standard Dual Channel PCI IDE Controller
Standard IDE/ESDI Hard Disk Controller

That is what we all suspected, didn't we?
You may want to pay more attention now to IDE Controllers.
As I mentioned earlier, they got changed within SP2 (and you just confirmed that observing your XPe SP1/SP2 images).
A quick dirty test could be if you grabbed pciide[x].sys binaries from SP1 and put them (replace) in your SP2 image to see if it
works.
You don't need to re-build SP2 image. You can use the old one you build with ACPI HAL that showed 7B BSOD.

The same could be done with other components you listed.

And it it does not help, try using the preFBA registry hives (or only the system hive) from XPe SP1 in SP2 image (SP2 binaries).

This all may appear to be a MS bug in SP2. Although it is weird that XPP SP2 works fine on the target.

KM