[Turbis]

Wait, how exactly do I slim windows 7 down with this app?
It says component removal isn't implemented yet :/

[grabben]

Turbis, on 12 May 2010 - 05:00 PM, said:

Wait, how exactly do I slim windows 7 down with this app?It says component removal isn't implemented yet :/

/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..

This post has been edited by grabben: 12 May 2010 - 05:22 PM

[Turbis]

grabben, on 12 May 2010 - 05:18 PM, said:

Turbis, on 12 May 2010 - 05:00 PM, said:

Wait, how exactly do I slim windows 7 down with this app?
It says component removal isn't implemented yet :/

/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.

This post has been edited by Turbis: 12 May 2010 - 05:30 PM

[grabben]

Turbis, on 12 May 2010 - 05:29 PM, said:

grabben, on 12 May 2010 - 05:18 PM, said:

Turbis, on 12 May 2010 - 05:00 PM, said:

Wait, how exactly do I slim windows 7 down with this app?
It says component removal isn't implemented yet :/

/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..

[sjoerdhooft]

myselfidem, on 12 May 2010 - 12:09 AM, said:

sjoerdhooft, on 11 May 2010 - 01:13 AM, said:

myselfidem, on 10 May 2010 - 11:46 PM, said:

Hello!
Which is the software you use to burn your ISO file made by 7Customizer?

I didn't burn it but used the ISO file in VMware...

Hello
I remember it happens to me one time - with the valid and correct key - but I don't really remember the reason !
You can try to make a new ISO file, but before deleete all the files inside the folder "work" except: mount; Themes; bootorder.txt; etfsboot.com; EXTRACT.EXE (originals files and folders).
And at the section: unattend; write inside all fields, because if you live some fields blank, setup may fail.
I hope that will help you

Well, that didn't work either. I finally removed the key from the unattended setup and al doing it now without a key. It's too bad but I don't have another solution, especially since the key works when the installation is done. So weird...

[myselfidem]

sjoerdhooft, on 14 May 2010 - 08:28 AM, said:

myselfidem, on 12 May 2010 - 12:09 AM, said:

sjoerdhooft, on 11 May 2010 - 01:13 AM, said:

myselfidem, on 10 May 2010 - 11:46 PM, said:

Hello!
Which is the software you use to burn your ISO file made by 7Customizer?

I didn't burn it but used the ISO file in VMware...

Hello
I remember it happens to me one time - with the valid and correct key - but I don't really remember the reason !
You can try to make a new ISO file, but before deleete all the files inside the folder "work" except: mount; Themes; bootorder.txt; etfsboot.com; EXTRACT.EXE (originals files and folders).
And at the section: unattend; write inside all fields, because if you live some fields blank, setup may fail.
I hope that will help you

Well, that didn't work either. I finally removed the key from the unattended setup and al doing it now without a key. It's too bad but I don't have another solution, especially since the key works when the installation is done. So weird...

You said

Quote

Yeah, I got it straight from Microsoft, and used it for manual installations...

Hello
Maybe you can try the tool MSKeyViewer for checking the key inside the registry:
MSKeyViewer
I've found some help here:
http://social.techne...95-57b40891bcc1
http://www.msfn.org/..._1
Maybe you can contact Microsoft and asking what is the problem with Autounattend.xml?
Help and support Microsoft:
http://windows.micro...lid-product-key
https://support.micr...prid=14019&st=1
I hope that will help you!

This post has been edited by myselfidem: 14 May 2010 - 02:46 PM

[TheWalrus]

Blue, cook us something we can test pls
Like, more tweaks or something at least

[TheWalrus]

Oh btw.
I am playing around with version 0.4.4 again after briefly trying RT7Lite. I think the start menu customization could use a slight revamp. For example, Remove default programs and Remove devices (it applies almost to all btw)... is misleading, cause when you dig in Start menu's properties, you just tick the checkbox to enable or uncheck to disable - the way it works in 7C atm is exact opposite

[blue4603]

@ myselfidem

Quote

