Why doesn't my Embedded XP image make use of IRQs beyond 15?

[Bill Allen]

I can't seem to convince my Embedded XP image to allow or assign IRQ
resources beyond the traditional 0-15. My XP Pro images readily make use of
interrupts 16, 17, and 18 when allocating hardware resources to devices, but
my Embedded XP image would rather deny resources to devices, leaving them
non-functional, than assign IRQ16 and beyond. What components or settings am
I missing?

 

[Mark K Vallevand]

I think you need to select the APIC computer. I don't have XPe available
right now, so I can't check anything. But, I remember 'standard' and 'APIC'
computer components. I think. Maybe.

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.

 

[Mark K Vallevand]

I think I meant ACPI.

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.

 

[Bill Allen]

Thanks for the reply. I have already included the " Advanced Configuration
and Power Interface (ACPI) PC" component in my image, so I suspect the cause
of my problem involves some other component/components.

 

[thomas.mayr]

Hello Bill,
Did you find a solution ? Because I have the same problem and I found
no solution up to now.
I installed XP prof. on the board and APIC works. Then I created a XP
embedded image ( with tap.exe - APIC component is also included !)
and APIC doesnt work !?
The only strange thing that I found is: In Target Designer, the
component "Advanced programmable interrupt controller" has the size of
0 KB !?

regards,
Tom

 

[Bill Allen]

Tom:

The solution for me was to remove the "Advanced Configuration and Power
Interface (ACPI) PC" component and substitute the ""Microsoft ACPI-Compliant
System" component. On re-build, everything was hunky-dory. Hope this helps.

Bill Allen

 

[mtb68]

Thank you Bill for your fast response and your usefull hint.
I removed "Advanced Configuration and Power Interface (ACPI) PC" component"
and add "ACPI-Uniprocessor PC" (it doesnt work without a "Base" PC component
!) and now it works !!

regards,
Tom