Discussion:
Understanding Windows XP HAL replacement
(too old to reply)
Erik Droszcz
2009-02-10 08:34:01 UTC
Permalink
Hi,

So far when I have created my reference image (in VMWare) it has been set to
ACPI Uniprocessor PC when I run Sysprep. In my Sysprep.inf I have no settings
under [Unattended] that has to do with HAL. So far I think it has been
working well, I think.

But how do I know if the HAL would be wrong at a computer where I deployed
my image? Would the computer not boot at all? Or what common issues can one
see on a computer with incorrect HAL type?

Now I thought I should update my reference image with Johan’s HAL
replacement script. But there are a couple of things I don't really
understand.

First off I want to make sure I get the correct files copied to
C:\Drivers\UniProcHAL

halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?

ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?

ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?

Next thing I am wondering about is how Sysprep.inf is used when deploying my
captured reference image. Even if MDT updates the Sysprep.inf during
deployment I though Sysprep.inf only was used when running Sysprep.exe to
seal the image? But is it first used when sealing the image, and then used
again when the reference image is deployed and the target computer boots into
mini setup?

I guess what I am trying to figure out is when are the changes that
Z-HalDetect.wsf does to Sysprep.inf during deployment of the reference image
actually used by Windows XP?

I would really appreciate your help to get my thoughts on HAL replacement
straightened out :)

Regards Erik
DaveMills
2009-02-11 00:27:30 UTC
Permalink
On Tue, 10 Feb 2009 00:34:01 -0800, Erik Droszcz
Post by Erik Droszcz
Hi,
So far when I have created my reference image (in VMWare) it has been set to
ACPI Uniprocessor PC when I run Sysprep. In my Sysprep.inf I have no settings
under [Unattended] that has to do with HAL. So far I think it has been
working well, I think.
But how do I know if the HAL would be wrong at a computer where I deployed
my image? Would the computer not boot at all? Or what common issues can one
see on a computer with incorrect HAL type?
Usually BSOD, but in my experience WDS does not even list incompatible HAL's as
an image that can be deployed.
Post by Erik Droszcz
Now I thought I should update my reference image with Johan’s HAL
replacement script. But there are a couple of things I don't really
understand.
First off I want to make sure I get the correct files copied to
C:\Drivers\UniProcHAL
halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?
ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
Next thing I am wondering about is how Sysprep.inf is used when deploying my
captured reference image. Even if MDT updates the Sysprep.inf during
deployment I though Sysprep.inf only was used when running Sysprep.exe to
seal the image? But is it first used when sealing the image, and then used
again when the reference image is deployed and the target computer boots into
mini setup?
I guess what I am trying to figure out is when are the changes that
Z-HalDetect.wsf does to Sysprep.inf during deployment of the reference image
actually used by Windows XP?
I would really appreciate your help to get my thoughts on HAL replacement
straightened out :)
Regards Erik
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
Erik Droszcz
2009-02-17 19:01:14 UTC
Permalink
Johan, any chance you could help me out :) ?

Regards
Erik
Post by DaveMills
On Tue, 10 Feb 2009 00:34:01 -0800, Erik Droszcz
Post by Erik Droszcz
Hi,
So far when I have created my reference image (in VMWare) it has been set to
ACPI Uniprocessor PC when I run Sysprep. In my Sysprep.inf I have no settings
under [Unattended] that has to do with HAL. So far I think it has been
working well, I think.
But how do I know if the HAL would be wrong at a computer where I deployed
my image? Would the computer not boot at all? Or what common issues can one
see on a computer with incorrect HAL type?
Usually BSOD, but in my experience WDS does not even list incompatible HAL's as
an image that can be deployed.
Post by Erik Droszcz
Now I thought I should update my reference image with Johan’s HAL
replacement script. But there are a couple of things I don't really
understand.
First off I want to make sure I get the correct files copied to
C:\Drivers\UniProcHAL
halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?
ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
Next thing I am wondering about is how Sysprep.inf is used when deploying my
captured reference image. Even if MDT updates the Sysprep.inf during
deployment I though Sysprep.inf only was used when running Sysprep.exe to
seal the image? But is it first used when sealing the image, and then used
again when the reference image is deployed and the target computer boots into
mini setup?
I guess what I am trying to figure out is when are the changes that
Z-HalDetect.wsf does to Sysprep.inf during deployment of the reference image
actually used by Windows XP?
I would really appreciate your help to get my thoughts on HAL replacement
straightened out :)
Regards Erik
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
unknown
2009-02-17 19:47:26 UTC
Permalink
My Z-HalDetect.wsf script detects the HAL type during deployment and
makes the necessary updates to sysprep.inf (and for addressing changes
in the XP SP3 mini-setup, also add the files needed for some system to
get to the mini-setup)

