Everything posted by Legolash2o
-
Windows 7 Toolkit v1.0.2 FINAL
There is a problem with the Unattended Creator at the moment and i need to look into that bug... A)It shows x86 when it's created but when you integrate it, W7T will auto change it to amd64... I think so, i need to test this out. Sorry, Unattended.xml stuff is not my strong point but i will fix it
-
Tweaks [Merged]
In v1.3.0.41A+ you can now select reg files on the AIO Tool (Tweak Tab), you don't have to convert the reg file, Win Toolkit will do this for you. This new feature lets you import your own custom tweaks via Win Toolkit. ------------------------------------------------------ My point is that you don't have to make a request for every tweak BUT if you think a tweak will be great for other users, feel free to share in this thread. Also make sure W7T does not already contain the tweak(s). --Zimmer--- a handy reference for tweaks is the Group Policy Settings Reference - this lists the registry keys here's the direct link to the Win 7/Server 2008 sheet... WindowsServer2008R2andWindows7GroupPolicySettings.xlsx (612 KB)
-
Faster integration of updates?
I have just finished coding faster integration of LDR/QFE updates, Regarding what you said about the DISM output... I've never managed to get it to give output on-the-fly, so there is nothing i can do to increase speed of normal integration (without LDR/QFE) option. If any user has previously used the QFE/LDR option in the past, from the next version it should be more than twice as fast
-
Windows 7 Toolkit v1.3.0 ALPHA
Warning: This is an alpha, report all bugs here and requests in the requests forum. Remember this is an alpha, there are still big changes to come. P.S. The download link contains more info about the program itself. If you have a problem, bug, glitch, etc... then please make a new topic
-
Windows 7 Toolkit v1.0.2 FINAL
I have temporarily unlocked the new Component Removal in the All-In-One Integrator tool, let me know how it works!
-
Windows 7 Toolkit v1.0.2 FINAL
I have managed to get the component removal on the AIO form working so it will remove all the packages from all the images you select instead of just the one. However this won't be available until v1.0.3 and i have not added all of the packages to the list yet which is a boring task
-
Weird component removal behaviour
Just couldn't be bothered, i've released it on MSFN... http://www.msfn.org/board/topic/152688-win6x-registry-tweak/
-
Weird component removal behaviour
Lol, not sure if i can be bothered to release it, if you want i can send you the source code and you can release it if you want?
-
Weird component removal behaviour
Done and works, if you run with /L it will output all components to a text file.
-
Weird component removal behaviour
The Component remover i was on about is on the All-In-One Integrator, the same tool which you integrate updates, drivers, etc... The /L thing would be easy to do, but should i add it..... maybe
-
Weird component removal behaviour
As posted on MSFN, i'm now on build v1.3.4 with more another bug fix. Also, i've managed to get the Component Removal on All-In-One working so you can now remove packages from all Window versions in the image automatically, but it won't be visible until W7T 1.0.3
-
Weird component removal behaviour
EDIT: I have completed v1.3.3 which let's you use this tool on the current installed OS but not sure if it actually needs releasing... Total amount of changes i've done *the /m is no longer needed, will do the task by default *fixed a bug where it did not work if there was a space in the mountpath. *Win32Security.dll file is no longer needed *Added new colours, errors are displayed in Red *Fixed bug crashing at end of running *Fixed bug where it cannot unmount registry if something fails *Added specific component selection *Fixed some other bugs *Added an appropriate small icon for the app Also normally you will have to put the specific component name i.e. "/c Microsoft-Hyper-V-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7601.17514" but if for example you put "/c Microsoft-Hyper-V-Common-Drivers-Package" it will show all packages starting with that. Top picture is on default run whilst bottom is a specific component.
-
Weird component removal behaviour
I've already done a few modifications to it myself and fixed quite a few bugs with that tool, it's a great little tool. I will add the feature you are describing to it As i said above i'm planning on doing some work to it by moving it to the All-In-One section so it will remove stuff from all the images you select and not just one at a time
-
Windows 7 Toolkit v1.0.2 FINAL
That error only occurs when there are missing files in the DriverPacks
-
Windows 7 Toolkit v1.0.2 FINAL
build 37 has been released, some drivers did not get expanded so i've added the unknown file types so that they will now Also, fixed a few bugs/glitches i have found in the error logs. Just to save people from asking.... I will not be starting v1.0.3 until i receive no more error logs, i want all the bugs to be fixed before i start it
-
Weird component removal behaviour
Make sure you remove the components from all images, then it may shrink more... I'm planning on doing some work on the Component Removal
-
Silent Install Error
Yeah it's best to directly integrate IE9, i will look into the issue above.
-
Windows 7 Toolkit v1.0.2 FINAL
It's abit tough at the minute, my laptop has broken and I'm waiting for a part from China. I will continue once ive replaced my faulty motherboard.
-
Windows 7 Toolkit v1.0.2 FINAL
Permanent
-
Windows 7 Toolkit v1.0.2 FINAL
Personally i only integrate the drivers i need and not the whole driver packs lol If i want all the drivers in my install i just copy the folder to the DVD source and manually add them after install to keep the install.wim down
-
Windows 7 Toolkit v1.0.2 FINAL
The drivers still add to the list when the driver causion appears and DISM still tries to integrate them. I will be having a look at it.... The 2nd part of your post i may have to get back to you on that one
-
Windows 7 Toolkit v1.0.2 FINAL
W7T integrates them into the boot.wim anyway
-
Windows 7 Toolkit v1.0.2 FINAL
It's add them in standard mode but it also integrates them into the boot.wim I'm not sure if they need to be integrated as text mode with windows 7 (i know you did with XP). Please feel free to try and let me know if it works or not
-
Important News
I'm not fully back im slowly getting back into it, already fixed about 4 bugs, but i still need to go through about 300+ error logs
-
Windows 7 Toolkit v1.0.2 FINAL
On the main screen select Force Unmount and select the folder it mounted to (default is C:\W7T\Mount).