I've tried successfully 7Customizer_0.4.4 with Windows XP Pro SP3 x86 and Unattended Install for Windows 7 Ultimate x86 (same architecture)!
I use WAIK for Windows 7 (KB3AIK_FR.iso)-installed successfully.
It takes more time but the result is all fine. Here is the log file:

Nice. Thanks for the feedback.

Quote

I've made also a new French.lng for 7Customizer_0.4.4:
French.lng 0.4.4

OK. I will include it in the next release.

@ grzegorz7853

Quote

Hi.

I create a 7customizer 0.4.4 - Polish.lng
http://www.mediafire.com/?otm4iwe11lm
Translated (i think) - 90% (sorry, my english is not professional)


Regards

Thanks. I will include it in the next release.



@ TheWalrus

Quote

Blue, cook us something we can test pls
Like, more tweaks or something at least

Do not rush man you will get something soon

Quote

Oh btw.
I am playing around with version 0.4.4 again after briefly trying RT7Lite. I think the start menu customization could use a slight revamp. For example, Remove default programs and Remove devices (it applies almost to all btw)... is misleading, cause when you dig in Start menu's properties, you just tick the checkbox to enable or uncheck to disable - the way it works in 7C atm is exact opposite

I will look into that later since the focus now is on removing components.

Regards

[blue4603]

@ grabben

Quote

@Blue4603
Possible you could tell how u managed to get removal part to work ?
Just interesting/facts..

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:

