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.

Similar Messages

  • Bootcamp: hal.dll and disk error SOLVED. Simple workaround

    Many people had the "hal.dll missing" and "No disk" error while trying to install Windows with bootcamp on OSX leopard. I read a lot of workarounds and solutions, which some are complicated and some just don't work.
    Here is my simple workaround to get rid of errors:
    (Principle: force the shell of windows to appear before installation, so that we can quick format the bootcamp partition with" format" command)
    1. Create a windows partition with bootcamp as usual (if you have already one then restore the OSX partition)
    2. Restart and boot on windows cd. (press the option key ("alt") during restart)
    3. When bluescreen appears and drivers are loading, press repeatedly F6 and F10. You should get a message that no SCSI disk was found and that you should press "S" or "enter" to continue. Press "enter". Now you should get a black screen in console mode.
    4. Now we format the bootcamp partition. Type this: "FORMAT C: /Q /FS:NTFS". Put FAT32 instead of NTFS if you want the file system to be FAT32.
    5. Press 'Y' to confirm.
    6. Restart the computer, boot on cd, and install windows as usual. When arrived on partitionning during install, DO NOT REFORMAT!!!! Install on the partition    that we just created before!
    PS: I think that bootcamp just messes up the windows partition. That's why you get "disk error". When formatting during the windows installation, the partition is correct for windows but it overwrites entirely the bootcamp partition instead of just formatting it. I think that the quick format from the shell does just change the file system without modifying the partition itself. However, it works, so why bother why it does?....
    Let me know if you have difficulties.
    Message was edited by: febex

    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)

  • BSOD 24 times in a row always the same hal.dll+6034 & ntoskrnl.exe+15c4e9 error on windows 8.1 pro, really need help badly.

    My first BSOD occurred about 10 days ago, randomly and frequently, totally I have been through 24 dumps, that's really not a happy experience, right? Any help will be appreciated! Thanks in advance.
    FIY, I uploaded as much information as I can provide for someone better help me.
    Here's my onedriver link:
    https://onedrive.live.com/?cid=D750E66988BCA5D6&id=D750E66988BCA5D6%214287
    Content all 24 minidump files plus blew:
    cupz.html
    DriverList.txt
    dxdiag.txt
    EventApp.txt
    EventSys.txt
    Hosts.txt
    MSINFO32.nfo
    RAMMon - SPD Info.html
    SystemInfo.txt
    Windowsupdate.log

    Hi,
    From your dump file, we could see the following information:
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 7F, {8, ffffd0006e548130, ffffd0006e563ff0, fffff8002313a323}
    *** WARNING: Unable to verify timestamp for epfw.sys
    *** ERROR: Module load completed but symbols could not be loaded for epfw.sys
    Probably caused by : epfw.sys ( epfw+2069d )
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: ffffd0006e548130
    Arg3: ffffd0006e563ff0
    Arg4: fffff8002313a323
    Debugging Details:
    BUGCHECK_STR: 0x7f_8
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from fffff800231d64e9 to fffff800231ca9a0
    STACK_TEXT:
    ffffd000`6e547fe8 fffff800`231d64e9 : 00000000`0000007f 00000000`00000008 ffffd000`6e548130 ffffd000`6e563ff0 : nt!KeBugCheckEx
    ffffd000`6e547ff0 fffff800`231d45f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    ffffd000`6e548130 fffff800`2313a323 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb4
    ffffd000`6e563ff0 fffff800`23139710 : 80000000`004c0121 00000000`00000000 00000000`00001010 80000000`004c0121 : nt!MiAllocatePoolPages+0x87
    ffffd000`6e564040 fffff800`2331e4d3 : 00000000`00000000 80000000`004c0121 80000000`00000000 80000000`004c0121 : nt!ExpAllocateBigPool+0xd0
    ffffd000`6e564130 fffff800`06e2069d : 80000000`004c0121 ffffd000`6e5648c0 80000000`004c0121 80000000`004c0121 : nt!ExAllocatePoolWithTag+0xa83
    ffffd000`6e564200 80000000`004c0121 : ffffd000`6e5648c0 80000000`004c0121 80000000`004c0121 00000000`00000000 : epfw+0x2069d
    ffffd000`6e564208 ffffd000`6e5648c0 : 80000000`004c0121 80000000`004c0121 00000000`00000000 fffff800`06e1ea92 : 0x80000000`004c0121
    ffffd000`6e564210 80000000`004c0121 : 80000000`004c0121 00000000`00000000 fffff800`06e1ea92 ffffd000`6e564350 : 0xffffd000`6e5648c0
    ffffd000`6e564218 80000000`004c0121 : 00000000`00000000 fffff800`06e1ea92 ffffd000`6e564350 00000000`00001000 : 0x80000000`004c0121
    ffffd000`6e564220 00000000`00000000 : fffff800`06e1ea92 ffffd000`6e564350 00000000`00001000 80000000`004c0121 : 0x80000000`004c0121
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    epfw+2069d
    fffff800`06e2069d ?? ???
    SYMBOL_STACK_INDEX: 6
    SYMBOL_NAME: epfw+2069d
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: epfw
    IMAGE_NAME: epfw.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 520cebd6
    FAILURE_BUCKET_ID: 0x7f_8_epfw+2069d
    BUCKET_ID: 0x7f_8_epfw+2069d
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x7f_8_epfw+2069d
    FAILURE_ID_HASH: {3a545e72-b251-678f-639a-8254aaae9c2a}
    Followup: MachineOwner
    These were Related to epfw.sys ESET Smart Security driver. I would like to suggest you remove it and use the built-in defender.
    Karen Hu
    TechNet Community Support

  • Disk Error, Hal.dll Error, No bootable device error - Every other error.

    Hi,
    I've been trying for ages to install xp using bootcamp. I have windows xp sp1, which i've slipstreamed to create an SP2 version. I also have access to the family backups of every OS we've ever bought, including a mix cd of windows xp MCE, XP home, XP professional - all SP2.
    I moved to the mac a year or so ago - I've installed windows more times than I've rolled out of bed in the morning.
    I had it working back when I was running Tiger - I upgraded to leopard - decided I wanted to try a reinstall of windows, formatted the drive and followed all the steps to install.
    The main issue is that when I insert the windows install CD - it never gives me a chance to format the disk. I tried installing parallels and using that to boot up XP, and it does give me an chance - but after that install is finished I get the Hal.dll error.
    I removed the bootcamp drive but after installing refit - it still shows up on the boot menu. Somehow, my HDD's GUID partition table & MBR for the windows partition is messed up.
    At the end of the day - I've tried everything I can think of to install windows. And it just won't go. It used to work - what's changed? Any suggestions?
    Cheers in advance.

    I too had problems with Hal.dll and "Disk Error".
    Installing XP on my Mac Mini with 10.5.1 Leopard (fresh install on a new HDD), I got the Hal.dll error (my 2nd time with this lovely error, the first being on a iMac with Leopard). According to Billbear from this thread:
    http://forum.onmac.net/showthread.php?t=2793&page=5
    You will get Hal.dll when you try to install XP on a partition that isn't the last partition on the disk. I tried this solution, and it worked for me. I previously had:
    1) Leopard
    2) XP
    3) User partition
    And changed it to:
    1) User partition
    2) Leopard
    3) XP
    Next, however, I got a different error -- the dreaded "Disk Error". I tried the Apple support solution (formatting as NTFS instead of converting from FAT to NTFS), but I got the same error. I read somewhere (can't remember which thread, since I looked at so many) that you might get the problem if XP wasn't installing on C: drive. So I changed my partitioning from
    1) User partition (FAT)
    2) Leopard (HFS+)
    3) XP (FAT)
    To:
    1) User partition (HFS+)
    2) Leopard (HFS+)
    3) XP (FAT)
    The installer saw the XP partition as C: and was able to install smoothly (Quick reformatting to NTFS). I then used Disk Utility to change the User partition from HFS+ to FAT, and everything works fine!

  • Disk Utility internal error message

    I am receiving an error message every time I try to repair permissions on my MB running OS X 10.4:
    error:
    Disk Utility Internal Error
    Disk Utility has lost its connection with the Disk Management Tool and cannot continue. Please quit and re launch Disk Utility.
    Tried that several times to no avail. After quittting Disk Utility, system becomes very sluggish and Finder stops responding.
    I then booted from the installation CD and ran a Hard Disk integrity check. It checked Ok. Then I tried a permission repair and got the exact same error message quoted above.
    Any help?

    There was a problem with this a couple of years ago involving iTunes Library Receipt files. See [Mac OS X 10.3: Repair Disk Permissions 'Disk Utility has lost its connection with the Disk Management Tool.|http://docs.info.apple.com/article.html?artnum=303132].
    It seems unlikely that would surface now, but the suggested fix is worth trying. The article also mentions looking at Console log. Console is in Applications/Utilities.
    Also, see this recent thread in the Panther forum:
    http://discussions.apple.com/thread.jspa?threadID=1585878

  • Disk Utility: Burn error: 0x80020022 The device failed to respond...

    I've been working on archiving a ton of video to DVD. I'm using Dual-Layer discs to minimize the amount of physical storage space needed for the finished project. I burned several discs in iDVD in July and regularly received errors. Then the drive suddenly stopped loading any type of media. Anything I inserted would spin briefly and then eject. Repaired permissions and followed steps outlined here and here. Took the Mac back to the store where I bought it (sadly, not an Apple Store - nearest one is 12 hrs away) where naturally it performed flawlessly for the store rep.
    So I took it home and resumed burning, now saving as a disc image (ignoring iDVD's warning about the performance of DVDs burned this way) and using Disk Utility, since iDVD didn't seem to be reliable. Burned about 25 discs, error-free, in this fashion, then three days ago, got the error: "Unable to burn “Disc 19.img”. (The device failed to respond properly, unable to recover or retry.)"
    Retried the same image, and it worked. Then burned two more in the same fashion with no errors. Today I got the same error again. Logs are identical for each failed burn, except for the time span between certain lines.
    Price of DL media being what it is, I'd hate to keep ruining discs if there's something I can do to avoid it. I suppose it could be bad media, but it seems odd that I'd get two bum discs that close together after burning so many without issue. Checked the site and the forums, and there doesn't seem to be any answers. Does anyone have any ideas? (Other than "try a different brand of media." I've got a buttload of these discs and it's too late to return them now.) Even if it just helps determine where the issue lies. Warranty will be up soon, so if it's hardware related, I need to get it taken care of quick.
    Media: Philips DVD+R DL 8x
    *Drive info:*
    HL-DT-ST DVDRW GS21N:
    Firmware Revision: SA15
    Interconnect: ATAPI
    Burn Support: Yes (Apple Shipping Drive)
    Cache: 2048 KB
    Reads DVD: Yes
    CD-Write: -R, -RW
    DVD-Write: -R, -R DL, -RW, +R, +R DL, +RW
    Write Strategies: CD-TAO, CD-SAO, CD-Raw, DVD-DAO
    Media: Insert media and refresh to show available burn speeds
    DiscUtility.log:
    2009-10-03 08:54:01 -0600: Burning Image “Disc 22.img”
    2009-10-03 08:55:15 -0600: Image name: “Disc 22.img”
    2009-10-03 08:55:15 -0600: Burn disc in: “HL-DT-ST DVDRW GS21N”
    2009-10-03 08:55:15 -0600: Erase disc before burning: No
    2009-10-03 08:55:15 -0600: Leave disc appendable: No
    2009-10-03 08:55:15 -0600: Verify burned data after burning: Yes
    2009-10-03 08:55:15 -0600: Eject disc after burning
    2009-10-03 08:55:15 -0600:
    2009-10-03 08:55:15 -0600: Preparing data for burn
    2009-10-03 08:56:30 -0600: Opening session
    2009-10-03 08:56:35 -0600: Opening track
    2009-10-03 08:56:35 -0600: Writing track
    2009-10-03 09:01:37 -0600: Finishing burn
    2009-10-03 09:02:37 -0600: Closing session
    2009-10-03 09:02:38 -0600: Finishing burn
    2009-10-03 09:38:37 -0600: Burn failed
    2009-10-03 09:38:37 -0600: The device failed to respond properly, unable to recover or retry.
    2009-10-03 09:38:37 -0600: Additional information can be found in the ~/Library/Logs/DiscRecording.log log file.
    2009-10-03 09:38:37 -0600: Unable to burn “Disc 22.img”. (The device failed to respond properly, unable to recover or retry.)
    DiscRecording.log:
    Disk Utility: Burn started, Sat Oct 3 08:55:15 2009
    Disk Utility: Burning to DVD+R DL (CMC MAG D03) media with DAO strategy in HL-DT-ST DVDRW GS21N SA15 via ATAPI.
    Disk Utility: Requested burn speed was 47x, actual burn speed is 4x.
    Disk Utility: Burn failed, Sat Oct 3 09:37:15 2009
    Disk Utility: Burn sense: 4/44/90 Hardware Error,
    Disk Utility: Burn error: 0x80020022 The device failed to respond properly, unable to recover or retry.
    Message was edited by: Weasel42

    I have encountered the same problem. I have a Mac Book Pro from 2007, and it has gone through 3 DVD writers so far, all of which have ruined DVD+R DL disks. I have occasionally been able to burn one, but usually during verify, I get this error message:
    Communication to the disk drive failed: 0x8002022
    And disk utility fails with a "Invalid B-tree node size" error
    Oddly, when I try to burn a disk near capacity (6.5Gb or more) it is more likely to fail than if I burn a smaller disk.
    I've been using Memorex DVD+R DL disks, but I have used other brands in the past but they have failed, too. Out of about 50 disks so far, I have had success with about 5.

  • "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?

  • DISK ERROR and also HAL.DLL error - I can't install XP SP2

    Hi guys,
    I'm at my wits end and am fed up by errors I've been getting trying to install XP SP2. I bought my Mac because of bootcamp interoperability as I need to use Windows applications for my work, so I get the best of both worlds. Parallels is out of the question as I don't get the speed I need.
    I have a late-2007 revision 24" iMac (3gb/24"/2.4 C2D) and had Bootcamp running perfectly before upgrading to Leopard (with 10.4.9/10) - almost too perfect: it just worked! I have since upgraded to Leopard and today went to reinstall Windows as I did a clean install and wiped everything to start from scratch.
    I have spent 4 hours reading forum after forum trying permutation after permutation of options and can't get it to work. I get
    DISK ERROR
    PRESS ANY KEY TO RESTART
    When installing on any volume size using Fat32, and if I format NTFS, I get an error about a missing HAL.DLL.
    I have verified that under both Fat32 files are copied as expected. Confirmed drive format as Fat32.
    I also have the latest firmware update that was delivered a week or so ago via software update. I don't know if this could be the cause?
    This is frustrating me beyond belief. If anyone can help, it'd be very very much appreciated.

    I have also been having serious issues, and this worked for me also. Before (In Leopard with BootCamp 2.0) I could partition ok, and everything else, but the Windows installer just wouldn't give me the option of reformatting the drive (formatted to FAT32 by BootCamp v. 2) to NTFS. To re-iterate, if you're having these DISK ERROR problems, do the following:
    Backup all files
    Use Leopard/Tiger install disk to wipe the entire hard drive (all volumes mac and pc) with Disk Utility (this may not be necessary, but it could clear up the problem)
    Install Tiger (10.4)
    Run Bootcamp (in Tiger), partition, install Windows, and install drivers
    Install Leopard (you may choose "erase" within the Installer since this will just wipe the Mac partition)
    Now you're good to go. For running Bootcamp on Tiger, you will need to download BootCamp beta 1.4, there is at least one mirror (and a 1.3 one too) that you can easily find with google. Also, if you're having trouble installing with the beta after December 2007, try setting back the clock and disconnecting from the Internet.
    Although it is very strange that Bootcamp 2.0 (or Leopard) have broken the ability to install.

  • 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

  • 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 error during/after Win XP SP2 installation

    At the moment I'm trying to install Win XP (SP2) into a bootcamp partition. I have a Mac Pro with 4 HDDs.
    HDD1: OSX
    HDD2: free
    HDD3: OSX Data (raid 1)
    HDD4: OSX Data (raid 1)
    The setup I'd like to have is:
    HDD2:
    (1) Bootcamp-Partition (NTFS ~75GB)
    (2) Bootcamp-Scratch (NTFS ~150GB)
    (3) Scratch (HFS+ ~250GB)
    I partitioned the disk that way (with FAT32 instead of NTFS) and booted from the Windows install disk. The installer starts, reformats disk (1) to NTFS and copies data onto the disk.
    After the first reboot it breaks with hal.dll error. The files are on the disk but boot.ini seems to be corrupt. The "bootcfg" command from the recovery console is not working - it only duplicates the wrong entry in boot.ini.
    After the third non-working installation I tried to move the Bootcamp-Partition into the middle, OSX in front:
    (1) Scratch (HFS+ ~250GB)
    (2) Bootcamp-Partition (NTFS ~75GB)
    (3) Bootcamp-Scratch (NTFS ~150GB)
    Same error.
    Any hints on howto do that? Or will I have to move the Bootcamp-Disk to the end? How to succeed in having the Bootcamp-Scratch as 'D:' in Windows if I swap those two partitions?
    BTW: I succeeded to install WinXP on the same disk before. Back then I only had a 75GB Bootcamp-Partition on the disk (no other partition) and had the disk in Bay 3. But I moved it to Bay 2 because of performance problems in Bay3/4 (PIO-mode) and don't want to waste 400GB in the future .

    First of all I believe this is not the right place to discuss the issue. This issue is related to the Windows operating system file corruption and I think the physical location of the hard drive is not the cause of the issue.
    The hal.dll file is a system file which holds the hardware access layer information and linking the necessary components. This include the information about all the hardware resources for the operating system. What you had done to change the hardware configuration files in the boot.ini looks ok. Also you can try this link.
    http://shanegfowler.wordpress.com/2007/01/10/missing-haldll-error-corrupt-bootin i-file-quick-fix/
    Hope that helps you........

  • 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 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

  • SCCM 2012 - OSD - HAL.dll error (windows XP) using USB

    Hi
    SCCM 2012
    I'm creating OSD for Windows XP  and create .iso files
    1. I create ISO files
    2. make the USB bootable
    3. Copy the ISO files in content in USB
    4. Boot from USB,  when it finish I;m getting the HAL.dll error
    Please advise
    Robert

    The hal.dll is missing?
    http://support.microsoft.com/kb/314477/en-gb
    Juke Chou
    TechNet Community Support

  • Hal.dll error - HP Mini 1030 NR fails to boot following XP reinstall.

    Following a reformat of the solid state HDD and subsequent reinstallation of XP from the recovery disc, I receive the following message: "Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll" - I've tried multiple fixes using the "expand" (copy) command from the XP recovery disc to replace the .dll file as well as rebuilding the boot.ini file. Any suggestions would be appreciated...

    Hi Paul - thanks for your suggestions...
    The associated HP Mini 1030 utilizes a 16 GB SSD as its only drive other that a removable SD card. It has worked well within my home network for web based applications (streaming, MP3's, news etc.) in my kitchen for the last year. It was configured new with a no frills bare bones XP platform. I removed all extraneous programs except for a basic antivirus routine. Eventually however, the SDD became filled to capacity with security updates and other file allocation clutter typical of the XP platform and I started getting memory warnings.
    As I've done with other XP machines, I reformatted the SDD and have attempted to reinstall the operating system using the associated recovery disc as supplied from HP. I consistently get the "Hal error" early in the bootup process and as a result, Windows will not launch.
    I read through the MS links you included and have the following comments:
    Suggestion #1 - Unless I'm missing something, I can't change the "computer type" in the control panel as the laptop will not boot to windows.
    Suggestion #2 - Forcing a system Hal... would like to try this but am not sure what configuration I'm looking for with this type of laptop (Standard PC?).
    Any other thoughts? thanks again for your help...

Maybe you are looking for