Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by yogurt

  1. :doh: thanks for the highlighting. I've taken a look at both tools. Neither of them do anything that I cant already do in my modded windows shell. Beyond Compare is a tool I use often when comparing a large number of files and folders. Woks good for me.

    Auslogics Duplicate File Finder was interesting. Digital Volcano Duplicate Cleaner, looks promising on the surface, but in reality the program is limited to one feature only, so to get anything useful you got to $$$$. With only one feature enabled you may as well call it trial ware. $29.95 is not bad, but I think $12.95 would be more of a reasonable price for what the tool can do. Anyhow in the end I decided to add it to my arsenal of tools. Best Regards.

  2. ...the solution might be to implement the "duplicates" as shortcuts or hard links so that there is really only one copy of each file, even if there are more than one place to access it.

    You suggestion to use symbolic links sounds interesting, I suppose the links could act as placeholders to the parent .inf file for that specific branch of the hardware device.

    There are also some duplicate finder type apps, Auslogics Duplicate File Finder and Digital Volcano Duplicate Cleaner are two free ones that come to mind, that might be able to do a quick search for true duplicate drivers, that is if they are really identical.

    The tools you also suggested look interesting. I wonder if they are free :D Thanks for sharing.

  3. @bphlpt, thanks for sharing your insight.

    After taking a closer look under the hood what your saying makes perfect sense, However, why not just have one let say 'WinALL' or 'Win7xVista' exclusively instead of having 2 folders holding the exact same set of files? Some Driver Pack categories follow this convention quite nicely while others don't. It not a big deal for someone who understands the mechanics of device drivers, but it can be quite daunting to someone who is just starting out.

    Nonetheless, The folders are so will documented it's quite easy to deduct the dupes when used in conjunction with Win Tool Kit's sorting options :D I started of with over 300 inf files and was able to eliminate over 200 redundant dupes without adverse effects in a matter of 10 minutes :o

    To illustrate here is a list of 20 drivers for System X (Before Consolidation) As you can see their are 5 duplicates across 21 folders.


    Here is the same list of drivers for System X with 0 Duplicates in using only 8 folders (After Consolidation).

    Much easier to manage and less scrolling :D


  4. Do you need to keep them and integrate them?

    That's more or less I was wondering when I posted...

    Here is what I've been able to figure out thus far. Take for example a memory card reader like The Broadcom Card Reader Model X

    The Card Reader resides on two branches of the Device Manager -- SD host adapters (Broadcom SD Host Controller) + Storage Controllers Branch (Broadcom Memory Stick) Both devices share the same ,<driver.inf>.

    Upon introducing the device to windows for example, during installation, Windows will search for the device.inf across the entire driver db for a suitable drier.inf and will stop on the first .inf file it finds that matches the HWD and install. The same process applies to pretty much all devices connected to a windows machine.

    In essence, the <device>.inf in directory 'A' which is identical to the <device>.inf in Directory B will get processed for the Broadcom Card Reader. So wherever it resides in the driver pack doesn't matter, The important thing is the HWID.

    Driver Packs such as the ones found at Driver Packs.net have 100's of duplicates within their folder structure. The same .inf file that resides in the vista folder may also have dupe in the win7 folder. for the same hardware. The files in each folder are identical for that specific piece of hardware.

    I'll be testing some theories tomorrow and post my results here. Hope this makes sense.

  5. I noticed that duplicate driver files are highlighted in blue in AiO Integrator.

    Is their any reason why I need to hang on to these duplicates?

    EDIT : Disregard, I found the answer browsing thru the various DriverPack folders. It seems the duplicates belong to devices that are on the same device branch for that hardware / class

  6. "aren't selected in the preset"

    Which preset are you on about?

    1. Start update catalog

    2. Select KUC Windows 7 x64

    3. All 'New Updates' (Recommended) by default :D are selected for download, nothing selected under 'Additional' (Optional)

    3. Complete the Download Process

    4. Browse to <download> folder and you will see that To folders for AD LDS and RSAT with updates inside that were not initially selected from step 3

  7. Problem B: ''server or AD LDS'' and ''server or RSAT'' are in the Additionals (Optional) category. They shouldn't be downloaded, since they aren't selected in the preset, and also don't have nothing to do with the main (New Updates) Recommended'' category.

    Lego, I can confirm this behavior here too. Test V28 on Windows 7 x64.

  8. As the title suggest : Is it possible to remove an addon once it has been integrated using Win Toolkit All-in-One Integrator?

    I'm thinking not, but I thought I'd ask just the same, and for the benefit of anyone else who might be want to know.

    It's not really a big issue for me, It just means I'll have to be more diligent with my builds. Any insight is much appreciated.

  9. After several hours of reading, I think I finally finally understand the mechanics of updates and hotfixes. For anyone reading this thread, here are links to some very well written articles that may help you in understanding the complex mechanics of windows updates. Although the text is somewhat advanced, I recommend anyone who integrates updates to their offline image to give it a once over.I had to read them 3 times before It finally made sense to me.

    GDR, QFE, LDR...WTH?

    Later related blog entries (as the topic grew in its scope and version numbering/branch identification changed after Windows Server 2003)

    Branching Out (2009-05-18)

    - gives a generic overview of the branching mechanism, with examples

    Service Packs – Levels vs Installers (2009-05-29)

    - distinguishes between “service pack level” and “service pack installer” for disambiguation

    GDR & LDR : The Next Generation (2010-07-14)

    - describes how to verify the version/branch of a given binary on XP/2003, Vista/W2K8 and Win7/W2K8R2

  10. @RicaNeaga

    Thanks for a clear a concise reply. It's quickly all becoming clear as day. In terms of updates, frankly, I'd rather stay on the very safe side, aka GDR. Just to be sure I understand let me run this by you one time to be sure I understand before I integrate a bunch updates.

    As I understand, With the LDR option disabled, any updates I integrate that have an LDR fix in the package will install the GDR component and drop a placeholder for future reference. The LDR placeholder is there to notify Windows Update Agent in the event that a new update comes out fhat contains a GDR fix to the LDR placeholder. Is that about right, or did I miss something?

    I read a post yesterday where you are warning members not to integrate KB2685811 and KB2685813. Does your warning still apply with the current stable release of Win Toolkit?

    Do you know how Win ToolKit handles updates like rvkroots.exe and KBXXXXX.reg? Can these types of files be integrated via Win Toolkit Updates tab or Installer tab?

  11. just three questions regarding the LDR Mode option in the AiO Integrator.

    I have read thru this entire post, I understand the lingo for the most part, it's Just a little to advanced for me at this stage.

    What i would like to know Is, if their is some sort of benefit to enabling the LDR-QFE option in AiO integrator.

    I've read somewhere that LegoLash2o uses this option all the time. But I just don't understand why or it's purpose.

    If I understand correctly the updates in the GDR branch are the most important ones, while the updates in the LDR branch are not so important and only apply to a small fraction of windows users.

    1. Why would I want a bunch of updates that may not even apply to my configuration?

    2. In what circumstances would I want to enable the LDR option in WinToolkit?

    3. What are LDR placeholders?
  12. I'm not entirely clear on the conclusion of this topic. Are KB2685811 and KB2685813 still an issue? Or can they be safely integrated without any adverse effects?

    Well, both things I'm going to say now are related to users that download your app but don't read all the threads here, so having warnings / hotfix tweaks in your app that are automatically selected when some hotfixes are added in AIO would help them alot. Hope you'll see I'm not asking this for me.

    for anyone who reads this post, I have two warnings:

    1. KB2685811 and KB2685813 may generate issues even if installed in LDR mode. I'm strongly recommending NOT to install them, as they're not important updates

  13. Scenario,

    I would like to integrate and install McRip System Files using the AiO integrator. However the installer requires admin rights for a successful install.

    So i'm wondering if the 7z SFX module can help me in getting the job done. or perhaps simply turning off UAC in via answer file. Like so...

    <settings pass="offlineServicing">
    <component name="Microsoft-Windows-LUA-Settings" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[url="http://schemas.microsoft.com/WMIConfig/2002/State"]http://schemas.micro...fig/2002/State"[/url] xmlns:xsi="[url="http://www.w3.org/2001/XMLSchema-instance%22>"]http://www.w3.org/20...hema-instance">[/url]

    I'm wondering if something like, adding xml to the manifest of the SFX module using reshack might help, but I'm note sure If it's safe, or even how to code it so it works with the installer.

    This is an example snip of the manifest found in rvkroots.exe

    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
    <requestedExecutionLevel level="requireAdministrator" uiAccess="false"></requestedExecutionLevel>

    The installer supports the switches /VERYSILENT /NORESTART, I've taken a look at this post which provides some insight, but I would prefer to either use the Answer File method or 7z Modified Module as oppose to using WinRAR SFX as suggested in to mentioned post.

    Any insight would be much appreciated. Best Regards.

  14. If the price is right, you sure can!! :dancing:

    Nice bridge, too rich for my check book. Sorry No :sad01_anim: SALE! All I got for trade is this Re-invented windows Disc. :P

    Hows the Windows 8 Learning curve coming along? I'll be having a look at Win 8 on release day. I figure for $14.95, why not.
  15. @McRip

    I have other things to do as well.

    Fixed. It seems that you have a static IP. That' good.

    Thanks for the addition to the server white-list. But it seems I still cant connect with WTK No problem connecting with the beta. I've turned off my local firewall, still no success. I don't think it's anything in my router, because I can still connect with the WTK Beta. I've also tried flushing the DNS resolver cache, still no success.

    My ISP doesn't use a proxy server, At least none that I can see.

    I was under the impression that my Routers WAN IP was dynamic, if it's static as you suggest, all the better. Any ideas? Perhaps trying on another PC, but i don't think so.

  • Create New...