Jump to content

Recommended Posts

Posted

Hi,

Just a quick question i created a wim and ghost build for a Dell laptop this laptop had two partions the dell partition and the OS target partition.

the build went on perfectly from wim pxe wds install, and fromthe standard ghost build disk install.

I then got in 4 more of the same laptops. The wim build failed to install. but ghost image worked fine.

this had me stumped for a couple of hours i couldnt figure out why it failed to install. it then dawned on me that the laptop have had there Dell partition deleted and the imageX wim was looking for it files on the partition 2.

Not 100% sure why the ghost image didnt have any problems but it didnt.

Is there any way to make a wim partition independent. as the the laptops that i am building may have different partition setups.

Hope that made sense.

Paul


Posted

I think it's because ghost does a sector-by-sector image capture and it also saves your partition boot record; whereas ImageX does not capture the boot record by default unless you tell it to.

I don't know the command for including boot sector but the GUI version (GImageX) has an option for "boot".

  • 2 weeks later...
Posted

was the wim image of the OS partition?

if so you are required to generalize the image before capturing. otherwise it will just BSOD and reboot loop.

to do this in windows vista you run the sysprep tool found in the windows\system32\sysprep folder. and tick the generalise box.

this will remove all installed drivers and main HAL information, this will be rebuilt on first bootup. unsigned drivers will not be re-installed.

Posted
was the wim image of the OS partition?

if so you are required to generalize the image before capturing. otherwise it will just BSOD and reboot loop.

to do this in windows vista you run the sysprep tool found in the windows\system32\sysprep folder. and tick the generalise box.

this will remove all installed drivers and main HAL information, this will be rebuilt on first bootup. unsigned drivers will not be re-installed.

That's only for Vista. The ThreadOP didn't mention which operating system he was deploying.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...