Jump to content

yogurt

Members
  • Posts

    348
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by yogurt

  1. Update April 13, 2014
     
    I will no no longer be updating my add ons which are found throughout this forum. all files will eventually be deleted. Moving forward, I need my online storage for other projects. It was a pleasure to work with Win Toolkit. It is certainly a workhorse that i want in my Deployment Kit. Thanks everyone. I will continue to visit for as long as this project remains active. I really like the community here. PEACE OUT!
     
    K-Lite Codec Pack x86/x64 v9.7.5 (All Variants)
     
    The four variants of the codec pack mentioned below include both 32-bit and 64-bit installers. If you have a x64 version of Windows, then both 32-bit and 64-bit versions of the codec pack will be installed. They work together in complete harmony. It is important to also have 32-bit codecs on a 64-bit system because many applications are still 32-bit, including Windows Media Player! 
    There are several different variants of the K-Lite Codec Pack. Ranging from a very small bundle that contains only the most essential decoders to a large and more comprehensive bundle. The global differences between the 5 variants can be found below.
     
    Note: This installer should work for ALL languages & architectures. Add these as silent installers... No switches needed.
      
    Download:

    The basic variant contains everything you need to play all the common video file formats. Such as AVI, MKV, MP4, OGM, and FLV. This pack is for those who like a small no-nonsense pack. It is small, but powerful.


    Basic x86/x64:Link Removed

    MD5: 48b749d2858c3344b7130336f5cb097c Size: 20.8 MB
     
    The standard variant contains a few additional features compared to the basic variant. It contains Media Player Classic, which is an excellent player for video files. It also has (better) support for playback of DVDs. This pack is recommended for the average user.


    Standard x86/x64:Link Removed

    MD5: e81ab3bed9b90fb84d9d7a0c4d3c2211 Size: 25.4 MB
     
    The full variant has some extras compared to the standard variant. It additionally contains madVR, GraphStudioNext, and a few more audio decoders. This package is suitable for power users.


    Full x86/x64:Link Removed

    MD5: fc3fcdb4240d851fafaab00a08bb8e2f Size: 30.4 MB
     
    The mega variant is the most complete pack. It additionally contains VFW/ACM codecs for video encoding/editing. It also contains a few extra tools and DirectShow filters.


    Full x86/x64:Link Removed

    MD5: 7a185260b3d0e4d60ffc0d706a6fbe36 Size: 34.1 MB

  2. Updated...

     

    Integrated: The latest virus definition version is: 1.145.381.0 | Released: Feb 23, 2013 09:51 PM UTC

    Integrated: Network Inspection System (NIS) version is: 17.36 / 18.36

     

     

    Updated...now you can force the installation language

    <installer>.exe xx-XX and/or <installer>.exe /ai xx-XX
    Thanks to McRip for the SetIni suggestion, it was tough figuring out how to do this but turns out the solution was very simple
  3. @ricktendo

     

    Thanks for your insight on NIS, I will add it to the package today. As for the all languages in one (intl) I left them out because I felt adding it to my package would overlap with your repack. However, now that you mention it, if you don't mind, I'll do it. Thanks for your permission to adopt some of your config.txt

     

    The only thing would be to remove the Market="EN-US" from setup.ini right? That would auto install the lang. native to that specific machine right?

     

    Since you are making a package with the definitions as well you should think about adding NIS

    http://www.wincert.net/forum/topic/11016-repak-microsoft-security-essentials-x86x64-v42223-intl/?p=95953

    Feel free to use any config.txt code from my repack (you should at least grab all the languages and edit setup.ini to remove Market so you have a true AIO)

  4. how can i get sure to just install gdr?
    MCRip offers both, where is a source for all gdr since today?

     

    To ensure the GDR branch of an update gets installed via Win Toolkit check

     

    All-in-one Integrator > Options > Updates > LDR/QFE mode (Unchecked).

     

    Doing this will ensure that only the GDR branch of the update gets installed.

  5. Thanks, Rick, I couldn't find any documentation on %S parameter for the 7zSD custom module, so i took a shot in the dark. I will post an update in the next day or so. Your insight would be much appreciated. Best Regards.

     

    Yes, I mean outside next to your installer.
     

    <your_installer>.exempam-fe.exempam-fex64.exe 


    If you look in the config.txt you will find %%S, this will translate to the path/folder your sfx is run from.

  6. What, no credit?

     

    Sorry, Updated with a note with credit info.

     

    And you are doing it wrong, the updates (mpam-fe*.exe) installers you zipped will not get executed (even if you use /ai.) Leave mpam-fe*.exe outside the archive

     

    When you say leave mpam-fe*.exe outside the archive, do you mean outside the SFX or outside the x86 / x64 directory in the 7zip file. Can you elaborate please.

     

    BTW I was working on (but stopped) a true AIO MsSecEs istaller, one with ALL languages...You have to download ALL the installers to get the xx-XX sub folders with setup.dll.mui+EULA.RTF and edit setup.ini to remove Market=EN-US

    This should now install correctly on any language Windows...

     

    I'm also planning to continue your work with an all languages add-on / installer, that it if its okay with you. I presumed you had discontinued work on Security Essentials base on a post I saw in Installer Repack Requests

  7. Update April 13, 2014
     
    I will no no longer be updating my add ons which are found throughout this forum. all files will eventually be deleted. Moving forward, I need my online storage for other projects. It was a pleasure to work with Win Toolkit. It is certainly a workhorse that i want in my Deployment Kit. Thanks everyone. I will continue to visit for as long as this project remains active. I really like the community here. PEACE OUT!

     

     

    post-40893-0-55977200-1361075164.jpg
     
    Microsoft Security Essentials x86/x64 v4.2.223 (Int'l)
    Integrated: The latest virus definition version is: 1.145.381.0  |  Released: March 5, 2013 03:49 PM UTC
    Integrated: Network Inspection System (NIS) version is: 17.36 / 18.36

    About: This installer should work for ALL languages & architectures. Run this installer with /? or /h for detailed language mode (MUI) instructions. The default system language is used if not specified. Add these as silent installers. All switches are optional.

    Download:

    Link Removed
    File: mseinstall_x86_x64_Intl_March_5_2013.exe (159.5 MB)
    MD5: 9c5c27ca6c192b8bd09ecc5539295b1a
     

    Config:

    ;!@Install@!UTF-8!GUIMode="2"GUIFlags="8"RunProgram="hidcon:setini.exe \"%%T\\%%P\\setup.ini\" Compat Market RunProgram="%%P\\setup.exe /s /runwgacheck /o"RunProgram="x86:mpam-fe.exe /q"RunProgram="x64:mpam-fe%%P.exe /q"RunProgram="x86:nis_full.exe /q"RunProgram="x64:nis_full%%P.exe /q";Thanks goes out to 'ricktendo' for his insight and guidance in helping me create this installer.;!@InstallEnd@!

    Supported Languages:

    bg-BG cs-CZ da-DKde-DEel-GRen-USes-ESet-EEfi-FIfr-FRhr-HRhu-HUit-ITja-JPko-KRlt-LTlv-LVnb-NOnl-NLpl-PLpt-BRpt-PTro-ROru-RUsk-SKsv-SEth-THtr-TRuk-UAvi-VNzh-CNzh-TW
  8. if wintoolkit scan on every drive with a letter and additionally on x:\sources\apps

     

    The Correct path is %dvd%\apps

     

    how can i define in wintoolkit to not integrate all the installers to the iso root?

     

    At this time all apps integrated via Win Toolkit will integrate to iso root. Optionally you can move the apps folder to another medium like a USB Flash Drive.

     

    The reason to not integrate Apps into the iso is space so how to do it?

     

    you can move the apps folder to another medium like a USB Flash Drive.

  9. I'm going to try Mr_Smartepants suggestion and test on my next. build. All this new information on driver integration has brought me to rethinking my process for cleaning up DriverPacks. Thanks everyone for sharing your insight.

     

    For deleting duplicate files, you'd be better served scanning/deleting duplicate .inf files only. Then scanning the folders for any folder that doesn't contain a .inf and deleting that "empty" folder.

×
×
  • Create New...