<?xml version="1.0" encoding="UTF-8"?>
<_7Customizer>
	<Components>
		<Componenet id="NaturalLanguage" name="Natural Language" requiredForStableSystem="false" size="500" group="system"> 
			<Description> blah blah blah</Description>

			<DependantComponenets />
			<NeededFor />

			<Files>
				<File path="Windows\System32\NlsData0000.dll" method="delete"/>
				<File path="Windows\System32\NlsData0001.dll" method="delete"/>
				<File path="Windows\System32\NlsData0002.dll" method="delete"/>
				<File path="Windows\System32\NlsData0003.dll" method="delete"/>
				<File path="Windows\System32\NlsData0007.dll" method="delete"/>
				<File path="Windows\System32\NlsData0009.dll" method="delete"/>
				<File path="Windows\System32\NlsData000a.dll" method="delete"/>
				<File path="Windows\System32\NlsData000c.dll" method="delete"/>
				<File path="Windows\System32\NlsData000d.dll" method="delete"/>
				<File path="Windows\System32\NlsData000f.dll" method="delete"/>
				<File path="Windows\System32\NlsData0010.dll" method="delete"/>
				<File path="Windows\System32\NlsData0011.dll" method="delete"/>
				<File path="Windows\System32\NlsData0013.dll" method="delete"/>
				<File path="Windows\System32\NlsData0018.dll" method="delete"/>
				<File path="Windows\System32\NlsData0019.dll" method="delete"/>
				<File path="Windows\System32\NlsData001a.dll" method="delete"/>
				<File path="Windows\System32\NlsData001b.dll" method="delete"/>
				<File path="Windows\System32\NlsData001d.dll" method="delete"/>
				<File path="Windows\System32\NlsData0020.dll" method="delete"/>
				<File path="Windows\System32\NlsData0021.dll" method="delete"/>
				<File path="Windows\System32\NlsData0022.dll" method="delete"/>
				<File path="Windows\System32\NlsData0024.dll" method="delete"/>
				<File path="Windows\System32\NlsData0026.dll" method="delete"/>
				<File path="Windows\System32\NlsData0027.dll" method="delete"/>
				<File path="Windows\System32\NlsData002a.dll" method="delete"/>
				<File path="Windows\System32\NlsData0039.dll" method="delete"/>
				<File path="Windows\System32\NlsData003e.dll" method="delete"/>
				<File path="Windows\System32\NlsData0045.dll" method="delete"/>
				<File path="Windows\System32\NlsData0046.dll" method="delete"/>
				<File path="Windows\System32\NlsData0047.dll" method="delete"/>
				<File path="Windows\System32\NlsData0049.dll" method="delete"/>
				<File path="Windows\System32\NlsData004a.dll" method="delete"/>
				<File path="Windows\System32\NlsData004b.dll" method="delete"/>
				<File path="Windows\System32\NlsData004c.dll" method="delete"/>
				<File path="Windows\System32\NlsData004e.dll" method="delete"/>
				<File path="Windows\System32\NlsData0414.dll" method="delete"/>
				<File path="Windows\System32\NlsData0416.dll" method="delete"/>
				<File path="Windows\System32\NlsData0816.dll" method="delete"/>
				<File path="Windows\System32\NlsData081a.dll" method="delete"/>
				<File path="Windows\System32\NlsData0c1a.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0001.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0002.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0003.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0007.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0009.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons000a.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons000c.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons000d.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons000f.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0010.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0011.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0013.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0018.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0019.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons001a.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons001b.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons001d.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0020.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0021.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0022.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0024.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0026.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0027.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons002a.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0039.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons003e.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0045.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0046.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0047.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0049.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons004a.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons004b.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons004c.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons004e.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0414.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0416.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0816.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons081a.dll" method="delete"/>
				<File path="Windows\System32\NlsLexicons0c1a.dll" method="delete"/>
				<File path="Windows\System32\NlsModels0011.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0000.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0001.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0002.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0003.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0007.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0009.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData000a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData000c.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData000d.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData000f.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0010.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0011.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0013.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0018.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0019.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData001a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData001b.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData001d.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0020.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0021.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0022.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0024.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0026.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0027.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData002a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0039.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData003e.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0045.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0046.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0047.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0049.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData004a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData004b.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData004c.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData004e.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0414.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0416.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0816.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData081a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsData0c1a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0001.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0002.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0003.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0007.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0009.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons000a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons000c.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons000d.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons000f.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0010.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0011.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0013.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0018.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0019.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons001a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons001b.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons001d.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0020.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0021.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0022.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0024.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0026.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0027.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons002a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0039.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons003e.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0045.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0046.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0047.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0049.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons004a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons004b.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons004c.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons004e.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0414.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0416.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0816.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons081a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsLexicons0c1a.dll" method="delete"/>
				<File path="Windows\SysWOW64\NlsModels0011.dll" method="delete"/>

				<File path="Windows\winsxs\Manifests\x86_microsoft-windows-naturallanguage*.manifest"  method="delete"/>
				<File path="Windows\winsxs\Manifests\amd64_microsoft-windows-naturallanguage*.manifest"  method="delete"/>
			</Files>

			<Directories>
				<Directory path="Windows\winsxs\x86_microsoft-windows-naturallanguage*" />
				<Directory path="Windows\winsxs\amd64_microsoft-windows-naturallanguage*" />

			</Directories>

			<Registry>
				<Keys>
					<Key path="DerivedData\Components\x86_microsoft-windows-naturallanguage*" part="components"/>
					<Key path="DerivedData\Components\amd64_microsoft-windows-naturallanguage*" part="components"/>

				</Keys>
				<Values />
			</Registry>

		</Componenet>

		

	</Components>
</_7Customizer>

It is a simple example that could be understood without explination. However, here a brief explaniation:

This part is where you define the components info.

<Componenet id="NaturalLanguage" name="Natural Language" requiredForStableSystem="false" size="500" group="system"> 
			<Description> blah blah blah</Description>

			<DependantComponenets />
			<NeededFor />

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.

[myselfidem]

myselfidem, on 14 May 2010 - 12:45 PM, said:

sjoerdhooft, on 14 May 2010 - 08:28 AM, said:

myselfidem, on 12 May 2010 - 12:09 AM, said:

sjoerdhooft, on 11 May 2010 - 01:13 AM, said:

myselfidem, on 10 May 2010 - 11:46 PM, said:

Hello!
Which is the software you use to burn your ISO file made by 7Customizer?

