Jump to content

alvinkhorfire

Member
  • Posts

    104
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Malaysia

Posts posted by alvinkhorfire

  1. Just integrate IE9 over Win7 SP1 or Win7 SP0, but without updates added first!

    Integrate first IE9 and after the updates.

    What do you mean by updates? Do you mean just IE-based updates like security fixes for IE and language files for IE? Or, by updates, do you mean all Post-SP1 Windows updates (msu files), including hotfixes for other Windows components?

    I always integrate Windows Updates according to their release dates. As for now, IE 9 is integrated lastly to a Windows 7 SP1 image as it is the newest update at present.

  2. There are 2 ways to incorporate Windows updates (msu files) and drivers to a Windows 7 image:

    1. Integration via RT 7 Lite or vLite (some modification is required.)

    2. Audit mode

    The scope of my question is just limited to just Windows updates and drivers. It is because to integrate software via RT 7 Lite, I believe that silent installers are required. On the other hands, any installer can be used in Audit Mode, which should be a much better method to incorporate other software, like Microsoft Office.

    My question is: Which of the two methods produces the more optimal, cleaner and efficient Windows 7 image? In other words, the install.wim should be smaller. My guess is the integration via RT 7 Lite, but I could be wrong and that is why I require some advice here.

    In audit mode, the Windows installation files have been fully expanded. Then, I have to restart the computer and boot the system into a WinPE disk, in order to compress all Windows files back into install.wim. I guess that the install.wim created in such way will be slightly bigger and will not be optimal.

    Thank you for the information given.

  3. why don't you download the full exe from the Downloadcenter and run /X:C:\IE9 to extract the IE9.

    I understand that. However, the end result is a cab file. The current version of RT 7 Lite cannot integrate cab file. That is why I prefer the MSU version over both full exe and cab version.

    Anyway, thanks for your suggestion, MagicAndre1981. :)

  4. I can give you my opinion for now, but I hope that other experts like maxXPsoft, ricktendo64, MagicAndre1981 and Kelsenellenelvian can provide a response which is more accurate than mine.

    Well, the MSU version and CAB version are the same. Integrating either of them to Windows 7 SP1 image via DISM should yield the same result. However, the current version of RT 7 Lite cannot integrate cab file. That is why I prefer the MSU version. If you integrate Internet Explorer 9 via DISM, it makes no difference in using either of them.

    Correct me if I am wrong.

  5. The direct links for MSU version of Internet Explorer 9 RTM has been provided by ricktendo64 in his post. Thanks. :thumbup

    Thus, with the msu version, it is easier for me to directly integrate it via RT 7 Lite or DISM, to a Windows 7 SP1 image. Compared to integration of Internet Explorer 8 to Windows Vista SP2, integrating Internet Explorer 9 is much easier. Quoted below are steps to integrate Internet Explorer 8. Yes, it is redundant and useless to know now, but it shows a clear comparison between integrating these 2 versions of Internet Explorer.

    Integrate Internet Explorer 8 into Windows Vista SP2 using vLite:

    Extract IE8-WindowsVista-x86-ENU.exe with WinRAR to end up with a .msu file.

    Rename the extracted .msu file to .cab and open it with WinRAR.

    Inside the that cab file, is another cab file. The cab file, in the cab file is the one you need to use for integration.

    So in short:

    Exe -> Msu -> Cab -> Cab

    The last one, Windows6.0-KB944036-x86.cab is for integration use.

    (Or, go to C:\Windows\SoftwareDistribution\Download to copy the .cab file. ie8.msu cannot be integrated using vLite.)

  6. I am using 64 Bit Windows 7. I would like to know the direct link to download the MSU Version Of Internet Explorer 9 (Windows6.1-KB982861-x64.msu).

    I realize that there are links to download the exe version (IE9-Windows7-x64-enu.exe). Well, with the msu version, it is easier for me to directly integrate it via RT 7 Lite or DISM, to a Windows 7 SP1 image.

    Thank you very much for your help.

  7. bapt

    What is that famous KB you mentioned? Is it KB947821?

    aviv00

    You mentioned in your first post that use RT 7 Lite first and then use VLite to remove winsxs [use rebulid all image with RT 7 Lite to save time 30 mins and u NEED to recapture the image!].

    1. By the word of recapture, do you mean by just capturing via GImageX? Or, do I still have to apply (not mount) the image and capture the image?

    2. Since you rebulid all image with RT 7 Lite, the slimmed down Windows image still contains all editions of Windows 7 SP1, right? Thus, in order to remove other undesired edition of Windows (like Home Premium and so on), vLite must be used. Is this statement correct?

  8. i just did another test & no errors after vlite

    u could try this way:

    1) ensure waik 2.0 is installed

    2) in cmd prompt, go to Program Files\Windows AIK\Tools\amd64 and execute wimmountinstall /install

    3) copy wimmount.sys from above folder to Program Files (x86)\vLite\wimfltr\x64

    4) rename wimfltr.sys (this is the vista version) to something else such as wimfltr2.sys as you will need it later

    5) rename the copied wimmount.sys to wimfltr.sys

    6) right click wimfltr.inf Program Files (x86)\vLite\wimfltr\x64 folder to install

    7) using gimagex or imagex, mount install.wim and then dismount wim with commit changes. this should take a while around 20 minutes depending on pc. u should only need to do this once to a wim unless u start from afresh

    8) go back to the vlite wimfltr folder and rename wimfltr2.sys to wimfltr.sys (also rename wimfltr.sys back to wimmount.sys)

    9) right click wimfltr.inf and install again. this will copy the vista version back to system32\drivers

    10) use vlite

    u may need to switch between the 2 filters when using imagex and vlite

    For Step 7, GImageX is used with Seven ImageX. For Step 10, vLite is used with Vista wimfltr. Okay, I get that.

    Questions:

    For Step 8, do I have to install WAIK 1.1 (Vista) or just have to rename wimfltr2.sys? Other than that, if I want to install WAIK 1.1 (Vista), do I have to uninstall WAIK 2 (Windows 7) first? In other words, can I keep both WAIKs installed without one affecting another?

  9. I am using Windows 7 SP1 64 BIt. I want to know how I can integrate KB943790 (64 Bit) to Windows 7 SP1 image, either by DISM or RT 7 Lite.

    Compared to other Windows hotfixes, this hotfix does not have xml file inside the msu file. Thus, if you select to integrate it using RT 7 Lite, this hotfix will highlighted as red, meaning that it cannot be integrated directly.

    If I choose to integrate via DISM, the command prompt will state the hotfix cannot be integrated.

    My question is that how should I do in order to integrate it to Windows 7 SP1 image?

    Thanks for the advice given.

  10. WAIK 2 is for 7 I thought. 1.1 is for vista. 1.1 was released in 2008, 2 was released in 2009 and 3 this month. WAIK 2 should have the wimmount.sys, that is what I have.

    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.

  11. Yes, I am facing the same problem with the "samlib.dll in system32 folder" error when I tried to vlite Windows 7 SP1 (MSDN).

    For another case, I tried to mount Windows 7 SP1 (not vLited) via GimageX (from WAIK for Windows Vista) and ran a batch file to remove some redundant fonts. When I tried to install this slightly slimmed down Windows 7, I too encountered the same samlib.dll error. Man, it is frustrating.

    Well, I should used WAIK for Windows 7, but the reason for using WAIK for Windows Vista is that I want to use vLite to slim down Windows. At first, I thought that the samlib.dll error is due to my rather aggressive preset. Thanks to your guys, I have known that the culprit is SP1.

    I usually perform the following steps (from left to right) to slim down Windows 7 (SP0) with no error, as recommended by aviv00. Tha batch file is from dead0. Thanks to them.

    RT 7 Lite > Batch file to remove fonts > vLite

    RT 7 Lite still could not completely remove some components which can be removed by vLite, so I need to use them both. Now that I started to use Windows 7 SP1, such method is no longer possible. Sigh!

    RT 7 Lite is slow mainly because it needs to mount the Windows image in Temp folder. However, vLite does not do that and is much faster. Still, I am very much hopeful that RT 7 Lite can be further improved, so that it can remove the components previous removed by vLite.

  12. Thanks for the links. It has been a great help. I presume that the links are from Microsoft Update Catalog, right? Next time, when I encounter such hotfix in the form of cab file, I will proceed to Microsoft Update Catalog.

    Slightly off topic a bit. I want to ask question regarding the KB976902 msu file via RT 7 Lite. This program will certainly force you to slipstream Service Pack 1 into the Windows 7 RTM image, before you can integrate other hotfixes. Then again, this KB976902 hotfix is intended to be integrated before the service pack is being slipstreamed.

    So, how should I solve this problem? Should I still use RT 7 Lite to slipstream Service Pack 1 first, and then subsequently integrate this hotfix?

  13. I am using 64-bit Windows 7. What is the proper way to install windows6.1-kb976902-x64.cab, which is manually downloaded from Microsoft Download Center? In other words, I am not using Windows Update to install the update.

    Even after I tried to extract the content of the cab file and click the individual exe files, it did not work.

    Thank you for the advice given.

  14. concou

    Correct me if I am wrong. I think that it is possible to remove some redundant fonts from Windows, without affecting the proper functionality of Windows. Well, nLite has an option to remove some fonts. I know that I should not compare between nLite and 7Lite as they are completely different software. Still, it would be good to see the future version of 7Lite that can remove fonts.

    Most probably, other users may have different needs. For me, I do not think that I would need anything more than Segoe UI, Tahoma, Times New Roman and Arial. Other fonts seem redundant to me, and may contribute to performance slowdown of my system. Then again, it is just my opinion, though.

×
×
  • Create New...