ACPI Uniprocessor vs Advanced Config and Power Interface PC

[Darren]

I've got an image I have included 3 sld's (converted from
pmq's created using tap.exe) into. They are all from MSI
motherboards (MS661FM-l, MSI651ML, and MSI650ML). The
MSI651ML includes the Advanced Config and Power Interface
PC component. The other 2 use the ACPI Uniprocessor
component. I'm not sure what either one does, but if
both are active, they conflict. My goal is to build one
image that will work with all 3 mobos. Is this
possible? How can I get the two components to play nice
together?

-Thanks

 

[KM]

Darren,

Recommended way: if your platforms are supported by different HAL components (it seems to be the case as you mentioned the PC
components), they cannot be supported by one XPe image. You will need to create different images to support the motherboards.

Needs testing: a while ago I was playing with HAL components and I recall (but I am not sure about it now and you'd need to do the
testing on your chipsets anyway) the ACPI uniprocessor is not in a conflict with the Advanced Config Power Interface PC component. I
haven't run those components in the same image through FBA but I switched the Dlls by using boot.ini's /HAL option. You can try the
same trick and see how it works for your platforms.

In any case, TD will error out if you include different HAL components from XPe Repository into your image. You will need to create
your own "HAL components" (which just includes the hal Dlls).

 

[Guest]

KM,
Thanks for the reply. We actually purchase our XP
licenses from your company. Imagine that Anywho,
I am interested in your second method of "same image
through FBA but I switched the Dlls by using
boot.ini's /HAL option". Is there anyway we can open a
dialogue via email([email protected])?

The problem I have with XPe is this. I came across XPe
when I was tasked with turning XP Pro into a kiosk. I
decided XPe would suit our needs better (obviously before
I knew more about XPe). Our systems are built on an x86
platform. We purchase and build our own pc's in house.
Every four months or so, mobo companies change their
boards. So, every four months or so I have to build
another image. This becomes a tech support nightmare.
Microsoft had to take this into consideration when
designing XPe.

If you have some time, I like to talk with you. No
offense to BSquare, but they seem to spend more time with
CE than XPe.
-Darren

-----Original Message-----
Darren,

Recommended way: if your platforms are supported by

different HAL components (it seems to be the case as you
mentioned the PC

components), they cannot be supported by one XPe image.

You will need to create different images to support the
motherboards.

Needs testing: a while ago I was playing with HAL

components and I recall (but I am not sure about it now
and you'd need to do the

testing on your chipsets anyway) the ACPI uniprocessor

is not in a conflict with the Advanced Config Power
Interface PC component. I

haven't run those components in the same image through

FBA but I switched the Dlls by using boot.ini's /HAL
option. You can try the

same trick and see how it works for your platforms.

In any case, TD will error out if you include different

HAL components from XPe Repository into your image. You
will need to create

 

[Slobodan Brcin \(eMVP\)]

Hi Daren,

Few weeks ago there has been discussion between Konstantin and me about this
topic. You can find in this thread how to make image that will universally
support all previous and new hardware without using and going trough TAP
steps just by adding new driver files.

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=OSZmtlSC
EHA.1544%40TK2MSFTNGP09.phx.gbl&rnum=10&prev=/groups%3Fq%3DKonstantin%2BSlob
odan%2Bgroup:microsoft.public.windowsxp.embedded.*%26hl%3Den%26lr%3D%26ie%3D
UTF-8%26oe%3DUTF-8%26group%3Dmicrosoft.public.windowsxp.embedded.*%26scoring
%3Dd%26selm%3DOSZmtlSCEHA.1544%2540TK2MSFTNGP09.phx.gbl%26rnum%3D10


This is something how we do it in our company as well, small series that
must work on different platforms, but since we use multiprocessor ACPI only
devices then at least I don't have to worry about different HAL.

You can try to use "Standard PC" component for base hal support.

And make your component to copy files like "halacpi.dll, halaacpi.dll,
halmacpi.dll" with that names (without changing names to system32 folder)
for complete list you should see file hal.inf

My guess is that since it is described in hal.inf file XPe during the FBA
will detect and copy appropriate hal file to hal.dll.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[KM]

Darren,

I can open the a dialogue via email. No problem.
However, right now I have nothing to add to my previous and Slobodan's posts.
Basically, the test I did was similar to this: I made a few components that brought up driver specific files (inf, binaries) to the
image under appropriate directories. Then I also made a component to bring all the HALs in to the image. And played with boot.ini
switch.
The good thing is that you CAN have Standard PC HAL and ACPI HAL (for example) in the same image (I could even see both HALS
registered in the Device Manager). My machine was ACPI compatible. The same was for ACPI and ACPI Uniprocessor (but here I don't
recall it precisely).

You can read about the HAL switch here http://www.sysinternals.com/ntw2k/info/bootini.shtml.
Again, keep in mind that switching HALs is NOT recommended (and most of times "not working") solution.

Feel free to shoot me an email to konstmor@nospam_hotmail.com if you need more help.