1 of 1 people found this helpful
On your image capture settings are you using imagew v2 for the type of image setting? If so by default the options to capture are set to capture the entire drive. When you are saving the OSD script the is a pop-up window that appears with additional options for the imaging tool. If you look at those options you will see /d:0 as one of the switches. That sets it to capture the entire drive 0, including all partitions. If you change that to /d:0@3 it will only capture partition 3 on drive 0.
What that is saying then, is the code behind the GUI to select which partition to capture is broken? .. if you have to manually change it later in the GUI popup of the command line.
I captured the actual partitions not the whole drive, my partitions are pretty small (40 Gigs) to make sure I don't have any issues pushing it to a machine with a smaller hard drive.
I actually solved this in a more round abaout way. I had an extra drive here, so I put that in my machine. My images will both have their own drive on the logical active partition and then this shouldn't be a problem.
Thanks for the info on the /d switch though, thats exactly what I will need now to capture images across different disks.
No the gui is not broken. The gui only references which partition is the system partition. It does not indicate which partition to capture.