+ Post New Thread
Results 1 to 5 of 5
Windows Thread, file missing or corrupt after WDS deployment in Technical; We have created an image for a dell USFF 760 pc. The image came down ok. When the pc came ...
  1. #1

    Join Date
    Feb 2007
    Location
    Hereford
    Posts
    213
    Thank Post
    5
    Thanked 3 Times in 3 Posts
    Rep Power
    16

    file missing or corrupt after WDS deployment

    We have created an image for a dell USFF 760 pc.
    The image came down ok. When the pc came to startup is sais windows could not start because the following file is missing or corrupt: <windows root>\system32\hal.dll
    please reinstall re-install a copy of the above file.

    This is a fresh install of win xp. NON oem.
    Its not a hdd issue, cos i tried another one.

    I have also tried replacing the hal.dll, ntoskrnl.exe and ntkrnlpa.exe on the base image.

    Any help much appreciated.

    DG

  2. #2

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Are you trying to use the image on different hardware? The HAL generally throws up errors if the hardware is different, or if you were using the same system but with a single core CPU and then a dual core CPU.

    You could trying performing a Windows repair, then creating a secondary image from this. It's possible large OEMs may use slightly varying components, despite the name/model being identical.

  3. #3

    Join Date
    Feb 2007
    Location
    Hereford
    Posts
    213
    Thank Post
    5
    Thanked 3 Times in 3 Posts
    Rep Power
    16
    Quote Originally Posted by Michael View Post
    Are you trying to use the image on different hardware? The HAL generally throws up errors if the hardware is different, or if you were using the same system but with a single core CPU and then a dual core CPU.

    You could trying performing a Windows repair, then creating a secondary image from this. It's possible large OEMs may use slightly varying components, despite the name/model being identical.
    the hardware is identical
    dell usff pc 760

    Multi cpu

    We think it may now be caused by a hidden partition dell use.

    Dan

  4. #4

    Join Date
    Apr 2007
    Location
    Bournemouth
    Posts
    72
    Thank Post
    13
    Thanked 4 Times in 2 Posts
    Rep Power
    15
    This error can be caused by a number of things after WDS.... but it is always hardware related. You are correct in assuming it is a hidden partition. I assume you, like me, always delete all the partitions before installing a WDS image? If you then install an image that had a seperate parition the boot.ini file will point to an incorrect partition and stupidly the Hal.dll error is the one that shows. All you need to do is rebuild the boot table. If you have a number of machines I advise you to either rebuild the boot table and resend the image to the server, or open up the image and put the correct boot.ini file i nthe root of your system drive.

    To rebuild: Boot to your windows disk, press R for recovery console, type in bootcfg /rebuild, agree to replace, Identifier "Windows XP Professional" and then leave the options blank after. Beware this can often leave traces when loading windows so edit your boot.ini once in Windows and remove the old line.

    That should do it

  5. 3 Thanks to Bobo:

    adamchapman (3rd August 2009), dirtydog (6th November 2009), speckytecky (7th November 2009)

  6. #5
    dirtydog's Avatar
    Join Date
    Sep 2008
    Posts
    301
    Thank Post
    47
    Thanked 29 Times in 16 Posts
    Rep Power
    23
    Quote Originally Posted by Bobo View Post
    This error can be caused by a number of things after WDS.... but it is always hardware related. You are correct in assuming it is a hidden partition. I assume you, like me, always delete all the partitions before installing a WDS image? If you then install an image that had a seperate parition the boot.ini file will point to an incorrect partition and stupidly the Hal.dll error is the one that shows. All you need to do is rebuild the boot table. If you have a number of machines I advise you to either rebuild the boot table and resend the image to the server, or open up the image and put the correct boot.ini file i nthe root of your system drive.

    To rebuild: Boot to your windows disk, press R for recovery console, type in bootcfg /rebuild, agree to replace, Identifier "Windows XP Professional" and then leave the options blank after. Beware this can often leave traces when loading windows so edit your boot.ini once in Windows and remove the old line.

    That should do it
    legend - fixed my problem

SHARE:
+ Post New Thread

Similar Threads

  1. SOLVED - WDS - PXE Missing Menu
    By bmdixon in forum O/S Deployment
    Replies: 9
    Last Post: 6th July 2010, 11:39 AM
  2. Replies: 7
    Last Post: 13th May 2009, 01:13 PM
  3. Corrupt PPT file
    By wesleyw in forum Office Software
    Replies: 1
    Last Post: 23rd April 2009, 06:52 PM
  4. Missing or Corrupt <Windows root>\system32\ntoskrnl.exe on Wise S90 Thin Client
    By networkdemon in forum Thin Client and Virtual Machines
    Replies: 0
    Last Post: 3rd September 2008, 08:54 AM
  5. Ntoskrnl.exe Is Missing Or Corrupt
    By flashsnaps in forum Windows
    Replies: 14
    Last Post: 5th February 2008, 12:20 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •