'Add the UpdateHAL command to the Sysprep.inf file. OLogging.CreateEntry "Updated SYSPREP.INF to replace HAL with uniprocessor PIC HAL", LogTypeInfo OUtility.WriteINI Sysprep, "Unattended", "UpdateUPHAL", """ACPIPIC_UP,c:\windows\Inf\Hal.inf""" 'Add the UpdateUPHAL command to the Sysprep.inf file. 'This is the PIC chipset (which is always uniprocessor) OLogging.CreateEntry "Windows PE is using HAL " & sHalType(0), LogTypeInfo SHalType = oShell.RegRead("HKLM\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\HardwareID") OLogging.CreateEntry "Configuring HAL replacement", LogTypeInfo This will tell us if we are running on a PIC or an APIC chipset. 'Get the HAL type from the registry (from Windows PE). OLogging.CreateEntry "f initialized.", LogTypeInfo Sysprep = oEnvironment.Item("DeploySystemDrive") & "\sysprep\Sysprep.inf" '// Global constant and variable declarations
If you can not get it to work, let me know, and i will write a more detailed guide on how to do this on my blog, og google it, there are plenty of infor on how to do this out there. Place it just after the OS has been deployed.
wsf script and yoy need to place ZTIUtility.vbs from MDT in your script folder as well (the utility script handles the writing to sysprep, and logging) You need to add a script to you TS that updates your HAL.
Those are missing somewhere, but could they be stopping the PC from booting up and if so how can I fix them? Released the resolved source C:\_SMSTaskSequence\ContentCache\BDC5CD73-A94C-4BED-B10E-46167FAA369Bįailed to find a suitable device driver for device 'ATA Channel 0'.įailed to find a suitable device driver for device 'ATA Channel 1'.įailed to find a suitable device driver for device 'RamDisk'.įailed to find a suitable device driver for device 'ROOT\ACPI_HAL\0000'.įailed to find a suitable device driver for device 'ROOT\VOLMGR\0000'.įailed to find a suitable device driver for device 'Generic volume'.įailed to find a suitable device driver for device 'USB\ROOT_HUB\4&17611003&0'.įailed to find a suitable device driver for device 'USB\ROOT_HUB\4&28CCEDB4&0'.įailed to find a suitable device driver for device 'USB\ROOT_HUB\4&30397EF5&0'.įailed to find a suitable device driver for device 'USB\ROOT_HUB20\4&1CDC4E97&0'.
The task sequence execution engine successfully completed the action (Apply Device Drivers) in the group (Install Operating System) with exit code 0Īction output: quence\ContentCache\BDC5CD73-A94C-4BED-B10E-46167FAA369B
Here is from SCCM server at applying drivers in my TS.
One of which is a hal but I'm not sure if its the issue. I am recieving the following issues though and I need help understanding them. I have seemed to get rid of that error with some chipset research and what not. I was wondering if anyone has run into similar problems or if anyone knows how I can recieve a driver file for this processor? Any help would be greatly appreciated.Īnother update. I did even more digging on the internet and found no where that you can obtain CPU drivers, since I guess people like myself don't think they are needed. I looked through my numerous drivers I have in SCCM, none of which are CPU drivers. This is the driver the the Intel M Processor 1.6, but I thought Windows XP would already have this in the cache. I am getting the Unable to find a suitable device driver for device:ĪCPI\ACPI003\0 -> From what I can tell its an AC power adapter driverĪCPI\FIXEDBUTTON\2&DABA3FF&0 -> Also an AC power adapter driver for the fixed buttonĪCPI\IBM0057\4&61F3B4B&0 -> Also power relatedĪCPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_13\_0 3 of which seem to not be mission critical but there is one that is keeping me stumped. I finally did some digging into the logs and found there are 4 drivers that aren't loading. I did several tests and none of them resulted in success. I thought it was a mass storage device or a HAL issue. I know this is a frequent issue by doing my research but none of those fixes work. When I do a safe mode option it loads up to agpcpq.sys. At the reboot, the computer just comes up to a black screen and freezes. When I run the task sequence everything runs fine until the reboot where it installs the configuration manager client. I've been having an ongoing issue with the T42 specifically.
I've got a universal image working for all our computers in the company except the T4x series from IBM.