grabben

1. Download all updates using steven4554 update list & wud 2. Mount your version you want to update (or perhaps all?) 3. Integrate them 4. Dismount 5. Export to compress and replace the old one with the new one. And use setupcomplete.cmd to install updates like netfx, java and other programs, place them on the dvd.

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 Ill hold on until then Uhm I got it working I tink. SP1 was the issue i think. Like i said, i unpacked it to a new folder and it worked fine. It wasnt a language issue. The tool works just fine removing components etc.

Create the recoverydisks would be a good thing to start with. But you can try mount the recoverypartition by giving it a driveletter and see if you can find an install.wim or install.swm files. You cant slipstream SP2 with vista, you need to use reverse integration:)

I am afraid I did not understand your question, could you be more clear? Regards Absolutely:) I was whondering if 7C (in the future) could scan for packages, language packs and drivers so they can be removed. I know you can remove drivers/updates if they are in the list to be integrated. And also, I noticed there's xml files for each component to be removed. Is it done by you manually or by 7C? Im sure you can have the components tab search for everything that can be removed and list them nicely:)

Weekends (Thursday and Friday). Regards Would it be possible for you to have 7C search for packages and list them & also being able to remove them? To remove language packs, drivers and updates and then components:)

blue4603 is working to fix the "bug" with Windows 7 SP1 version, that I'm guessing you tried to use with 7Customizer! However, keep in mind that all your changes you've made, are lost if you delete 7Customizer files and unzip a new time 7Customizer_0.5.0.rar! Of course! Like for the file "bootorder.txt"! *Edit: I've tried with your language file translated (Swedish) and works fine (old one, include inside 7Customzer)! No problem found using Windows 7 SP0 image! Stupid i were. Ill doublecheck, seems like Im suing 7601. of course i know everything will be deleted. I also updated the translation today:)

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 I tried the new translated swedish file, but after deleting the folder, i unpacked it again and it still woudnt work (even though eng is standard) unless i moved it to a new folder.

Well then what is the problem? I unpacked the 7customizer_0.5.0 3-4 times and they all had the same problem.

Allright here's mine:) Edit: When i coped the 7C 05 fodler i have on my computer to moms, then it works fine.. but not on mine, i will unpack it again for the 3rf time. Edit 2: When not trying to run it from D:\7Customizer_0.5.0 it doesnt work but from D:\New folder it works fine. log.zip

A workaround is to select another image and after select a new time your image you want customize: log.txt Of course! I must have renamed the file or something, thanks ill try that Edit: Nope that didnt work. I even (earlier) removed the 7C 05 folder, still doesnt work.

Interesting idea. I havent integrated both x64 and x64 into same boot.wim, not sure if it will work but please try There is a good tutorial on MDL Forum for creating a complete working AIO. I was saying you need to inject critical drivers (x86, ethernet perhaps, cpu/chipset) into index2 of boot.wim and then same drivers to Install.wim index:1 and finally inject 64bit drivers to install.wim Index:2

Only if you want make changes inside "boot.wim" images or WinRE for Windows 7 SP1! *Edit: 7Customizer_0.5.0.rar available at the first page for download Ohyeas! Not many components yet but its a beta! I have translated all parts except the tweaks section (excluded themes/wallpapers) Just remember to change fileextension:) Edit Wth is this? =====STARTING log.txt======== === 7Customizer Started=== 7Customizer verion: 0.5.0 Beta 1 7Customizer path: D:\7Customizer_0.5.0\7Customizer.exe Current directory: D:\7Customizer_0.5.0 OS: Microsoft Windows NT 6.1.7601 Service Pack 1 OS architecture: AMD64 Work folder found: True Mount folder found: True Themes folder found: True Languages folder found: True Extract utility found: True Configuration file found: True bootorder.txt file found: True Boot sector file found: True Components folder found: True Number of components xml: 3 Elevated: True Loading Language: Begin Unexpected Error: Object reference not set to an instance of an object. at _7Customizer.Form1.loadlang(String lang) at _7Customizer.Form1.Form1_Load(Object sender, EventArgs e) =====FINISHED log.txt======== Swedish05.txt

Only one boot.wim of course:) Inject drivers to Install.wim index 1 (Ultimate 32Bit, x86) and then 64bit to Install.wim index 2.

Its not needed but its recommended. @Blue4603 I found a misspell @ createisoafterapply Immediatly is mispelled, not a big deal but just to notify:)

I will translate this tool again if I can..

Testers are always needed!! 7Customizer works fine (0.4.4) but a new version should be released pretty soon so there's some testing to be done.

What he wrote. packapgepath is good if you want to integrate specific packages but if you want them all, its the <path to folder>

Why expand msu's? Just use /Add-package command to integrate them:)

it says "XP / 2003 x86" right? Then it is only for 32Bit.

C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /Mount-Wim /WimFile:D:\7\Sources\install.wim /index:1 /MountDir:D:\mount C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /image:D:\mount /Add-Package /PackagePath:D:\lp.cab C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /image:D:\mount /Gen-LangIni /Distribution:D:\7 C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /image:D:\mount /Set-AllIntl:hr-hr C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /image:D:\mount /Set-TimeZone:"Central Europe Standard Time" C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /image:D:\mount /Set-SetupUILang:hr-hr /Distribution:D:\7 C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /image:D:\mount /Gen-LangIni /Distribution:D:\7 C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /image:D:\mount /Get-Packages /Format:Table C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /image:D:\mount /Get-Intl C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /Unmount-Wim /MountDir:D:\mount /commit mkdir D:\temp expand D:\lp.cab -f:* D:\temp xcopy D:\temp\setup\sources\hr-hr\* D:\7\sources\hr-hr /cherkyi xcopy D:\temp\sources\license\hr-hr\* D:\7\sources\license\hr-hr /cherkyi C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /Mount-Wim /WimFile:D:\7\Sources\boot.wim /index:2 /MountDir:D:\mount xcopy D:\temp\setup\sources\hr-hr\* D:\mount\sources\hr-hr /cherkyi xcopy D:\temp\sources\license\hr-hr\* D:\7\mount\license\hr-hr /cherkyi copy D:\7\sources\Lang.ini D:\mount\sources\Lang.ini C:\Program Files\Windows AIK\Tools\amd64\Servicing\dism.exe /Unmount-Wim /MountDir:D:\mount /commit rd /S /Q D:\temp I already knew that..

and how to do this Using dism mount-wim, dism add-package and dism unmount-wim.

It will fit on a DL DVD yep, the Vista SP2 AIO is slightly over 4.6 GB i think or something like that.

Ah thanks for the clarification Not 100% awake!

this is bad because when i integrate language this is only tool which have translated installation and not only gui after installation Yea its bad beacuse StefanRTR hasnt worked with this tool for a very long time and it is definitly unsupported. It barely worked with SP0 and now SP1 is released. Its easy to localize the setup and you have to install WAIK anyway so ou might as well want to learn something about this process: by doing it yourself the manual way:)