ACPI, Standard PC collision

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@nospam_yahoo.com> wrote in message
news:OGEbVosVHHA.4828@TK2MSFTNGP05.phx.gbl...

> 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

>
>

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@nospam_yahoo.com> wrote in message news:OGEbVosVHHA.4828@TK2MSFTNGP05.phx.gbl...

>> 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

>>
>>

>
>

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@nospam_yahoo.com> wrote in message
news:uHvdw7sVHHA.5068@TK2MSFTNGP03.phx.gbl...

> 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@nospam_yahoo.com> wrote in message
>> news:OGEbVosVHHA.4828@TK2MSFTNGP05.phx.gbl...

>>> 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
>>>
>>>

>>
>>

>
>

I got the dependency checker to pass after deleting all the Standard PC and
associated dependents...

Now I am getting a ton of errors related to not finding files...here is a
sample of my log file:

/////////////////////////////////////////////////////////////////////
// configuration file: InfEmXPCtrlr.slx
// purpose: Microsoft Target Designer boot image build log
// created: 02/22/2007 03:25 PM
/////////////////////////////////////////////////////////////////////

Performing a dependency check...

Dependency check has been completed.

Emptying image folder...

Image folder has been emptied.

Successfully cleared the destination folder: C:\Windows Embedded Images\.
R:
Starting run-time build at: 2/22/2007 3:29:07 PM...
R: Building: "Base Component [Version 5.1.2600, R2010]"...
R: Building: "Base Performance Counters [Version 5.1.2600.2180, R2890]"...
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"perfos.dll"
R: Error 1005: File not found: "perfos.dll"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"perfproc.dll"
R: Error 1005: File not found: "perfproc.dll"
R: Building: "Base Support Binaries [Version 5.1.2600.2180, R2890]"...
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"wextract.exe"
R: Error 1005: File not found: "wextract.exe"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"extrac32.exe"
R: Error 1005: File not found: "extrac32.exe"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"diantz.exe"
R: Error 1005: File not found: "diantz.exe"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"packager.exe"
R: Error 1005: File not found: "packager.exe"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"grpconv.exe"
R: Error 1005: File not found: "grpconv.exe"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"msidle.dll"
R: Error 1005: File not found: "msidle.dll"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"makecab.exe"
R: Error 1005: File not found: "makecab.exe"
R: Building: "Basic TCP/IP Networking [Version 5.1.2600.2180, R2890]"...
R: Building: "BDA IPSink [Version 5.1.2600, R620]"...
R: Building: "BDA MPE Filter [Version 5.1.2600, R620]"...
R: Building: "BDA Slip De-Framer [Version 5.1.2600, R620]"...
R: Building: "Beep Driver [Version 5.1.2600, R620]"...
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"beep.sys"
R: Error 1005: File not found: "beep.sys"
R: Building: "Bluetooth Device (Personal Area Network) [Version
5.1.2600.2180, R2890]"...
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"bthpan.inf"
R: Error 1005: File not found: "bthpan.inf"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"bthpan.sys"
R: Error 1005: File not found: "bthpan.sys"
R: Building: "Bluetooth Device (RFCOMM Protocol TDI) [Version 5.1.2600.2180,
R2890]"...
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"tdibth.inf"
R: Error 1005: File not found: "tdibth.inf"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"rfcomm.sys"
R: Error 1005: File not found: "rfcomm.sys"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"BthEnum.sys"
R: Error 1005: File not found: "BthEnum.sys"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"wshBth.dll"
R: Error 1005: File not found: "wshBth.dll"
R: Building: "Bluetooth File Transfer [Version 5.1.2600.2180, R2890]"...
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"fsquirt.exe"
R: Error 1005: File not found: "fsquirt.exe"
R: Building: "Bluetooth HID Device [Version 5.1.2600.2180, R2890]"...
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"input.inf"
R: Error 1005: File not found: "input.inf"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"hidserv.inf"
R: Error 1005: File not found: "hidserv.inf"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"hidusb.sys"
R: Error 1005: File not found: "hidusb.sys"
Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"hidbth.inf"
R: Error 1005: File not found: "hidbth.inf"




"Albert Gomez" <albertg@qualitau.com> wrote in message
news:uBN%23UBtVHHA.1636@TK2MSFTNGP02.phx.gbl...

> 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@nospam_yahoo.com> wrote in message
> news:uHvdw7sVHHA.5068@TK2MSFTNGP03.phx.gbl...

>> 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@nospam_yahoo.com> wrote in message
>>> news:OGEbVosVHHA.4828@TK2MSFTNGP05.phx.gbl...
>>>> 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
>>>>
>>>>
>>>
>>>

>>
>>

>
>

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@nospam_yahoo.com> wrote in message news:uHvdw7sVHHA.5068@TK2MSFTNGP03.phx.gbl...

>> 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@nospam_yahoo.com> wrote in message news:OGEbVosVHHA.4828@TK2MSFTNGP05.phx.gbl...
>>>> 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
>>>>
>>>>
>>>
>>>

>>
>>

