[MrJinje]

C: drive oranges, now your catching on, when you mount your WIM the files inside the mount folder are actually your C: drive. Any changes you make will show up in your installation as the new C: drive. That's the secret, Install.wim is the C: drive.

Not sure told you it looks like the DVD sources folders, but it doesn't.

Apples, Oranges, I'd rather pluck a Peach any day of the week.

[rasty]

I guess I am at square one. How to make a new install disc with the updates and drivers. I thought I could use Dism.

[Gremo]

 Hey thank you for helping I'm now able to integrate some drivers of my notebook (nvidia, audio, wifi) using DISM. Look at my guide (it's in Italian, but its quite clear) here. I'm still looking for an help on Intel Chipset Installation Utility and LManager (keyboard/fn buttons for acer and some packard bell notebook). Also still looking for a simple way of backup and restore activation!

[rasty]

Oh great!. First Greek, now Italian.

[Gremo]

rasty, on 17 March 2010 - 03:51 PM, said:

Oh great!.  First Greek, now Italian.  

JUST look at the "code" sections in that topic, it's really quite simple. 

[rasty]

Somehow . . . thru this thread . . . I have entered an alternate universe

[grabben]

Mr.Jinje the man!


How bout some kind of update for your tool?
Some kind of remake of GUI and add other "tools" using dism?

Not sure what that could be tho but i guess having a small app instead of using WAIK is a good thing.

[MrJinje]

rasty, on 17 March 2010 - 02:33 PM, said:

I guess I am at square one. How to make a new install disc with the updates and drivers. I thought I could use Dism.

All this can do is edit your install.wim and boot.wim files. This cannot make you a new install disk, after you integrate your drivers/updates using DISM, then use PowerISO or OSCDIMG.exe from the WAIK to create a new ISO.

Gremo, on 17 March 2010 - 03:42 PM, said:

I'm still looking for an help on Intel Chipset Installation Utility and LManager (keyboard/fn buttons for acer and some packard bell notebook).

Easy way is to install them into a live OS, then use something like Driver Magician Lite to export them. Here is the link for the portable version.
http://www.drivermag...PortableDML.zip

If the LManager is an application and not a driver it may not work, but you will definitely be able to export your chipset drivers from a live OS

This post has been edited by MrJinje: 17 March 2010 - 10:45 PM

[rasty]

MrJinje, on 17 March 2010 - 10:36 PM, said:

All this can do is edit your install.wim and boot.wim files. This cannot make you a new install disk, after you integrate your drivers/updates using DISM, then use PowerISO or OSCDIMG.exe from the WAIK to create a new ISO.

I guess there is no way around downloading the WAIK. Although PowerISO will let you open a .wim and extract the contents, there is no option to save in .wim format.

[MrJinje]

Let it be known that DISM Tool™ is not for people looking for something that can replace vLite. There are plenty of other stickies with user friendly GUI's attempting to clone vLite's interface/capabilities. If you wait until Saturday, Bensam56 is releasing the next version of 7Lite, it is more of a vLite replacement than DISM Tool™

and FYI. Use PowerISO to make your ISO, not edit your WIM. What you do is open your .ISO file with PowerISO, then you dragon-drop your modified WIM (the one you mentioned in your first post) into your ISO and save as a new ISO file.

[rasty]

Mr. Jinje:

The whole problem I have been having is how to stuff these modified folders back into a .wim image file. I don't remember where I read this, but on my way here, I seem to recall reading that having/using Dism meant that you did not have to install the Waik. From my experience so far, I haven't found any alternative yet to downloading and installing the Waik.

Since I have been working on this since LAST Saturday, I guess waiting a couple more days won't matter.

I do appreciate the DISM Tool™, so thanks for that.

[MrJinje]

rasty, on 18 March 2010 - 12:15 PM, said:

Mr. Jinje:

The whole problem I have been having is how to stuff these modified folders back into a .wim image file.

Your kidding me right ? The way to "stuff" the modified files back into the Install.wim is by hitting the Commit button. Which I am pretty sure you mention doing in your very first post. My bad for not knowing what you were talking about, but at first glance I thought you were already done.

rasty, on 17 March 2010 - 11:51 AM, said:

I added drivers and updates (packages).
I committed the changes.

So my guess is they are already stuffed. Did you try re-building your ISO with the modified Install.wim, that is the next step.

This post has been edited by MrJinje: 18 March 2010 - 01:09 PM

[Makave2345]

