blue4603

@grabben Hmmm. I still did not fully understand. I recommend you wait for the components XML explanation and maybe you will find your answer. Also, 7Customizer reads the all XMLs in the components folder and dynamically build the tree you see in the components tab (The explanation of components XML will fully clear this). So, everyone, do not rush. Be patient and wait till the weekend and I will prepare the explanation and then you could ask your questions . BTW , grabben , did 7customizer worked with you? or still there is a problem? Regards

@grabben I am afraid I did not understand your question, could you be more clear? @Schemek What you did is a very great job and that what I am aiming for, to let people help me in building the XMLs for every component. I will post a guide for the components XML in this weekend that will explain how to create a component XML. It is on the to do list on the first post. Also, as I always say, keep an eye on the to do list on the first post to know what I am up to. I appreciate your help. @mrookie Thank you. I appreciate your help. Regards

@ mrookie Could you post your log.zip? @pedilover As I mentioned many times, driver integration issues are not related to 7Customizer. They are either the issues with the drivers you are integrating or DISM issues. Weekends (Thursday and Friday). Regards

@ myselfidem Use Winrar to extract the file. @grabben Which language you selected in 7Customizer? I think you chose a different language file and now there is a problem in that language file or maybe you translated 7Customizer and used your translated file? Regards

@grabben There is a problem in one of the language files. @myselfidem No the zip file is not empty. there is a file inside which you could extract it and then open it with notepad or any text editor. Regards

@myselfidem Thanks man. Now I will be able to fix this bug. @TheWalrus Do not worry about that. As I mentioned this is a beta release. I will post what is still missing and what is still needed. Also I will post the components XML explanation. So be patient Regards

Guys, if there is a bug or an issue please attach the log.zip found in 7Customizer directory. Do not post log.txt anymore. Regards

@pedilover I will put it in the changelog in the first post when I release 0.5. Regards

@ dmikester1 Hmmm. The problem is that I do not have an upgrade disc to test 7Customizer. However I will try to find one and I will report back to you. Regards

@TheWalrus Kinda of. @pedilover @grabben @TheWalrus Please guys discuss issues releated to 7Customizer only. @coucou Do not worry about that. Read about the way I am implementing the component removal. @ascatem I will find if that is possible or not and will reply back. Regards

@myselfidem @grabben Thanks for the link. I will read it later and try to implement it after the components removal. @TheWalrus Hmmmm. For the next release, no. However, I am implementing a way to give everyone to integrate custom tweaks using 7Customizer. Regards

@grabben Hmmmm. I think I have read about that somewhere. I think I will first read about this method and find out whether it causes problems or not. Regards

@ShamanNeo Thanks. I will integrate it with the next release. @jinkazama Thanks.I will integrate it with the next release. I will try to add these entries in a future release. @ascatem If it is only supported officially by Microsoft. Regards

@grabben Probably yes. @TheMightySpud You aren't doing any stupid. It is just a bug in 7C. I think that you are using a modified windows installation source. Try to use an untouched installation source. Regards

@marcusj0015 I will not release the source code until there is someone ready to take the development of 7Customizer. Which I think, I will have the chance nowadays to continue. Regards

@ medp7060 Could you attach your log. It will be more helpful. Regards

Do not worry about that. If someone requested me to complete 7Customizer, I will make sure he have enough experience to do so. Regards

I am afraid I do not have an answer for this question right now because there are so many things in my head. Regards

Greetings, Thank you all for your patience and support. 7Customizer is not dead at all and I said previously if someone wants to complete my work, just contact me. For all the past months, I received only one request. If any one else, with enough experience in programming,wants to continue 7Customizer, do not hesitate and PM me. Also, if you do not like 7Customizer , you have many alternatives. Regards

Hi, I know that lots of you are upset of me because I disappeared for a long period. I know it is frustrating but let me explain to you what happened to me. Three years ago I was diagnosed with an illness called panic disorder. Read about it here. From the article you will get to know that a person will suffer panic attacks. These panic attacks have symptoms like short breath, rapid heart rate sweating .. etc (read about it here)and what is worst you feel like you are going to die or you are going to be crazy. I went to a doctor and he prescribed a medicine for me. I took this medicine for about one year and few months. I regained my health. However, the past months the panic attacks returned back.I was so frustrated and so upset because I already regained my health and every thing seemed OK. I was so confused. I even wanted to quit my job. However, I calmed down and googled for some techniques to overcome this. Now, I am doing well and regained my health. I hope you understand and accept my apology. If one of the forum members is suffering from this illness, you could pm me and talk about it. Regarding 7Customizer, I will continue development if the forum members still want me to or I could provide the source code and let someone else continues it. Also thanks grabben for your support. Regards

@ TheWalrus OK. I will see what I could do about this issue. 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

@ grabben 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 Nice. Thanks for the feedback. OK. I will include it in the next release. @ grzegorz7853 Thanks. I will include it in the next release. @ TheWalrus Do not rush man you will get something soon I will look into that later since the focus now is on removing components. Regards

@ henrique araujo Thanks I will include it in the next release. @ sjoerdhooft OK. I have two questions for you. What is the edition you are customizing? What is the edition you bought? I think you are customizing an edition that your serial does not match it. For example you cannot take a serial for home basic and use it for home premium. I hope that helps. Regards

@ grabben Thanks I will included in the next release. Everything progressing smoothly. I should have finished it earlier but I was busy. @ nerd-light @ pedilover What I am concentrating on is not the components but how to remove them. The first component I worked on is Natural Languages (x86 and x64) and it worked fine. @ RickSteele Thanks for the feedback. @ sjoerdhooft Did you tried to install Win7 manually with your key? @ grabben @burn You could also test an x64 guest on a x86 host. I think you need to enable the processor visualization (Intel-VT for Intel or AMD-V for AMD) if your processor support it (I think most of the core series support this). Regards