Martin H

When running a batchfile with a 'for' loop(*.exe) and the /integrate switch on a folder with all the updates, then the updates gets installed chronologically and you can only change the order by renaming the updates into another chronological order, but you shouldn't do that, however...

nLite's 'Runonce' section just adds a batchfile(nlite.cmd) to winnt.sif's 'GuiRunOnce' section. It's your own responsibility to get your batchfile executed during setup, so that means you make your changes to cmdlines.txt, winnt.sif or nLite's 'Runonce' section, before you make the ISO with nLite or cdimage.exe.

nLite by default directly integrates all supported updates and only the un-supported updates are added to svcpack.inf and the installers copied to '\I386\SVCPACK' and installed at T-13. You can change this behaviour by going into the 'Advanced' settings in nLite, and e.g. disable direct integration, so that all updates are added to svcpack.inf and the installers copied to '\I386\SVCPACK' and installed at T-13, but i don't see why anyone would, though...

When using the svcpack.inf method(or the /integrate method), then all the installers for the updates are included on the disc and installed during Windows setup(T-13), which then means that an additional space and time overhead is added into the equation. However, if you use nLite or HFSLIP to update your Windows source directly, then the installers for the updates isn't included on disc or even installed at all, since all the updated files and needed reg entries have been directly integrated into your Windows source. This is the benefit from using nLite or HFSLIP over the svcpack.inf method. Personally, then i preffer using a post-SP2 update pack(Xable's) to get my Windows source up-to-date, but that's a matter of taste... In my humble oppinion, then nLite is such a convenient and centralized platform for controlling all those common tasks like updates, drivers, unattended settings, reg tweaks, patches and component removals, and with a level of control so that it dosen't leave anyhting to be desired...

thank's jcarle One brilliant piece of app you've coded there, mate

I have never personally tried WUD, so i don't know if it support the optional updates, but atleast i'm sure that it suports all the high-priority updates and that means that you will get all the important critical, security and reliability updates. The optional updates are either not very important, or meant to fix issues that only affact specific groups, like with e.g. specific hard/software combination etc.

I integrate Xable's light post-SP2 update pack into my Windows source with nLite. Personally, then i don't care about the optional or unofficial updates and just want's the high-priority updates installed as also is recommended by Microsoft themselves here in this Windows Update FAQ : For people that also want's the optional and unofficial updates + other extra's additionally, then RyanVM's post-SP2 update pack is a very good choise (i have linked to his latest beta pack announcement, which is up-to-date) Edit: Sorry, i have just reread the post, and now see that the OP is after a manual solution, so in that case, then IMHO there is only one way to best do this, and that's to use WUD to download the post-SP2 updates and then to use svcpack.inf to get them installed at T-13 during Windows setup.

...Just for anyone not aware of it, then RyanVM has a current update pack available : http://www.ryanvm.net/forum/viewtopic.php?t=5761 It's a beta release, but it is stable however

RyanVM's beta update pack from his forum, is up-to-date, and which i would recommend instead of using non-stable MS testing products. If you only want the high-priority updates, then i can highly recommend Xable's update pack instead. As for the rest of your questions, then please search the forum for the info yourself, as it isn't hard to find, and as i don't use those things myself...

If you don't want to use an update pack, then use Windows Updates Downloader to download the updates and the svcpack.inf method to integrate them into your Windows source.

It's not and hence, that link...

Related info here : http://www.msfn.org/board/index.php?s=&amp...st&p=730086

