[IcemanND]

what happens if you do nothing iwth the hal, at least when putting on another uniprocessor hal system or on a MP hal system? Nothing should have to be done in either case. If it goes back to the ACPI hal then you would have to change it.

[lkeneston]

If i leave it, the hal used when building is used, which is uni, i guess i could do that then just change the hal after manually, but thats too much for some of our staff.

[_jd_]

Moments ago I built an XPP SP2-based sysprep image on an Intel P4 non-HT system, which is identified in Device Manager as "ACPI Uniprocessor PC". I then restored the image on an Intel P4 HT system, rebooted, let mini-setup complete and the PC rebooted without hitting safe mode. When I login I see a message re: "Windows has finished installing new devices... restart... yes|no". If I check device manager "APCI Multiprocessor PC" is listed. I've used none of the HAL-related entries in sysprep.inf, no magic with cmdlines.txt to detect/replace the HAL and did not call sysprep w/ the -pnp switch. As far as i can see, mini-setup was able to detect and install the appropriate HAL, which is the behaviour I would expect in your case if the image was built on an "ACPI Uniprocessor PC" system, such as the Dell D810. I have no idea why you're seeing the behaviour you're reporting...

[IcemanND]

what _JD_ see's is what I have experienced. when starting with a UP HAL and going to the MP HAL it is installed automatically at the first full boot.

[lkeneston]

i wanna say i tried that and it hung on boot up, but i can't remember, i'll try again, and let you, thats a good start, Thanks..

[lkeneston]

ok, takes a bit but it boots up, but it uses the hal shows Advanced Configuration and Power Interface (ACPI) PC, It won't auto detect the mp hal

[lkeneston]

ok, now i tried the original image i had that hung when i chose the mp hal,
i chose nothing and it loaded the Advanced Configuration and Power Interface (ACPI) PC,
However, when i went to computer in device manager and clicked roll back, the machine rebooted came up found the mp hal, then rebooted again, all is good as per

http://www.msfn.org/board/index.php?act=ST...=70&t=27202

Now the question is can i roll it back from a script? after first reboot?

[_jd_]

lkeneston, on Oct 9 2006, 07:50 PM, said:

ok, takes a bit but it boots up, but it uses the hal shows Advanced Configuration and Power Interface (ACPI) PC, It won't auto detect the mp hal

Did you dump a new sysprep image that excluded your HAL selection scripts or re-use the existing image and simply bypassed your HAL selection script? If you built a new image, on which system did you build the new image? Which system did you restore it the image to?

[lkeneston]

I still used the script but bypassed it, but then I changed it again, I created a folder called hals in the system32, then created 2 copies of each hal like this HALACPIa, HALACPIb, a is for desktops, b is for laptops in the script,in each of those directories is the perspective hal files. When you chose a machine before mini setup ends it creates a runonce that runs a batch file on first boot up that manually replaces all the hal files, when it is done it actually asks to reboot, I tried it on 2 separate machines, now that I have those batch files a and b I can add install scripts that can differ from machine or desktop vs. laptop.
I work nights tonight but I’ll post the .reg, and bat files to show you.

This post has been edited by lkeneston: 10 October 2006 - 10:48 AM

[lkeneston]

Example

Attached File(s)

•  pickhal.txt (1.17K)
  Number of downloads: 22
•  HALMACPIb.txt (262bytes)
  Number of downloads: 23
•  HALMACPIb.reg.txt (334bytes)
  Number of downloads: 20

[_jd_]

I'm out of ideas. My sysprep images are built on a P4 non-HT system that's detected as an "ACPI Uniprocessor PC". These images can be applied without issue on P4 HT or Core Duo system, both are properly detected as an "ACPI Multiprocessor PC" after mini-setup. The only thing i've done is add "UpdateUPHAL=ACPIAPIC_MP,%WINDIR%\Inf\hal.inf" to my sysprep.inf file to make the installation of the proper HAL cleaner, otherwise I get a prompt on the first login re: finalizing installation of the proper HAL. No other magic has been done...

[lkeneston]

Well it's working now, and i'm tired of working on it right now ;}
Your idea seems to be the way to go if i only had 2 different hals, once we get rid of some of the older boxes i'll have that chance i guess.
I appreciate the assistance.

[jalarson]

lkeneston, on Oct 11 2006, 12:36 PM, said:

Well it's working now, and i'm tired of working on it right now ;}
Your idea seems to be the way to go if i only had 2 different hals, once we get rid of some of the older boxes i'll have that chance i guess.
I appreciate the assistance.

lkeneston

A couple of quick questions for you:

Where are you generating your files from that get copied over in the .bat file specifically the hal.inf and the ntkernal files?

and

Are you running this in cmdlines.txt or guirunonce?

Thanks,

Jay