The script does the following:

1. If the machine is a Advanced ACPI - Nothing
2. If the machine is a UniProc ACPI - Copy the HAL files and update
sysprep.inf
3. If the machine is a MultiProc ACPI - Copy the HAL files and update
sysprep.inf

If you onle have UniProc and MultiProc HALs, there is no need for the
script.

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com



On Tue, 17 Feb 2009 11:01:14 -0800, Erik Droszcz
Post by Erik Droszcz
Johan, any chance you could help me out :) ?
Regards
Erik
Post by DaveMills
On Tue, 10 Feb 2009 00:34:01 -0800, Erik Droszcz
Post by Erik Droszcz
Hi,
So far when I have created my reference image (in VMWare) it has been set to
ACPI Uniprocessor PC when I run Sysprep. In my Sysprep.inf I have no settings
under [Unattended] that has to do with HAL. So far I think it has been
working well, I think.
But how do I know if the HAL would be wrong at a computer where I deployed
my image? Would the computer not boot at all? Or what common issues can one
see on a computer with incorrect HAL type?
Usually BSOD, but in my experience WDS does not even list incompatible HAL's as
an image that can be deployed.
Post by Erik Droszcz
Now I thought I should update my reference image with Johan’s HAL
replacement script. But there are a couple of things I don't really
understand.
First off I want to make sure I get the correct files copied to
C:\Drivers\UniProcHAL
halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?
ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
Next thing I am wondering about is how Sysprep.inf is used when deploying my
captured reference image. Even if MDT updates the Sysprep.inf during
deployment I though Sysprep.inf only was used when running Sysprep.exe to
seal the image? But is it first used when sealing the image, and then used
again when the reference image is deployed and the target computer boots into
mini setup?
I guess what I am trying to figure out is when are the changes that
Z-HalDetect.wsf does to Sysprep.inf during deployment of the reference image
actually used by Windows XP?
I would really appreciate your help to get my thoughts on HAL replacement
straightened out :)
Regards Erik
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
Erik Droszcz
2009-02-18 11:34:01 UTC
Permalink
Thanks Johan!

I think I have a good undertanding of what the script does. But what I am
not sure of is what files I should copy and rename. I am following your
guide...

"This script assumes the following files are being present in
C:\Drivers\UniProcHAL
hal.dll (Rename from halaacpi.dll to hal.dll)
ntkrnlpa.exe
ntoskrnl.exe"

Can I grab those files from my virtual machine where I build the reference?

halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?

ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?

ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?

