RicaNeaga

Now it's working (online driver installer), however it installs all the drivers selected, and not ONLY those needed for the system. Also, two glitches - a windows like this appears after each installed driver, so I have to check ok 65 times for 65 drivers, and also the red warning window ''are you sure you want to install this unsigned driver bla bla'' appeared one time.

A simple feedback for the current pnputil online driver installer in 1.4.0.8 - it doesn't work. It doesn't even install one driver or an entire folder... not to mention selecting only the needed drivers (present on the system).

In my case there's another weird behaviour, or maybe others didn't noticed it. There's something wrong with the new RunOnce (Windows 7 Toolkit Installer 4.2.1). Just before first logon, during installing switchless installers, it gets in a loop. As usual, I went away from the computer, expecting to find the desktop at my return. Insted, I got 10 (!) different windows of W7T, all stuck at the 7th installer out of 19 (Kel's Runtimes 1.4). So the first 6 switchless installers were installed 10 times on my pc. It may be a conflict with Kel's installer, but since also other people is having a similar problem... myabe it's duplicable if other people won't interfere with the process. But please also check Kel's installer.

Also another duplicate (or having the same goal) - the 500 ms delay aero peek desktop category tweak and the speed-up desktop explorer category tweak. And also please provide a more detailed explanation to the system category Enable MAC File Sharing, what exactly does it stop / enable / add. Always was curious about this one...

I have some further observations / small glitches regarding tweaks: 1. At start-up&shut-down category - shutdown quicker and kill services quicker at shutdown - aren't they doing same thing? Maybe the kill serives quicker should be deleted... 2. At the Explorer - the Disable Tool tips tweak - what is this supposed to do? it's not working, if it reffers to the taskbar notifications... Also, please take a look at this post... regarding tweaks, maybe you'll have the time to implement some of those, or other in that thread

Used version 4 of 1.4.0 and the IE9 msu red bar is gone, I decided to move those other msu's to the switchless installer folder, so they'll be run at first logon. However, the cabs SoLoR specifically made for DISM are beeing integrated by DISM, but W7T is adding a red bar to them, instead of a green one. You can find them here. Please fix this for next update.

Windows update cabs were also in red... and they shouldn't. In the end, maybe this red/green bars visual-only feature isn't very useful, considering those red bars can scare people away, and it has nothing with W7T, since DISM alone may be to blame. However, I do have one curiosity. My habit before W7T forced me to do otherwise was to always integrate IE9 msu the last... I used to rename it, by putting a ''z'' letter in front. Can you please send me Legolash a beta build without that always-install-first-IE9-msu feature? I'm curious to see if the red bar applies again to IE9...

For me until now red is the IE9 x64 msu, KB917607, KB943790 and KB971033.

I don't want to start a new thread so I'm posting here... Right now I'm in the process of integrating updates to an offline image via AIO. What does the red bar mean / stand for? Since I'm pretty sure that grean means ok... Hope it doesn't mean those updates weren't integrated...

That script is driverpacks-folder tyed. It's like saing ''Hey, Apple has an alternative to Flash''. It's just my take on this, my opinion. And I really don't like the current way driverpacks for windows 7 looks like. That's why I ''wasted'' so much time updating it / making it windows 7 - only / adding drivers to it...

Great! I have four suggestions: 1. The name of that folder maybe shouldn't be so common - a Drivers folder is also in windows directory; a ''W7TDrivers'' folder name (that a user can copy to the usb root, or make another ISO and include it) I think will be more appropriate; 2. An option in the ISO Maker that isn't checked by default, to also add/copy the ''W7TDrivers'' folder to the root of the iso; 3. Make the the implicit and only option that pnptuil only installs the needed (found on the system) drivers; if advanced users, that aren't interested in saving HDD/SSD space and for other reasones, want to have an AIO disk, with all the drivers on the planet integrated, then DISM can already do that for them. 4. An option to also delete all the not-present-on-the-machine / not-needed-drivers Microsoft drivers (if it is doable), to further save HDD/SSD space; but I don't know if this will have the potential for potential failures (bluescreens etc) afterwards... in case other hardware is added to the system. For non-important drivers (chipset, mass storage, usb), such a risk I think will be very close to 0. LE: and a fifth suggestion - please recheck Mr. ricktendo's post from this thread.... maybe will help