>
>

Albert,

A few tips here:
- Please make sure the WSH (Windows Script Host) engine is the latest on your 2K OS install. The v5.6 is the latest there, I
think.
- Try upgrading the dev OS to XP (SP2). the toolkit works fine there.
- Turn off/disable/uninstall any AV software you might be running on your development station.

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

>I got the dependency checker to pass after deleting all the Standard PC and associated dependents...
>
> Now I am getting a ton of errors related to not finding files...here is a sample of my log file:
>
> /////////////////////////////////////////////////////////////////////
> // configuration file: InfEmXPCtrlr.slx
> // purpose: Microsoft Target Designer boot image build log
> // created: 02/22/2007 03:25 PM
> /////////////////////////////////////////////////////////////////////
>
> Performing a dependency check...
>
> Dependency check has been completed.
>
> Emptying image folder...
>
> Image folder has been emptied.
>
> Successfully cleared the destination folder: C:\Windows Embedded Images\.
> R:
> Starting run-time build at: 2/22/2007 3:29:07 PM...
> R: Building: "Base Component [Version 5.1.2600, R2010]"...
> R: Building: "Base Performance Counters [Version 5.1.2600.2180, R2890]"...
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "perfos.dll"
> R: Error 1005: File not found: "perfos.dll"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "perfproc.dll"
> R: Error 1005: File not found: "perfproc.dll"
> R: Building: "Base Support Binaries [Version 5.1.2600.2180, R2890]"...
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "wextract.exe"
> R: Error 1005: File not found: "wextract.exe"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "extrac32.exe"
> R: Error 1005: File not found: "extrac32.exe"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "diantz.exe"
> R: Error 1005: File not found: "diantz.exe"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "packager.exe"
> R: Error 1005: File not found: "packager.exe"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "grpconv.exe"
> R: Error 1005: File not found: "grpconv.exe"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "msidle.dll"
> R: Error 1005: File not found: "msidle.dll"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "makecab.exe"
> R: Error 1005: File not found: "makecab.exe"
> R: Building: "Basic TCP/IP Networking [Version 5.1.2600.2180, R2890]"...
> R: Building: "BDA IPSink [Version 5.1.2600, R620]"...
> R: Building: "BDA MPE Filter [Version 5.1.2600, R620]"...
> R: Building: "BDA Slip De-Framer [Version 5.1.2600, R620]"...
> R: Building: "Beep Driver [Version 5.1.2600, R620]"...
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "beep.sys"
> R: Error 1005: File not found: "beep.sys"
> R: Building: "Bluetooth Device (Personal Area Network) [Version 5.1.2600.2180, R2890]"...
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "bthpan.inf"
> R: Error 1005: File not found: "bthpan.inf"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "bthpan.sys"
> R: Error 1005: File not found: "bthpan.sys"
> R: Building: "Bluetooth Device (RFCOMM Protocol TDI) [Version 5.1.2600.2180, R2890]"...
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "tdibth.inf"
> R: Error 1005: File not found: "tdibth.inf"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "rfcomm.sys"
> R: Error 1005: File not found: "rfcomm.sys"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "BthEnum.sys"
> R: Error 1005: File not found: "BthEnum.sys"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "wshBth.dll"
> R: Error 1005: File not found: "wshBth.dll"
> R: Building: "Bluetooth File Transfer [Version 5.1.2600.2180, R2890]"...
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "fsquirt.exe"
> R: Error 1005: File not found: "fsquirt.exe"
> R: Building: "Bluetooth HID Device [Version 5.1.2600.2180, R2890]"...
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "input.inf"
> R: Error 1005: File not found: "input.inf"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "hidserv.inf"
> R: Error 1005: File not found: "hidserv.inf"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "hidusb.sys"
> R: Error 1005: File not found: "hidusb.sys"
> Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found: "hidbth.inf"
> R: Error 1005: File not found: "hidbth.inf"
>
>
>
>
> "Albert Gomez" <albertg@qualitau.com> wrote in message news:uBN%23UBtVHHA.1636@TK2MSFTNGP02.phx.gbl...

>> 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@nospam_yahoo.com> wrote in message news:uHvdw7sVHHA.5068@TK2MSFTNGP03.phx.gbl...

>>> 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@nospam_yahoo.com> wrote in message news:OGEbVosVHHA.4828@TK2MSFTNGP05.phx.gbl...
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>

>>
>>

>
>

Thanks for your help KM...I am finding I have installation issues as
well...I am going to focus on them for now. I will make another attempt
soon.
Thanks,
Albert
"KM" <konstmor@nospam_yahoo.com> wrote in message
news:OMtqnFuVHHA.5108@TK2MSFTNGP06.phx.gbl...

> 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@nospam_yahoo.com> wrote in message
>> news:uHvdw7sVHHA.5068@TK2MSFTNGP03.phx.gbl...

>>> 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@nospam_yahoo.com> wrote in message
>>>> news:OGEbVosVHHA.4828@TK2MSFTNGP05.phx.gbl...
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>

>>
>>

>
>