yogurt

@Legolash2o L0L... As a practice I always look under the hood to see whats in there. I remember a time when I a cut and paste a script I found on the net without giving much thought to what commands it may contain, thinking tthat it it was from a trusted source I ran the script without skipping a beat.Instead of helping me fix the problem it screwed my webserver and I lost all my data. Never again shall I be so careless.

:doh: Corrected, thanks dude.

Support Windows Toolkit -- The best darn DISM / ImageX Tool to surface on the net. @Komm @McRip EDIT :: I've noticed that servers that power the Win Toolkit update catalog has been going offline more than usual these last few weeks. For what reason, I can only begin to guess. However, I suspect that the servers may be down because of a spike in traffic from Win Toolkit users or perhaps not. High traffic websites such as those maintained by McRip and Komm typically have SLA's that dont provide enough of a bandwidth allowance for the ammount of traffic these servers generate. SLA's that provide the necessary bandwidth for high traffic sites tend to cost more money. It can get quite expensive for non-profit projects such as Win Toolkit and the Update Catalog. Bandwdth costs have been going up for the last 5 years (Smartphones, Hi-Speed Internet, etc...) ISP's are always in reaching in our pockets for more.... I would like to extend an offer of 5gb of webspace and generous allowance of bandwidth for couple of month, If my suspicions are incorrect and the servers are simply down for Maintenance, all the better. Anyhow, thats it. Keep up the great work and best regards.

Here is an interesting article I stumbled upon for those of you who are wondering about the Remote Differential Compression algortithm. Debunking the Vista Remote Differential Compression Myth Disable or not to enable / disable RDC. Check it out. it's worth a look see, You might be suprised.

@amaltom61 @Komm ISP's can be picky regardless of SLA's. Something is going-on that's for sure, Come on Komm, you got nothing to loose. Keep up the good work, I support your efforts.

I made Komm an offer to host his website for free for a month or two while he gets things sorted out with his current ISP, but I have yet to receive a response. Komm, if your reading this, the offer still stands. Send me a PM if your interested and I'll setup an FTP account. Were talking about a server over at Hostgator or Rackspace. My current SLA reads unlimited bandwidth allowance. Of course I'll have to double check with my sales rep first to be sure. But let me know if your interested.

If it's not to much to ask, could you please post MD5 Hashes so users are able to verify the integrity of their downloads. Many Thanks for this addon.

@Kormann If it's not to much to ask, could you please post MD5 Hashes so users are able to verify the integrity of their downloads. Many Thanks for this addon.

The 'Enable CMD' option turns on the 'Command Tab' found in the AddOn Maker tool of Win Toolkit 1.4 and 1.5. "DISM.exe /Image:%WIM% /Disable-feature /FeatureName:WindowsMediaPlayer /Featurename:MediaCenter"

@Compstuff, Funny you should mention AlternateStreamView. When I became aware of my the problem, I didn't feel like having to right click on each each driver file to unblock it manualy, with over 100+ files, that would have been insane and time consuming. So I went looking for a tool that would help me get the job done in bulk. Low and behold, nirsoft had just the thing in their massive asernal of useful tools. I have since added AlternateStreamView to my nirsoft suite of tools. And I dont have to lower security, another plus.

Curious, doesn't the WIM spliter tool allow users to span a wim over multiple CD/DVD? as described here. Request ::

Interesting list, I personaly dont recomend removing any components with the exception of a select few. e.g. International Themes, Games, and few non essenstial accessories. Other than I'm sure to run into problems. Problems may occur especially during a Service Pack installation. Anyhow I just wanted to put my 2 bits in.

My list of drivers are not being integrated. Nor do they appear in the mounted wim ..\windows\inf. The only drivers that do get integrted are the the last 3 on the list. I've attached pre and post integration sreenshots for review and consideration. I'm going to try with DISM next. In the meantime any insight would be much appreciated. EDIT :: Okay, I figured out what was happening here. It turns out that Windows 7 flaged all the drivers I donwloaded from the net with a Data Stream that blocks admin access to the file. Windows does this automatically to prevent malicious software from unkknown sources from infecting the host computer. As a result DISM was not integrating any of the files I download because they had been flaged with a Data Stream. More about this behaviour and how to disable it using Group Policy can be found here. Drivers to be integrated Integrated

