sysprep hal error
Help!
I cannot get my sysprep image to work. Here is the order in which I'm trying to get sysprep working:
1. prep a machine (xp pro sp1)
2. copied sysprep folder to c:\[root] (sysprep 2.0)
3. ran sysprep -bmsd
4. i replaced the Hals in system32\ (with expanded Halacpi.dl_ to hal.dll and NTOSKRNL.EX_ to ntoskrnl.exe)
5. ran sysprep (with "mini setup" and "dont reset grace period for activation" selected)
6. reseal > shutdown
even if i powered up the machine after doing this id get a hal error (windows could not start because the following file is missing or corrupt: <windows root>system32\hal.dll. please re-install a copy of the above file" (so it wont even work on the source machine much less on a different machine)
any help would be GREATLY appreciated![:)]
I cannot get my sysprep image to work. Here is the order in which I'm trying to get sysprep working:
1. prep a machine (xp pro sp1)
2. copied sysprep folder to c:\[root] (sysprep 2.0)
3. ran sysprep -bmsd
4. i replaced the Hals in system32\ (with expanded Halacpi.dl_ to hal.dll and NTOSKRNL.EX_ to ntoskrnl.exe)
5. ran sysprep (with "mini setup" and "dont reset grace period for activation" selected)
6. reseal > shutdown
even if i powered up the machine after doing this id get a hal error (windows could not start because the following file is missing or corrupt: <windows root>system32\hal.dll. please re-install a copy of the above file" (so it wont even work on the source machine much less on a different machine)
any help would be GREATLY appreciated![:)]
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Imaster
18 years ago
Right concept, incorrect sequence order. Try this link for the answer:
www.multipcimage.com[8|]
www.multipcimage.com[8|]
Posted by:
rob929rr
18 years ago
We do a similar thing here, except we don't actually replace the ntoskrnl.exe file.
1. Create image using unattend.txt, sysprep in factory mode (winbom.ini all the apps).
2. Sysprep, reseal.
3. Create image
When the PC boots up, it boots up a windows 98 command shell. I then use AWK and another utility to ascertain the hardware we are running on and put the appropriate HAL.dll file in place (ACPI, STD, etc). I then modify (well copy over) boot ini to that it no longer boots W98.
You obviously have to include all the files to do this within the build itself. It also means you have to convert to NTFS after this happens (so W98 can read the FS) and set all of your FS perms.
re: drivers.
All the drivers for all my PC types are also included in the build under C:\Drivers\ and sorted accordingly. eg C:\Drivers\Audio\ADI198x.
before sysprepping I run a vbscript which enumerates all of these folders and pumps it into sysprep.inf into the following section:
[Unattended]
OEMPnPDriversPath = C:\Drivers\Audio\ADI198x;C:\Drivers\Audio\Soundmax;etc;etc
1. Create image using unattend.txt, sysprep in factory mode (winbom.ini all the apps).
2. Sysprep, reseal.
3. Create image
When the PC boots up, it boots up a windows 98 command shell. I then use AWK and another utility to ascertain the hardware we are running on and put the appropriate HAL.dll file in place (ACPI, STD, etc). I then modify (well copy over) boot ini to that it no longer boots W98.
You obviously have to include all the files to do this within the build itself. It also means you have to convert to NTFS after this happens (so W98 can read the FS) and set all of your FS perms.
re: drivers.
All the drivers for all my PC types are also included in the build under C:\Drivers\ and sorted accordingly. eg C:\Drivers\Audio\ADI198x.
before sysprepping I run a vbscript which enumerates all of these folders and pumps it into sysprep.inf into the following section:
[Unattended]
OEMPnPDriversPath = C:\Drivers\Audio\ADI198x;C:\Drivers\Audio\Soundmax;etc;etc
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.