Hal.dll

Dear Team,
We have a problem with Hal.dll files missing many computers ( XP pro Sp3 and windows 2003 sp3 ). when we restarted the computers . we got it error msg .hal.dll missing please copy hal.dll files . why the problem happened how we can solve this issue .

Suriya Subash,
Have you recently changed the boot order in the BIOS??
You probably need to restore this from the recovery console on the Win XP CD (If you have this?).
Look at this link: http://pcsupport.about.com/od/fixtheproblem/ht/restorehaldll.htm
Bob.
Robert Brindle. MCSE, MCSA & MCP/Cisco CCNP & CCNA.

Similar Messages

Problem with installing OS. hal.dll missing or corrupt

I feel I have a hardware issue with this laptop. It is a M115-S3095. I had XP home installed but had driver issues. Now I have the recovery disk with it I get "Error 10DD0A0057". One time I did get my retail XP copy to install it gave me "hal.dll is missing or corrupt". To add to the mix I can not boot a Linux OS Disk. It just get to the installing logo and thats it. The hard drive has been tested good , Memory check was good. So just to pick brains and I know some of you know alot more than me...Do we need a motherboard replacement ? I work on alot of laptops and this is a new one on me. Thanks in advance for any input.

> On Thu, 28 Sep 2006 17:18:05 GMT, [email protected] wrote:
>
> > I've tried creating a completely new image , it also seems to happen if we
> > use the image to reimage the exact same computer ( no hardware
> > diffrences)... any ideas?
>
> did it work before? what has changed?
> --
>
> If you have already compiled drivers or have linux.2 please put them on
> http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
> Live BootCd and USB Disk from Mike Charles
> http://forge.novell.com/modules/xfmod/project/?imagingx
> eZie http://forge.novell.com/modules/xfmod/project/?ezie
>
> Marcus Breiden
>
> If you are asked to email me information please change -- to - in my e-mail
> address.
> The content of this mail is my private and personal opinion.
> http://www.edu-magic.net
yes , on one computer we have used that image before without any other
problems. The computer we are using is the exact same model as the one we
used to take the image from.
In the other case we are taking a computer and imaging it to another drive
in order to replace the drive. So everything is the same , except for the
drive.

Guide to overcome hal.dll error - disk error & other errors.

