IMAGEX WINPE HAL ERROR > Deployment Forum Community Forums

Wednesday, January 07, 2009

Library

Resources

Community

About

Community » Forums

Member Login

StandardLiveID

User Name:

Password:

Remember Login

Forgot Password ?


Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Unanswered Active Topics

Forums Search

Subject: IMAGEX WINPE HAL ERROR

Prev Next

You are not authorized to post a reply.

Author

Messages

indigo6

Posts:8

03/06/2008 6:40 AM
Hi All, I have just taken and image from a Dell755 that had been syspreped with mass storage drivers included. (I took the image using gimagex.exe and booting to winpe 2.0 CD) The source pc is xpsp2. The image applied fine but now when i boot the pc i get an error about HAL.dll missing Can anyone shed any light on this? thanks

Pyrosoft

Posts:48

03/09/2008 11:12 AM
Create a .reg file with the following HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\ALIGNMENT LessThan4GB REG_DWORD 0 Between4_8GB REG_DWORD 0 Between8_32GB REG_DWORD 0 GreaterThan32GB REG_DWORD 0 Before you apply the image set PE to load that .reg file. Then clean the drive with format c: /q/y Then set the boot sector using bootsect /nt52 c: Let us know how it goes

indigo6

Posts:8

03/12/2008 8:55 AM
thanks kindly for your reply! i was starting to think no one was here to help i will try this...can you explain it to me though and tell me why you think its neccesary as i had no idea i would ever have to do something like that just to get an image to apply to the same hardware model. once i understand it fully i will implement it straight away thanks again indigo

YIMA

Posts:11

03/13/2008 8:35 AM
Indigo6: It's known as the the 'Uberbug'. In a nutshell, WinPE is based on the Vista boot.wim, and the way it format hard drives will not allow XP to function properly. So the registry entry above is added to the WinPE environment during run-time, telling it how to format the PC so the XP image can be installed on it without issues. If you look at the BSOD message on your screen it will have a blurb about "unmountable volume". Cheers. YIMA.

indigo6

Posts:8

03/13/2008 10:11 AM
right, thanks. However i dont get a BSOD i get a normal blak background with dos style text error. basically a boot a error regarding missing or corrupt HAl file. i presume i can double click a reg file in PE as normal and then format drive as mentioned above then run the bootsect command and then finally apply the image... thanks,

FarmerPete User is Offline

Posts:168

04/07/2008 1:34 PM
Are you trying to do anything special with the HALs? If not, you may want to do an offline edit on your WIM file and replace the Hal.dll file.

indigo6

Posts:8

04/07/2008 4:16 PM
thanks for the reply, I have now solved the error. it was down to the Uberbug as others have stated i had to created a reg file and run it before using diskpart then prep the drive using diskpart AND then run bootsect AND then image the drive etc...guess what it worked! if you read my orginal post you will see that the HAL is fine as i used ghost image from the same souce pc and it was fine this is how i new that it must be something with winpe environment. a very useful lesson since then i have written a complete 'how to' on this subject as i think that other can rally beneft from my experiences here. I went to a live MS conference on using winpe and boy they didnt tell us that it was this hard but now i have it working it does seem easy. anyway i will post my stuff when im back from holiday. im in the dominican republic right now! cheers indigo

FarmerPete User is Offline

Posts:168

04/08/2008 9:35 AM
I was just checking about updating HALs as I personally use a HAL replacement script. The script works fine 90% of the time, but on one image, it goes nuts when it is imaged onto a system that uses the SAME hal as the imaged system was. Thus I had to make an exclusion on the task sequence to not run on a few models. It does make me laugh that I can turn a ACPI MultiPC image into anything I want except a ACPI MultiPC HAL using my script.

Pyrosoft

Posts:48

05/01/2008 2:00 AM
If you add this ComputerType="Advanced Configuration and Power Interface (ACPI) PC" to your unattend.txt then it will force it to come out as ACPI when you build the reference image, this can be applied to any hardware (Uni or Multi) if you need it to boot up, and when you come to use the script it'll always have something to upgrade

You are not authorized to post a reply.

Forums > Related Technologies > Windows Preinstallation Environment > IMAGEX WINPE HAL ERROR

ActiveForums 3.7

Forum Policies

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.

Privacy Statement | Terms Of Use