1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

hal.dll missing or corrupt

Discussion in 'Windows XP' started by Christer, 2007/01/03.

  1. 2007/01/03
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Hello all!

    A friend gave me a call asking for help. His Windows XP does not start but says that "Windows could not start - C:\%system root%\system32\hal.dll is missing or corrupt. Reinstall hal.dll" or words to that effect.

    I have searched Windows BBS but found no conclusive answer. Am I right in deducting from the search results that the Recovery Console will not fix this?

    Will a Repair Installation fix this without losing any data (pretty vital)?

    What is the likelyhood of hard disk error or any other hardware error causing this?

    Thanks for your time,
    Christer
     
    Christer,
    #1
  2. 2007/01/03
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    I went google on it and found an indication that the Recovery Console might fix it:

    I have not "heard" anyone cheering after a successful fix.

    How can the boot.ini file get corrupted? I believed it was written to during installation only.

    Some google hits indicate hardware (hard disk) error.

    Christer
     
    Christer,
    #2


  3. to hide this advert.

  4. 2007/01/03
    surferdude2

    surferdude2 Inactive

    Joined:
    2004/07/04
    Messages:
    4,009
    Likes Received:
    23
    Hi Christer,

    A couple of ways come to mind. The user has edited the file incorrectly. A dual boot system deleted and boot.ini still lists the old system.

    Others are possible but those cover most cases I think.

    Although your directions for activating and using the Recovery Console via booting the XP installation CD are valid, unfortunately there are several users of OEM equipment that did not get such a CD nor was the RC installed on their box when sold. In those cases it is quite important to have on hand the "XP quick boot" floppy or CD that I have previously mentioned often. :)

    There is also available a "boot.ini edit" floppy that allows editing the boot.ini file when the system is unbootable. A Google search should turn it up.

    HTH

    Edit: EditBootIni

    XPQuickBoot

    XPquickboot.txt
     
    Last edited: 2007/01/03
    surferdude2,
    #3
  5. 2007/01/03
    Bill Castner

    Bill Castner Inactive

    Joined:
    2006/08/30
    Messages:
    1,980
    Likes Received:
    0
    Use the XP CD to boot to recovery console.

    attrib -r -s -h c:\boot.ini
    del c:\boot.ini

    bootcfg /Rebuild

    fixmbr
    fixboot

    exit
    -------------
    That will work always unless the HAL.DLL file is really missing. In that case you need to use Recovery Console again and EXPAND a HAL.DL_ file to the root of the boot drive, but try this first:

    attrib -r -h -s C:\hal.dll
    copy c:\windows\ServicePackFiles\i386\hal.dll c:\
    attrib +r +h +s C:\hal.dll

    exit
     
    Last edited: 2007/01/03
    Bill Castner,
    #4
  6. 2007/01/03
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Hi dude!

    I understand that corruption of the boot.ini file would be possible under the circumstances you mention but my friend has not done anything like that. He has just shut down one evening and tried to restart the next morning. That's why I am doubtful about the boot.ini corruption and lean towards hard disk error.

    I will try to find and download the tools you mention. They may come handy.

    Christer
     
    Christer,
    #5
  7. 2007/01/03
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Hi Bill!

    The other instructions I found did not mention deleting boot.ini and rebuilding it. It makes sense, though, to start with a "clean sheet of paper ".

    When I get there, if BIOS recognizes the hard disk, I will follow your steps.

    Christer
     
    Christer,
    #6
  8. 2007/01/03
    surferdude2

    surferdude2 Inactive

    Joined:
    2004/07/04
    Messages:
    4,009
    Likes Received:
    23
    OK, Good luck with your friend's problem.

    As we have discussed in the past, no boot.ini file at all is better than a corrupt one. The system will boot without it so not to worry.

    All the best.
     
    surferdude2,
    #7
  9. 2007/01/03
    Bill Castner

    Bill Castner Inactive

    Joined:
    2006/08/30
    Messages:
    1,980
    Likes Received:
    0
    If any other OS is installed, it will not boot without it.
    If XP is on an extended/Logical volume, it will not boot without it.
    You have will have reasonable luck if XP is installed on the first, Primary, and active partition.

    The odds go steadily down to zero in any other configuration.

    XP distinguishes its boot volume (called by Microsoft the System volume), and the volume where the OS files are found (called again oddly by Microsoft the Boot Volume, against all common sense). The point of the boot.ini is to tell NTLDR, in the System Volume, where to find the OS files in the Boot volume. The system and boot volumes can be on different drives and partitions, are are in fact on diffferent drives/partitions for any multi-boot.

    One last thing of importance in the boot.ini file is it instucts NTLDR whether a driver for the disk is necessary, or whether the BIOS is capable of the chore without help. This is sent to NTLDR by the ARC path logic:

    disk() == BIOS only
    RAID() == driver required
    MULTI() == both -- but a driver is required. It may come in this instance from a BIOS on the driver controller board.
     
    Last edited: 2007/01/03
    Bill Castner,
    #8
  10. 2007/01/04
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Well, my friend couldn't wait for me to set time aside for his computer. He took it to his son who installed the hard disk (fathers) in his own computer and copied all the important stuff to his hard disk (sons). The hard disk (fathers) is now back where it belongs and the son has started trouble shooting.

    I guess this is the end of this thread but thanks all for your assistance!

    Christer
     
    Christer,
    #9
  11. 2007/01/04
    Bill Castner

    Bill Castner Inactive

    Joined:
    2006/08/30
    Messages:
    1,980
    Likes Received:
    0
    Like a bad penny, it will be back.
     
    Bill Castner,
    #10

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...