 HAL.DLL missing or corrupted on /APPLY |
  |
 Apr 14 2008, 02:05 PM
Post
#1
|
|
|
K-Mart-ian Legend  Group: Members Posts: 1159 Joined: 28-April 06 From: Buffalo, NY Member No.: 94953 OS: Server 2008 x64 
 |
Alright here is a weird one that I haven't experienced yet, although I have a lead on it already.
I have a machine that I captured an XP image from. The volume table is as follows: vol 0: ltr=c; label=; FS=NTFS; Type=Part; Size=61GB; Status=Healthy; Info=; vol 1: ltr=; label=; FS=FAT32; Type=Part; Size=14GB; Status=Healthy; Info=Hidden; I created the image as follows: CODE [diskpart] select disk 0 select part 1 select vol 1 assign letter=d: [imagex] imagex /capture c: z:\image.wim "C Drive" /compress fast imagex /capture d: z:\image.wim "D Drive" /compress fast Then I redploy the image back onto the source machine. The only difference is that the partitions are backwards because of Microsoft's Standard Practices for using diskpart. CODE [diskpart] select disk 0 clean create part pri size=14096 select part 1 assign letter=d: format fs=fat32 quick create part pri size=62220 active assign letter=c: format fs=ntfs quick exit [imagex] imagex /apply z:\image.wim "Drive C" C: imagex /apply z:\image.wim "Drive D" D: [diskpart] select disk 0 select part 1 select vol 1 att vol set hidden att vol set nodefaultdriveletter set id=12 [imagex] attrib c:\boot.ini -R +A -S -H copy v_boot.ini 1 attrib c:\boot.ini +R -A +S +H The boot.ini is replaced because the boot volume is now different than the one that was captured. All I did was change the VOLUME(1) to (0) but should I need to change that to (2)? So on bootup I get the HAL.DLL is missing or corrupted, but if I use NTFSDOS (or reboot back into the PE) I can see that the file is there. Also now the vols look the same as above, except the Vol #s are switched. LMK if anyone has any ideas. |
 |
 
|
|
Apr 22 2008, 07:37 PM
Post
#2
|
|
|
Newbie Group: Members Posts: 16 Joined: 9-March 05 Member No.: 47120 
|
QUOTE (Tripredacus @ Apr 15 2008, 06:05 AM)  Alright here is a weird one that I haven't experienced yet, although I have a lead on it already. I have a machine that I captured an XP image from. The volume table is as follows: vol 0: ltr=c; label=; FS=NTFS; Type=Part; Size=61GB; Status=Healthy; Info=; vol 1: ltr=; label=; FS=FAT32; Type=Part; Size=14GB; Status=Healthy; Info=Hidden; I created the image as follows: CODE [diskpart] select disk 0 select part 1 select vol 1 assign letter=d: [imagex] imagex /capture c: z:\image.wim "C Drive" /compress fast imagex /capture d: z:\image.wim "D Drive" /compress fast Then I redploy the image back onto the source machine. The only difference is that the partitions are backwards because of Microsoft's Standard Practices for using diskpart. CODE [diskpart] select disk 0 clean create part pri size=14096 select part 1 assign letter=d: format fs=fat32 quick create part pri size=62220 active assign letter=c: format fs=ntfs quick exit [imagex] imagex /apply z:\image.wim "Drive C" C: imagex /apply z:\image.wim "Drive D" D: [diskpart] select disk 0 select part 1 select vol 1 att vol set hidden att vol set nodefaultdriveletter set id=12 [imagex] attrib c:\boot.ini -R +A -S -H copy v_boot.ini 1 attrib c:\boot.ini +R -A +S +H The boot.ini is replaced because the boot volume is now different than the one that was captured. All I did was change the VOLUME(1) to (0) but should I need to change that to (2)? So on bootup I get the HAL.DLL is missing or corrupted, but if I use NTFSDOS (or reboot back into the PE) I can see that the file is there. Also now the vols look the same as above, except the Vol #s are switched. LMK if anyone has any ideas. This has certainly got something to do with your boot.ini file. I was getting the same result and had to change the volume number to 2 to get it to work for me |
|
|
|
|
Apr 23 2008, 12:24 PM
Post
#3
|
|
|
K-Mart-ian Legend Group: Members Posts: 1159 Joined: 28-April 06 From: Buffalo, NY Member No.: 94953 OS: Server 2008 x64
|
Not only did I find that out... I figured that the volume ID would start at zero but it starts at one instead. I also realised that since I wasn't creating an EFI or other special partition, the recovery partition wasn't required to be part 1, so I changed the pathing and it now works properly.
|
|
|
|
|
May 15 2008, 09:00 AM
Post
#4
|
|
|
Group: Members Posts: 2 Joined: 15-May 08 Member No.: 192046 OS: 98SE 
|
Hi
You forgot the /boot switch your line should look something like this: imagex /capture c: z:\image.wim "C Drive" /boot /compress fast Tamir |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 2nd December 2008 - 11:04 PM |
All trademarks mentioned on this page are the property of their respective owners
MSFN is not affiliated with Microsoft
Copyright © 2001-2008 msfn.org
Privacy Policy
MSFN is not affiliated with Microsoft
Copyright © 2001-2008 msfn.org
Privacy Policy