grabben

I do it this way. I get all the files and registry entries from the manifest files so i only need this define a component. var c = new Component2(@"Calculator", Accessories, false) { CheckFs = (image, wim) => wim.FileExists(Path.Combine(System32, "calc.exe")), ComponentNames = new List<string> { @"x86_microsoft-windows-calc", @"amd64_microsoft-windows-calc", @"x86_microsoft-windows-calc.resources", @"amd64_microsoft-windows-calc.resources" } }; Also interesting:) hey, when can we see an update of WinIntegrator ?

Sounded like that yea but im not sure how others do and dont know how nuhi did it (nLite & vLite)..

Hmmmm. Glad you asked. Actually what I am doing is simple. Here is an explanation (for advanced people) To remove components we need to 1. Delete Files 2. Delete Folders 3. Delete Registry keys 4. Modify file (Delete some line or modify a line) 5. Modify registry keys To do this I came up with a simple solution. I created an xml file that has the components information and what to delete and to modify. Here is an example: The <Files> section defines the list of files to be deleted or modified. The <Directories> section defines the list of directories to be deleted. The <Registry> section defines the list of registry keys or values to be deleted or modified. Notes: 1. you could use wildcards in the name of files and directors and registry keys. 2. Later on I could add a section for keeping files (a do not delete section) In this way everyone could help. Also if certain DLL or certain file or certain registry value causes the system to be unstable then we could easly remove it from the list. I hope the explanation helps you in understanding what I am doing. Feel free to ask questions or give feedback and suggestions. Definitly looks interesting and seems to work fine. Yep, im also looking forward to try next release No suggestions or real feedback atm but goodluck:)

Possible to integrate keys directly to edition if you want.

That'll be tough work if you want Windows, linux and mac all together but it should be doable .

How can it activate as OEM licens if your using a MAK license ?

Hei grabben it's normal that you feel its confusing at first, specially if you are new at this. I sugest you read it all once or twice (complete timeline explanation at the end) and once you understand it, start working on it. This guide has many small steps and if you make a mistake in one, everything's screwed up. The text is small due to a forum update and I kinda liked it. Keeps things in perspective and reduces the changes of you skipping a step. I'm trying to get the next guide update as small as possible, but I think I'm gonna need to program some stuff myself to cut some steps down. Windows Vista is tricky as hell Thanks Andregcasal for reply. Yea well i read a few times.. i just lack motivation/whatever you want to call it for doing things like this but im trying to Ive read the guide few times but still seems like a mess to me but one more time. Vista? Hm what updates can we be expecting?

/Hugest facepalm ever. You cant slim down 7 with 7C yet beacuse (as u answered your own question) that function isnt implented yet.. Thanks for the hugest facepalm ever, but I was referring to Zumoc's post showing his slimmed down windows 7, pojken. I have read the RT7lite thread and noticed he posted the same thing there, so I am going to assume he used RT7lite and posted his results here aswell for the purpose of showing off. No problem You wrote " 7 down with this app?" so i figured u mustve ment 7Customizer and nothing else. Slimming down windows 7 can be done, theres a few threads here on msfn, one is WinIntegrator thread (but no work's been done for a long time) and then we have something else.. install.wim_tweak or something..

/Hugest facepalm ever. You cant slim down 7 with 7C yet beacuse (as u answered your own question) that function isnt implented yet.. @Blue4603 Possible you could tell how u managed to get removal part to work ? Just interesting/facts..

Anyone ?

Export vista and windows 7 to a new install.wim and use the imagex /export <old path> <index> <new path> <name> command ? Did that and moved the new install.wim to windows 7 dvd\sources.. It doesnt work for me, says installation cant proceed or something, i also created new clg files..

EXACTLY what are you trying to do ?

I cant get windows 7 and vista to work together when using imagex command like you.. atleast i dont think so.

So you just used the imagex /export command to make one big install.wim and then made a new .iso ? and thats it ? No folders from server 2008 R2 dvd ?

One Vista/7 dvd could be interesting/nice to have Edit: What guide did you follow ? the one posted in multi image thread ?

Man the guide is sooo confusing and the text is small? why make the fontsize that small ? Can the guide be more clear ? explain more? Or am i to stupid... as usual!

Ooooh yes I understand, that's the manual way. I managed to change the setup screen language with some tool. I guess that when unattended file is used then the setup language is not important because it is supposed to be unattended and that's why is always at english. yea exactly its the manual way . Hm possible, im not sure or maybe its just a component in unattended that makes it skip language selection for setup. Hi Grabben. After some try and error I didnt manage to select the setup language but I managed to change the setup language from Autounattend.xml You can change in Autounattend.xml these lines and set whatever language you want: Then the setup will be in the language you want. Hm thanks, altho id like to change the setup language myself and not in the unattended file

Yep i know it works you can just copu everything to a usbstick if you want, using xcopy <path> /e /h .Just make sure its formatted and active..

Hm.. doubt this but ill try again thanks. Sweet the component feature is working:)

How could you install 64bit in virtualbox ? :/

Could you post the key part from the unattended file ? Here, of course without the key itself, do you need more info?: <UserData> <ProductKey> <Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxx</Key> <WillShowUI>onerror</WillShowUI> </ProductKey> <Organization>Org NAME</Organization> <FullName>User NAME</FullName> <AcceptEula>true</AcceptEula> </UserData> Looks right to me but what do i know:/. Sure its right key for right edition ? :/ Yeah, I got it straight from Microsoft, and used it for manual installations... Weird, sorry i cant help you man. Altho i read today that Blue managed to get his removal part working, atleast with the first component!

Could you post the key part from the unattended file ? Here, of course without the key itself, do you need more info?: <UserData> <ProductKey> <Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxx</Key> <WillShowUI>onerror</WillShowUI> </ProductKey> <Organization>Org NAME</Organization> <FullName>User NAME</FullName> <AcceptEula>true</AcceptEula> </UserData> Looks right to me but what do i know:/. Sure its right key for right edition ? :/

Thanks alot urie tcntad MDL.

Could you post the key part from the unattended file ?

Ofcourse not. If you choose to modify ultimate you modify ultimate and only ultimate.