locked
HAL.wsf in 2010? -Dead machine after OS load RRS feed

  • Question

  • I've been running 2010 for a few weeks and just ran into one machine model that won't boot after XPsp3 OS has been loaded.  The symptoms match those of the incorrect HAL loaded -machine stops at agpCPQ.sys in safe mode generally means the next step loading the HAL is failing. 

    For MDT 2008 I tracked a down "fixed" script that had to be loaded in the task sequence:
    after "Inject drivers"

    add command line to run HAL.wsf
      -this seemed to do a good job adjusting the HAL drivers

    But even with this changes in 2010, I still get a dead machine. -I'm pretty certain I have all the same drivers available since I imported them from the 2008 driver share.

    more info:
     found the old BDD.log for the same machine imaged with MDT 2008 and it once identified the HAL:
    ...
    Property HALName is now = acpipic_up
    ...
    Copying HALACPI.DLL to C:\Windows\System32\    HAL    9/22/2009 3:14:40 PM    0 (0x0000)
    Copying NTOSKRNL.EXE to C:\Windows\System32\    HAL    9/22/2009 3:14:40 PM    0 (0x0000)
    Copying NTKRNLPA.EXE to C:\Windows\System32\    HAL    9/22/2009 3:14:41 PM    0 (0x0000)
    rename HAL and Kernal files    HAL    9/22/2009 3:14:41 PM    0 (0x0000)
    HAL processing completed successfully.    HAL    9/22/2009 3:14:41 PM    0 (0x0000)
    ...

    -Now in 2010 the same machine produces:
    ...
    Property HALName is now = acpipic
    ...
    Skipping Device ACPI_HAL\PNP0C08 No 3rd party drivers found
    ...

    -Odd that the HALName would be different.. I have a sinking feeling!



    Wednesday, November 11, 2009 3:43 PM