tistou77

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

ok thank you for your feedback

I've tested with a "take ownership" that works, Monkie53'software (to change the date) does not work for me (error message) I used another software, changed the 3 dates "winsxs" folder (and contents) on 13/07/2009 and that's OK with vLite, no problem I also change the date of the "windows" folder (not contents) on 14/07/2009 is what to do or not?

I removed the protection on any files contained in winsxs (and also winsxs) with software to modify the attribute, and I changed the date of winsxs and all content I used vLite, reboot and mounted install.wim with gimagex winsxs is the date of 13/07/2009 (the 3 dates) and all content winsxs also and I always corrupt files

I tested other software to change the date and time I set 13/07/2009 and 20h20mn00s for winsxs and all contents of winsxs Some folders in winsxs are to 14/07/2009 (I know not why) save the change, and unmount install.wim reboot and mount install.wim with gimagex and the .dll, .exe files are still corrupted ... I'm testing on a x64... after, why changing the date of winsxs, Vlite that will be compatible? I tested with Windows 7 and sp1 integrated, "date modified, etc...." are not changed and it works very well and the "creation date" is the same (creation date: 14/07/2009) for 7 sp1 MSDN and 7 sp0 and sp1 integrated thank you to explain EDIT: after I tested on a install.wim where I customize some dll (imageres, etc. ...) but no problem with windows 7 and sp1 integrated

for winsxs, I can do it, but I receive an error message for all files/folder located in winsxs (it's good and not?) and "Change_Folder_Date_Time" how to do, then? I can not change the date? thanks

yes

the "take ownership " does not work with me, I right click on winsxs but nothing happens (the window "cmd"opens and closes, immediately) Why? and I can not use the "Change_Folder_Date_Time" (see above) thanks

yes

I can not change the date and time .... I mounted install.wim, use the "Take Ownership" in the winsxs folder (I did not even have time to see the Windows command prompt ) and it not work, the file is still locked (delete and rename) but I can not change the date with "Change_Folder_Date_Time" what do I forget? thanks

hello monkie53 thank you for your great work if I understand it, take possession on the "windows" and "winsxs" folder (when mounted install.wim with Gimagex example), and apply your patch, right? thank you very much

thank you for this list I will add spwizimg.dll in SysWOW64 WinMgmt.exe in System32 Will someone an idea to make it compatible Vlite with 7 sp1 MSDN?