GDism ELDI : A GUI for managing WIM images (akhirnya bisa mengubah file dot wim)

A while back I introduced DISM, the new tool of the Windows 7 WAIK (Windows Automated Installation Kit) for managing WIM images. I was complaining then that Microsoft doesn’t offer a GUI (graphical user interface) for such an important tool. The nice thing about Windows is that if Microsoft doesn’t provide a function, someone else steps into the breach. ELDI was kind enough to link to his free DISM GUI GDism ELDI in my original post. I’ve taken a quick look at the tool.
Let me start with the tool’s downside. It requires the Java Runtime Environment (JRE). I think it would be more useful if it were a portable application. However, if you use GDism only on your desktop, it is certainly more convenient than using DISM on the command prompt.
GDism also requires you to install the Windows Automated Installation Kit (AIK) for Windows 7because it launches DISM from its GUI. I didn’t find an option to tell GDism where DISM is located, so I just copied all its files to the folder where all the WAIK tools are located (C:\Program Files\Windows AIK\Tools\PETools). I suppose adding the directory to the PATH environment variable would have worked as well.
To run GDism, you have to launch the “Instalar” file. If you don’t speak Spanish, you might want to switch the tool’s user interface to English. You can find the switch in the lower right pane on the mount tab.
I won’t discuss all of GDism’s functions because that would essentially boil down to describing DISM. You can mount WIM images and apply all kinds of changes, such as adding packages or drivers. The main advantage of using GDism is that you don’t have to remember all the command line switches and can just focus on your main task. The DISM messages are displayed in GDism’s lower pane and are also logged in a text file; therefore, you won’t miss anything that DISM has to complain about.
Let me know your experiences if you tried the tool.
If you are interested in GUI for DISM, you may also like GImageX, a GUI for ImageX.
I make this small program in java for use the Dism.exe present in Windows 7 with GUI or Visual Mode, you can mount/unmount images *.wim, edit it, commit changes, add/remove updates, add/remove drivers, upgrade to higher edition, make iso image, convert packages msu to cab, etc,

Commands you can use on GUI or Visual Mode:
* Mount-Wim
* Commit-Wim
* Unmount-Wim
* Get-WinInfo
* Get-MountedWinInfo
* CleanUp-Wim
* Get-Packages
* Add-Package
* Remove-Package
* Get-Drivers
* Get-DriverInfo
* Add-Driver
* Remove-Driver
* Get-Features
* Enable-Feature
* Disable-Feature
* Get-Apps
* Get-AppsPatches
* Get-CurrentEdition
* Get-TargetEditions
* Set-Edition
* Set-ProductKey
* Convert MSU to CAB
* Make ISO
You must need the JRE installed (Java Runtime Enviroment).

v3.0.2: Fixed Progress Bar
v3.0.1: Fixed Close aplication
v3.0: ReMake all code!!

Explain in a simple way how to use the GDism.

To Serve:

1. The image is a single *.wim file you supercompreso and which contains the operating system files (install.wim) or multiple files depending on the case.

2. In order to decompress and edit the files within this image, use the Dism or Imagex, both fulfill this function, but Dism is more oriented towards the seven and is newer than the imagex.

3. To view the contents of the *.wim image, you must "mount" the image to a directory, this would be similar to unzip the files in a directory, this will temporarily to close these files must "unmount" the image again.

4. When we look at what's in this picture is nothing that the folders and files that will be on drive C, in the case of install.wim, any changes to these files will be reflected when the operating system to install these files will go to the drive .

5. For this reason we can add drivers, add updates and even change some system files from that folder, making sure to save your changes when you remove the image.

6. Each of the functions of dism is used in commands by writing each of the parameters, so the the Gdism design, which is the GUI in English, translated would be something like user visual interface.

As Used:

0. To see the use of any command, we can write Dism /?, therefore Dism /? to help specify a command in the command.

1. In Mount Wim tab, go to "Mount", "Unmount" and "Commit changes". To mount the image, we first look for the *.wim image, then the directory where you uncompress all the files. Each *.wim image may have various editions, e.g. HomeBasic, Starter, Ultimate, etc, each of these issues has an index or number that identifies it within the *.wim, for this select the "Index" of of interest. Also choose if you only want to see its content without making any changes and mount the image so the "Read Only", otherwise it will be on "Commit Changes".

2.To see what the index and what are the issues that have a *.wim image, go to the Info tab Wim, and we give "WimInfo" if not already assembled, "MountedWimInfo", if it is mounted and want detailed information.

3.When editing an image can save changes without removing it for further work, we give "CommitWim", for when we've finished all the changes we will "UnmountWim", if some reason do not want to save the changes, then dismantle with "Read Only", so be unmounted without saving.

4.When disassembling for any reason fails us, then stay orphaned files in the installation directory to remove must be removed completely by, for these cases is used "CleanUpWim", sometimes we must "close the explorer" to unmount an image.

5. To push updates go to the Packages tab, selecting a single file can *.msu or *.cab or an entire folder that contains these packages, then go to "AddPackage."

6. Delete an update for this you must write the exact name of the package, to know that package are already inserted in the image to go to "GetPackage" from there copy the exact name of the package and "RemovePackage", e.g. Package_for_KB2028749~31bf3856ad364e35~amd64~~6.1. 1.0

7. "OnLine" lets us do what we do to the image mounted, but our operating system in execution, so we can install multiple updates through our system.

8. The drivers are the same idea of the updates.

9. High Edition allows us to upgrade an image from one edition to another, for example spend a Starter to HomePremium, this will see that issues are possible to convert the current image "GetTargetEditions", then select which is the desired version and we "SetEdition" if want to give a key to the new edition upgraded using the "SetProductKey."

10. Process List, created in order to automate many actions by pressing the right buttons and go running as the previous completed, ie, assembling and disassembling takes time, so I can mount, package converting, insert updates, add drivers, unmount, create iso, in this order provides instructions and everything will be automatic and sequential.

11. Create iso, Oscdimg tab, this would be the last step, when we create our iso image to be recorded on DVD, in anger tag name, and the option to boot only serve to create images of sight or seven.In the source folder will always select the folder where the directory and other sources, so that everything will stay in the DVD.

12. To msu cab, this utility serves to convert the format msu updates in cab format, highly recommended before inserting the updates happen to cab, you can choose a single *.msu file or a folder full of them, will choose the destination folder where saved *.cab.



Back To Top