Re: ACPI, Standard PC collision

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Albert,

Looking at the manufacturer manual should help you understanding whether particular feature is supported by hardware.

But regardless, you are building an embedded image. Which means you are defining the feature you want to support on the target from
software standpoint. You don't necessarily have to bring in the support for CompactPCI unless your final device specs say so.

When you remove that component you again can see who is trying to bring it back in.
When I have doubts about some components and their dependencies (looking at the hardware docs is certainly option #1) I often
explore dependencies with:
- Dependency Explorer tool (part of XPeTools package on www.xpefiles.com)
- turning off auto-resolve dependency option in TD and just manually resolve the dependency stack. You can have the
auto-resolver to do the first dependency check (dirty job) and then remove some components you don't need, turn off the
auto-resolver and start exploring what the dependency checker is trying to pull in.

--
=========
Regards,
KM

KM,
I did run TAP and I am using the imported device object in Target Designer.

I am using a Dell PowerEdge 860 with a P4 2.66Ghz CPU, 768mb ram. I am not sure if it supports Compact PCI.

I have tried removing it, but it leads to a host of other errors. I will back up the image and try doing this again...
Albert


"KM" <konstmor@xxxxxxxxxxxxxxxx> wrote in message news:uHvdw7sVHHA.5068@xxxxxxxxxxxxxxxxxxxxxxx
Albert,

How did you get hat component in your runtime? Did you use TAP on the target (dev) machine to import and include required
platform components?
Does your hardware really support CompactPCI?

If not, try removing CompactPCI and see if some other component is trying to pull it in back.

If that component appears to be your platform macro (the TAP imported result), you can always disable that dependency there
(assuming you selected "Selector Prototype" as the prototype for the platform macro component in CD).

--
=========
Regards,
KM

KM,
It appears to be the following object:

Component: "Generic CompactPCI CPU board[Version 5.1.2600.1106, R1507]" requires at least one additional enabled component not
in the configuration

After I removed all other ACPI and standard PC objects, the above object gave me an error requiring the need for the Standard PC
object. All the other components called for ACPI object.

I am currently using a dual boot setup with windows 2000...the windows 2000 device manager uses the ACPI Uniprocessor PC.
Albet

"KM" <konstmor@xxxxxxxxxxxxxxxx> wrote in message news:OGEbVosVHHA.4828@xxxxxxxxxxxxxxxxxxxxxxx
Albert,

You should analyze (or at least let us know here) what components in your config are trying to pull in the Standard PC HAL.
Some of macro components (WinLogon macro, etc.) will try to include that HAL unless you clear the appropriate checkbox on the
macro component settings page.

If you target is ACPI one processor PC the ACPI Uniprocessor PC is the AAHL you'd want to use if you were to leverage the HAL
features of the hardware. It makes sense to switch to Standard PC HAL only in some very rare cases such as you don't need ACPI
features, you want to turn off some enhanced power management or you want to create an image to target multiple platforms with
different HAL.

--
=========
Regards,
KM

I keep getting the following error:

Error 1106: Multiple active components collision between: "ACPI Uniprocessor PC [Version 5.1.2600.2180, R2890]" and:
"Standard PC [Version 5.1.2600.2180, R2890]"

I have tried removing the components that require the standard PC object, but it leads to many more problems. I know the
system uses ACPI Uniprocessor PC object, but have no idea why some components are requiring the Standard PC object.

Is there an easier way to resolve this issue? It seems to me that the ACPI Uniprocessor PC object should satisfy any
requirements for the Standard PC object...is this correct?
Albert










.

Relevant Pages

  • Re: Common Control Libraries
    ... Is it possible that dependencies are differents when we have Standard ... PC configuration instead of ACPI Uniprocessor PC configuration? ... the dependency I stated about storprop is probably ... For example, in the ACPI Uniprocessor PC configuration, the Windows ...
    (microsoft.public.windowsxp.embedded)
  • Re: ACPI, Standard PC collision
    ... I did run TAP and I am using the imported device object in Target Designer. ... (assuming you selected "Selector Prototype" as the prototype for the platform macro component in CD). ... After I removed all other ACPI and standard PC objects, the above object gave me an error requiring the need for the Standard ... If you target is ACPI one processor PC the ACPI Uniprocessor PC is the AAHL you'd want to use if you were to leverage the HAL ...
    (microsoft.public.windowsxp.embedded)
  • Re: ACPI, Standard PC collision
    ... Dependency Explorer tool (part of XPeTools package on ... If that component appears to be your platform macro (the TAP imported ... object gave me an error requiring the need for the Standard PC object. ... All the other components called for ACPI object. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Standalone VB exe
    ... libraries or components and so that it uses nothing other than the ... standard Dependency File and it tells me that my program requires a ... The exe does run fine as a "stand alone exe" on all ... standard VB6 project with just a few bits of code and create a Dependency ...
    (microsoft.public.vb.general.discussion)
  • Re: ACPI, Standard PC collision
    ... If that component appears to be your platform macro, you can always disable that dependency there ... After I removed all other ACPI and standard PC objects, the above object gave me an error requiring the need for the Standard PC ... If you target is ACPI one processor PC the ACPI Uniprocessor PC is the AAHL you'd want to use if you were to leverage the HAL ...
    (microsoft.public.windowsxp.embedded)