Okay to start off with - guide for installing bootcamp.
DISCLAIMER:
I take no responsibility at all - whatsoever for any damage the following steps cause to anything. If you follow this guide and then are annoyed at me in any way - don't be - you followed these steps knowing they could be dangerous to your hard drive / computer / sanity / etc. That said - good luck & these steps should work for everyone.
requirements: XP SP2 CD & a copy of parallels would be useful. Also a non-apple usb keyboard for step 1 if the apple one doesn't work during xp bootup.
1. First try the usual bootcamp assistant method. Insert the xp disk, in the setup make sure you format the drive to NTFS (not quick). If you don't get this option - skip to step 3.
2. Reboot and hopefully everything will go without a hitch. If it doesn't and you get a hal.dll error or any other kind of error go on to the next step.
3. Boot up mac os x. Install parallels desktop.
4. Insert your windows xp sp2 cd.
5. Create a new virtual machine using a virtual hard drive saved in your documents folder somewhere.
6. Configure it so that the bootcamp drive is added as an extra secondary drive in the virtual machine. (Little plus button down at the bottom).
7. Install XP onto the virtual machine - don't activate or anything, just get to the desktop stage as fast as possible.
8. Parallels will have already asked for your password to dismount the boot camp drive.
9. Double click my computer in the virtual machine, then hold down ctrl+shift and click on the BOOTCAMP partition in the my computer window.
10. Click format.
11. Select NTFS as file format, check enable compression - do not check quick format.
12. Wait till its finished and then power down the virtual machine.
------- The following steps are taken from http://communities.vmware.com/thread/114529 and were written by MandarMS from the vmware forums. I have edited the guide a little - (you'll see where). Thanks and all credit to MandarMS.----
13. (James: Close parallels)
14. Quit all applications in Host Mac OS X
15. Open Terminal utility from Macintosh HD : Applications : Utilities folder.
16. Key-in the following command
$ sudo fdisk /dev/rdisk0
17. Preferably take the screenshot of the output or Note down the output (for restoring MBR).
18. Key-in the following command
$ sudo fdisk -e /dev/rdisk0
setpid 3
Choose 07 (as the partition type)
write
Y
Restart your Mac System
(James: EDIT - BELOW IS AN EXAMPLE OF THE OUTPUT OF THE PROGRAM IF YOU ARE UNSURE OF WHAT TO TYPE IN WHERE - This confused me at first but really helped in the end - James)
For more details please check the example shown below:
$ sudo fdisk -e /dev/rdisk0 (this will help to change the MBR)
$ fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> setpid 3 (Enter “setpid 3” press enter key)
Starting Ending
#: id cyl hd sec - cyl hd sec start - size
*3: 0B 1023 254 63 - 1023 254 63 1127792680 - 337356448 Win95 FAT32L
Partition id ('0' to disable) 0 - FF: [C] (? for help) 07 (Enter 07 Partition table)
fdisk:*1> write (enter “write” press enter key, This will change the MBR)
Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] Y (Press Y to modify changes)
Writing MBR at offset 0.
$ fdisk: 1> exit (enter “exit”, press enter key)
19. Restart your Mac System
------ Back to me again.
20. Welcome back - your drives have just been fixed. Reboot again and insert the windows xp sp2 cd. Hold down option at startup and boot from the cd.
21. Go through the setup again - this time don't do anything to the drives when it asks you to format.
22. wait...
23. It'll reboot......
24. It'll install..... if it doesn't - skip to step 26
25. Welcome to windows, install your drivers and reboot a couple more times. You're good.
26. (it didn't work... you got the hal.dll error or something similar) Boot up mac os x again and launch parallels.
27. Start up the virtual machine - open up BOOTCAMP in my computer.
28. Click view - folder options
29. View types > make sure you can see hidden files and folders, view system files and etc.
30. Right click boot.ini and click properties
31. Uncheck read-only.
32. Click okay - open boot.ini in notepad.
33. If you're on a mac with 2 partitions: 1 mac hd, 1 bootcamp, delete everything in the boot.ini file and copy and paste the following into it:
\[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
\[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
Obviously change the name to suit. Save it and reboot - you should be good to go now.

Hi. Your bootcamp drive should be drive C. It shouldn't matter what drive letter it is really, you make the virtual machine disk as a virtual disk saved in your documents folder and hook it in to use your physical bootcamp drive.
Ensure you've typed in the correct command and correct password. Press enter after you type in the password. You won't see it as you type it in, and you may need to wait some time afterwards before you'll see the next prompt. Leave it 2 minutes.
Sorry I've been abroad.. hope you have it worked out by now anyway mate.

No luck installing Windows XP SP2 on Macbook hal.dll error

1. I partitioned 45GB with Boot Camp Assistant.
2. Loaded Win XP SP2 CD and started installation.
3. Formatted BOOTCAMP partition on NTFS Quick (Also tried NTFS normal [slow])
4. After it copies everything to the drive and reboots I get a hal.dll missing/corrupt error.
I have tried repartitioning dozens of times and have tried 3 different Windows CDs
Thanks for your help
Message was edited by: pesqair

Startup from the windows CD,
delete the 200MB sized partition and the Bootcamp partition.
Then make a new NTFS partition from the new space and install XP.
It's the 200MB partition that has something to do with boot record, Bootcamp does not recognize it's own partition as bootpartition!
Good luck installing windows!

Hal.dll corrupted error on startup

Hi there.
I recently had rather a nasty bout of spywere problems. after tryign Norton anti-spywere, i have the following problem;
On startup, i get the toshibas splash screen, and then the error message :
Windows cannot find the file: hal.dll
it may be corrupted. please re-install the file
i have the solution to this (from the microsoft tech-support site) but the laptop (an R 10-101) has no floppy drive, and i have no setup disk, so i cannot get a recovery console to fix things.
Is it possible to get a setup disk without buying another copy of windows, or is it possible to get a boot CDrom as oppose to a Floppy Disk?
Thanks,
Matt

Hi
HAL (Hardware Abstraction Layer) is an operating system programming layer that enables the operating system to operate with a hardware device.
The missing or cannot find hal.dll, \windows\system32\hal.dll, or \winnt\system32\hal.dll error message may be experienced on a Microsoft Windows 2000 or Microsoft Windows XP system when the boot.ini becomes corrupted or when a user is attempting to dual boot a computer.
The easiest way to solve the issue is to recover the OS because the boot.ini will be new created.
But you can also check this sites how to solve the problem.
http://www.kellys-korner-xp.com/xp_h.htm
http://www.computerhope.com/issues/ch000490.htm
Furthermore on this site you can find a description how to built a own bootable Windows CD-Rom.
http://www.nu2.nu/pebuilder/
Good luck

How do i re install the file windows root\system32\hal.dll from a black screen

I was given two of the exact same computers a compaq presario c500 c501nr. One had major cosmetic issues and the other the mother board was no good so i put them together to make one good one. everything went well except i now have a black screen on boot up that says [please re-install a copy of this file<windows root>\system32\hal.dll.] how do i go about finding that and installing it? it runs windows vista

if you follow all 7 steps you can directly download a trial here: http://prodesigntools.com/photoshop-elements-10-direct-download-links-pse-premiere-pre.htm l
and activate with your serial number.
if you have a problem downloading, you didn't follow all 7 steps, or your browser does not accept cookies.
the most common problem is caused by failing to meticulously follow steps 1,2 and/or 3 (which adds a cookie to your system enabling you to download the correct version from adobe.com).
failure to obtain that cookie results in an error page being displayed after clicking a link on prodesigntools.com

BSOD hal.dll+12903 and ntoskrnl.eve+185543

I have been working on this PC for quit some time the person before me had no records of what was wrong with the PC or what he did to correct it. The PC shuts down at random and freezes at times, I had changed the UPS, the power cord and even noticed that
the heat sink was loose fixed that. Still the PC kept freezing, I decided to go ahead and re-install Win7 now its BSOD and I used Bluescreenview to view the errors and hal.dll and ntoskrnl.exe appeared. I ran a mem test and it was ok ran an HD test and still
good. Any help is appreciated thanks in advance.
Running Win 7 pro 64bit
4gig ram
video: NVIDIA GeForce 8400GS
mobo: P5N-E SLI
==================================================
Dump File         : 061914-34788-01.dmp
Crash Time        : 6/19/2014 9:02:30 AM
Bug Check String :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`04cbe038
Parameter 3       : 00000000`b2000000
Parameter 4       : 00000000`00010014
Caused By Driver : hal.dll
Caused By Address : hal.dll+12903
File Description : Hardware Abstraction Layer DLL
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f880
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\061914-34788-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 270,984
Dump File Time    : 6/19/2014 9:04:35 AM
==================================================
==================================================
Dump File         : 061914-38735-01.dmp
Crash Time        : 6/19/2014 8:55:48 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041790
Parameter 2       : fffffa80`017ac900
Parameter 3       : 00000000`0000ffff
Parameter 4       : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f880
File Description : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f880
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\061914-38735-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 270,984
Dump File Time    : 6/19/2014 8:57:53 AM
==================================================

Tmtz15
There wer all related to hardware and called BCC124
Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see
if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though
it is"possible" that it is driver related (rare).
Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games,
utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine
is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should you find yourself in the situation of having performed all of the steps
above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
More advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
Wanikiya and Dyami--Team Zigzag

13" MacBook boots to hal.dll issue - Help!

I recently tried to install Windows XP using bootcamp, I read somewhere the section that bootcamp makes needed to be wiped or deleted, so it doesn't use the default structure. So I deleted the partition, I selected Windows to install to the new space. Although, it installed XP in the NTFS layout, and then refused to boot up, claiming hal.dll was missing.
Everytime I start the MacBook it boots to this screen, I have tried MANY commands for Windows through using the advice of others who have had this issue, but none worked. After trying and trying, it eventually claimed something had been corrupted. I cannot remove the disk and cannot get it to boot to OSX. I have tried CommandOF to try and get the disk out but nothing happened.
I have tried almost every thing I can think of, could someone please give me some advice and help me solve this?!
Thank you!

No joy unfortunately, it claims 'There is no floppy disk or CD in the drive', when there clearly is. I do not know the letter allocations of each partition or drive, so cannot try it another way.
Is there any way I can just get back into OSX and delete the Windows partition? I have really tried to use key commands on boot up but it just goes to the Windows partition.
Thanks,
Max

Cant boot missing hal.dll file - HELP!

I have just installed my new MSI board, and I have a dreadful problem. I cannot get my computer to boot. It tells me that windows cannot start because the following file is mssing or corrupted: Hal.dll
In fact the file is there. I know this because if |I leave the windows install disk in the computer it boots ok. I have tried using the rebuild command from the recovery console, and the repair option, but so far it does not work.
Has anyone else had a similar problem? I had no problem with my old board, and so I thought it might be something to do with this new board. Are my settings incorrect?
I have SCSI as well as IDE drives, and I cannot tell if the boot.ini file is pointing to the right drive, but I suspect it is.
Please help!
Dan

hal.dll is a dll which interfaces your hardware to the operating system (Hardware Adapter Layer).
I don't know which operating system you are using, so I can't tell you the total answer to your problem.
When you boot from your hard drive (as opposed to floppy disk or cd-rom), it will always look for the initial hardware loaders ($ldr$, ntldr, etc) from the boot drive (normally "C") prior to looking at boot.ini. From there it will give you a choice of which operating system to load.
Incidentally, the loader is a dos based program so only knows about drives 1 & 2.
the easiest way to get the operating system on the second drive, is to use the install disk from windows by executing "cd-rom":/setup.exe from the start menu.
After removing the current version of the OS from the scsci drive, you may then install onto the scsi drive. Ensure that the scsi controller is enabled for booting, so it's BIOS is enabled.
Hope this helps.
kd1im (MCSE)

MOVED: Windows cannot boot because of missing/corrupt hal.dll! Help!

This topic has been moved to Operating Systems.
Windows cannot boot because of missing/corrupt hal.dll! Help!

Hi,
make sure you have disconnected all non-essential external devices (printers, scanners, external harddisk) prior to installing BootCamp Windows.
Leave only mouse, keyboard and display connected.
Make sure that your XP CD is either retail or OEM/systemBuilder version and not a manufacturer-bundled one.
Also make sure that the CD is 'clean' (no dust, no scratches, etc.).
Use the BootCamp Assistant to revert back to one single OSX volume.
Use OSX Disk Utility to Verify your harddisk and repair permissions.
Retry the XP installation from scratch.
Generally using NTFS is more likely to not getting the 'missing hal.dll' error.
Stefan

"disk error" or "hal.dll' missing

I kept getting "hal.dll" missing after the initial dos-style XP install, and googling about led me to believe it was because I was deleting the boot camp partition during xp setup and re-formatting as NTFS.
So I tried just selecting the BOOTCAMP partition as is, and now the error is different - it simply says "disk error" at XP boot up.
Note this is BEFORE the actual XP install, this is the restart after the initial XP copying files setup bit.

I also got "disk error" message when I first installed XP WITHOUT formatting the Windows partition. After I formatted it everything works fine.
I also got "hal.dll" error when I created 2 partitions on Windows BUT formatted only the partition that I installed the XP on. I believe the error was because that unformatted partition. I haven't tried formatting both partition yet, though.
Have any of you tried nerowolfe's advice? Did it work?

Hal.dll error error message: here is the solution !

Thanks to endership for the procedure. For people who were getting the hal.dll missing file error message or for those who are wondering about the right way to install Windows XP SP2 with Bootcamp, here is the steps you have to follow.
1) First, get an original Windows XP SP2 cd and be sure that your CD is bootable and that you can access the recovery console in a repair function (not all the cds got the function, so be careful).
2)After, you go in Apple applications, utilities and you click on the boot camp assistant
3)If you got a Windows partition already created that is not working, resulting from a bad installation of Windows with bootcamp, just merge the two partitions (windows and mac os x) using the restore function.
4)Use 32 Go for Windows (default option) and be sure that your Windows cd is in the drive and launch the installation.
Computer will reboot in the installation program after that all the drivers has been loaded (the blue screen lasting about 5 minutes).
5)Once your are in the installation menu, just select the option that takes you to the repair console.
6)You will get a C: command line, sort of MS-DOS. Like mentionned enderfish, type "diskpart" to visualize the partitions created and be sure that the c: drive is labeled "bootcamp". Just return to repair console in the c: command line.
7)type the following command line:
FORMAT c: /Q /FS:NTFS
You will get a quick format of the c: drive in the NTFS file system. It will also probably work in FAT32, but I've never tried.
8)After that the format has been done, hit the POWER button to reboot.
9)You will be back in the installation menu; you'll also have to wait once again during 5 minutes for the drivers loading process.
10)Once you get in the installation blue screen, just choose the partition that has been created and choose to let the file system intact.
11)Windows XP will be copying install files on the HD, install Windows XP SP2.
12)Once, the installation is done and you entered in Windows (if you followed the instructions carefully), insert in the cd drive, the Leopard CD and install Windows drivers.
13)Reboot
14)Enjoy!
Message was edited by: Bert770

In my experience (because this happened to me), I found that it was a -user error- (mine). I reviewed Apple's instructions (which said to reformat the BOOTCAMP partition) and DELETED the BOOTCAMP "C:" partition (from within the XP installer) first. When you do this, it combines with partition with the "unused" 128MB partition that separates the Mac partition from "C:".
Apparently the 128MB partition really -is- used for something; probably to help redirect XP to the proper location to find hal.dll (which is why the file -even if repaired/replaced- continues to be reported as missing/corrupted). Even XP's automatic repair won't fix this issue (as it proceeds to copy -everything- anew and still fail upon reboot with the same error).
The answer seems to be "don't delete the C: partition". Instead, just select it, hit ENTER and, -in the next screen-, format the partition (Quick is OK). Everything proceeds properly at that point.
I just finished doing seven iMacs and tried quite a number of alternate solution (suggested here and elsewhere). The only thing that worked consistently was following Apple's directions!
By the way, once I got one Mac working properly (using FAT32 as I had only a 32GB partition and I wanted to have the PC partition appear on the Mac's Desktop if we booted into OSX), I imaged the partition and tried restoring it to another Mac on which I had only used BootCamp Assistant to partition the drive. Booting into XP produced the same hal.dll error. However, if I restored to a partition that had already had a successful XP installation done to it in the proper manner, this replacement of the partition's data with the image's data was successful. (I don't know why. I tried both a "master" image and a "compressed" image; only the compressed image worked and only as noted above.)
I'm not writing this to come off as a guru; rather, this is simply what ended up working for me and I thought others might benefit from knowing what mis-steps I took (and would then not follow in those mis-steps).
Barry

Boot Camp ****: HAL.DLL and other problems

Okay I am really frustrated, so if I come off like a jerk... well, I don't mean to, but my frustration is going to bleed into the tone of this post. Let me ask you not to reply that I have a bad Windows CD. I've been a gosh darn network administrator for over ten frakking years now, and I successfully use the same bleeping CDROM disk on dozens of other computers all the bleeping time.
Okay, now that I've got that off my chest, here's the situation: I have a Windows XP Pro CD with Service Pack 3 slipstreamed into it. I downloaded it from Microsoft. My organization has a Select Agreement with them, so we can do that. There is a winnt.sif file on it that automates a few things (such as entering the key number), but it allows me to do the partitioning and formatting manually.
If I leave the partition as FAT32, then when the Windows installer attempts to reboot into the GUI portion of the install, then it says, "Disk Error. Press any key to restart." Pressing keys does nothing, so I have to power it off.
If I format the partition with NTFS (tried both Quick and Full formats with the same results), then it finishes the text mode portion of the install, reboots, and tells me that I'm missing HAL.DLL.
I have tried several different sizes of partitions (partitioning with the Boot Camp utility... not the Windows installer), and been through the text portion of Windows install at least a dozen times. I have searched the Net, and failed to find a CD that would allow me to attempt installing Windows off my RIS server. I have burned new copies of my CD onto CDR and CDRW media. The only thing I cannot do is obtain an original XP CD since our organization isn't big enough to qualify for Microsoft to send us Select CD's (and my boss ain't gonna pay for a retail copy just so that I can run Boot Camp). And please don't ask me if I'm properly licensed to install Windows on my Mac. I know the Windows EULA inside and out. It's all legit.
Any help here would truly be appreciated.

Perhaps you need to use an XP cd with sp2 slipstreamed, install boot camp update 2.1, then SP3.
The following URL has a note: --> http://support.apple.com/downloads/BootCamp_Update_2_1_for_WindowsXP
Important: Installation of Boot Camp 2.1 is required before installing Windows XP Service Pack 3 (SP3)

Windows could not start because the following file is missing or corrupt. Windows root\system32\hal.dll.

Windows could not start because the following file is missing or corrupt. Windows root\system32\hal.dll. anyone can help

Have a read here http://support.microsoft.com/kb/314477/en-us
Maybe it helps
Stefan

Error Message: Missing \SYSTEM32\HAL.DLL

Anyone familiar with this error message when booting into Windows XP on a Macbook?
This problem began when I attempted to setup multiple partitions for Windows, using the disk management utility for Windows XP:
"Windows could not start because the following file is missing or corrupt:
<windows root>\system32\hal.dll
Please re-install a copy of the above file"
Before trying to make more partitions, everything ran A-OK.
Please advise if you have run into this.
Thanks,
Mbs

I have the same problem with bootcamp and parallels.
Replacing the dll does not help.
btw: at the moment it seems to bee that xp does not work with bootcamp at all.
After installation I get a drive error. Looking up the support pages it is suggested to format the bootcamp volume before installing xp.
I tried this with the xp-installer (ntfs format) and from parallels using the old DOS format command.
No method worked.
After trying to run the bootcamp-xp in parallels I finally got the dll-error.

Hal.dll

Similar Messages

Maybe you are looking for