Re: ACPI, Standard PC collision

Tech-Archive recommends: Speed Up your PC by fixing your registry

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: 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: ACPI, Standard PC collision
    ... I did run TAP and I am using the imported device object in Target Designer. ... If that component appears to be your platform macro (the TAP imported ... After I removed all other ACPI and standard PC objects, ...
    (microsoft.public.windowsxp.embedded)
  • Re: ACPI, Standard PC collision
    ... Performing a dependency check... ... If that component appears to be your platform macro (the TAP imported ... After I removed all other ACPI and standard PC objects, ...
    (microsoft.public.windowsxp.embedded)
  • Re: video controller vga compatible
    ... "dumppo cap" will list the capabilities of ACPI. ... It could be a registry entry, ... For the rest of the stuff, have you tried installing drivers? ... If the computer entry says "Standard PC", ...
    (microsoft.public.windowsxp.hardware)
  • Re: BIOS writing to and reading from illegal IO port
    ... I realize now that my current HAL configuration is already Advanced ... Configuration and Power Interface (ACPI) so I kinda understand why to choose ... to disable ACPI in BIOS before reinstalling as Standard PC. ...
    (microsoft.public.windowsxp.help_and_support)