RicaNeaga

For anyone interested - I'm also using DISM GUI 3.1 - performs basic stuff like mounting and unmounting with saving the changes. I use it to add to the boot.wim the unattended file and fix this issue. Unfortunately this isn't a default option in W7T. And there are also other basic tools for DISM out there. But none equals W7T

One more bump for this - hope it gets into 1.3.0. Reason - I use another software to do this integration of the unattended file, and it's not so nice&coasy. I think the implementation of this request is not so complicated, so...

Make sure you go into BIOS and check the load optimised defaults, then save (F10) and restart.

Merry Christmas! :dancing:

@Mr_Smartepants I do have a BIG problem, but not with a specific driverpack issue, but with how driverpack is conceived for vista & 7 & server - all in the same pack. It's VERY wrong. I'm going to show you why here, at wincert, by making a guide for W7T users (after making a general guide in another language somewhere else, and afterwards translating them into english), because I consider W7T to be the BEST tool for integrating drivers (also I'll explain myself in the future). Why I'm not going to do this at driverpacks? Because you're very violent in language there, and if someone disagrees with you, the purpose of the conversation won't be if that person is correct or not, but to bring as many arguments (both true and false) just to show them they are wrong - anyone who disagrees with you is wrong from the start. I'm not the arguing type, so I won't post any more replyes here, but I cannot ignore some false arguments you wrote here (aka the technique of arguing for the sake of arguing &link uttering): you know better than I that this is NOT true, so I won't bother demonstrating this. For now. You know better that there are some mixed drivers, for example Intel chipset ones. And Intel made a DIFFERENT FOLDER FOR WINDOWS 7 for a purpose, because ONLY those drivers are meant for windows 7. And... again WRONG. I can integrate anytime into 7 via DISM those kind of mixed chipset Intel chipset drivers (ONE example), that were meant only for previous OSes than windows 7, But hey, you know better, wright? I'm curious how you'll try next to find arguments just to show me I'm wrong, not because I intend to reply (I won't), just for fun. Also, don't get me wrong, I really love what you've done for XP - best solution out there.

STOP using Driverpacks!!! They are VERY good for XP, but for windows 7 - and for use with W7T - are DISASTROUS!!! The reason is simple: they include also Vista versions of those drivers besides 7 ones, in some cases even XP drivers (Intel LAN foe example - maybe they deleted them lately, I dunno), sometimes x86 drivers in the x64 pack and viceversa. I LOVE the way W7T integrates drivers by default (with support also for foreign characters - method 3 / slower), so 99,99% not W7T is to blame. Please unpack ONLY your needed video driver (with winrar/7zip/etc if it's Nvidia/ATI), and integrate only the Drivers folder inside (that contain .inf files). I'll make a guide for integrating drivers and also upload my pack somewhere (only for 7, updated and selected - much better to use with W7T than driverpacks's ones) probably in ~two-three weeks from now, and also a guide for W7T (I can't promise I'll respect my deadline, since I have to translate that guide also in english). 'Till then please read the previous sentence once again.

After having some issues, I decided to investigate further, and came out with the following list of working tweaks (tested on a live system, and not through W7T for now), which aren't included in W7T: Working useful tweaks for an overclock-er / bench-er: 7. Set Paging File To c:\pagefile.sys = 512 Mb (with the following description: only use this for a system that has at least 4 GB of RAM, 6 or more preferred) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management] "PagingFiles"=hex(7):63,00,3a,00,5c,00,70,00,61,00,67,00,65,00,66,00,69,00,6c,\ 00,65,00,2e,00,73,00,79,00,73,00,20,00,35,00,31,00,32,00,20,00,35,00,31,00,\ 32,00,00,00,00,00 8. More started threads / tasks by default - this isn't recommended if you're into power saving / global warming / saving the planet. It contradicts the concept of IDLE, as it always keeps a number of tasks (workers) active and ready. More about it here. You can change the last two digits of the dword with any number from 01 to 16. I decided to use 08 - 8 threads always active - the middle number. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Executive] "AdditionalCriticalWorkerThreads"=dword:00000008 "AdditionalDelayedWorkerThreads"=dword:00000008 NOT working tweaks - it would be very useful ones: - Change power plan - the changing of the preffered power plan described by zavan at post isn't working at all. Hopefully someone can make a working .reg for this, or maybe an .inf out of the powercfg guide from here. So, the following code is useless for setting the preffered plan to High performance... Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{025A5937-A6BE-4686-A844-36FE4BEC8B6D}] @="Power Options" "PreferredPlan"="8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\User\Default\PowerSchemes] "ActivePowerScheme"="8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c" I also attached the working tweaks. More started threads by default.reg Page file - 512 MB.reg

Once again I bring to your attention how nlite handles presets - see here - maybe you'll consider something similar for W7T in the AIO presets, for example a check box for all the subcategories (see here - check boxes also for Addons, Components, Services etc), so from a preset file we can choose only a section that interests us at a specific moment. Thank you.

In W7T 1.3.0 v84 there is no explanation of this in the description of removing IIS. Or have you hidden that dangerous option, and the IIS components shown by W7T are ok to remove?

KB2581464 was superseded (for the moment) by KB2496290 (v2). But next week maybe we'll say that another KB superseded both of them, so KB2496290 cannot be used in the description.

1. In the description of the system tweak Improve USB Storage Devices Performance - quote: KB2581464 is needed for this to work. This update however is long gone from SoLoR's update pack, since it was superseded. So a better enunciation would be smth like Make sure you slipstream latest SoLoR's updates for this to work. 2. USB Boot Prep leaves behind a .txt document called T (qouted below) on the drive C: after running Full Format NTFS. Maybe that txt file can be deleted by default with W7T. Done. 3. Once again I bring to your attention how nlite handles presets - see here - maybe you'll consider something similar for W7T in the AIO presets, for example a check box for all the subcategories (see here - check boxes also for Addons, Components, Services etc), so from a preset file we can choose only a section that uinterests us at a specific moment. If no 3 is not a liitle thing, then I'll make a request for it in the appropriate section of the forum

Request filled

Sorry, I thought we should use that switch besides the regular ones to remove the cancel button. I was wrong, it's an internal switch. Thanks for the explanation,

Thank you for the update and please include in the first post info about the /qb! switch. Also, one question: Can I use this addon also for Windows XP x86? I'm asking since yumeyao is rather absent in the last weeks.

Thanks for the bump. I think it's easy to implement - the unattended only needs to be copyed to the root of the index 2 boot.wim besides the root of the dvd - and it really is a life-saver for MANY users (since USB 3.0 drives are becoming so popular). Thanks again.

Talked about a while back, hopefully will be in W7T 1.3.0 final.

As I've found out here, there is a solution (ricktendo found about it) for my problem (and many others's) with unattended aren't working when windows is installed from some usb devices (with ssd controllers inside for example) - the solution is to copy the unattended .xml file also to boot.wim (index:2) besides the root of the dvd/usb. So, please Legolash, make this the default way of integrating the unattended file through W7T.

Solor extracted the cabs here, however I don't know how to integrate them to an offline image - the CAB Installer from W7T only installs the cab updates to the currently installed OS on your computer. Hopefully ricktendo will enlighten us on how to do this, and maybe at some time we'll be able to do this easily through W7T.

You've removed sample music. Start again the process without removing any media from windows.

Waiting/hoping Legolash will make the operation described here the default way unattended is applyed through W7T, so any other explanation if that happens is futile.

And one more thing - the setting <RegisteredOrganization>xxxxxx</RegisteredOrganization> isn't required for an unattended setup for windows 7. I've deleted the .xml from 2 days ago, because my final complete unnatended xml file looks like the one attached right now, perfect for me. Thanks again, myselfidem Autounattend.xml

I can confirm that there is a solution (ricktendo found about it) for my problem (and many others's) with unattended aren't working when windows is installed from some usb devices (with ssd controllers inside for example) - as I've said here, the solution is to copy the unattended .xml file also to boot.wim (index:2) besides the root of the dvd/usb. So please Legolash, consider this to be a bug, and change the way unnatended is applied (so that is copied to boot.wim also), both through AIO and also through WIM Manager.

About Input Locales - it's best from my experiences with the unattended file made by myselfidem to use the windows 7 values instead of xp/vista ones. I mean this values instead of this values. If not, for example if I choose the usual US input locale from xp/vista (0409:00000409), I get two inputs in win7 - US International and US English, instead of only US International if I use the win7 values (0x00020409).

PROBLEM SOLVED Yep, I can confirm rick's method works. With the help of this guy also I managed to mount boot.wim via dism manually, and yes, copying the unattended.xml file to the mounted boot.wim (index 2) solves the problem. Thanks again to all the smart members of wincert

Nevermind, I figured it out here. Thanks again myselfidem for that beautiful unattended xml