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:

[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.

[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.

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:

[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.

[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

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.

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