• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 533
  • Last Modified:

Corrupted or missing HAL.dll after restoring a disk image.

I created a disk image for cloning purposes and when I tried to restore it to another Computer, I received the message stating that the HAL.dll was missing or corupted and to copy another to Windows\system32.  I have re-done the image, tried extracting the HAL.dll from my windows disk and everything else I could think of, but to not avail.  My question is this, what causes this message after restoring an image?  My first thought is that the hardware abstaction layer is just different enough between the machines to cause the problem.  However, I've tried two different versions of the image on 4 different machines, all Dell Optiplex 270's that are identical, (they are from the same order with consecutive serial numbers and I imaged them a while back, so I'm pretty confident they are identical.)

Could it be a problem with the image?  I've done this a few hundred times, and have received this message maybe six times in the past.  But the problem is generally fixed with a new image.  Not this time.  I'm at a loss and any help wold be appreciated.

Thanks.

Bruce
0
BruceWDenen
Asked:
BruceWDenen
1 Solution
 
purfusCommented:
Well before I begin to speculate, what program are you using to create the images?
0
 
Irwin SantosComputer Integration SpecialistCommented:
yeah
0
 
DemonieCommented:
What version of Windows are you running?
Is there some kind of dual boot on the image?
The boot.ini file may be corrupted, which could of course mean more files are corrupted.  There is a solution for this but if more files are corrupted in won't help very much... check out : http://support.microsoft.com/support/kb/articles/Q289/0/22.asp
0
A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

 
nobusCommented:
if you put the image on another type of hardware, it will not work like this.   Look here :

http://65.24.134.81/KipSolutions/MovingXPNewMotherboard/MovingXP.htm      move XP to other mobo
http://support.microsoft.com/?scid=kb;nl;314070                       "     "     "    "      "   
0
 
BruceWDenenAuthor Commented:
I am using Drive Image 2002, and the OS on the base machine is Win XP SP2.  No dual boot, nothing fancy.  I build the base machine straight up the same way I always do it and imaged it.  Then I tried to restore the image to other "identical" machines.  Funny thing happened last night though,  I tried to restore one of the images,(I've made 3 at this point) on a 5th Optiplex 270 (identical to the others, from the same order and all that) and it worked perfectly.  So my guess it has to be something with the PC that the image is being restored to.(?)

I checked the boot.ini on the base machine and it was fine.  No way to check it on the target because it won't boot up far enough to do check it.

nobus,  I thought of that because there had been a MB exchange on a couple of these PC's, but when Dell sent the new MBs I assumed they would send the same hardware!!(?) and there were no problems when the new board went in.  But after reading the article I'm going to give that a try and see if that works.  I'll let you know.
0
 
nobusCommented:
i thought  you implied the hardware was different in your post. That would account for your error and problems.
0
 
ElletechCommented:
The HAL is NOT IDENTICAL! A HAL is very specific to the system for which it is DYNAMICALLY created for! It may be possible to use a HAL on a system which may have a very similar setup, but it genearlly will fail! As you move on working with the system, after a while you will begin to get hardware failures, blue screens, and dll coruptions.

Unless you are tring to create backup copies, you need to come up with another way for creating software replicas on systems.

I recommend, if this is what you are trying to do, you create answer files for each computer, and then roll out multiple copies of the operating system.

Good Luck.
James
www.Elletech.com
0
 
BruceWDenenAuthor Commented:
Nobus,  I tried what the article suggested about setting the IDE controller drivers to standard and so foar so good.  I had to re-install the chipset drivers.  I'll let you know if anything else shows up as a problem.  Thanks.
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now