romantiq
Content Type
Profiles
Forums
Events
Posts posted by romantiq
-
-
Speaking about imagex, dead0, I agree with you. But GIMAGEX don't need wimfltr (maybe because somehow is integrated his own in exe or in dll files). That is the reason I prefer GIMAGEX : shortest way to success
. But,, anyway, by your effort, the case is solved.EDIT .
In fact, wimmount is used for mount/unmount operations, like Microsoft help says :
Copy the following files into the same folder as gimagex.exe:
wimgapi.dll
wimmount.inf
wimmount.sys
WimMountInstall.exe
wimserv.exe
imagex.exe (optional, but handy if you also want to use the orginal command-line version of imagex)
You should now be able to run gimagex.exe from this installation folder to capture and apply WIM files. If you also wish to be able to mount WIM files then you need to also install the wimmount.sys driver by running WimMountInstall.exe.
0 -
I tested three times already with following few steps :
1. use GIMAGEX with install.wim , tabs APPLY, then CAPTURE of desired image; i placed wimgapi.dll for Win7 (downloaded from win a win7 PE project) in Gimagex folder and that was enough ;
2. use VLITE in "original state" - vista vimfltr and wimgapi.dll copied in the wellknown folders.
No need switching between wimfltr an winmount ! No need WAIK (I never hadn't hve that kit in my computer just wimgapi.dll for GIMAGEX).
Vlite and GIMAGEX don't use common files, because they running in separated environments. Believe me, wimfltr.sys of Vista was ONLY vimfltr used in entire operation, and ONLY for vlite. Who needs winmount.sys ?!
That's all, 2 simple steps, and I installed without any error 3 various images from Windows 7 SP1 AIO kit.
And to be shure, I worked with fresh instaled OS every time..
0 -
I just tested Gimagex/Vlite method on Windows 7 Homepremium x86. It works fine, like x64 version. Of course by using Apply/Capture in Gimagex, we select one specific image from install.wim (in my wim, 3 is Homepremium). I don't know how to apply Gimagex to all images in wim. But is not a problem, because the purpose of this action is to obtain a specific "lite version" ...
The instructions from bapt are very accurate, follow step by step and all will be OK.
0 -
The content of ISO must be extracted (WinRAR, UltraISO,...) into a folder. Then you can see a folder named "sources" where exists a file named install.wim. With Gimagex , mount that file in an empty folder, then unmount with commit changes (check this option in gimagex). Then you can use vlite. I hope that is clear.
0 -
The package removal works perfect with vista imagex (and more quickly, is true). And imagex removal works fine with vlite for Windows 7 images.
0 -
Well done, bapt ! It works indeed ... We are greatiful to dead0 - in special, and then to all those who gave as the ideas.. I am shure that, one day, , an another Dino Nuhagic will follow the excellent work of vlite creator !
0 -
I tried but after vlite operation , gimagex don't recognize the image. This metod works with RTLite, not with VLite
0 -
Is there another topic named "Safe WinSxS Removal With Vlite and RT Lite". Posters complains about same problem with Windows 7 SP1 RTM. But, look at these :
"""http://www.autoitscr...-tools/gimagex/
download it from there
choose the apply tab choose the install.wim that already lited with rt lite
and choose empty dir for destination
after it done choose capture tab
use maximum compressing and ultimate edition and fill up it with name """
and the replay :
"""Thanks, applying right now, will come back to update if it works!
*UPDATE: this works. Install finished with no errors. Tried first method: apply and capture from gimagex
Thanks again aviv00! """
Yes, is about Windows 7 SP1 image !!! . Read that topic ... From what I understand , FIRST is RTLite and THEN is mount/commit with GImageX v2.0.17 (dead0 wrote - FIRST mount/commit with imagex and THEN VLite, reverse order, if consider VLite instead RTLite ) . I will try with VLite . Maybe is working that way !
In fact is about apply/capture image ...
Forget about this ! Doesn't work ! Sorry !
0 -
Than you can change the date of winsxs folder, no ? I hope for you, my brain is on fire and I decide to watch some movies just to forget about painfull SP1 (I have the impression that Microsoft plans to release his own Lite Edition and vlite performances looks like an unwanted competition).
0 -
Strange : any of the images in kit which i mount with gimagex works fine with take ownership, but try the long way : Folder Properties Security Advanced Owner Edit and select your user from list , confirm the message, etc.
0 -
Maybe is a stupid question : your user is administrator ?
0 -
I mounted image no 3 (Home Premium) in gimagex , Take Ownership runs in CMD window for long time to be observed (10-15 min). Change Date prog worked and nou I see that only the 2 folders had to be modifyied, not all files in the 2 folders (monkey 53, sorry for missunderstanding)
0 -
Do you have cheched Read and Write in mounting step ?
0 -
Monkie53, I used an imagex batch (attached) which includes the ownership part for mounting install.wim, then I used a third party program to modify date. I verified in every moment files attributes just to be shure that the date is 07/13/2009 (all 3 dates). Even in final vlited ISO. I applied date modifications to ENTIRE Windows folder including subfolders (and , of course, including winsxs folder). But winload error is still there. I will try your application and i will modify dates in windows (without subfolders) and winsxs only (like you sayed). And I will use gimagex too ...
0 -
Ok, seems like Vlite causes erros in installation process by modifying files "digital signature" , so windows don't recognize files version. I think I will compare files in vlited wims from both versions of W7 SP1 (MSDN and slipstreamed). Sounds like is a crazy move, but what els can I do?
0 -
The question is : removing WHAT component(s) generates Vlite crash ? Some components of SP1 have something particular : another architecture, different dependencies ? But why in MSDN kit only? Questions ...
0 -
Sorry for my english too
(I am romanian) ... My work with Windows 7 is a little bit complex, because I use "7elite32" method for size reduction (vlite + some batches, another topic in this forum). This metod worked fine with original W7 kit, but in W7SP1 case my problem is the poor size reduction applied to original W7 kit+SP1. So I have tried MSDN SP1 kit and - surprize - vlited image don't work ! Windows cannot start after the first reboot . Too shame because the image and installation size both are very small, much smaller than image obtained with W7 original+SP1. I am sure that vlite must be "adapted" to the MSDN kit and therefore I believe that replacing wimfltr and wimgapi is seemed a good ideea.0 -
Dates of install.wim or boot wim are not relevant, is the date of release creation (depends of the creator) , but the rest of files date is 11/20/2010 when SP1 MSDN was released. Setup files, bootmgr and many other files are different (not just by date) between images and I think that vlite have problems with newest SP1 files.
0 -
named "07/13/2009 kit", the one that have SP1 slipstreamed. Vlite works perfect with that image.
0 -
Bapt, your image is based to original 07/13/2009 kit (I vlited this kit with no problems - see my post ...) so you dont need to modify the date. Date modification maybe useful for the "11/20/2010 SP1 kit". Btw, I used Total Commander for that task (submenu Change Attributes in Files menu).
0 -
I wish I tell that your - everyone - solution solved my problem, but my "lite" installation of W7 SP1 vlited fails - after first restart of installation - with a blank screen, with white text, telling me that : "Windows fails to start" with error code 0xc0000428, "Windows cannot verify digital signature of file : C:\Windows\System32\winload.exe", and inviting me to reboot with Windows 7 repair disc. In fact, i tried many times to install.
BUT, if SP1 is slipstreamed in original kit - with original 07/13/09 files (i found that kind of kit in a Legolash release) - w7 vlited installation works without any problem !!! In fact i applied that solution in my computer and works even today. Seems like 11/20/2010 kit have a compatibility problem (in vlite I see 3 patches in that kit, and vlite label that kit "Windows 7 with Service Pack 1", ... in 07/13/2009 I can see just SP1 patch and no reffrerence to SP1 in the very first screen after launching application.
0 -
Thank you very much, nuhy. You are suggested to fix my problem ! If my presets are good in your computer, the only explanation is THE KIT OF VISTA. The full release - 32 and 64 bit together in one DVD - don't works, but the release only for 32 works perfect. But I don't buy this edition, I'm waiting for a new version of VLITE, maybe I have luck, because, I repeat, VLITE 1.0 works with my kit, instead of the VLITE 1.1.
Thank you again for wasting time with my presets.
0 -
The attached file is an image of error, right on pressing the button.
0 -
Sorry for not be clear... After the selection of desired items to remove, when I pushed the "APPLY" button, an error window appeared, a .netframework error, and in DETAILS section - all those things described in first message. Options to resolve : CONTINUE and CANCEL, but altogh I pressed CONTINUE, nothing happened, no ISO creation, no other message, nor in VISTA or XP SO. VLITE 1.0 works fine, but VLITE 1.1b generates this error.
0
. But,, anyway, by your effort, the case is solved.
. Too shame because the image and installation size both are very small, much smaller than image obtained with W7 original+SP1. I am sure that vlite must be "adapted" to the MSDN kit and therefore I believe that replacing wimfltr and wimgapi is seemed a good ideea.
can vlite 7SP1 ?
in vLite
Posted
Is simple : that question was solved in topic : [sOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN) - three topics above,. The solution is that :
"I tested three times already with following few steps :
1. use GIMAGEX with install.wim , tabs APPLY, then CAPTURE of desired image (I preffered Home Premium) ; i placed wimgapi.dll for Win7 (downloaded from win a win7 PE project) in Gimagex folder and that was enough ;
2. use VLITE in "original state" - vista vimfltr and wimgapi.dll copied in the wellknown folders.
No need switching between wimfltr an winmount ! No need WAIK (I never hadn't hve that kit in my computer just wimgapi.dll for GIMAGEX).
Vlite and GIMAGEX don't use common files, because they running in separated environments. Believe me, wimfltr.sys of Vista was ONLY vimfltr used in entire operation, and ONLY for vlite. Who needs winmount.sys ?!
That's all, 2 simple steps, and I installed without any error 3 various images from Windows 7 SP1 AIO kit.
And to be shure, I worked with fresh instaled OS every time.. "
Read more in that topic for more information. I had same error as you and this solution is working perfectly.