lol don't get mad. and thanks! I ain't in a hurry.

I understand that. I was asking you to make (smth like) a silent installer, that runs this online drivers app automatically (for ex.) at first logon (as the rest of the silent installers, like ricktendo's .net4), and installs only the needed drivers from a batch folder of hundreds of drivers. I already mentioned the advantages in the first post, as an alternative to the DISM way of installing drivers. Please don't be mad because I insist on this feature - I really consider it CLEARLY SUPERIOR to DISM integrating of drivers especially for novice users. Hope you'll consider solving my request at some time in the future

If the only solution is to run it at first logon, with the other switchless installers, then it's ok. I would have preffered it to give that drivers to the windows installation process during the second phase, but better this then nothing.

I won't interfere anymore with this discussion, since I don't know how to implement my request, but once again I remind you that there is a similar working solution for XP only, that does exactly this (the app runs before the second phase of windows xp install process) - Driverpacks BASE.

I had no problems whatsoever integrating those exact silent installers from different usb sticks... usb 3.0 / ssd-based etc... with different versions of W7T. I for one don't think it's a usb-stick-related-problem.

That's what I was talking about... ways to make this happen Thank you ricktendo for the solution!

Legolash, I don't understand what you're saying. I'm not requesting what ricktendo already has requested, I'm requesting that somehow through W7T, the Online driver installer to be integrated into an offline image (alongside maybe a user-generated driver pack / folder), and run before the second phase of windows installation starts. About the second question, it depends - sometimes there is a mention in the .inf (like a NTamd64 6.1 for windows x64 drivers, or a NTx86 6.1 for 7 x86, or even a clear mention in the beginning - windows 7 driver), sometimes it isn't and you have to manually download the individual drivers from the producer's support site (like I already did for many). But this isn't the issue since I'll make public this pack very soon (I'm now trying to set up a ftp-like solution, and if I can't, I'm going for the usual mediafire option). The problem is how this tool can be run before the second phase of windows installation starts. And this is where I hope ricktendo / Kelsenellenelvian will help a little. Or maybe even someone from driverpacks, since a similar solution is implemented in their driver installer tool for windows xp (DriverPacks BASE).

I'm talking about the new online drivers installer found in 1.4.0, with the features described by ricktendo here. Why would anyone need it? What are the advantages over integrating the drivers with DISM? 1. This would make an AIO driver + windows 7 ISO truly possible, making the probability of conflicts even lower (the example of the AMD PCIE filter chipset driver installing on Intel-based systems comes to mind); 2. On the system only the needed drivers are installed and copied to drive C:, so a balast content with other drivers will be avoided; 3. Useful for a novice user, that doesn't have to hand-pick the needed drivers, but can ''integrate'' hundreds of them without any other worry. After months of work (not continuous work, of course), I'm finalizing a pack of ONLY-windows-7 drivers, based on the driverpacks - heavily updated and more organised. And with such a powerful tool, the usefulness of such a pack will be even greater - people will not have to hand-pick their drivers and just integrate all the folder. Such a behaviour is unfortunately also common now with W7T users for integrating the current driverpacks, and this is not a very good idea. So I don't know if this is doable, and to be more precise if this utility can be run before the second phase of windows installation starts. It has to because that's when the windows installation process starts to look for the (microsoft integrated) drivers needed. And this is just exaclty what the great driverpacks integrating tool can do ONLY for windows xp. I also hope ricktendo and Kelsenellenelvian will comment on this one.

This is going to be in 1.4.0. I just wanted to say before this thread is closed that I love the way it's implemented.

The last screen from the post above is just WOW. The same concept applied to the tweaks section will probably help ALOT. It's the same interface as in nlite / vlite. However, in tweaks section some categories have MANY tweaks, like Internet Explorer. Maybe something like Internet Explorer Basic, Internet Explorer Advanced etc will be better, aka dividing those heavy categoies into mini-categories.

1.4.0 FTW! NO to final version, YES to solving requests and YES to adding tweaks!

Including KB2675468?

So only the IE9.exe doesn't get integrated through W7T, or also the IE9.msu (latest KB982861)? :cold: :g:

*** Update request filled ***