Sorry, i don't know the answer to your first question, other than to simply recommend that you start over completely fresh with a clean reinstall of nLite and a clean source, and then to remake the ISO with your 'Last Session.ini' preset, but for your second question, then you either need to download all the Post-SP2 updates by yourself, or to download a post-SP2 update pack and then you just add all the updates, or the update pack, into nLite's 'Update Packs and Addons' section. If you decide to use a post-SP2 update pack, then you have two main choises; Xable's or RyanVM's post-sp2 update packs. The difference beeing, that Xable's pack is a light pack, which only features high-priority updates, whereas RyanVM's pack features both high-priority, optional and unofficial updates. Other than this, then RyanVM's pack also has some extra stuff included other than just updates, whereas Xable's pack hasen't, but instead he makes addon's available with extra stuff(RyanVM also makes extra addons available). Finally, then RyanVM's pack uses the QFE branch updates, whereas Xable's pack uses the GDR branch(except for one reported buggy GDR update). The difference between GDR and QFE branch updates, is that the QFE branch is cumulative and includes both the GDR branch update + all previously released hotfixes for the updated files, whereas the GDR branch only includes the GDR branch update. Hotfixes are developed quickly to provide fast support to specific customer situations, but they possibly hasen't gone through as thorough a testing phase as the GDR branch updates which is specifically developed to fix wide-spread issues. Xable's Update Pack : http://xable.net/xp-sp2-update-pack-contents.php RyanVM's Update Pack : http://www.ryanvm.net/forum/viewtopic.php?t=5761 If not wanting to use a post-SP2 update pack, then i would recommend using jcarle's 'Windows Updates Downloader' to download all the post-SP2 updates and then integrate them into your Windows source with nLite : http://wud.jcarle.com/

*LOL* Amen to that @saeckman Latest patched builds from clsid and Co. : ffdshow tryouts : http://sourceforge.net/project/platformdow...group_id=173941 Media Player Classic : http://sourceforge.net/project/platformdow...group_id=205650

@king_td To transform 'Windows XP Media Center Edition 2005' from the 2 CD's into 1 CD-R or 1 DVD+/-R, then you need to edit all entries of '%cd2name%' into '%cd1name%' in 'txtsetup.sif' and to copy the contents of CD2 into your CD1 source folder. If you don't use nLite and want's to fit everything into 1 CD-R, then delete all the unneeded folders(if you don't know which, then look in MSFN's Unattended guide under: 'Advanced Users > Slimming down your CD/DVD'). @geek I apologise and will remember that for the feuture. Edit: geek was faster

Set 'AutoLogon' to 'None' and don't remove/disable OOBE. For your Classic theme problems, then you must be enabling something that you shouldn't have(like above), so post your 'Last Session.ini' file from '%programfiles%\nLite\Presets\'.

If it's possible or not, is besides the point on this forum, since it wouldn't be legal, as you do not own a WinXP-MCE license... Edit: After having reread the post, then it seems as though the OP did infact allready own a WinXP-MCE license, so i apologise for my previous statement..

Yeahh, sorry about that, i should of course have mentioned that only 'hidcon.exe' should be used from the 7z archive, but thank you Arie for your help Anyway, i have edited my previous post to include Oleg Scherbakov's great little 2KB utility 'hidcon.exe' as an attached file, and i apologise for previously having directly linked to it... CU, Martin.

Have you actually read the link you just posted ? Hint: It's an update for 'Windows XP with SP2 - VL' with the MUI pack allready installed...

Obviously, you will need the polish SP3 version for slipstreaming into a polish Windows source... For your other question, then you need Microsoft's MUI pack, to transform the source language from english to polish. The MUI pack however, is only legally available for volume license customers, like e.g. through the Microsoft Open or Select volume licensensing programs.

Although i have never personally tried it(as i use the 'with SP2' source), then i'm pretty sure that you have misunderstood nuhi, as you clearly should be able to slipstream SP2 onto a 'WinXP with SP1(a)' source or a SP1(a) slipstreamed source. Granted, it will be a little cleaner if done on a WinXP source without any SP's included(by MS) or slipstreamed(by yourself), as there will be redundant files like e.g. : .\WIN51IP.SP1 .\i386\sp1.cab .\i386\sp1.cat But other than this, then there is absolutely no problems by doing this whatsoever! SP's are specifically made to support scenarious like this...

