tap52384

After dual-booting Vista and XP for almost 24 hours, I must say that nLite has made a large difference. A standard Vista Enterprise install w/ Office 2007 takes the same amount of space as XP with many more programs installed, including Visual Studio 2005, Office 2007, and others. Keep up the good work on both nLite and vLite. It will be quite an accomplishment to skim Vista to less than 700 MB. Computing has not been the same since the introduction of permanent component removal. Thanks nuhi!

To Shutdown Immediately: shutdown.exe -s -f -t 00 where: -s (shutdown) -f (force applications to close) -t (time until shutdown in sec.) -r (restart)

control panel --> display --> appearance tab --> windows and buttons dropdown box --> Windows Classic OR Disable Themes: Right-click My Computer --> Properties --> Advanced tab --> Under "Performance," click "Settings" --> uncheck "use visual styles and buttons"

HTML?/

nice...that's impressive!

bad...why do you want to remove it? You can remove Internet Explorer and keep its functionality in Firefox using the IE Tab extension, if that's a concern...

Why not use an arraylist as the queue? That way you can store the objects as objects and then cast them when you need to use them.

I second the use of a .reg file.

I concur; IBM laptops, especially the newest models, come with enough stuff to stifle the power of the Thinkpad T60, slowing its startup significantly. I have an R51, and I used nLite to remove unnecessary components and used the registry tweaks outlined above to achieve significant results.

There is a small bug where if you try to integrate wmp11 after wmp11 is already integrated, i believe that Cannot create a file when that file already exists: perhaps one of the cabbed files is what it is referring to? Additionally, this error does not break the previous successful integration.

Could it become a requirement to include the name of the used visual styles and other applications that appear on the desktops? That way, everyone could improve their desktops with the goodness shown here!

I used the WMP11 Integrator last night, and it worked like a charm!

ASMS Compression is found by clicking Advanced on the Hotfixes page. Additionally, because more components are available from 1.0.1 to 1.2.1, the most likely explanation would be that more components have been divided up to better take away only the functionality you desire to get ride of. For example, Floppy Support (in the hardware section), used to remove Format Drive support. With version 1.2.1, they are now separate, allowing further customization than before.

I plan to use this integrator to the fullest. Thanks for the various utilities you have released! Your windows updates downloader is the best!

After using the /integrate switch with these files extracted from WMP 11 Final: umdf.exe WindowsXP-MSCompPackV1-x86.exe wmfdist11.exe wmpappcompat.exe wmp11.exe I went into the $OEM$ folder, created the $$ folder (windows), then created the System32 folder (files in this folder would go to c:\windows\system32\) and placed these to files to be copied into the system32 folder: wmdrmsdk.dll mfplat.dll Worked like a charm. This method directly integrates WMP 11 into your Windows XP installation source.

I'm trying an ISO where I integrated using the /integrate switch the following files: umdf.exe WindowsXP-MSCompPackV1-x86.exe wmfdist11.exe wmpappcompat.exe wmp11.exe In that order also...I figured that wmp11 should be last...I'll let you know how this turns out...

I tried WMP 11 using the built-in /integrate switch, and I received an error about wmdrmsdk.dll not being found. Has anyone found a way around this to truly integrate WMP 11 Final?

You can integrate WMP 11 Final manually if you wish, after extracting the contents of wmp11-windowsxp-x86-enu.exe. You would do this by: wmp11.exe /integrate:C:\XPCD where C:\XPCD is the path to your installation source I didn't test to see if nLite can integrate it, but I know that with its "remove duplicate files" option, it should be able to clean it up...

I have used nLite for the last two years, and I know that there isn't any spyware within the program. To end it all, simply state which file is causing this infection. Ad-aware results, as was posted earlier, have a detailed log which explains what is causing the spyware related infections on a computer. No need for hostility, but it's not nice to accuse nuhi, who has been dedicated for at least two years to delivering a product of unprecedented quality to allow extranneous files and features to be removed permanently from Windows XP. It is events like these that discourage people from sharing their hard work with the world, desiring to avoid the harsh scrutiny of the envious and the unappreciation by the selfish.

If you have already downloaded updates in the specified folder, is it supposed to notice these and color the boxes beside those hotfixes? Currently, build 724 hasn't really scanned the folder to see if hotfixes already exist and to color those choices automatically. Is there something I'm doing wrong?

Are you referring to Quick Launch? Right-click the taskbar and go to properties and then enable quick launch. If that's not it...

Not to be the bad guy, but isn't Ultimate the combination of all the other versions, or do I have that wrong?

Since your virtual pc does not have the same devices as your thinkpad, it won't be able to give you an accurate account if what you're doing isn't working, thus the results are inconclusive. nLite has the ability to integrate drivers into the installation media. If you are worried about missing functionality, simply use nLite without using components, simply to integrate and update the installation source, integrate hotfixes, addons, and even themes, and then other options like patching for 3rd party visual styles. What thinkpad do you have? If you have a pretty recent one (at least manufactored in 2002, I had a Thinkpad R31, I now have a Thinkpad R51, used nLite with both) then the IBM Software Installer should be able to help you if integrating the driver is not a concern of yours. Honestly, I do not have the battery driver integrated, but instead installing automatically during the first login after setup completes, but by creating an nLite addon, it's possible to have drivers install during the last stages of the XP setup installation.

How is wireless information, such as network configurations, wep keys, etc, stored in Windows XP? If they are in the registry, are they encrypted, just as the product key is encrypted within the registry? Does anyone know of how to find this information, and if possible configure networks from the registry?

nLite can integrate hotfixes into the source...