Regards Erik
Post by unknown
My Z-HalDetect.wsf script detects the HAL type during deployment and
makes the necessary updates to sysprep.inf (and for addressing changes
in the XP SP3 mini-setup, also add the files needed for some system to
get to the mini-setup)
1. If the machine is a Advanced ACPI - Nothing
2. If the machine is a UniProc ACPI - Copy the HAL files and update
sysprep.inf
3. If the machine is a MultiProc ACPI - Copy the HAL files and update
sysprep.inf
If you onle have UniProc and MultiProc HALs, there is no need for the
script.
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
On Tue, 17 Feb 2009 11:01:14 -0800, Erik Droszcz
Post by Erik Droszcz
Johan, any chance you could help me out :) ?
Regards
Erik
Post by DaveMills
On Tue, 10 Feb 2009 00:34:01 -0800, Erik Droszcz
Post by Erik Droszcz
Hi,
So far when I have created my reference image (in VMWare) it has been set to
ACPI Uniprocessor PC when I run Sysprep. In my Sysprep.inf I have no settings
under [Unattended] that has to do with HAL. So far I think it has been
working well, I think.
But how do I know if the HAL would be wrong at a computer where I deployed
my image? Would the computer not boot at all? Or what common issues can one
see on a computer with incorrect HAL type?
Usually BSOD, but in my experience WDS does not even list incompatible HAL's as
an image that can be deployed.
Post by Erik Droszcz
Now I thought I should update my reference image with Johan’s HAL
replacement script. But there are a couple of things I don't really
understand.
First off I want to make sure I get the correct files copied to
C:\Drivers\UniProcHAL
halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?
ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
Next thing I am wondering about is how Sysprep.inf is used when deploying my
captured reference image. Even if MDT updates the Sysprep.inf during
deployment I though Sysprep.inf only was used when running Sysprep.exe to
seal the image? But is it first used when sealing the image, and then used
again when the reference image is deployed and the target computer boots into
mini setup?
I guess what I am trying to figure out is when are the changes that
Z-HalDetect.wsf does to Sysprep.inf during deployment of the reference image
actually used by Windows XP?
I would really appreciate your help to get my thoughts on HAL replacement
straightened out :)
Regards Erik
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
unknown
2009-02-18 18:50:59 UTC
Permalink
You can grab the from a virtual machine, or fom the i386 folder...

The benefit of gather them from a live os, is that they (hopefully)
are the lastet version (pacthed)

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com


On Wed, 18 Feb 2009 03:34:01 -0800, Erik Droszcz
Post by Erik Droszcz
Thanks Johan!
I think I have a good undertanding of what the script does. But what I am
not sure of is what files I should copy and rename. I am following your
guide...
"This script assumes the following files are being present in
C:\Drivers\UniProcHAL
hal.dll (Rename from halaacpi.dll to hal.dll)
ntkrnlpa.exe
ntoskrnl.exe"
Can I grab those files from my virtual machine where I build the reference?
halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?
ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
Regards Erik
Post by unknown
My Z-HalDetect.wsf script detects the HAL type during deployment and
makes the necessary updates to sysprep.inf (and for addressing changes
in the XP SP3 mini-setup, also add the files needed for some system to
get to the mini-setup)
1. If the machine is a Advanced ACPI - Nothing
2. If the machine is a UniProc ACPI - Copy the HAL files and update
sysprep.inf
3. If the machine is a MultiProc ACPI - Copy the HAL files and update
sysprep.inf
If you onle have UniProc and MultiProc HALs, there is no need for the
script.
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
On Tue, 17 Feb 2009 11:01:14 -0800, Erik Droszcz
Post by Erik Droszcz
Johan, any chance you could help me out :) ?
Regards
Erik
Post by DaveMills
On Tue, 10 Feb 2009 00:34:01 -0800, Erik Droszcz
Post by Erik Droszcz
Hi,
So far when I have created my reference image (in VMWare) it has been set to
ACPI Uniprocessor PC when I run Sysprep. In my Sysprep.inf I have no settings
under [Unattended] that has to do with HAL. So far I think it has been
working well, I think.
But how do I know if the HAL would be wrong at a computer where I deployed
my image? Would the computer not boot at all? Or what common issues can one
see on a computer with incorrect HAL type?
Usually BSOD, but in my experience WDS does not even list incompatible HAL's as
an image that can be deployed.
Post by Erik Droszcz
Now I thought I should update my reference image with Johan’s HAL
replacement script. But there are a couple of things I don't really
understand.
First off I want to make sure I get the correct files copied to
C:\Drivers\UniProcHAL
halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?
ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
Next thing I am wondering about is how Sysprep.inf is used when deploying my
captured reference image. Even if MDT updates the Sysprep.inf during
deployment I though Sysprep.inf only was used when running Sysprep.exe to
seal the image? But is it first used when sealing the image, and then used
again when the reference image is deployed and the target computer boots into
mini setup?
I guess what I am trying to figure out is when are the changes that
Z-HalDetect.wsf does to Sysprep.inf during deployment of the reference image
actually used by Windows XP?
I would really appreciate your help to get my thoughts on HAL replacement
straightened out :)
Regards Erik
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
Erik Droszcz
2009-02-18 20:07:03 UTC
Permalink
Thanks alot Johan! :)

