compstuff

Their are a few other VERY IMPORTANT rules which you seem to be completely ignorant of: 1) Treat people with courtesy and respect 2) Don't be soo judgemental & arrogant 3) Think before you speak or write And one that my Grandmother taught me and I love: If you have nothing good to say about someone DON'T SAY ANYTHING ... you really need to check your arrogance at the door!!!

I agree with bphlpt but adminxp your making a very large assumption when calling some one a noob and you shouldn't assume what someone is thinking. I have done more slim down XP setups for special apps than you can imagine and although it would be nice to have one for 7 I would just go the services route now due to the exact reasons that have been mentioned and also my inexperience with 7 and what does and does not work.

Oh My NO need to apologize... I appreciate the feedback and support... after all thats what makes a great support forum and this is certainly a great tool and I look forward to its continuing development. I have done literally years of testing and using Driverpacks and RVMI which is why I recognize many names on here. From what I see of this so far it seems like a tool I may be using for the next few years

No... this is a clean initial setup with WT7 from a working technet ISO... no ANYTHING except looking to check SoLoR updates after selecting my file source. I come from some old world techniques and I ALWAYS prepare a new and clean mount from my ISO and do a SoLoR update and then use a copied version of that updated mount to THEN do my Mass Storage and CPU drivers... then I make a copy of THAT mount and use the copy for tweaks etc. Thats my testing method from doing HUNDREDS of tests with RVMI and Driver Packs. SO once again this was a untouched extraction of files from my ISO and then selecting it.

I just checked the same files source with 96 and it works fine

I am trying a new clean AIO and when I select my source files (which are the same as I used with the other tests) I get the following error. I tried again with a new extraction of my ISO files and got the same error

sorry I should have been clearer... need more coffee :-) When I do the SoLor SP1 Updates downloads, I select my folder and then Win 7 x64...it searches for all the updates and ALWAYS tells me I need KB2603229

WT7 constantly shows me kb2603229-x64 to download but never recognizes that it's already there.

Any thoughts on this? I will be doing some testing today and would appreciate any advice before I do... thanks

It actually in the very first response... you extract them and add them to the DVD by overwriting the exisiting files There is a lot of other info on here about this and also Rick's link help explain and even a general google search will explain more than I can

WOW that completely throws me now since I thought Rick and LegoLash told me to check that option... also before 95 I used either 93 or 94 to completely integrated all of SoLors updates with that option checked and had no problems at all

I'm still not clear despite the answers so I will ask in a different way that may make a little more sense: What is the actual sequence of processes that take place when using the tool? If my ISO or extracted installation folder is on drive F and I start the AIO process what happens next? Does it mount to the "MOUNT" folder and then start processing the addons, updates etc by using the TEMP folder as a scratch pad? So are we copying or writing from MOUNT to TEMP and then back to the source??? I am trying to figure out how to optimize a 2 drive system with regard to I/O writes and reads I hope that asks this question a little more clearly...

I am still a newbie and learning this tool and I don't really see some of the addons I'm looking for so I am interested in trying this to create my "base" addons that I will use in all my installs. Shockwave Flash Acrobat Reader Java K-Lite Codec Packs MalwareBytes Maybe a few others Will the addon maker work for these or are their other tools/solutions? ***When you hit HELP in the addon maker it gives you some info about CrapCleaner***

I thought I read this somehwere here before and I am reading info about Ricks solution so I am wondering if W7T has the ability or already injects the autounattend.xml directly to the boot.wim image index 2

I'm trying to send it I just don't see how to attach a file

Hmmm I created a new xml file with the key and the "skip" selected... it seemed fine so I ran the install and once again: The unattend answer file contains an invalid product key. Either remove the invalid key or provide a valid product key in the unattend answer file to proceed with Windows installation.

I'm on it :-)

Awesome.. I will test it as soon as ist out and report back

I took the same source files and deleted the autounattend and ran an install... in went fine and I then activated the install with the same key I am trying in the xml file so the key and the install files seem fine

Its windows during the initial setup

I seem to be having the same problem. I am using my technet WIN7 Enterprise and using my valid key with the skip auto activation and yet it keeps telling me I have an invalid key.

Its the User State Migration Tool (USMT) 4.0 update and they go here: C:\Program Files\Windows AIK\Tools\USMT\x86 C:\Program Files\Windows AIK\Tools\USMT\amd64 So I guess I don't need to update this for an installation

What folder/location do the files from Windows6.1-KB2023591-x64 actually go? I don't see where scanstate and loadstate go...

I use a WIN7 dual hard drive laptop for all my work but I only have 4GIG mem so I don't use a RAM drive (I just order 2x4GIG RAM upgrade so will start using RAM drive soon). One of my drives is an SSD so should I create both the W7T temp and mount folders on the SSD for best performance?

I just updated to the latest version and took a look at the SoLoR updates again. I noticed the folder column and then did some further checking and it all became crystal clear to me :-) ..W7T handles thse updates AWESOME and of course SoLoR's work is also incredible as well! Thanks for the tool and thanks for the help.