grabben

Hey guys and girls:) I have a script to do stuff to a mounted 7 image (in my case ultimate 32bit) and new option is to apply unattended (created by 7Customizer 0.4.4) I used the "Dism /image:path to mount /apply-unattended:path to unattended.xml" to do this and operation is sucessful.. But it doesnt work anyway, i still have to enter username, password etc etc after setup, any solutions?

I've found (French site) an explanation about your question - blinking cursor: When you want creating a text file, like : >> %work%\Logs\LP.log That means that the text were displayed inside the file text and not inside the command promt! It is the reason you have a blinking cursor! I already know that and its pretty obvious.. but i want it to show in the prompt and write to logfile, not sure if thats doable?

I've tried to have a log file. And the only thing I read inside "LP.log" is that "operation successfully"! I think it's not useful, but the result is the same: the package - language en-US - is integrated and you can see the log file also inside: %Systemdrive%\Windows\Logs\DISM\dism.log You can see the options for DISM inside "7Customizer\work\testdism.txt" or with "DISM /? >C:\dism.txt" with the command prompt. If I try to have a log file I have the same result you discribe! But the result is the same. I don't know the reason why the text doesn't appear inside the command prompt!? Maybe Blue can give us an answer. You can see that the integration is 99,9%. I think it's because the package is alredy integrated, because I've made this operation many times! Yea, i hope blue can answer this question, i asked at MDL forum as well.. but no reply there yet.. dism /logpath: gives alot of text that doesnt make a lot of sense to us though, but ">> .log" just writes the whole process into a textfile.. wellwell its not a big issue. Im also using options to set keyboardlayout but hmm

Not sure if videodrivers are required for setting your own resolution and refresh rate but just an idea..

Sorry brother, I am actually trying to integrate language pack not only in boot.wim but in the entire installation files. Great, when I tried with 7 customizer it was giving some error but I don't remember the error code and now when I was trying once again it is not letting me do anything. It is giving me this message "Uncxpected error: see the log" when I am selecting the director of installation files. Mind it there are not spaces in the entire path of the installation files. For problems with 7Customizer, check out the supportthread for the app.. Install.wim Dism /Mount-Wim /WimFile:dvd\sources\install.wim /index:1-5 Dism /MountDir:mountDism /image:mount /add-package /packagepath:"lp.cab Dism /Unmount-Wim /MountDir:mount /commit Boot.wim #1 Dism /Mount-Wim /WimFile:dvd\sources\boot.wim /index:1 /MountDir:mount Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\lp.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-scripting_sv-se.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-srt_sv-se.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-wds-tools_sv-se.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-wmi_sv-se.cab Dism /image:mount /Gen-LangINI /distribution:mountDism /Unmount-Wim /MountDir:\mount /commit Boot.wim #2 Dism /Mount-Wim /WimFile:dvd\sources\boot.wim /index:2 /MountDir:mount Dism /image:mount /add-package /packagepath:waik\winpe-fontsupport.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\lp.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-setup_sv-se.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-setup-client_sv-se.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-scripting_sv-se.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-srt_sv-se.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-wds-tools_sv-se.cab Dism /image:mount /add-package /packagepath:WinPE_Langpack\ark\sv-se\winpe-wm_sv-sei.cab Dism /image:mount /Gen-LangINI /distribution:mountDism /Unmount-Wim /MountDir:mount /commit You will have to replace ark with architecture (amd64 or x86)sv-se with your own languageand rest is selfexplainingMake sure to run deployment tools command prompt as administrator..

You need to tell us more.. 7Customizer doesnt integrate language to boot.wim, only install.wim cant remember bout vlite and 7lite i have no real experience.. What is the error you get?

Lol@ blue: For some kinds of buttons you may use the same label (for example for the "Browse" button, with only one label you can name them all). You'll have less rows in the file (I know, I'm lazy ).Thats a good idea. use same label for Browse, insert and remove buttons perhaps.Is it "perfetto" (perfect?) I realy dont speek italian but the language is kinda beatiful and so is the country + i have a friend living there:)

Same with swedish but that happens

Have you at first created the folder "logs"? Because if it doesn't exists the file log isn't created.And I see a space beetween work and backslash (work \)!Could you show your command?Example, when I try to have an log file or an text file for the command DEL:I create at first the folder: logs (like your example).C:\del /? > C:\7Customizer_0.4.4\work\logs\del.log (or del.txt)About the Editor, I've sometimes the same problem: I think it happens when two or may guys are writing and posting at the same time inside the same topic!Ofcourse i let my script first create that folder called "logs". yea i misspelled but problem is not that its not creating the logfile beacuse it does BUT if i have it create logfiles like the command "<dism command >> work\logs\lp.log" for example, the process wont show in the cmd window but just a blinkinh cursor. Here's the command: "%WAIK%\Tools\%arch%\Servicing\dism.exe" /image:"%work%\mount" /add-package /packagepath:"%work%\lp\%lp%" >> %work%\Logs\LP.log You think that could be the problem with the editor ? hmm maybe, im not sure. Hey blue, how's it going with component feature ? getting very eager to try it out

Yea, think thats better, a checkbox for autologon perhaps

Ahaaaa thats why it looked allright. Anyone can help me on my issue bout the logging ?

Sure you can, but you need XP MUI packs Links somewhere on MDL forum

Yea that one to create an AIO with multiple versions of 7 and/or vista on one install.wim And you copied the eula and license etc, and still doesnt work? I have the same problem.. whonder whats wrong.

I prefer this way beacuse then you still have the option to choose language yourself for setup (ok that doesnt really set language).You dont get that option if you specify it in a unattended file..I posted the dism commands in the 7Customizer thread, few pages back..Edit: Here it is;

Ill try it myself soon, maybe the german guys have an older version or try to "frame" 7C ? Edit: Same for me, correct lines in the xml file Edit2: What the f... is wrong with the s***ty quick editor ?! <value>123456</value> Another edit: How does 7C write to the logfile ? For my script im using >> work \logs\lp.log But the cmdwindow wont show the process, it writes directly to the logfile and i get a blinking cursor.. anyone can help on this? I want the cmdwindow to show the process and i want it to log to a file.

Cool Cool, not bad, Grabben, not bad Thanks:) Posting link here anyway: http://www.sweclockers.com/forum/22-microsoft-windows/917387-guide-hur-man-anvander-7customizer/ Hm i cant find something wrong with the unattended.. but what do i know:/ just really weird

Update on my guide: Re-wrote it completely to update it for Version 0.4.4. The link is still the same:)

Update on my guide: Re-wrote it completely to update it for Version 0.4.4. The link is still the same:)

you mean blabla.msi ? No, standard exe i think.. if the exe isnt unpacking something to a tempfolder..

Well i dont know what your errormessage says, but mine says that installation cannot proceed. Which guide did you follow? I have read that you need to copy the EULA files into first boot.wim and then to sources\license but that doesnt work anyway.

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 .