x90 and v90 Imaging Question

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
  • #1163
    • Total Post: 4
    • Newbie

    After bringing the base image of either system to a machine, creating a custom image and then pushing the image back into WDM, the image size is the size of the drive including unused space. Is there a method to remove the unused space from the custom image, or is this a bug with the 4.5.3 version of WDM?Factory images are 4-500mb and the custom image is 2gb. Any information would be helpful.


    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Nuke,

    You are correct, the factory image has a script that expands it to the size of the available flash in a one off process.

    When you “pull” an image with WDM it takes a sector by sector copy of the drive so you get one VERY large image.

    Currently there is no way around this as WDM does not have compression of the image built in – it would be a very nice feature. Only choice is use a third part tool like ghost,


    • Total Post: 4
    • Newbie

    I had a feeling that I was stuck with what i had in terms of image sizes. I appreciate the quick response.



    • Total Post: 20
    • Regular Joe
    • ★★

    depending on your needs and dedication, VMWare p2v the box, shrink it to just over the “used” space, then “pull” it?

    It’s a theory I’ve heard of but never tested it due to time constraints.

    I don’t think partitioning will work at it will still snap c: and d: and come to 2gb. Pushing 2gb down a WAN isn’t the pinnacle of centralised remote management 😡

    • Total Post: 11002
    • Jedi Master
    • ★★★★★★★

    I have just tested P2V last week to create a XPe VMware session for testing. P2V does not run on XPe. So I ended up on good old Ghost and BartPE.


    • Total Post: 53
    • Back Stage Pass
    • ★★★★

    I have had good success with using our Ghost server. The one trouble spot you run into is the Wyse terminals (atleast the older models, we currently have 9150’s for most of our systems) do not like to do a direct network boot, so you have to create Ghost network boot floppy disks. (slightly slower loading)

    I have pulled a 1gb image from a V90L (which really was only about 450mb) and pushed it down to a 512mb V90L. Same with a 256mb 9150 build to a 512mb 9150. Just make sure you use the command line switches -fni and -fdsp, do not use -auto or -sure, and it will prompt you and ask if the partition size is correct and you can modify it from there to expand or shrink depending on the application.

    If you would like more details, let me know and I can send screenshots.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.