Shutdown by power switch with MinLogon
Mike Warren
I have an image I am happy with except the computer will not shutdown
by pressing the power switch.
The only computer component that I can get to work without a BSOD
on boot is "Standard PC" even though XPPro uses "Advanced
Configuration and Power Interface (ACPI) PC". This may be the root of
my problem.
I have included "ACPI Power Button" and "ACPI Fixed Feature Button"
without success.
I have searched through many messages on Google Groups with the same
problem and it seems there was a bug but it is now fixed.
The problem exists with both "Command Shell" and "Task Manager Shell".
If I execute FBA.exe -shutdown the computer will not power off but displays
"It is now safe to turn off your computer" message.
I even tried adding "Disk Dump Drivers" component because someone said
that had cured the problem for him.
WinLogon images I have created previously for this same hardware have
worked correctly but too many unwanted components are pulled in if I use
WinLogon.
Does anyone have a suggestion of what to do next?
-Mike
KM
Since your BIOS supposrts ACPI, you will have to make ACPI HAL working on your image.
This will fix the power switch issue.
What BSOD you got with ACPI component in configuration?
Did you get the image built from TAP output imported?
KM
Mike Warren
> Since your BIOS supposrts ACPI, you will have to make ACPI HAL
> working on your image. This will fix the power switch issue.
Ok, that's what I thought.
> What BSOD you got with ACPI component in configuration?
0x0000007B (0xF8950528,0x0000034,0x00000000,0x00000000)
> Did you get the image built from TAP output imported?
Importing TA output causes the same error and I haven't tried TAP
since moving to Minlogon. I'll try that again.
-Mike
Slobodan Brcin (eMVP)
Make sure that you add components like:
Microsoft ACPI-Compliant System
Microsoft ACPI-Compliant Embedded Controller
Advanced programmable interrupt controller
Plug and Play Software Device Enumerator
And of course components requred to boot from your disk medium. (For disk, pci, ide controler)
This is not related to shell components but to driver components. Please give us more details of your boot medium so we might help
you. And also BSOD number error would be nice.
> If I execute FBA.exe -shutdown the computer will not power off but displays
> "It is now safe to turn off your computer" message.
ACPI kernel should help you with that. Just add single or multi processor component.
What QFE's do you use. MS fixed some power problems in new minlogon image.
Also look at how you can use WM_POWERBROADCAST on minlogon in your application to catch button press. Then you can do shutdown.
HTH,
Slobodan
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:%23OG82Ck...@TK2MSFTNGP14.phx.gbl...
Slobodan Brcin (eMVP)
This is common error:
http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr7b/default.aspx
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/search?group=microsoft.public.windowsxp.embedded&q=0x0000007b&qt_g=1&searchnow=Search+this+group
Let me know if you need more help.
Just let us know how and where is your disk connected.
Regards,
Slobodan
PS:
You can remove most non critical component for boot from TAP results. Or you can use standard drivers that will work on all devices
of certain type.
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:uoSs7ck3...@TK2MSFTNGP15.phx.gbl...
KM
>> What BSOD you got with ACPI component in configuration?
>
> 0x0000007B (0xF8950528,0x0000034,0x00000000,0x00000000)
You are missing a critical device component. Include IDE channels, PCI Bus, disk drive components (include all 3 disk components).
http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr7b/default.aspx
Or you can do a quick trick - in your current working image that is based on Standard PC HAL, disable the Standard PC component and
add ACPI one (make sure to use the proper one, you can check it with TAP output). Resolve dependencies, rebuild and re-deploy the
new image.
>> Did you get the image built from TAP output imported?
>
> Importing TA output causes the same error and I haven't tried TAP
> since moving to Minlogon. I'll try that again.
TA will provide you output that is likely missing some critical components. In my case, for instance, it was IDE Channels that TA
did not pick up.
And, of course, check :
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/search?group=microsoft.public.windowsxp.embedded&q=7B&qt_g=1
Konstantin
Mike Warren
> This is common error:
> http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr7b/default.aspx
> http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/search?group=microsoft.public.windowsxp.embedded&q=0x0000007b&qt_g=1&searchnow=Search+this+group
>
> Let me know if you need more help.
> Just let us know how and where is your disk connected.
I understand the error but all I do is swap "Standard PC" with any of the
following:
ACPI Multiprocessor PC
ACPI Uniprocessor PC
Advanced Configuration an Power Interface (ACPI) PC
Doing only this one thing causes the image to go from working correctly
except for the power switch problem to generating the BSOD on first boot.
The computer is a standard ACPI PC mainboard (AOpen) with one IDE HDD
and one IDE DVDROM drive.
I have already included all the components you mentioned in your other message.
> Make sure that you add components like:
> Microsoft ACPI-Compliant System
> Microsoft ACPI-Compliant Embedded Controller
> Advanced programmable interrupt controller
> Plug and Play Software Device Enumerator
>
> And of course components requred to boot from your disk medium. (For disk,
> pci, ide controler)
> You can remove most non critical component for boot from TAP results.
I'll try TAP again shortly.
> Or you can use standard drivers that will work on all devices of
> certain type.
This is exactly what I am trying to achieve.
Slobodan Brcin (eMVP)
Add:
- ACPI Multiprocessor PC
-Microsoft ACPI-Compliant System
-Microsoft ACPI-Compliant Embedded Controller
-Advanced programmable interrupt controller
-Plug and Play Software Device Enumerator
- All three Disk Driver components.
- Direct Memory access controler
- FAT
- FAT Format
- Motherboard resources
- Mount Manager
- Numeric Data processor.
- PCI Bus
- Both PnP components.
- Processor
- System CMOS real time clock
- Sytem timer.
- PCI standard host CPU Bridge
- PCI Standard PCI-toPCI bridge
- PCI Standard RAM controler
- Programable Interrupt controler.
- PCI Stadnard EISA bridge
- PCI Standard ISA bridge
- Standard Dual Channel PCI IDE Controller.
- Standard IDE/ESDI Hadr disk controler
HTH,
Slobodan
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:u$OOL1k3...@TK2MSFTNGP12.phx.gbl...
KM
> I understand the error but all I do is swap "Standard PC" with any of the
> following:
>
> ACPI Multiprocessor PC
> ACPI Uniprocessor PC
> Advanced Configuration an Power Interface (ACPI) PC
>
> Doing only this one thing causes the image to go from working correctly
> except for the power switch problem to generating the BSOD on first boot.
This is wierd. Especially considering the fact that you were running XP Pro on the target with ACPI HAL.
Any chance of connecting to the target with KD?
> The computer is a standard ACPI PC mainboard (AOpen) with one IDE HDD
> and one IDE DVDROM drive.
>
> I have already included all the components you mentioned in your other message.
>
>> Make sure that you add components like:
>> Microsoft ACPI-Compliant System
>> Microsoft ACPI-Compliant Embedded Controller
>> Advanced programmable interrupt controller
>> Plug and Play Software Device Enumerator
>>
>> And of course components requred to boot from your disk medium. (For disk,
>> pci, ide controler)
>
>> You can remove most non critical component for boot from TAP results.
>
> I'll try TAP again shortly.
You won't necessarily have to re-deploy the new image but rather compare the images to see what components you were missing.
And one more way to include necessary components - get TAP running on any ACPI desktop computer. Then just grab the list of
components from the output (or most important components) and implement it in your image. This may be the fastest way.
KM
Mike Warren
> Or you can do a quick trick - in your current working image that is
> based on Standard PC HAL, disable the Standard PC component and add
> ACPI one (make sure to use the proper one, you can check it with TAP
> output). Resolve dependencies, rebuild and re-deploy the new image.
That's exactly what I'm trying to do.
>>> Did you get the image built from TAP output imported?
>>
>> Importing TA output causes the same error and I haven't tried TAP
>> since moving to Minlogon. I'll try that again.
I just tried a test with TAP. I started with a blank configuration, imported
devices.pmq and resolved all dependencies. This image gives the same 7B
error. I'm now really lost. This is the procedure I originally used for testing
with SP1. I'm now using SP2.
-Mike
KM
> I just tried a test with TAP. I started with a blank configuration, imported
> devices.pmq and resolved all dependencies. This image gives the same 7B
> error. I'm now really lost. This is the procedure I originally used for testing
> with SP1. I'm now using SP2.
Do you mean SP1 TAP based image (ACPI) worked on the same target without problem?
If it is not what you meant, can you try it with SP1? Although if you don't have a separate dev machine with SP1 installed, you are
going to have to go back to SP1 on the main dev machine :-(
Also, you mentioned XP Pro.. Was it SP1 or SP2 XP Pro?
KM
Mike Warren
>> This is the procedure I originally used
>> for testing with SP1. I'm now using SP2.
>
> Do you mean SP1 TAP based image (ACPI) worked on the same target
> without problem?
Unfortunately, it wasn't very scientific. I have been just "mucking around"
with XPe while waiting for SP2. Now I've got SP2, I have to get serious.
One of my successful images was created with that procedure on SP1.
I have 3 units of our target machine here now. One has XP Pro SP1,
one is unformatted and the third one is what I'm testing with.
> If it is not what you meant, can you try it with SP1? Although if you
> don't have a separate dev machine with SP1 installed, you are going
> to have to go back to SP1 on the main dev machine :-(
Two of the components Slobodan listed were not in my image. When I added
them I was able to get past first boot but it stopped on the same 7B error on each
boot after that.
I think I'll try a simpler config starting with Slobodans list. If that doesn't work
I'll upgrade the XPPro machine to SP2 and try again.
-Mike
Slobodan Brcin (eMVP)
> Two of the components Slobodan listed were not in my image. When I added
> them I was able to get past first boot but it stopped on the same 7B error on each
> boot after that.
Which two component did help you? It might be important.
Also it is highly uncommon that after you go trough FBA your image stop booting. What disk type do you use for booting?
> I think I'll try a simpler config starting with Slobodans list. If that doesn't work
> I'll upgrade the XPPro machine to SP2 and try again.
This won't help you. XPe tools are working fine for you on SP1 so you may leave it be since it will not have an impact on XPe image
that you create.
Regards,
Slobodan
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:uCGFBIn3...@TK2MSFTNGP15.phx.gbl...
Mike Warren
>> Two of the components Slobodan listed were not in my image. When I
>> added
>> them I was able to get past first boot but it stopped on the same 7B
>> error on each boot after that.
>
> Which two component did help you? It might be important.
> Also it is highly uncommon that after you go trough FBA your image
> stop booting. What disk type do you use for booting?
Standard IDE/ESDI Hard Disk Controller
PCI Standard RAM controller
I'm using a basic IDE HDD with 2 partitions. The first partition is 500MB
and marked active. The second is about 200GB. Both are formated with
NTFS.
>> I think I'll try a simpler config starting with Slobodans list. If
>> that doesn't work I'll upgrade the XPPro machine to SP2 and try
>> again.
>
> This won't help you. XPe tools are working fine for you on SP1 so you
> may leave it be since it will not have an impact on XPe image that
> you create.
I tried this but still have the 7B error on second boot.
Here is more detail in case you can see something that will give you a clue.
Created a new config.
Added all the components on your list plus NTFS.
I then auto resolved dependencies. This required adding "Command Shell"
and "English Language Support"
I connected the target system hard drive to my dev machine through a USB/IDE
adaptor.
Performed a quick NTFS format on the 500MB partition of the target drive.
Copied the files from my image folder to the 500MB partition of the drive.
Stopped the USB/IDE adaptor.
Removed drive and fitted to target using an IDE cable directly to the motherboard.
Booted target.
-Mike
Mike Warren
> So in last attempt you did not used any of components provided by TA/TAP,
> right? This is good since you now know at least that inf files pulled by
> these components is not causing failure.
That's right.
> Also what chipset do you use. Or what platform?
It is a AOpen MX4SGI-4DN2 and uses the Intel 865G chipset.
http://asia.aopen.com.tw/Products/mb/MX4SGI-4DN2;MX4SGI-4DN2(P).htm
> Do you have an RS-232 or 1394 cable for establishing remote debugging from
> your targed machine? This would give you insight where is the problem.
> In windbg just type.
> 1. !devnode 0 1
> 2. !analyze -v
>
> And send us these results.
I have never used KD or windbg before and am having problems getting it to
work. Here are the results:
kd> !devnode 0 1
Error retrieving address of IopRootDeviceNode
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INACCESSIBLE_BOOT_DEVICE (7b)
During the initialization of the I/O system, it is possible that the driver
for the boot device failed to initialize the device that the system is
attempting to boot from, or it is possible for the file system that is
supposed to read that device to either fail its initialization or to simply
not recognize the data on the boot device as a file system structure that
it recognizes. In the former case, the argument (#1) is the address of a
Unicode string data structure that is the ARC name of the device from which
the boot was being attempted. In the latter case, the argument (#1) is the
address of the device object that could not be mounted.
If this is the initial setup of the system, then this error can occur if
the system was installed on an unsupported disk or SCSI controller. Note
that some controllers are supported only by drivers which are in the Windows
Driver Library (WDL) which requires the user to do a custom install. See
the Windows Driver Library for more information.
This error can also be caused by the installation of a new SCSI adapter or
disk controller or repartitioning the disk with the system partition. If
this is the case, on x86 systems the boot.ini file must be edited or on ARC
systems setup must be run. See the "Advanced Server System Administrator's
User Guide" for information on changing boot.ini.
If the argument is a pointer to an ARC name string, then the format of the
first two (and in this case only) longwords will be:
USHORT Length;
USHORT MaximumLength;
PWSTR Buffer;
That is, the first longword will contain something like 00800020 where 20
is the actual length of the Unicode string, and the next longword will
contain the address of buffer. This address will be in system space, so
the high order bit will be set.
If the argument is a pointer to a device object, then the format of the first
word will be:
USHORT Type;
That is, the first word will contain a 0003, where the Type code will ALWAYS
be 0003.
Note that this makes it immediately obvious whether the argument is a pointer
to an ARC name string or a device object, since a Unicode string can never
have an odd number of bytes, and a device object will always have a Type
code of 3.
Arguments:
Arg1: f8950524, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 8053771f to 804e30d9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f89500d8 8053771f 00000004 00000000 80087000 nt!DbgBreakPointWithStatus+0x4
f89504b8 80537832 0000007b f8950524 c0000034 nt!KeDeregisterBugCheckReasonCallback+0xbc8
f89504d8 806ce5b4 0000007b f8950524 c0000034 nt!KeBugCheckEx+0x1b
f8950640 806bcefb 80087000 00000000 80087000 nt!KeFindConfigurationNextEntry+0x115fd
f8950690 806b2f69 80087000 f89506ac 00034000 nt!KeFindConfigurationEntry+0x4fd2
f8950838 806b3fea 80087000 00000000 81fc8958 nt!SeTokenObjectType+0x16089
f8950dac 80576b24 80087000 00000000 00000000 nt!SeTokenObjectType+0x1710a
f8950ddc 804eed86 806b3797 80087000 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb
FOLLOWUP_IP:
nt!KeDeregisterBugCheckReasonCallback+bc8
8053771f 8b4dfc mov ecx,[ebp-0x4]
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeDeregisterBugCheckReasonCallback+bc8
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa
STACK_COMMAND: kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
KM
Did you set the symbol path?
You can set to something like :
srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
Follow instruction from thin link : http://www.microsoft.com/whdc/devtools/debugging/symbols.mspx
After the proper setup you will get more detail and readable results.
KM
Mike Warren
> Did you set the symbol path?
>
> You can set to something like :
> srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
>
> Follow instruction from thin link :
> http://www.microsoft.com/whdc/devtools/debugging/symbols.mspx After
> the proper setup you will get more detail and readable results.
Thanks, that helps. Is this any better?
kd> !devmode 0 1
No export devmode found
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INACCESSIBLE_BOOT_DEVICE (7b)
During the initialization of the I/O system, it is possible that the driver
... <snip> ...
Note that this makes it immediately obvious whether the argument is a pointer
to an ARC name string or a device object, since a Unicode string can never
have an odd number of bytes, and a device object will always have a Type
code of 3.
Arguments:
Arg1: f8950524, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 80536753 to 804e30d9
STACK_TEXT:
f895008c 80536753 00000004 ffdff408 00000000 nt!RtlpBreakWithStatusInstruction
f89500d8 8053771f 00000004 00000000 80087000 nt!KiBugCheckDebugBreak+0x19
f89504b8 80537832 0000007b f8950524 c0000034 nt!KeBugCheck2+0xa75
f89504d8 806ce5b4 0000007b f8950524 c0000034 nt!KeBugCheckEx+0x1b
f8950640 806bcefb 80087000 00000000 80087000 nt!IopMarkBootPartition+0x113
f8950690 806b2f69 80087000 f89506ac 00034000 nt!IopInitializeBootDrivers+0x4ba
f8950838 806b3fea 80087000 00000000 81fc8958 nt!IoInitSystem+0x712
f8950dac 80576b24 80087000 00000000 00000000 nt!Phase1Initialization+0xac7
f8950ddc 804eed86 806b3797 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
nt!IopMarkBootPartition+113
806ce5b4 8d85e4feffff lea eax,[ebp-0x11c]
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!IopMarkBootPartition+113
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa
STACK_COMMAND: kb
BUCKET_ID: 0x7B_nt!IopMarkBootPartition+113
Followup: MachineOwner
---------
Mike Warren
Oops,
I didn't even notice I had typed !devmode instead of !devnode.
-Mike
kd> !devnode 0 1
Dumping IopRootDeviceNode (= 0x81febdd8)
DevNode 0x81febdd8 for PDO 0x81febf10
InstancePath is "HTREE\ROOT\0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81feb8e8 for PDO 0x81feba30
InstancePath is "Root\ACPI_HAL\0000"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb0370 for PDO 0x81fea6f8
InstancePath is "ACPI_HAL\PNP0C08\0"
ServiceName is "ACPI"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fe8250 for PDO 0x81fd11b0
InstancePath is "ACPI\GenuineIntel_-_x86_Family_15_Model_3\_0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fe8130 for PDO 0x81fd41a8
InstancePath is "ACPI\PNP0C0C\2&daba3ff&0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb2258 for PDO 0x81f78e40
InstancePath is "ACPI\PNP0A03\1"
ServiceName is "pci"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f99628 for PDO 0x81fe9cb8
InstancePath is "PCI\VEN_8086&DEV_2570&SUBSYS_00000000&REV_02\3&13c0b0c5&0&00"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f99508 for PDO 0x81fe9ad8
InstancePath is "PCI\VEN_8086&DEV_2571&SUBSYS_00000000&REV_02\3&13c0b0c5&0&08"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f993e8 for PDO 0x81fe98f8
InstancePath is "PCI\VEN_8086&DEV_24D2&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&E8"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f992c8 for PDO 0x81fe95c0
InstancePath is "PCI\VEN_8086&DEV_24D4&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&E9"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f991a8 for PDO 0x81fe8e50
InstancePath is "PCI\VEN_8086&DEV_24D7&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&EA"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f98008 for PDO 0x81fe8b18
InstancePath is "PCI\VEN_8086&DEV_24DE&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&EB"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f98ee8 for PDO 0x81fe87e0
InstancePath is "PCI\VEN_8086&DEV_24DD&SUBSYS_040AA0A0&REV_02\3&13c0b0c5&0&EF"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f98dc8 for PDO 0x81fe84a8
InstancePath is "PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&13c0b0c5&0&F0"
ServiceName is "pci"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fd2ee8 for PDO 0x81fd38a0
InstancePath is "PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&1f7dbc9f&0&20F0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81fd2dc8 for PDO 0x81fd3568
InstancePath is "PCI\VEN_14F1&DEV_2F00&SUBSYS_200414F1&REV_01\4&1f7dbc9f&0&28F0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81fd2ca8 for PDO 0x81fd3230
InstancePath is "PCI\VEN_8086&DEV_1050&SUBSYS_04AFA0A0&REV_02\4&1f7dbc9f&0&40F0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81f98ca8 for PDO 0x81f78270
InstancePath is "PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&13c0b0c5&0&F8"
ServiceName is "isapnp"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f883f8 for PDO 0x81f88030
InstancePath is "ISAPNP\ReadDataPort\0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f882d8 for PDO 0x81fd2190
InstancePath is "ACPI\PNP0C02\1"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f881b8 for PDO 0x81f88f18
InstancePath is "ACPI\PNP0000\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0008 for PDO 0x81f88e00
InstancePath is "ACPI\PNP0200\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0ee8 for PDO 0x81f88ce8
InstancePath is "ACPI\PNP0100\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0dc8 for PDO 0x81f88bd0
InstancePath is "ACPI\PNP0B00\4&26dd0f47&0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fd0ca8 for PDO 0x81f88ab8
InstancePath is "ACPI\PNP0800\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0b88 for PDO 0x81f889a0
InstancePath is "ACPI\PNP0C04\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0a68 for PDO 0x81f88888
InstancePath is "ACPI\PNP0501\2"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81fd0948 for PDO 0x81f88770
InstancePath is "ACPI\PNP0400\1"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_FAILED_INSTALL
DevNode 0x81fd0828 for PDO 0x81f88658
InstancePath is "ACPI\PNP0C02\2"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fd0708 for PDO 0x81f88540
InstancePath is "ACPI\INT0800\4&26dd0f47&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f98b88 for PDO 0x81fb1e50
InstancePath is "PCI\VEN_8086&DEV_24DB&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&F9"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f98a68 for PDO 0x81fb1b18
InstancePath is "PCI\VEN_8086&DEV_24D1&SUBSYS_042EA0A0&REV_02\3&13c0b0c5&0&FA"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f98948 for PDO 0x81fb17e0
InstancePath is "PCI\VEN_8086&DEV_24D3&SUBSYS_042DA0A0&REV_02\3&13c0b0c5&0&FB"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81fb2138 for PDO 0x81fea9f0
InstancePath is "ACPI\PNP0C01\2&daba3ff&0"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81f97008 for PDO 0x81f97688
InstancePath is "ACPI\PNP0C0B\2&daba3ff&0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81f97150 for PDO 0x81fe91f0
InstancePath is "ACPI\ThermalZone\THRM"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb2ee8 for PDO 0x81fe90d8
InstancePath is "ACPI\FixedButton\2&daba3ff&0"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3ee8 for PDO 0x81fb3030
InstancePath is "Root\Ftdisk\0000"
ServiceName is "ftdisk"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3ca8 for PDO 0x81fb3df0
InstancePath is "Root\LEGACY_ACPIEC\0000"
ServiceName is "ACPIEC"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3a68 for PDO 0x81fb3bb0
InstancePath is "Root\LEGACY_KSECDD\0000"
ServiceName is "KSecDD"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3828 for PDO 0x81fb3970
InstancePath is "Root\LEGACY_MOUNTMGR\0000"
ServiceName is "MountMgr"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb35b0 for PDO 0x81fb36f8
InstancePath is "Root\LEGACY_PARTMGR\0000"
ServiceName is "PartMgr"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81fb3370 for PDO 0x81fb34b8
InstancePath is "Root\LEGACY_PCI\0000"
ServiceName is "pci"
State = DeviceNodeRemoved (0x312)
Previous State = DeviceNodeStarted (0x308)
Problem = CM_PROB_DEVICE_NOT_THERE
DevNode 0x81fb3130 for PDO 0x81fb3278
InstancePath is "Root\LEGACY_VGASAVE\0000"
ServiceName is "VgaSave"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
DevNode 0x81feaee8 for PDO 0x81fea030
InstancePath is "Root\SYSTEM\0000"
ServiceName is "swenum"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
DevNode 0x81feaca8 for PDO 0x81feadf0
InstancePath is "Root\SYSTEM\0001"
ServiceName is "update"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Slobodan Brcin (eMVP)
You should have posted this as txt file attachment, but nevertheless.
pciide did not initialized for some reason :-(
You might want to send us setupapi.log that was made during the FBA.
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/default.asp?url=/library/en-us/install/hh/install/troubleshoot_66a07114-953e-49aa-bebf-f9b4ca60a6dd.xml.asp
This all sound too strange. (Ability to pass FBA, and then in second boot XPe wont work)
Regards,
Slobodan
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:uOUeSxz3...@TK2MSFTNGP15.phx.gbl...
KM
DevNode 0x81fb3370 for PDO 0x81fb34b8
InstancePath is "Root\LEGACY_PCI\0000"
ServiceName is "pci"
State = DeviceNodeRemoved (0x312)
Previous State = DeviceNodeStarted (0x308)
Problem = CM_PROB_DEVICE_NOT_THERE
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.
If you still have similar platform running XP Pro, check what System Bus Extender is runinng there: pciide.sys or else?
KM
Mike Warren
> 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/default.asp?url=/library/en-us/install/hh/install/troubleshoot_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
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
> 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)
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
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:Oct6U$03EHA...@TK2MSFTNGP10.phx.gbl...
Slobodan Brcin (eMVP)
This is a very long shot but try going to MB manufacturer site and look for BIOS updates.
Regards,
Slobodan
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:uz%23tfO13...@tk2msftngp13.phx.gbl...
Mike Warren
> 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
> 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)
> > 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
I ment about the one from intel driver package. (But Iy should not make a 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?
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
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
>> 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 :-(
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
> 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)
Like I said look at the link:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/install/hh/install/troubleshoot_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" <miwaN...@iprimus.com.au> wrote in message news:uEIApj4...@TK2MSFTNGP12.phx.gbl...
Mike Warren
Thanks, I'll look into this.
-Mike
Mike Warren
> Like I said look at the link:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/install/hh/install/troubleshoot_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.
>> 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"
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)
Have you tried to install XPP SP2 on this computer?
Regards,
Slobodan
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:eDEoEI83...@TK2MSFTNGP12.phx.gbl...
KM
>>> 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"
FBALog.txt and SetupAPI.log again? :-)
> 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.
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
> 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)
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" <miwaN...@iprimus.com.au> wrote in message news:uydEMM93...@TK2MSFTNGP09.phx.gbl...
Mike Warren
>>>> 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"
>
> 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
>> 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.
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
Mike Warren
> 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).
I fixed the USB keyboard and mouse problem (Standard Universal PCI
to USB Host Controller was missing) and saved the pre and post FBA
images.
I then updated to XPe SP2 database and tools and built an image using
the same components. This image failed on second boot as expected.
I copied the system hive from the SP1 post FBA image and the image now
boots. It flashes up an error message about changing passwords and then
reboots itself continuously. I can understand that.
I have also tried copying all the driver binaries from the failed SP2 image
to the working SP1 image and it continued to work.
So it seems the problem is not with any new binaries but some registry
setting that is created during FBA?
> This all may appear to be a MS bug in SP2. Although it is weird that
> XPP SP2 works fine on the target.
Not so weird if it is not in any binaries.
-Mike
Mike Warren
I copied the config folder from the preFBA SP1 image to
the preFBA SP2 image.
This image failed with the 7B error on second boot. I'm confused
again.
-Mike
Slobodan Brcin (eMVP)
Can you post zip and post "system." registry file of post FBA SP2 image. I'm curious what is written by FBA under Enum branch.
Also you might try using regedit to edit this offline file and to remove all references to "installed" drivers then XPe will boot
trouhg critical DB driver entries like first time during the FBA. (This can serve you as a test to see what enties make your image
not boot)
Regads,
Slobodan
"Mike Warren" <miwaN...@iprimus.com.au> wrote in message news:OLyDamA4...@TK2MSFTNGP15.phx.gbl...
KM
> I then updated to XPe SP2 database and tools and built an image using
> the same components. This image failed on second boot as expected.
>
> I copied the system hive from the SP1 post FBA image and the image now
> boots.
Good progress.
> It flashes up an error message about changing passwords and then
> reboots itself continuously. I can understand that.
>
> I have also tried copying all the driver binaries from the failed SP2 image
> to the working SP1 image and it continued to work.
>
> So it seems the problem is not with any new binaries but some registry
> setting that is created during FBA?
>
>> This all may appear to be a MS bug in SP2. Although it is weird that
>> XPP SP2 works fine on the target.
>
> Not so weird if it is not in any binaries.
Well.. This may appear not to be a true statement. It is unknown until you find a cursed registry settings if exist.
Can you load post FBA SP1 and SP2 system hives offline (sequentially under the same key name), export them to .reg file (it wouldn't
be extremely huge file) and do a text diff between them?
Or it may be easier and smarter to just export Enum branches as you want to know about critical driver database.
Interesting to know if there appear any new subkeys in SP2 hive vs SP1's, or there are any missing ones. You can put the reg file on
your website so that we can take a look. Maybe something obvious will pop up :-)
Anyway, you are definitely narrowing problem step by step. And it means it is not a dead end.
Konstantin
Mike Warren
> Can you post zip and post "system." registry file of post FBA SP2
> image. I'm curious what is written by FBA under Enum branch.
www.cairnscarsound.com.au/temp/PostFBA-SP2-SYSTEM.zip
www.cairnscarsound.com.au/temp/PostFBA-SP1-SYSTEM.zip
I just noticed somthing in the postFBA SP2 config folder.
E:\Windows Embedded Data\SP2cPostFBA\XPE\system32\config>dir
Volume in drive E has no label.
Volume Serial Number is 645E-3AC9
Directory of E:\Windows Embedded Data\SP2cPostFBA\XPE\system32\config
12/12/2004 05:31 PM <DIR> .
12/12/2004 05:31 PM <DIR> ..
12/12/2004 02:56 PM 262,144 DEF$$$$$.DEL
12/12/2004 02:55 PM 86,016 DEFAULT
12/12/2004 05:31 PM 242,291 PostFBA-SP2-SYSTEM.zip
12/12/2004 02:55 PM 20,480 SAM
12/12/2004 02:56 PM 262,144 SAM$$$$$.DEL
12/12/2004 02:56 PM 262,144 SEC$$$$$.DEL
12/12/2004 02:55 PM 16,384 SECURITY
12/12/2004 02:56 PM 3,145,728 SOF$$$$$.DEL
12/12/2004 02:55 PM 2,961,408 SOFTWARE
12/12/2004 02:56 PM 1,048,576 SYS$$$$$.DEL
12/12/2004 02:55 PM 946,176 SYSTEM
11 File(s) 9,253,491 bytes
2 Dir(s) 14,395,068,416 bytes free
What are all the extra files?
-Mike
Mike Warren
> Can you load post FBA SP1 and SP2 system hives offline (sequentially
> under the same key name), export them to .reg file (it wouldn't be
> extremely huge file) and do a text diff between them? Or it may be easier and smarter to just
> export Enum branches as you
> want to know about critical driver database.
Wow. There's a lot of data there (and many differences) and I don't know what
I'm looking for. I'll keep looking.
> Interesting to know if there appear any new subkeys in SP2 hive vs
> SP1's, or there are any missing ones. You can put the reg file on
> your website so that we can take a look. Maybe something obvious will
> pop up :-)
See my reply to Sobodan.
> Anyway, you are definitely narrowing problem step by step. And it
> means it is not a dead end.
Really? It just seems to be getting more complicated to me :-)
-Mike
KM
Although there are a lot of differences between the hives, some things are very noticable.
Bu before we go any futher, could you do a quick sniff test? Can you replace the new SP2 swenum.sys (Plug and Play Software Device
Enumerator) by old SP1's swenum.sys in the SP2 preFBA image? Then deploy the image and let us know if it helps.
This is is just to make sure the new implementation of Device Enumerator does not cause the problem. From the PnP registry branch it
seems the system enumerates some devices differently on SP2 compared to SP1. (not just dynamic GUIDs)
Regards,
Konstantin
KM
Somehow on SP2 device enumerator does not want to recognize "Standard Dual Channel PCI IDE Controller". It knows it is a "IDE
Controller" but does not even set the right Service for it (pciide). The SP2 system just sets it up a LEGACY_PCI device.
I guess this explains the most important error of the SP2 KD log you showed us earlier (CM_PROB_DEVICE_NOT_THERE for ServiceName is
"pci").
This also may explain why:
- copying config dir from preFBA SP1 to preFBA SP2 did not help to fix the issue. The SP2 enumerator binary did not pick up the
right IDE Controller anyway.
- XP Pro SP2 worked fine on the target. The SP2 XP Pro is installed on the top of SP1 and therefore the right Enum reg.value for
the right IDE controller was already there (and that is probably how MS has tested XPP SP2).
So, I suggest one more experiment. If the SP2 *postFBA* image (the one that gets stuck on 7B BSOD), add the following reg key
content:
[HKEY_LOCAL_MACHINE\ControlSet001\Enum\PCI\VEN_8086 DEV_24DB SUBSYS_042DA0A0 REV_02\3 13c0b0c5 0 F9].
(you may replace the ControlSet001 to CurrentControlSet in this reg.path, all spaces should be replace by ampersand characters)
You may be better off exporting the reg key content from SP1 postFBA image and adding it offline to the SP2 postFBA image.
Let us know if it helps anyhow.
Konstantin
> Mike,
>
> Although there are a lot of differences between the hives, some things are very noticable.
> Bu before we go any futher, could you do a quick sniff test? Can you replace the new SP2 swenum.sys (Plug and Play Software Device
> Enumerator) by old SP1's swenum.sys in the SP2 preFBA image? Then deploy the image and let us know if it helps.
>
> This is is just to make sure the new implementation of Device Enumerator does not cause the problem. From the PnP registry branch
> it seems the system enumerates some devices differently on SP2 compared to SP1. (not just dynamic GUIDs)
>
> Regards,
> Konstantin
>
Mike
I'm posting from Google Groups as posting from Outlook Express is
rejected by the microsoft server.
Outlook Express could not post your message. Subject 'Re: Shutdown by
power switch with MinLogon', Account: 'msnews.microsoft.com', Server:
'msnews.microsoft.com', Protocol: NNTP, Server Response: '441 (629)
Article Rejected -- Ill-formed message id
'<Ok055dH4...@tk2msftngp13.phx.gb' in field 'References:'', Port:
119, Secure(SSL): No, Server Error: 441, Error Number: 0x800CCCA9
Is it me or the server?
Mike
> So, I suggest one more experiment. If the SP2 postFBA image (the
> one that gets stuck on 7B BSOD), add the following reg key content:
> [HKEY_LOCAL_MACHINE\ControlSet001\Enum\PCI\VEN_8086 DEV_24DB
> SUBSYS_042DA0A0 REV_02\3 13c0b0c5 0 F9]. (you may replace the
> ControlSet001 to CurrentControlSet in this reg.path, all spaces
> should be replace by ampersand characters) You may be better off
> exporting the reg key content from SP1 postFBA image and adding it
> offline to the SP2 postFBA image.
More ignorance on my part. How do I edit the system hive offline?
I tried loading the hive in regedit but it won't allow me to change
anything.
-Mike
sbr...@ptt.yu
Interesting I have looked at registries.
Apparently MS supported trough mshdc.inf file this part of your chipset
:-)
SP1 version of mshdc.inf file did not recognized your chipset so it was
using more generic drivers. (you might try using this inf
file in pre FBA image)
%PCI\VEN_8086&DEV_24DB.DeviceDesc%=intelide_Inst, PCI\VEN_8086&DEV_24DB
; Device ID for Intel ICH-5 (DUAL_GOOD_IDE)
In SP2 you must add at least one components that contain following
files:
intelide.sys
pciidex.sys
atapi.sys
So you might add for instance:
Component "Intel(r) 82092AA PCI IDE Controller" and then go to
component Resources and disable PnPID(819).
Try this.
Good luck,
Slobodan
sbr...@ptt.yu
First load hive (do not import it) to users group for instance.
The check access rights for your used at the key that you are
accessing. Usyaly it is limited to system. accont.
To avoid a need for changing security attributes (you can do that from
regedit and right click on key name) I'm starting regedit.exe from
system account by using my simple service.
Regards,
Slobodan
KM
Replying to the same (my) message I got the same OE error :-( But I was able to create another message (see below).
I don't know what is wrong with this particular branch :-( Wierd.
To finish investigattion about binaries, you may also want to try to replace SP2's binaries like pciide[x].sys.
KM
KM
I don't know what "special" I posted above :-)
Konstantin
KM
> More ignorance on my part. How do I edit the system hive offline?
> I tried loading the hive in regedit but it won't allow me to change
> anything.
I see Slobodan has already replied to this message of yours. So almost nothing to add to this except that to run regedit.exe under
Local System account you will need to launch a command like:
at <time> /interactive "cmd.exe"
(where set <time> to the one-two seconds ahead of the current time)
Or use runas.exe directly.
Regards,
Konstantin
Mike Warren
> In SP2 you must add at least one components that contain following
> files:
>
> intelide.sys
> pciidex.sys
> atapi.sys
>
> So you might add for instance:
> Component "Intel(r) 82092AA PCI IDE Controller" and then go to
> component Resources and disable PnPID(819).
> Try this.
Eureka!
Doing this has allowed the system to get to second boot and the system
also shuts down with the power switch. So I can confirm that the power
switch problem with MinLogon is fixed in SP2.
I will now move on to adding everything else I require and hope it all goes
smoothly.
I really appreciate the time you and Konstantin have put into solving this
for me. I am quite sure I would not have been able to do it on my own.
Regards
-Mike
KM
Great! I am glad you have finally fixed the problem :-)
This thread may be a good reference for future SP2 issues.
I have never thought about it but appearenly XPe will have some issues with SP2 as the image installation goes from zero (not from
SP1 as on XP Pro) and therefore has unlikely been tested by Microsoft as much as XPP SP2.
Regards,
Konstantin
Slobodan Brcin (eMVP)
Although not shipped on CD/DVD you can download from MSDN image of integral installation image of XPP with SP2. Also I think that it
can be bought this way as well.
Regards,
Slobodan
"KM" <konstmor@nospam_yahoo.com> wrote in message news:eE$LrmK4E...@TK2MSFTNGP12.phx.gbl...
KM
Interesting... I did not know that.
Will check it out.
Thanks for the info!
Konstantin
dso...@gmail.com
I don't think Minlogon has that feature.
Try putting Winlogon back and see whether it works.
~n
KM
Search NG archive for the thread where we discussed Minlogon, the feature and fixes for old Minlogon.
--
Regards,
KM, BSquare Corp.