I didn't burn it but used the ISO file in VMware...

Hello
I remember it happens to me one time - with the valid and correct key - but I don't really remember the reason !
You can try to make a new ISO file, but before deleete all the files inside the folder "work" except: mount; Themes; bootorder.txt; etfsboot.com; EXTRACT.EXE (originals files and folders).
And at the section: unattend; write inside all fields, because if you live some fields blank, setup may fail.
I hope that will help you

Well, that didn't work either. I finally removed the key from the unattended setup and al doing it now without a key. It's too bad but I don't have another solution, especially since the key works when the installation is done. So weird...

You said

Quote

Yeah, I got it straight from Microsoft, and used it for manual installations...

Hello
Maybe you can try the tool MSKeyViewer for checking the key inside the registry:
MSKeyViewer
I've found some help here:
http://social.techne...95-57b40891bcc1
http://www.msfn.org/..._1
Maybe you can contact Microsoft and asking what is the problem with Autounattend.xml?
Help and support Microsoft:
http://windows.micro...lid-product-key
https://support.micr...prid=14019&st=1
I hope that will help you!

An other way is to make changes inside Autounattend.xml and add at pass="specialize":
You can use Windows System Image Manager (WSIM) and validate the file Autounattend.xml after changes. At first select your image Windows.
Example for x86:

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ComputerName>Se7en</ComputerName>
            <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey>
            <RegisteredOrganization>MyOrg</RegisteredOrganization>
            <RegisteredOwner>myselfidem</RegisteredOwner>

More help for Autounattend.xml:
http://www.msfn.org/...seven-xml-here/
Maybe it's the solution.

This post has been edited by myselfidem: 15 May 2010 - 03:15 AM

[TheWalrus]

Blue, please make the product key save in presets too. This is annoying as hell And previously integrated drivers too (I assume it is possible). I often work on same image several times in a row and want to save as many clicks as possible.

[grabben]

blue4603, on 15 May 2010 - 02:07 AM, said:

@ grabben

Quote

@Blue4603
Possible you could tell how u managed to get removal part to work ?
Just interesting/facts..

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:)

[TheWalrus]

From the sound of it, I would almost think others remove components in a different way? At least Blue said he found a cool way of doing it. I think.

[grabben]

TheWalrus, on 15 May 2010 - 07:03 AM, said:

From the sound of it, I would almost think others remove components in a different way? At least Blue said he found a cool way of doing it. I think.

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

[TheWalrus]

error after loading a preset

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
at _7Customizer.Form1.loadToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
7Customizer
Assembly Version: 0.4.4.0
Win32 Version: 0.4.4.0
CodeBase: file:///D:/Programy/7Customizer/7Customizer.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

This post has been edited by TheWalrus: 15 May 2010 - 01:43 PM

[blue4603]

@ TheWalrus

Quote

Blue, please make the product key save in presets too. This is annoying as hell And previously integrated drivers too (I assume it is possible). I often work on same image several times in a row and want to save as many clicks as possible.

OK. I will see what I could do about this issue.

Quote

error after loading a preset

Could you attach your preset?

@ grabben @ TheWalrus

As I mentioned before, to remove a component you need to delete certain files and registry keys. I am storing the
info of the components to be removed in an XML. Others could save the info inside the code of their program.
The is no difference in how you remove components (remove some files and registry keys).
Saving the components info an XML make it open to anyone to change it or add to it.

Regards

This post has been edited by blue4603: 16 May 2010 - 01:11 AM

[TheWalrus]

Okay. Here yo go:

[stefanRTR]

TheWalrus, on 15 May 2010 - 07:03 AM, said:

From the sound of it, I would almost think others remove components in a different way? At least Blue said he found a cool way of doing it. I think.

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" }
            };

[grabben]

stefanRTR, on 16 May 2010 - 09:43 AM, said:

TheWalrus, on 15 May 2010 - 07:03 AM, said:

From the sound of it, I would almost think others remove components in a different way? At least Blue said he found a cool way of doing it. I think.

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 ?