rasty, on 18 March 2010 - 12:15 PM, said:

Mr. Jinje:

The whole problem I have been having is how to stuff these modified folders back into a .wim image file. I don't remember where I read this, but on my way here, I seem to recall reading that having/using Dism meant that you did not have to install the Waik. From my experience so far, I haven't found any alternative yet to downloading and installing the Waik.

Since I have been working on this since LAST Saturday, I guess waiting a couple more days won't matter.

I do appreciate the DISM Tool™, so thanks for that.

If your wanting to install drivers, updates, and software addons, and also create your finsished .iso give this a try...

http://www.wincert.n...-toolkit-06015/

And you can check out here for all the software addons I (*Reaper*) and others have made for this program.

http://www.wincert.n...toolkit-addons/

[rasty]

MrJinje, on 18 March 2010 - 01:01 PM, said:

Your kidding me right ?

Of COURSE I was kidding! NO-ONE could be that lame!

Nice talking to you'all. I have to go change my name now.

[ner]

followed, and injected 35 updates and also 19 drivers all reported at 100% suc, then committed and un-mounted copy install.wim backto dvd over write old file, and re-installed under virtual pc, not one of the updates installed nor can i see any drivers. so what has gone wrong i wonder - maybe an issue with commit??>

[MrJinje]

ner, on 04 April 2010 - 10:47 AM, said:

followed, and injected 35 updates and also 19 drivers all reported at 100% suc, then committed and un-mounted copy install.wim backto dvd over write old file, and re-installed under virtual pc, not one of the updates installed nor can i see any drivers. so what has gone wrong i wonder - maybe an issue with commit??>

Which image did you mount ? My guess is you mounted image #1, but actually meant to mount image #4 or #5 (ultimate x64,x86 respectively).

x86 default to this.

starter =1
home basic =2
home premium =3
pro=4
ultimae=5

x64 is different. (because it has no starter image)

home basic =1
home premium =2
pro=3
ultimae=4

To verify this, try installing either starter/homebasic into your VM and see whether or not the drivers/updates worked on that image. If yes, then just repeat the process on the proper image (for ultimate it is either #4 or #5) and you will be good to go.

[ner]

MrJinje, on 04 April 2010 - 11:18 AM, said:

ner, on 04 April 2010 - 10:47 AM, said:

followed, and injected 35 updates and also 19 drivers all reported at 100% suc, then committed and un-mounted copy install.wim backto dvd over write old file, and re-installed under virtual pc, not one of the updates installed nor can i see any drivers. so what has gone wrong i wonder - maybe an issue with commit??>

Which image did you mount ? My guess is you mounted image #1, but actually meant to mount image #4 or #5 (ultimate x64,x86 respectively).

x86 default to this.

starter =1
home basic =2
home premium =3
pro=4
ultimae=5

x64 is different. (because it has no starter image)

home basic =1
home premium =2
pro=3
ultimae=4

To verify this, try installing either starter/homebasic into your VM and see whether or not the drivers/updates worked on that image. If yes, then just repeat the process on the proper image (for ultimate it is either #4 or #5) and you will be good to go.

I see i selected 1 so not seen in installed version which is 5 - so sorry , maybe put this info on post 1?

thanks

This post has been edited by ner: 04 April 2010 - 11:28 AM

[ner]

Update

Selected the correct index number = 5 ran to incluide 35 updates and 19 drivers and works.

However I am going to use the prefered method of placing the drivers within OEm and call them through the xlm file, as it easier to update and manage the drivers going forward. But a really good tool, just some feedback for you by pressing the "More Info" button you get an empty folder called "DISM" on your desktop not sure what this is all about.

But never the less a good tool!

[ner]

ner, on 05 April 2010 - 06:05 AM, said:

Update

Selected the correct index number = 5 ran to incluide 35 updates and 19 drivers and works.

However I am going to use the prefered method of placing the drivers within OEm and call them through the xlm file, as it easier to update and manage the drivers going forward. But a really good tool, just some feedback for you by pressing the "More Info" button you get an empty folder called "DISM" on your desktop not sure what this is all about.

But never the less a good tool!

now, it would be great to have this tool updated, so that you can insert drivers and updates into all 4 images..... please?

[MrJinje]

ner, on 06 May 2010 - 03:35 AM, said:

now, it would be great to have this tool updated, so that you can insert drivers and updates into all 4 images..... please?

That can be done with a simple batch script. Here is the link.