Hi Chazz76 It just means that you should delete the '[GuiRunOnce]' section from 'winnt.sif' and then you instead call the batchfile that imports the RunOnceEx reg-entries from 'cmdlines.txt'. Yes, you don't need the 'for' loop if you use the 'enableextensions' method instead. Here's how i personally preffer to do the RunOnceEx method : Place your batchfile that imports the RunOnceEx reg-entries(mine's called 'setup.cmd') + all your programs(or even better, your silent switchless 7z SFX installers) into a folder placed into the root and which you name 'setup'. Then download 'hidcon.exe' from the attached file at the bottom of this post and also place it in the 'setup' folder(used to hide the command-prompt completely, unlike 'cmdow.exe' and it works perfectly from T-12 i.e. 'cmdlines.txt'). Then you make another folder in the root named '$OEM$' and in there you make a text file named 'cmdlines.txt' and in which you add the following : [Commands] "..\setup\hidcon.exe ..\setup\setup.cmd" It isn't possible to use environment variables in 'cmdlines.txt'(e.g. %systemdrive% etc) and hence, you need to do as i did above, if you want to get away with not having the RunOnceEx batchfile in the '$OEM$' folder(unless of course a direct path is used). I personally find it most convenient to just have one single folder(setup) in the root, which contains all my silent switchless 7z SFX installers, batch and reg-files and then just have the single 'cmdlines.txt' file in the '$OEM$' folder. This means that when something needs to be edited in a batchfile, or some installers needs to be updated, then i always just need to go into the 'setup' folder and make the changes, instead of having to e.g. first go into '$OEM$' and edit the batch-file there which imports the RunOnceEx reg-entries and then afterwards go into the 'setup' folder and replace some outdated installers... Here follows a snip of my batch file(setup.cmd) that imports the RunOnceEx reg-entries at T-12(cmdlines.txt) : setlocal enableextensions set setup=%~d0\setup set key=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx reg add %key% /v title /d "Installing Applications" /f reg add %key%\001 /ve /d "Acronis True Image Home v9.0" /f reg add %key%\001 /v 1 /d "%setup%\Acronis_True_Image_Home_v9.0.3677.exe" /f [...] reg add %key%\009 /ve /d "Importing Registry Tweaks" /f reg add %key%\009 /v 1 /d "regedit /s %setup%\setup.reg" /f reg add %key%\010 /ve /d "Restarting Windows" /f reg add %key%\010 /v 1 /d "%setup%\hidcon.exe shutdown.exe -r -f -t 60" /f endlocal I use nLite to integrate Xable's Light Post-SP2 UpdatePack, enable tweaks and unattended settings, add users and of course to remove unwanted components(my ISO without the added installers is only 115MB big and works perfectly for my purposses ). hidcon.exe

@jeremy Thank you very much, my friend CU, Martin.

@Ludwig Von Cookie Koopa I was expecting that you where using a NTFS filesystem... Defragging with Microsoft's defragging API's on a NTFS filesystem should be absolutely safe, unless the used app is seriously broken and dosen't make use of the API's propperly. However, something like a power failure can become a problem on FAT filesystems, though... @All Anyway, just wanted to say that UltimateDefrag hasn't got that reg-entry dependency anymore, which i posted about previously in this thread, and so now the single exe can run without the need for exporting a regfile I'm personally still using UltimateDefrag, as it IMHO does a very good job at defragging and optimizing the filesystem and while still being wery slim and unbloated and without needing any extra background processes and last but not least, since the UI drive representation can't be beaten I use UltimateDefrags 'Recency' mode, and leaves the settings as per default, which then mimmicks the fileplacement scheme used by Perfectdisk, as i most preffer that kinda scheme, since it will make feuture defrags faster and since i don't really like to place any files on the most slower part of the harddrive(the inner tracks - called 'archive' in UltimateDefrag), as i'm only using about 10% of the drivespace on my two partitions.

Correct. Grab the 'boot.img' file from your nLite program folder and place it in a folder together with 'cdimage.exe'. Then copy/paste the following into a batch file named 'makeiso.cmd' and which you also store in the same folder, and you also need to ammend the paths accordingly: Source path Destination path Volume label Then you just double-click on 'makeiso.cmd' whenever you want to make a bootable ISO.