I was really hoping you would do your famous deployment seminar at TechDays
2009 here in Sweden. But it will be fun to check out your Vista Performance
Tuning session :)

Regards
Erik
Post by unknown
You can grab the from a virtual machine, or fom the i386 folder...
The benefit of gather them from a live os, is that they (hopefully)
are the lastet version (pacthed)
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
On Wed, 18 Feb 2009 03:34:01 -0800, Erik Droszcz
Post by Erik Droszcz
Thanks Johan!
I think I have a good undertanding of what the script does. But what I am
not sure of is what files I should copy and rename. I am following your
guide...
"This script assumes the following files are being present in
C:\Drivers\UniProcHAL
hal.dll (Rename from halaacpi.dll to hal.dll)
ntkrnlpa.exe
ntoskrnl.exe"
Can I grab those files from my virtual machine where I build the reference?
halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?
ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
Regards Erik
Post by unknown
My Z-HalDetect.wsf script detects the HAL type during deployment and
makes the necessary updates to sysprep.inf (and for addressing changes
in the XP SP3 mini-setup, also add the files needed for some system to
get to the mini-setup)
1. If the machine is a Advanced ACPI - Nothing
2. If the machine is a UniProc ACPI - Copy the HAL files and update
sysprep.inf
3. If the machine is a MultiProc ACPI - Copy the HAL files and update
sysprep.inf
If you onle have UniProc and MultiProc HALs, there is no need for the
script.
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com
On Tue, 17 Feb 2009 11:01:14 -0800, Erik Droszcz
Post by Erik Droszcz
Johan, any chance you could help me out :) ?
Regards
Erik
Post by DaveMills
On Tue, 10 Feb 2009 00:34:01 -0800, Erik Droszcz
Post by Erik Droszcz
Hi,
So far when I have created my reference image (in VMWare) it has been set to
ACPI Uniprocessor PC when I run Sysprep. In my Sysprep.inf I have no settings
under [Unattended] that has to do with HAL. So far I think it has been
working well, I think.
But how do I know if the HAL would be wrong at a computer where I deployed
my image? Would the computer not boot at all? Or what common issues can one
see on a computer with incorrect HAL type?
Usually BSOD, but in my experience WDS does not even list incompatible HAL's as
an image that can be deployed.
Post by Erik Droszcz
Now I thought I should update my reference image with Johan’s HAL
replacement script. But there are a couple of things I don't really
understand.
First off I want to make sure I get the correct files copied to
C:\Drivers\UniProcHAL
halaacpi.dll - is it OK to expand halaacpi.dl_ from C:\WINDOWS\source\i386
to C:\Drivers\UniProcHAL and then rename it to hal.dll?
ntkrnlpa.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
ntoskrnl.exe - is it OK to copy it from C:\WINDOWS\system32 to
C:\Drivers\UniProcHAL?
Next thing I am wondering about is how Sysprep.inf is used when deploying my
captured reference image. Even if MDT updates the Sysprep.inf during
deployment I though Sysprep.inf only was used when running Sysprep.exe to
seal the image? But is it first used when sealing the image, and then used
again when the reference image is deployed and the target computer boots into
mini setup?
I guess what I am trying to figure out is when are the changes that
Z-HalDetect.wsf does to Sysprep.inf during deployment of the reference image
actually used by Windows XP?
I would really appreciate your help to get my thoughts on HAL replacement
straightened out :)
Regards Erik
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
Loading...