Win Toolkit 1.4.0.77 was released with a focus on Windows 7 SP1 and not so much for Windows 8, so the errors your experiencing in component removal are to be expected. From what I understand from the developer, 1.4.0.77 has gone [stable] and their will be no furhter releases of the 1.4 branch. (Lego, correct me if i'm wrong). I'm sure that WT 1.5 will blossome into a solid tool just as 1.4 has. Looking forward to it's release. Keep up the good work lego! :prop:

@foobuzz WinToolkit uses DISM and ImageX for pretty much all of it's functions. I know the DISM command line tool can be picky and cumbersome at times, but I've grown used to it over time. I use the DISM commad line tool along side with Win Toolkit often. With respect to to the :: exit code :: error, If my memory serves me right, this error has something to do with permissions and user rights. One should run DISM in an Elevated Command Prompt. As far as IE10 integration, it's diffucult to say for sure, but users should be able to integrate IE10 over IE9 or IE8. The same principles should hold true in either case, but thats just a theory for now.

@foobuz I can confirm that it is safe to remove IE8 packages, providing you Integrate the IE9 packages to replace the removed IE8 packages. Windows 7 SP1 contains two packages for IE8. Jest take a look a George King's post #4 for the package names. Also in my experience, You can leave the IE8 packages as they are and Integrate IE9 + updates packs with WT AiO integrator (DISM Tool) and the IE8 pacakges will be taken care of during integration. I prefer to remove the IE8 packages with DISM and then Integrate IE9.

I'm trying to install Windows 7 SP1 x64 from USB. Windows boots from my USB stick. I select a language for the UI. Click on install. I select the unallocated space on the targer hard drive and setup fails Setup is unable to create a system partions.... Heres the stange thing. When I try to install the image from DVD everything works like charm. The partions is created and windows installs 100%. Any insight would be much appreciated. It doesnt matter if the drive is unallocated, formated, or marked active. I've tried every which way under the sun. I've tried changing the order of boot devices, still no change. I've changed the drive mode in the BIOS from ACHI to IDE, still no change. I dont think windows 7 requires any boot critical drivers because setup sees and offers the drive as a prospect for installation, it just wont create the partition when I try to install from USB. Heres the stange thing. When I try to install the image from DVD everything works like charm. The partions is created and windows installs 100%. Any insight would be much appreciated.

Sweet. Thanks Reaper. Now, thats innovation.

This is option is for deleting all Silent Installers from your image. For example, if you have this option selected and start a session all your slient installers will be removed from the image upon completion of that one session . The option to delete silent installers will be automatically deselected (disabled) at the end of your session. The option is not selected by default. To return the AiO Integrator options to their default value, click the button to the left of the options window. Cheers!

@Legolash2o I created this thread because my search queries were not producing any relevant results, however as you can see in Post #8 their is an existing thread for addon issues. You may want to move this thread to the Addon Issues topic posted here. Best regards. EDIT :: Eureka! I've figgured out how the 'Program Files' variable workes when using the Addon Maker tool. If the addon is flaged x86 then and is integrated in an x64 system then using the %PROGRAMFILES% variable will copy files and folders to Program Files (x86). On a x86 (32-bit) system the same variable will copy files and folders to %PROGRAMFILES%. Seems a little strange but that how it behaves. Hope this helps those that are experiencing issues with this variable. Peace out.

@myselfidem Bravo, excellent work my friend. thank you for sharing this command. en français :: Bravo, excellent travail mon ami. merci pour le partage de cette commande

Thanks for your insight, much appreciated. To be clear, I'm not adding the environment variable manually, the resulting Tasks.txt is being created by the actual addon maker tool. The %ProgramFiles(x86)% variable is selectable from within the tool itself. en francais :: Pour être clair, je n'ai pas ajouter la variable d'environnement manuellement, le Tasks.txt résultante est créé par l'outil "addon creator" réelle. Le %ProgramFiles (x86)% variable peut être sélectionnée à partir de l'outil lui-même.

Well. really it's no big deal, It's only a small matter of editing the tasks.txt file manually. Taking me an extra 30 seconds. I just wanted to bring it to Lego's attention. Maybe it's residual from a deprecated feature? Also I've only just started to use the addon maker for simple tasks and I'm not all that familiar with all it's potential. So I may end-up just figuring out this odd behavior as I use it more more.

Hence the title of this post. Because that's where 32-bit apps go on 64-bit Windows 7 System. The app is 32-bit. None-the-less. When creating an AddOn The AddOn maker doesn't differentiate between system architectures. In Win Toolkit a user could create a 64-bit addon on a 32-bit system. The only time I would think this behavior would occur is if a 64-bit AddOn is integrated in a 32-bit system. Unless I'm not understanding something on how the AddOn Maker tool works.

le document en question de votre compte mediafire sont mis à privé. vos autres documents intéressant de regarder. Puis-je avoir un coup d'oeil?