ricktendo

AFAIK they are used by WSIM to tell what packages/updates are integrated in the image and what you can turn on/off with your autounattend.xml, not sure what else they are used for

Yes, keep boot and efi...you can put the x86 and x64 .clg files in sources with no problemo, they should be able to coexist because they have the same name as the image in install.wim, that is if you did the right thing renamed your images to add x64 to the name when you exported them Go ahead and create new .clg files after you integrate stuff...for this you need to use WSIM BTW I think you can also delete the .clg files (IDK I dont personally)

Post your autounattend.xml lets have a look (edit usernmae, pass and serial)

It does not work because no matter what keyboard you add with the regtweak it will change it back to whatever you have in your autounattend.xml

You can delete the \support & \upgrade folders and setup.exe & autorun.inf from the dvd root, also you can delete ALL the files in the \sources folder EXEPT: boot.wim, install.wim, *.clg (of what versions you still have in install.wim) and setup.exe (its REALLY IMPORTANT that you keep setup.exe in the \sources folder, you dont need the one on the dvd root)

If you place autounattend.xml inside boot.wim index 2 next to setup.exe it solves the problem of autounattend.xml not being detected when booting from a (diskpart created) bootable usb hard drive, why not try adding it to index 1 and/or 2 beforehand see if that solves the problem for your PE style install

My bad, you are enabling the features...why not use dism to enable them instead of the xml? for %i in (WAS-WindowsActivationService WAS-NetFxEnvironment WAS-ConfigurationAPI DesktopExperience InkSupport NetFx3 WAS-ProcessModel WirelessNetworking) do dism /Image:<path_to_mount_folder> /Enable-Feature /FeatureName:%i

Do you use dism at all? It would be best to disable the feature beforehand with dism

I would like to add this regtweak to XP, you right click on a computer in your network/worgroup list and choose "Connect with Remote Desktop Connection" and it launches RDC and connects to that PC I love this feature in Windows 7 and would like to add it to XP (not that it matters but I already have KB969084 RDC v7.0) Any help would be appreciated, like the GUID in the registry for that right click menu or switch to launch RDC and enter the PC name

Did not know you could select a already installed theme, thought it only worked to create oem.theme...will have to run some tests BTW would be nice if one could add more than one bg to the theme

20 GB is probably too little, 50 GB is more like it but I recommend 100

I think you are referring to how to make sure you have backed up the driver for injecting...go to %WinDir%\System32\DriverStore\FileRepository (after you have installed your driver the normal way) and sort by date and you should find your driver right there at the top, copy the folder to your desktop and delte the .PNF file and you have your driver for integrating Sorry for the double post, always get edit and reply buttons mixed up

Have you tried MassStorage DriverPacks?

Have a look at the tutorial by Shark007 But if you want highlight feature use foxit

ReadyBoost does however use the CPU, I read this in Autounattend.xml help file for WAIK when I was looking for how to enable ReadyBoost unattendedly

Using ReadyBoost is not the same as adding ram

You need to back up the <certificate>.xrm-ms (usually located, but not limited to: %windir%\system32\oem) and your oem serial (with a tool like magic jellybean) If you use the serial on the bottom of the PC you have to activate by phone I think

These vids may help a bit: How to make silent switch installers How to make INF theme addons How to make INF program addons Using WAIK

Should not need to remove the older driver, if the driver you integrate is newer then that is the one that will be used...are you sure you have the correct INF devil? BTW besam when are you going to add support for CABs? Its stupid not to

Thought you might be interested in a update for Microsoft Visual C++ 2008 Redistributable "v9.0.30729.4974" http://www.mediafire.com/?tdj2nmicmmy More info

nLite cannot integrate all the hotfixes in your .ini, only some...these are some that are not supported gdidettool.exe HMTCDWizard_enu.exe Windows-KB909520-v1.000-x86-ENU.exe WindowsSearch-KB940157-XP-x86-enu.exe IE8-WindowsXP-x86-ENU.exe Nor can it integrate regular installers like Firefox Setup 3.6.8.exe Thunderbird Setup 3.1.1.exe winamp5581_full_emusic-7plus_en-us.exe wlsetup-web.exe Also IE8 nor WMP11 can be integrated by nLite (look for addons to these) You are better off using a updatepack, look over on ryanvm.net/forum you will find a few Sorry for the double post, I hit reply instead of edit

mode con: cols=100 lines=10

Does not need to be signed, I have Win7 x64 and it works fine http://img191.imageshack.us/i/50184563.png/

TY so much this helped allot BTW where can I find the full list of DeviceCategory's? Example Display.Monitor.LCD PrintFax.Printer Imaging.Scanner etc Edit: nevermind, coffefriend link has them

Will you make a tutorial?