The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Please Help!! Issue with clean installation of windows xp

    Discussion in 'Windows OS and Software' started by Fenrir84, Oct 18, 2010.

  1. Fenrir84

    Fenrir84 Notebook Consultant

    Reputations:
    4
    Messages:
    113
    Likes Received:
    0
    Trophy Points:
    30
    Hi, my sister has a Samsung NC10 netbook which I did a clean windows xp when she first got it. Somehow she got virus in it and I try to format her netbook to do a clean installation of windows xp again. However, there is a problem occurred during the installation process which I could not figure out how to fix. Ok here is the problem, I use a usb drive to install windows xp on her netbook. First, I delete the partition and then install windows xp in that partition of C drive. So windows ask to format the drive. After formatting the drive, it starts to copy files and then restarts. After restarting I keep on getting this message "Windows could not start because the following file is missing or currupt: <Windows root>\system32\hal.dll. Please re-install a copy of the above file."

    I've done many clean installation of windows xp and windows 7 but never seen this type of problem before. Can someone kindly guide me to fix this type of problem? Thank you
     
  2. Nankuru

    Nankuru Notebook Evangelist

    Reputations:
    215
    Messages:
    592
    Likes Received:
    0
    Trophy Points:
    30
    This error usually occurs when Windows is installed on a different partition to the one specified in the bootl.ini file. Change that to the correct partition and is should work. If not it's somehing similar; the wrong partition specified somewhere in the boot process.