tistou77

it with 87 Updates integrated (7 x64 sp1) yes but with vLite, must install an update for the following updates are possible I prefer something clean Better to delete the file pending.xml after or it did not matter? thanks

1.37Go (7 sp1 MSDN) I prefer to use rt7lite to Vlite, no need to install the famous Update using rt7lite

If we remove winsxs (with rt7lie) but after you do not delete the file pending.xml How does it feel? thanks

in Gimagex, Capture tab, you have indicated Name: Windows 7 Professional (example) Description: Windows 7 Professional (example) ?? Me, I check the box, apply to this image or something like that (to create the image) in Vlite and installation of 7 launch directly I do not know if it makes a difference, but I have this in last session file

for install2.wim, you just indicate in the fields, when the. wim will create, he will have this name Me, I use first Gimagex then Vlite and I finally rt7lite if we use first rt7lite is an error message launching Vlite about the boot (boot-optimized by rt7lite and not "compatible" with vLite) Indeed, I have not yet to find how "unmount" I use "take ownership" on each folder and delete the files after

ok I do as you indicated above (but not first used rt7lite) how you made to "apply " on install.wim, and after unmounting? if I understood, you personalize 7 with rt7lite, and after you use Gimagex thanks

if we just mounting/dismounting install.wim with Gimagex, it not work (after using vLite, there are corrupt files) I have not tested it with just "export" but not sure it works PS: dism does not reduce the image size

I don't understand ^^

I start directly with Gimagex (not rt7lite) in the Apply tab, and after I finish with "Create " that's why the image is not unmounted after? no difference to this?? (except that the image is not unmounted) thanks

Then put the folders/files to install Windows 7 in the folder "x64_sp1" (for my example) with Gimagex, in the "Apply" tab Source: [path to file] x64_sp1\source\install.wim Destination: an empty folder (Mount in the screen) select the image used for install (Home, Pro, etc ...) and Apply when process is finished go "Capture" tab Source: empty folder path (Mount in the example) Destination: [path to file] x64_sp1\source\install2.wim Name: Windows 7 Pro (in the example) Description: Windows 7 Pro (in the example) Compression: Max leave the rest blank and Create when finished, in the [folder path] x64_sp1\source, delete install.wim and rename install2.wim in install.wim restart PC and launch Vlite normally (like if it's Vista)

so no need to install WAIK, change wimfltr.sys files, etc... just use the Gimagex 2.0.17 with Create and Apply tabs I tested 2 times and 2 times, no corrupted files with Windows 7 SP1 MSDN I will install tomorrow to be sure everything is OK I will explain in detail how I do

it works very well, just using first Gimagex and after Vlite I tested a second time to be sure

with rt7lite, there is no problem ...

you're tested? it's good?

if I understand should be used rt7lite, customize 7 as we want, once the process is complete, use Gimagex with the new install.wim done by rt7lite, right? thanks you very much EDIT: in the Capture tab, I put in destination [7lited win7]\sources\install2.wim and deleted install.wim (original) and replaced by install2.wim is good? but once the process install.wim mounted in the empty folder, is not unmounted after...

I was talking about the OS de dead0 bapt Sorry to say that you are wrong and xpJohnson is right instead. Quoted from Wikipedia: 1. WAIK 1.0—Released with Vista 2. WAIK 1.1—v6.0.6001.18000—Released with Vista SP1 and Windows Server 2008 Filename: 6001.18000.080118-1840-kb3aikl_en.iso Version: v936330AIK – Released: 4/9/2008–1375.9 MB 3. WAIK 2.0 - v6.1.7000.0—Released with Windows 7 Filename: KB3AIK_en.ISO 4. WAIK 2.0 RC: 6.1.7100.0—Released with Windows Vista Filename: KB3AIK_en.ISO 5. Win7 WAIK / WAIK 3.0: 6.1.7600.16385 Includes DISM.exe, same version number Filename: KB3AIK_en.ISO Version: v3.0—Released: 8/6/2009—1706.6 MB Windows AIK version 3.0 is the exact same as 2.0. The hash values of the ISO images are exactly the same. ok I had seen this for the WAIK 2 WAIK 2 => 6001.18000.080118-1840-kb3aikl_en.iso (4/9/2008) http://www.microsoft.com/downloads/en/details.aspx?FamilyID=94bb6e34-d890-4932-81a5-5b50c657de08

could not remove the components without using Vlite? with imagex or dism, directly the problem will be the same?

7 x86 of dead0 take 5GB of disk space, it does not remove many component unless it has installed software or other

when "ownership"in the winsxs folder and its contents, it is the owner is that possible to "TrustedInstaller" as owner after the change? thanks

WAIK 1.1 => WAIK for Windows Vista WAIK 2 => WAIK for Windows Vista SP1 et Windows Server 2008 WAIK3 => WAIK for Windows 7 not wimmount.sys on WAIK 2

with the wimmout.sys of WAIK3, imagex and gimagex does not run (error) with WAIK2 (Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008) there is no file wimmout.sys (just wimfltr.sys) and it is the same as that used with vlite

I'll try this wimmount.sys of the WAIK3 is not good?

I tested with Gimagex, and it works not after using vLite, there are corrupt files when I used Gimagex is the wimfltr.sys (windows\system32\drivers) of Vista I think I used Vlite "normal", with wimgapi and wimfltr.sys files (6.0 6001 18000) for Vista is not good? EDIT: OS of the PC where I'm testing is a 7 x64 (sp1 integrated)

it's Gimagex 2.0.17, it's good? if you just mount/unmount install.wim, is really simple I tested With Gimagex

you can not use Gimagex? must mount "install.wim" with imagex of the WAIK 2.0? and just need to mount (do nothing) and unmount the image with commit change (we have not done)? then run Vlite "normal" is that all? thanks