ricktendo

Ignore the core and extended MSI's, they are old .net4 installers only used for uninstall purposes Note: you have to use InstEd or Orca MSI editors and manually change the Sumary info setting of the package from External long filenames to Admin External long filenames (this normally happens automatically after you do a admin install but the .net installers fail to do this) BTW Universal Extractor can do a admin install if you run into any trouble

Harlem shake black edition is the only one I liked

This and coning (also the harlem shake) have got to be the STUPIDEST!!! sh!t ever invented

I think the max you can do is 1024x768, your resolutions should go to the max once your video driver installs during second reboot

Maybe installing it after login BTW that KB article says it "sometimes" happens, so it may not happen every time

Might be a gui sfx problem http://support.microsoft.com/kb/185294

Tienes que integar SP3 a tu ISO o conseguir un iso con Windows XP sp3 ya integrado Luego con nLite integras el paquete de actualizaciones UPL, .NET 4eu o el 5eu y este addon de Media Center (use el mismo serial que usa tu XP sp2)

No he jugado con esto, pero talvez este addon te ayude http://integrator.siginetsoftware.com/index.php?addons&id=241 No creo que funcione con nLite

Just tested it, you are correct

Yea you can do away with /norestart if the program does not prompt you to reboot, and your config looks good You could always add /norestart switch when you run your sfx, this will get passed along and added to all the RunProgram or AutoInstall commands This is why SetIni.exe in my MsSecEs installer works, when you add xx-XX parameter it is added to the SetIni RunProgram and completes the command...it is also added to the setup.exe command but setup.exe ignores this When you run my mseinstall_x86_x64_intl.exe es-ES this is what happens RunProgram="hidcon:setini \"%%T\\%%P\\setup.ini\" Compat Market " <- es-ES is added here after space completing the setini command Same goes when you use /ai es-ES, /ai is not added because the sfx recognizes this but it does not recognize es-ES so its passed along to the run commands

No... there NEEDS to be NORMAL quotes after RunProgram=<HERE>to the end of your command<HERE> Quotes and backslashes in between these two need to be formated like this: \" and \\ To clarify %%T will turn into the extraction path

The second one, and you can skip the msiexec part (you only need to use quotes if a filename or path has a space) ;!@Install@!UTF-8!RunProgram="AppleApplicationSupport.msi /qn /norestart TRANSFORMS=\"AppleApplicationSupport.mst\"" ;!@InstallEnd@!Add %%T\\ to the transforms if it cannot be found;!@Install@!UTF-8!RunProgram="AppleApplicationSupport.msi /qn /norestart TRANSFORMS=\"%%T\\AppleApplicationSupport.mst\"" ;!@InstallEnd@!

Mediafired

If you are on a sv-SV Windows you dont have to use the switch, it should do it automatically

Yes, SoLoR way back when got banned for hosting untouched Microsoft hotfixes...imagine what they will do if you take something of theirs and mod it

Be careful what you put on skydrive, it can get your email banned

Your loss, not mine

Shows how short sighted you are, 1- KUC option could only be available if it detects KUC executable in the same directory 2- KUC, NOT the toolkit will be in charge of downloading the updates 3- Who cares what komm did with his own server, its his to do with what he pleases... All lego needs to do: if wtk detects KUC in the same dir enable it, ask user for a path to a repo folder (with any updates (s)he has already downloaded,) after wtk mounts the image it runs KUC with the following command <kuc>.exe /DVD-Image-dir:<path_to_image_just_mounted> /up-dir:<any_temp_dir> /repo-dir:<repo_dir_specified_by_user>Then the user clicks next and stuff, choose what updates (s)he needs, uses kuc to download missing updates from his repo folder and the user finishes...then the toolkit executes the CMD files in the "up-dir" to copy files to add, now that all the updates are copied and laid out for the toolkit all it needs to do is integrate the "normal" updates like it would normally and ONLY extract and install the LDR updates in the LDR folder If you people want to blindly integrate updates not knowing if you need them or not be my guest, this is the last time you will hear me say this

Yes, .NET Framework v4.5 supersedes/replaces v4.0 (I only maintain 4.0 because 4.5 is not compatible with XP, Lego should remove it from WtK and maybe replace it with rebuilt)

When during the setup process does the install happen? 1st boot? audit? BTW don't integrate 4.0 along with 4.5, you only need 4.5 And your cmd line is right, /y or /ai will get the job done Edit: if you are still experiencing issues try the rebuilt, its the same as the default .net 4.5 installer but it has updates and the MZZ is better compressed to save space (run installer with /? to view command line options)

Yet another reason to add KUC support to the toolkit

mediafired

Uploaded to mediafire

Subidos a mediafire

Actualizado